-
Notifications
You must be signed in to change notification settings - Fork 111
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
Server crash due to response from one client #17
Comments
The same error for me: Any updates here? |
Reverting commit 6ad9c2c makes it works. |
Same. It happened to me on Node 8.10 / Ubuntu 18.04 if it is any help. |
Can confirm this issue is still ongoing - unable to use this application at the moment. |
Hi all I got this wokring a while back. I am on a plane, and on vacation, but will send fix later. Also part of it is I didn't even document all the things I tried and changed. However I have a node up now that SHOULD NOT crash https://goerli.network port 3000 try adding node, if you want to confrim. Cause alone I can only test so many nodes. |
Also I was able to bring up stable nodes on all the networks: I think the monitoring that Cudebro wrote is very useful when doing dev on the testnets. I alwasy run it in the background. Feel free to utilize. |
This solution doesn't work for me, I'm still having the same error
|
The error log is as follows:
Another instance of failure resulted in different logs. This failure was caused when netstats server was restarted and client reconnected itself:
Related to #10
The text was updated successfully, but these errors were encountered: