I encountered an unknown problem when I updated to the latest version of op-geth

[Leo-Li009]

Are you running the most up to date node software?

• Yes

Did you check the documentation?

• Yes

Did you check for duplicate questions?

• Yes

Issue Description

When I updated to the latest version of op-geth and restarted op-geth and op-node, I encountered the following problem

INFO [03-01|08:09:55.056] HTTP server started endpoint=[::]:8551 auth=true prefix= cors=localhost vhosts=*
INFO [03-01|08:25:32.935] Starting work on payload id=0xf41168c0d10e5ad8
WARN [03-01|08:25:35.269] Ignoring already known beacon payload number=116,835,480 hash=1e4767..a0bd09 age=3h16m38s
ERROR[03-01|08:25:35.283] Failed to create sealing context err="missing trie node a121e24acb7c347505f4e4741e577ef26b9b65fec6aa0b478fb6dda230198936 (path ) state 0xa121e24acb7c347505f4e4741e577ef26b9b65fec6aa0b478fb6dda230198936 is not available, not found"
ERROR[03-01|08:25:35.283] Failed to build payload err="missing trie node a121e24acb7c347505f4e4741e577ef26b9b65fec6aa0b478fb6dda230198936 (path ) state 0xa121e24acb7c347505f4e4741e577ef26b9b65fec6aa0b478fb6dda230198936 is not available, not found"
WARN [03-01|08:25:35.283] Served engine_forkchoiceUpdatedV2 conn=127.0.0.1:40048 reqid=45998 duration=3.547645ms err="Invalid payload attributes" errdata="{Error:missing trie node a121e24acb7c347505f4e4741e577ef26b9b65fec6aa0b478fb6dda230198936 (path ) state 0xa121e24acb7c347505f4e4741e577ef26b9b65fec6aa0b478fb6dda230198936 is not available, not found}"

I tried a lot of things like changing some parameters, rebooting constantly, changing the op-node, and I still keep getting this error, I'm sure it's the op-geth that's the problem and not the op-node, and the same datadisk works fine for me on another computer, but not on my current one!

Protocol Description

op-geth version: v1.101308.2
op-node version: v1.7.0
network name: op mainnet
chainid: 10
L1 chain: Locally run geth node

Node Logs

WARN [03-01|08:09:55.043] Engine API enabled protocol=eth
INFO [03-01|08:09:55.043] Starting peer-to-peer node instance=Geth/v0.1.0-unstable-0402d543/linux-amd64/go1.21.6
INFO [03-01|08:09:55.055] IPC endpoint opened url=/home/leo/op-ssd/chaindata/geth/geth.ipc
INFO [03-01|08:09:55.055] New local node record seq=1,694,117,146,229 id=46e19b80538f7408 ip=127.0.0.1 udp=0 tcp=30303
INFO [03-01|08:09:55.055] Started P2P networking self="enode://66802ca81fe651374ea229d3e23674a6d367049b1ec0ebc46729a4d36d09b894c2bb64d93ffc1b66074a8010c961430e5298298e5cd47a0b07d05462e06754fb@127.0.0.1:30303?discport=0"
INFO [03-01|08:09:55.055] Loaded JWT secret file path=/home/leo/op-ssd/op-geth/jwt.txt crc32=0xa1dc6b42
INFO [03-01|08:09:55.056] HTTP server started endpoint=[::]:8545 auth=false prefix=/ cors=* vhosts=*
INFO [03-01|08:09:55.056] WebSocket enabled url=ws://[::]:8546
INFO [03-01|08:09:55.056] WebSocket enabled url=ws://[::]:8551
INFO [03-01|08:09:55.056] HTTP server started endpoint=[::]:8551 auth=true prefix= cors=localhost vhosts=*
INFO [03-01|08:25:32.935] Starting work on payload id=0xf41168c0d10e5ad8
WARN [03-01|08:25:35.269] Ignoring already known beacon payload number=116,835,480 hash=1e4767..a0bd09 age=3h16m38s
ERROR[03-01|08:25:35.283] Failed to create sealing context err="missing trie node a121e24acb7c347505f4e4741e577ef26b9b65fec6aa0b478fb6dda230198936 (path ) state 0xa121e24acb7c347505f4e4741e577ef26b9b65fec6aa0b478fb6dda230198936 is not available, not found"
ERROR[03-01|08:25:35.283] Failed to build payload err="missing trie node a121e24acb7c347505f4e4741e577ef26b9b65fec6aa0b478fb6dda230198936 (path ) state 0xa121e24acb7c347505f4e4741e577ef26b9b65fec6aa0b478fb6dda230198936 is not available, not found"
WARN [03-01|08:25:35.283] Served engine_forkchoiceUpdatedV2 conn=127.0.0.1:40048 reqid=45998 duration=3.547645ms err="Invalid payload attributes" errdata="{Error:missing trie node a121e24acb7c347505f4e4741e577ef26b9b65fec6aa0b478fb6dda230198936 (path ) state 0xa121e24acb7c347505f4e4741e577ef26b9b65fec6aa0b478fb6dda230198936 is not available, not found}"

Additional Information

No response

Feedback

No response

[opfocus]

ethereum-optimism/op-geth#220 ethereum-optimism/optimism#8784

Two possibly related issues. If you are certain that neither of the aforementioned scenarios occurred (forced shutdown of op-geth or pruning was performed),
I'm unsure if it's due to an upgrade causing a mismatch with op-node. Perhaps you can try deleting the files LOCK, nodekey, nodes, and transactions.rlp located at ~/op-geth/datadir/geth#, as flushing them out through testing didn't lead to a crash. Then restart op-geth and op-node (not sure if it will help).

[Leo-Li009]

I tried deleting the files but it didn't work

[opfocus]

https://docs.optimism.io/builders/node-operators/management/snapshots#op-mainnet-archive-node Is it acceptable for you to use snapshot data to resynchronize it?

[Leo-Li009]

I tried removing the op's configuration parameter "
--l1.rpckind=debug_geth " and it's running successfully now!

[github-actions[bot]]

Hey @Leo-Li009, We hope your recent question was resolved to your satisfaction. Your feedback is invaluable and helps us improve our support services. Could you spare a moment to fill out a short feedback survey. Thank you for helping us improve our developer community.