-
Notifications
You must be signed in to change notification settings - Fork 809
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
Database corruption during restarts since switching to upstream v1.14.7 #360
Comments
It happened again a couple of times. That's a log excerpt from inactive sepolia seq-2.
|
Related: ethereum/go-ethereum#30119 |
Fix implemented in #368 - adds journal v0 to v1 migration code. ethereum/go-ethereum#28940 introduced a new journal format, but didn't add migration code. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We've recently merged in upstream v1.14.7 and during a sequencer restart, the following errors popped up:
So at startup, safe and finalized are reset to genesis. The op-node will then currently walk back to genesis. This was fixed locally by shutting down op-node, and using
op-wheel engine rewind --set-head --to 8460000
, but the source for this db corruption isn't clear yet.The text was updated successfully, but these errors were encountered: