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.

Sign up for GitHub

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

Jump to bottom

POSSIBLE FAST SYNC CORRUPTION - root cause analysis #4776

Closed

kamilchodola opened this issue Oct 18, 2022 · 0 comments · Fixed by #4787

Assignees

Contributor

kamilchodola commented Oct 18, 2022

Describe the bug
Error from title happened already few times on smoke tests but is not easy to reproduce - currently for about 100 nodes started it happened on two of them:
https://seq.nethermind.io/#/events?filter=Contains(NodeName,%20'Smoke-Tests-Snap-BranchesEth67-mainnet-lodestar')&signal=(signal-m33301~signal-m33302)
Above one on 18Oct2022 17:11:18

https://seq.nethermind.io/#/events?filter=Contains(NodeName,%20'Smoke-Tests-Snap-BranchesEth66-goerli-lighthouse')&from=2022-10-18T14:00:00.000Z&signal=(signal-m33301~signal-m33302)
This one is for goerli.

For goerli node already started Init.DiagnosticMode "VerifyTrie" - waiting for outcome as for now.

kamilchodola assigned asdacap and MarekM25

MarekM25 assigned damian-orzechowski

asdacap mentioned this issue

Make sure reset state root is in a lock #4787

Merged

11 tasks

asdacap closed this as completed in #4787

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment