-
Notifications
You must be signed in to change notification settings - Fork 546
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
On goerli ethstats, one of the clients causes server to crash #339
Comments
Was running it with Nethermind node so I will need to check if the data format is unexpected - still it should not cause server to crash. |
progress: 1 } |
including output from the logs of eth-net-intelligence-api |
How are you starting the server ? |
Could you also provide the full log ? I.e from startup to close. Also could you provide the PM2 log? |
seems that that our current test version has getLatestBlock JSON RPC failures |
Does Nevermind not have it implemented by chance ? Still looking into why it takes down the client. |
logs on Nethermind side look fine now (but I was fixing BigInteger parsing just today so maybe the new version solves it) 2019-01-04 23:19:35.9323|TRACE|49|JsonRpc.Modules.ModuleBase|eth_syncing request, result: 318134/318134 |
moved to goerli/ethstats-server#10 |
Running the latest version of eth-net-intelligence-api.
Each time I bring back my client it crashes the server at: https://stats.goerli.net/
The crash causes ethstats to display first:
Bad Gateway message (just tex on empty screen)
then
Service Unavailable message
CONFIG:
{
"name" : "node-app-goerli",
"script" : "app.js",
"log_date_format" : "YYYY-MM-DD HH:mm Z",
"merge_logs" : false,
"watch" : false,
"max_restarts" : 10,
"exec_interpreter" : "node",
"exec_mode" : "fork_mode",
"env":
{
"NODE_ENV" : "production",
"RPC_HOST" : "localhost",
"RPC_PORT" : "8546",
"LISTENING_PORT" : "30313",
"INSTANCE_NAME" : "Nethermind-VM1-Goerli",
"CONTACT_DETAILS" : "https://gitter.im/nethermindeth/nethermind",
"WS_SERVER" : "https://stats.goerli.net",
"WS_SECRET" : "[removed]",
"VERBOSITY" : 2
}
}
The text was updated successfully, but these errors were encountered: