-
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
BAD BLOCK cant syncing #625
Comments
Same here, started happening on two of my nodes 3 hours ago. |
Use |
Even if that works, that's a workaround. There's a bug that causes this to occur and stop nodes from syncing. |
start with *diffsync disabled, rewind the chain the way @khelle suggested and it should work. *with diffsync on it can happen again after rewind. few people in the discord chats had the same bad block problem |
So diffsync is the problem here? |
The same situation also appeared to me. Since version 1.14, test nodes and main network nodes are prone to sudden bad blocks and fail to synchronize. |
how did we run this ? im trying to ./geth_linux console and >debug.setHead("0xC97444") but the block not change |
Please check #628 to fix |
at 2021-12-03T15:24:32+0000 has given "########## BAD BLOCK #########" message and has been out of sync.
From 15:24 UTC to now still keep giving Bad Block message.
i have tried these steps:
1.Used with diffsync enabled (already enabled).
2. Restated geth client. ( 3 -4 times)
3. Restart without diffsync flag
I use geth v1.1.6. steps above doesnt resolve.
The text was updated successfully, but these errors were encountered: