-
Notifications
You must be signed in to change notification settings - Fork 208
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 blocks syncing mainnet using master branch #2132
Comments
More BAD BLOCKS: Block 1209015:
Block 2159017:
Block 3255621:
|
Block 4126439
Block 5235521:
Block 6023364:
Block 7957292:
|
Thanks @jcortejoso . Monitoring for the fix. |
Blocks |
Bisecting the problem on block
But I haven't yet looked what exactly goes wrong there.
|
Are we to assume 1.7.4 is unstable at this point or is it OK to run? |
All releases are stable and (should) sync without problems. This bug only refers to the unstable @aaronmboyd If you encounter problems with any release (as per the discord message), please open a new issue for that with all possible information. Thank you. |
confirmed the commit that @palango mentioned. I did a manual binary search testing syncs and got to the same result. I was a bit slowed down by another issue we have in master that was fixed before this. I haven't been able to pinpoint the exact issue in the commit that's the culprit yet, but I created a new branch from current master, reverting that commit, and the sync doesn't face that issue. |
I've just synced from scratch with the latest master ( e10394d )to 900k blocks without issues. I'll leave it longer but it seems that the previous problem was solved. |
The cause for this has been reverted in #2145. |
Expected Behavior
master
branch should be able to sync the hole chain for mainnetActual Behavior
Using
master
branch and golang 1.17.5, I get the next error:Steps to reproduce the behavior
master
compilationSystem Information
Using docker image
us.gcr.io/celo-testnet/geth:master
Chain/Network:
Mainnet
Thanks to Don Patterson from Discord for reporting.
The text was updated successfully, but these errors were encountered: