-
Notifications
You must be signed in to change notification settings - Fork 839
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
Failed to clean stale beacon headers err="filled header below beacon header tail: 45987 < 67388" #222
Comments
same here. tested several endpoints
|
SolvedI'm using my own beacon RPC by port 5052 STEPSOpen REST port: update your holesky node: Add in taiko node .env: (mine and @lagunovsky bootnodes) and set: Restart and delete old images: |
solved? i dont use own beacon rpc node |
yes it's fixed. |
Thanks for workaround |
Thanks for your feedback. I'm looking for the reason. This kind of problem will be very helpful for us to make the node more stable. |
@amis13 your bootnode is not working 🙂 original workaround working bootnode (which I manage):
|
previous enode that @amis13 provided was working perfectly and still is if I'm not mistaken |
Fixed, I've tested and you were right, mine request port isn't 30303, it's 30306: |
This issue is stale because it has been open for 30 days with no activity. |
This issue was closed because it has been inactive for a week since being marked as stale. |
Describe the bug
Failed to clean stale beacon headers.
I don't think there is a solution at the moment other than having to rebuild the docker
Steps to reproduce
you may have this error:
Beacon backfilling failed err="syncing canceled (requested)"
ERROR Failed to clean stale beacon headers err="filled header below beacon header tail: 45987 < 67392"
Spam policy
The text was updated successfully, but these errors were encountered: