-
Notifications
You must be signed in to change notification settings - Fork 78
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
Silent panic - concurrent write to websocket #3699
Comments
Probably related to checksum0/go-electrum#10. |
Occurred once more 😞
|
I'm seeing the exact same thing. And my uptime went from 99% to 86%. I've left my keep client in this state (because I'm now screwed for monthly rewards) if you need to debug. |
Node 18.118.184.107 is exhibiting the same behaviour - no 'diagnostics' response while 'metrics' does respond. Additionally, note it will lose rewards due to running v2.0.0-m4 and reporting it has no connectivity to the electrum node. |
Refs #3699 Depends on #3704 It happens that the keep-core client panics when interacting with the `go-electrum` library. We noticed a "concurrent write to websocket connection" error was thrown when calling `GetLatestBlockHeight()` function. The stack trace leads to gorilla/websocket/WriteMessage which is called from the `go-electrum` library. The latest block height call was already wrapped with a read mutex, but we should also wrap it with the write mutex to prevent such concurrent errors.
Hello,
I had a problem with my tBTC node. It failed silently but didn't stop completely. Peers/bootstraps connections worked, but Prometheus monitoring (https://monitoring.threshold.network/grafana/public-dashboards/1a09fa3a621c4837988b36f2d6ae6e24?orgId=0) lost him for some time (until I noticed it by viewing the above Prometheus).
I also noticed that endpoint
/metrics
worked after the failure, but/diagnostics
did not (infinite loading).In that case, the app should exit with an error code, then my system would start it again (I use containers).
I had to manually restart the node to be discovered by the monitoring to be qualified for rewards.
Logs
Tasks
The text was updated successfully, but these errors were encountered: