Closed thevops closed 1 year ago
Probably related to https://github.com/checksum0/go-electrum/issues/10.
Occurred once more 😞
2023/08/25 15:49:20 http: panic serving 10.121.1.207:35180: concurrent write to websocket connection
panic({0x1484a00, 0x1d5f640})
/usr/local/go/src/runtime/panic.go:844 +0x258
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.
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