[Node Operator Question] Node suddenly began reverting blocks, and now seems to be irrecoverable #419
Replies: 1 comment
-
The database may be damaged. You can restart op-geth to get more logs, which may have relevant information. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Are you running the most up to date node software?
Did you check the documentation?
Did you check for duplicate questions?
Issue Description
Whilst running today, our node suddenly reverted a number of blocks, dropping the block height from 120426290 back to 120407444. op-geth was killed by systemd, and shortly after the following emerged in op-node
When investigating, op-node appears to go through the steps of
op-node is now jsut going through the process of dialing peers and disconnecting, log sample
All error level logs here:
Protocol Description
Prior to issue we were running the following:
op-node: v1.7.1
op-geth: 1.101308.2
We are now running
op-node: v1.7.5
op-geth: 1.101315.0
op-node flags:
op-geth flags:
Node Logs
Only logs from op-geth are basically the below
Additional Information
No response
Feedback
No response
Beta Was this translation helpful? Give feedback.
All reactions