-
Notifications
You must be signed in to change notification settings - Fork 1k
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
Syncing halted after Bad block #7037
Comments
This has been happening consistently when starting reth with only set up peer my reth alpha 21 instance. After those messages I'm just getting invalid blocks.
Another restart and while reth looks fine, my 2 reth nodes seem to hate each other, they won't peer between them no matter what, only geth works. |
could you please share more logs and elaborate on your setup? |
@Rjected @shekhirin @joshieDo I've thought about this a bit and the part that struck out is:
this sounds like we started downloading blocks on restart and didn't start the pipeline immediately, not continuing the recent pipeline run. since this is the bodies stage, perhaps there's something off here after static files: ptal here @joshieDo @shekhirin
|
Sure! I wanted to sync the beta version, so I set up as trusted node to the beta the alpha 21 version and vise versa. Everything was syncing very fast, and I was tryin to push it further by tweaking the reth.toml file.
I though that I probably pushed the numbers more than some limit would allow me, so I tried reducing the numbers I increased in bodies stage, but the message would persist on every restart, even if After restarting the bad block message appeared:
Restarting led to nothing, since the node refused to connect anymore. |
this is an alpha node though, so I'm guessing it's not static file related |
I believe this is #6083 which we haven't fixed properly yet |
both there must be something else here, |
This issue is stale because it has been open for 21 days with no activity. |
This issue was closed because it has been inactive for 7 days since being marked as stale. |
Describe the bug
I restarted reth while syncing on stage 2, got the following message, and then my trusted peer (reth archive alpha 21) dropped and syncing halted. After restarting and connecting to a geth peer, the node kept syncing normally.
Steps to reproduce
steps above
Node logs
No response
Platform(s)
Linux (x86)
What version/commit are you on?
reth Version: 0.2.0-beta.1 Commit SHA: 91c7dd0
What database version are you on?
2
What type of node are you running?
Archive (default)
What prune config do you use, if any?
No response
If you've built Reth from source, provide the full command you used
No response
Code of Conduct
The text was updated successfully, but these errors were encountered: