-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
Failing to unregister sync peer which is not registered #220
Comments
I am running a fullnode and have been seeing the same issue since upgrading to the beta release. The node will periodically stop syncing for several minutes at a time, and when checking the logs the last message logged before syncing stopped will be similar to:
Sometimes the issue resolves itself after a few minutes and the node will start syncing again, but on several occasions, I've had to stop the node and restart to fix it. When the issue does resolve without a restart, no log messages are emitted for the duration of the freeze. There are no warning/error messages (aside from the "peer removal failed" messages) when syncing starts again. |
For me it doesnt restart syncing automatically, it keeps throwing the error in the bsc.log file I have attached. I have to manually stop geth and restart it. Worst part is it happens randomly at anytime so you have to keep checking if your node is in sync. It has happened twice today already, once after a few hours and once within a few minutes after having restarted geth. On the third run now! |
Same issues here, would like to know how did you finally resolve this? The node kept logging the
My hardware currently is 4C32G with 1T SSD(IOPS 5000). |
The version of my geth client is 1.10.3 |
Hi team. I get the same error in v1.1.8, how is it handled please? |
#856 fixed |
Using the latest beta release - v1.1.0 beta
A custom node went out of sync so we checked the logs and it looks like it was trying to drop a bad peer but it couldn't stating that the peer is not registered. We had to manually restart geth to fix the issue. This seems like this problem mentioned here - ethereum/go-ethereum#22077
Attaching the bsc.log file, please advise.
bsc.log
The text was updated successfully, but these errors were encountered: