Attempting to unsafe reorg using backupUnsafe even though it is empty #581
Replies: 5 comments
-
I encountered the same problem... |
Beta Was this translation helpful? Give feedback.
-
https://docs.optimism.io/builders/chain-operators/management/operations#stop-op-geth |
Beta Was this translation helpful? Give feedback.
-
@opfocus seems like its the root issue. But was wondering what's the cause, as on mainnet geth is able to recover itself in such cases.
Do you mean you need to restart both op-node and op-geth, if for example you only need to restart one of them? |
Beta Was this translation helpful? Give feedback.
-
Following the startup sequence in the documentation will reduce error messages in the log. But I don't mean to say that it must be done. The original text of the document is: |
Beta Was this translation helpful? Give feedback.
-
I am encountering the same issue:
It seems the unclean shutdown caused it, however our other Geth nodes for ETH mainnet run just fine with unclean shutdowns. |
Beta Was this translation helpful? Give feedback.
-
Bug Description
Can't sync node after restart
Steps to Reproduce
Snapsync on Base
Restart a few times (not sure about that steps, but eventually at some restart it happens).
even if all restarts are graceful
Node will switch to fullsync
And sometimes it will never sync after that
Expected behavior
Node should catch the tip after restart
Environment Information:
Ubuntu 22
us-docker.pkg.dev/oplabs-tools-artifacts/images/op-node:v1.7.3
us-docker.pkg.dev/oplabs-tools-artifacts/images/op-geth:v1.101311.0
Configurations:
https://github.com/smartcontracts/simple-optimism-node/blob/main/scripts/start-op-node.sh
https://github.com/smartcontracts/simple-optimism-node/blob/main/scripts/start-op-geth.sh
Logs:
Geth:
There are the logs of node during trie missing error
Additional context
L1 rpc and beacon are pingable from inside containers, node and geth p2p ports are opened
Beta Was this translation helpful? Give feedback.
All reactions