-
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 even after restoring everything. #619
Comments
i got this error with 1.1.6 too... 2 nodes just stopped syncing, both are showing |
Same error, node stopped syncing. Bad blocks error
|
yes same error i getting what is the solution ? i using v.1.16 |
Yes, it's a bug, please refer to #628 |
We have responded to the question and will proceed to close the case as we didn't get any additional question after 3days. |
After being the node synchronized correctly for 3 days it has given a bad block error and has been out of sync.
t=2021-12-01T11:07:34+0000 lvl=eror msg="\n########## BAD BLOCK #########\nChain config: {ChainID: 56 Homestead: 0 DAO: <nil> DAOSupport: false EIP150: 0 EIP155: 0 EIP158: 0 Byzantium: 0 Constantinople: 0 Petersburg: 0 Istanbul: 0, Muir Glacier: 0, Ramanujan: 0, Niels: 0, MirrorSync: 5184000, Bruno: <nil>, Berlin: <nil>, YOLO v3: <nil>, Engine: parlia}\n\nNumber: 13082000\nHash: 0xeafc056d4cd2355235e385604eb86c9fc3da295a5ac6b292dcd518aad81c96c7\n\t 0: cumulative: 130165 gas: 130165 contract: 0x0000000000000000000000000000000000000000 status: 1 tx: 0xabe7acccb273e1d5c63977f184ff1c0ddf9e56a0ef1bec4681e07c443d4661db logs: [0xc0aaf80000 0xc0aaf800b0 0xc0aaf80160 0xc0aaf80210 0xc0aaf802c0] bloom: 00a0000000000000000000108.......
This is what I have tried to try to fix it:
After several hours without syncing, the same bad block error occurs again and it never gets to sync even though I have deleted the entire database.
I am using 1.1.4
The text was updated successfully, but these errors were encountered: