Skip to content
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

Closed
dgdeivid opened this issue Dec 1, 2021 · 5 comments
Closed

Bad block even after restoring everything. #619

dgdeivid opened this issue Dec 1, 2021 · 5 comments
Labels
question Further information is requested

Comments

@dgdeivid
Copy link

dgdeivid commented Dec 1, 2021

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:

  • I have rebooted both the server and the node multiple times. I have shutdown the node correctly waiting for the cache to be saved.
  • I have started the node without using this command, and using it: "--snapshot = false --syncmode = fast"
  • I have deleted all databases by deleting the entire node data directory.
  • I downloaded the latest snapshot and tried to sync the node from snapshot again, just like I did the first time.

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

@keefel keefel added the question Further information is requested label Dec 1, 2021
@cipig
Copy link

cipig commented Dec 3, 2021

i got this error with 1.1.6 too... 2 nodes just stopped syncing, both are showing ########## BAD BLOCK #########

@adamiss5138
Copy link

adamiss5138 commented Dec 3, 2021

Same error, node stopped syncing. Bad blocks error

t=2021-12-03T17:06:31+0100 lvl=info msg="Downloader queue stats" receiptTasks=0 blockTasks=0 itemSize="96.21 KiB" throttle=682 t=2021-12-03T17:06:31+0100 lvl=info msg="Skip duplicated bad block" number=13,162,406 hash=0x25ebe8fee3ad73705be527f1c45541bb061eaa3542745883751cf2f8c5602ca8 t=2021-12-03T17:06:31+0100 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: 13082000, Berlin: <nil>, YOLO v3: <nil>, Engine: parlia}\n\nNumber: 13162406\nHash: 0x25ebe8fee3ad73705be527f1c45541bb061eaa3542745883751cf2f8c5602ca8\n\t 0: cumulative: 39328 gas: 39328 contract: 0x0000000000000000000000000000000000000000 status: 0 tx: 0x6797bdd8007d487ad20b3d1ed891d14005078760f4e174f68dc1938968342f3d logs: [] bloom: 00000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000...

@serfiraz21
Copy link

yes same error i getting what is the solution ? i using v.1.16

@keefel
Copy link
Contributor

keefel commented Dec 8, 2021

Yes, it's a bug, please refer to #628

@RumeelHussainbnb
Copy link
Contributor

We have responded to the question and will proceed to close the case as we didn't get any additional question after 3days.
Please proceed to join our Discord channel for more discussion at https://discord.com/invite/binancesmartchain

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

7 participants