-
Notifications
You must be signed in to change notification settings - Fork 20.3k
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
Full Sync fails on block 3804607 with BAD BLOCK ERROR: invalid gas used #17261
Comments
Very interesting.. when you say two attempts, does that mean that you removed the datadir in between attempts? Or just restarted? Because if the latter, I would suspect disk corruption. If the former, well, then that's very very odd. We regularly do full syncs for testing. |
"sudo geth --datadir /media/nuc/970_EVO_500GB/ethereum_full removedb" between, starting the third |
the 3rd, 4th attempts failed on some random blocks (before block 3804607) due to db corruption
|
same issue |
same issue here: |
Same issue here: Geth/v1.8.13-stable/linux-amd64/go1.10.3 at block 4181244.
|
Same issue here: 1.8.14-stable |
Same issue.
|
Having same issue in 1.8.16 for 3804607 block. Any solution for this, yet?? |
Confirmed same issue on Was running sync with "geth --syncmode "full" --cache 24000 Stalls on the same error every time I restart geth |
FWIW, tx 0x5ec195b89aa8f2385de7d1b5ffd9d7e9f0c96a8f26837886d9d0897402c9c7dc seems to be the problematic one. |
Same issue here as well
|
Facing same issue on ubuntu 16. How can we overcome this? |
Power overwhelming. |
Looks like you are getting block data from a peer with an invalid chain. |
This was fixed by #18165 . The blocks reported here are all in the range where a certain exchange created >65K contract instances within a short time span. If you ran geth with large cache allowance, the ref counter would overflow and suddenly the code for that contract would be pruned by the in-memory pruner. |
Same issue in: Geth |
System information
Geth version: 1.8.12-stable-37685930
OS & Version: Ubuntu 18.04
Expected behaviour
Syncing
Actual behaviour
Looping through peers on block 3804607 with BAD BLOCK ERROR: invalid gas used (remote: 1329607 local: 1541792)
2 attempts - same block, same error
Steps to reproduce the behaviour
sudo geth remove db
sudo geth --cache 11000 --syncmode full
Logs:
The text was updated successfully, but these errors were encountered: