forked from ethereum/go-ethereum
-
Notifications
You must be signed in to change notification settings - Fork 277
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
Node stuck at "looking for peers" until a service restart #868
Comments
Hi @ncavedale-xlabs can you try set |
I got the same error after upgrading to version 5.6 - seems like the chain id is wrong for some reason. trace output:
|
Same error with 5.6 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
System information
One of our testnet nodes has seemingly lost connection to all peers and cannot reconnect. As a result, the node was not getting new blocks. It remained in this state for several hours, until we restarted the service and then it was able to catch up normally.
This is the second time it happens to us, just don't remember if the first one was also on testnet or mainnet.
Expected behaviour
Node should be able to find/reconnect to peers and keep syncing
Actual behaviour
Node loses connection to peers and doesn't find/reconnect to any peer until
l2geth
is restartedSteps to reproduce the behaviour
N/A
Backtrace
Node was importing new chain segments until it wasn't:
The text was updated successfully, but these errors were encountered: