This repository was archived by the owner on Mar 15, 2022. It is now read-only.
This repository was archived by the owner on Mar 15, 2022. It is now read-only.
Nonce too high error. #90
Description
Starting today I suddenly keep getting this error when running my node.
l2geth-replica_1 | INFO [03-06|16:38:55.310] Syncing transaction range start=4175326 end=4177162 backend=l2
l2geth-replica_1 | DEBUG[03-06|16:38:55.311] Applying transaction to tip index=4175326 hash=0xd25d9918fe9d7927d6c14d41c5f925480c48dd985d0e3bb0377199caf226ee55 origin=sequencer
l2geth-replica_1 | DEBUG[03-06|16:38:55.312] Attempting to commit rollup transaction hash=0xd25d9918fe9d7927d6c14d41c5f925480c48dd985d0e3bb0377199caf226ee55
l2geth-replica_1 | ERROR[03-06|16:38:55.312] Problem committing transaction msg="nonce too high"
l2geth-replica_1 | ERROR[03-06|16:38:55.312] Got error waiting for transaction to be added to chain msg="nonce too high"
l2geth-replica_1 | ERROR[03-06|16:38:55.312] Could not verify error="Verifier cannot sync transactions with BackendL2: Verifier cannot sync transactions with backend l2: Cannot sync transactions with backend l2: Cannot apply transaction: nonce too high"
l2geth-replica_1 | DEBUG[03-06|16:38:55.755] Served eth_getBlockByNumber conn=172.19.0.3:59580 reqid=863 t=132.468µs
l2geth-replica_1 | INFO [03-06|16:38:56.310] Syncing transaction range start=4175326 end=4177163 backend=l2
l2geth-replica_1 | DEBUG[03-06|16:38:56.311] Applying transaction to tip index=4175326 hash=0xd25d9918fe9d7927d6c14d41c5f925480c48dd985d0e3bb0377199caf226ee55 origin=sequencer
l2geth-replica_1 | DEBUG[03-06|16:38:56.311] Attempting to commit rollup transaction hash=0xd25d9918fe9d7927d6c14d41c5f925480c48dd985d0e3bb0377199caf226ee55
l2geth-replica_1 | ERROR[03-06|16:38:56.312] Problem committing transaction msg="nonce too high"
l2geth-replica_1 | ERROR[03-06|16:38:56.312] Got error waiting for transaction to be added to chain msg="nonce too high"
l2geth-replica_1 | ERROR[03-06|16:38:56.312] Could not verify error="Verifier cannot sync transactions with BackendL2: Verifier cannot sync transactions with backend l2: Cannot sync transactions with backend l2: Cannot apply transaction: nonce too high"
l2geth-replica_1 | DEBUG[03-06|16:38:56.760] Served eth_getBlockByNumber conn=172.19.0.3:59582 reqid=864 t=171.777µs
l2geth-replica_1 | INFO [03-06|16:38:57.309] Syncing transaction range start=4175326 end=4177163 backend=l2
l2geth-replica_1 | DEBUG[03-06|16:38:57.311] Applying transaction to tip index=4175326 hash=0xd25d9918fe9d7927d6c14d41c5f925480c48dd985d0e3bb0377199caf226ee55 origin=sequencer
l2geth-replica_1 | DEBUG[03-06|16:38:57.311] Attempting to commit rollup transaction hash=0xd25d9918fe9d7927d6c14d41c5f925480c48dd985d0e3bb0377199caf226ee55
l2geth-replica_1 | ERROR[03-06|16:38:57.312] Problem committing transaction msg="nonce too high"
l2geth-replica_1 | ERROR[03-06|16:38:57.312] Got error waiting for transaction to be added to chain msg="nonce too high"
l2geth-replica_1 | ERROR[03-06|16:38:57.312] Could not verify error="Verifier cannot sync transactions with BackendL2: Verifier cannot sync transactions with backend l2: Cannot sync transactions with backend l2: Cannot apply transaction: nonce too high"
l2geth-replica_1 | DEBUG[03-06|16:38:57.764] Served eth_getBlockByNumber conn=172.19.0.3:59584 reqid=865 t=165.284µs
I am running an Optimism replica node, cloned op-replica and everything worked fine for weeks, until suddenly today when I rebooted, I got all these error.
Anyone any idea what could have gone wrong?