-
Notifications
You must be signed in to change notification settings - Fork 20.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
Ful Sync: BAD BLOCK #22689
Comments
I'm facing the same issue on the same exact block ERROR[04-17|09:36:21.648]
########## BAD BLOCK #########
Chain config: {ChainID: 1 Homestead: 1150000 DAO: 1920000 DAOSupport: true EIP150: 2463000 EIP155: 2675000 EIP158: 2675000 Byzantium: 4370000 Constantinople: 7280000 Petersburg: 7280000 Istanbul: 9069000, Muir Glacier: 9200000, Berlin: <nil>, YOLO v3: <nil>, Engine: ethash}
Number: 12244000
Hash: 0x1638380ab737e0e916bd1c7f23bd2bab2a532e44b90047f045f262ee21c42b21
Error: could not apply tx 122 [0x2e91ec8bde129768ad253384dc6002e66cd878de2bc393373998a8c4ac3a456e]: gas limit reached
############################## |
This block is the Berlin HardFork - please read: https://blog.ethereum.org/2021/03/08/ethereum-berlin-upgrade-announcement/ and install the latest geth |
I confirm this fixed the issue for me. |
Fixed for me as well |
Synopsis
Geth stops working after finding a bad block:
(please see the whole backlog in the end).
Similar issues:
What I understand from these issues is that, as geth sifts through enormous amounts of data, with more time and data, the probability for a random erroneous bit-flip goes up. And then it happens and then the (whole?) blockchain goes sour.
Do the unclean shutdowns (see the backlog below) increase this probability as well?
So instead of a bug, this is blockchain corruption?
Is there any way to remove the corrupted block .. or is the origin of the problem hidden somewhere deep down in the blockchain and the only way to solve this, is to download the whole thing again? (a think I'd rather avoid since I never got the fast sync to actually sync, see this).
System information
Geth version:
1.10
OS & Version: LInux (Ubuntu 18.04 LTS)
Expected behaviour
Actual behaviour
Geth stops as it finds a "bad block"
Steps to reproduce the behaviour
N/A
Backtrace
The text was updated successfully, but these errors were encountered: