Cannot seal block, payload ID is unknown

[DaraDoyoung]

Did you check the documentation?

• Yes

Did you check for duplicate questions?

• Yes

Issue Description

I am currently running Base mainnet with op-reth + op-node.
op-node seems to not work properly, giving out cannot seal block log.
What is the problem?

My run scripts:

// op-reth
op-reth node \
  --chain base \
  --ws \
  --ws.port=8546 \
  --ws.addr=0.0.0.0 \
  --ws.origins="*" \
  --rollup.sequencer-http https://mainnet-sequencer.base.org \
  --http \
  --http.port=8545 \
  --http.addr=0.0.0.0 \
  --http.corsdomain="*" \
  --http.api="eth,web3,net,txpool,debug,trace,admin,rpc" \
  --authrpc.addr=127.0.0.1 \
  --authrpc.jwtsecret=/home/ubuntu/data/jwt.txt \
  --authrpc.port=8551 \
  --ipcpath=/mnt/app/data/op-reth-data/reth.ipc \
  --datadir=/home/ubuntu/data/op-reth-data \
  --port 30304

// op-node
op-node \
  --l1=http://{l1_endpoint}:8545 \
  --l2=http://127.0.0.1:8551 \
  --network=base-mainnet \
  --rollup.load-protocol-versions=true \
  --rpc.addr=0.0.0.0 \
  --rpc.port=9545 \
  --l2.jwt-secret=/home/ubuntu/data/jwt.txt \
  --l1.trustrpc=true \
  --l1.beacon=http://{l1_endpoint}:5052 \
  --p2p.listen.ip=0.0.0.0 \
  --p2p.listen.tcp=9222 \
  --p2p.listen.udp=9222 \
  --rollup.config=/home/ubuntu/data/rollup.json \
  --verifier.l1-confs=4 \
  --rollup.load-protocol-versions=true

BTW my l1 has blob data.

Logs

t=2024-11-05T09:15:11+0000 lvl=info msg="Starting P2P sync client event loop" peer=16Uiu2HAmHPhvZqNchJNhhBsFCjpB3ikQ1b9mN434HTvWm7RLqjUp
t=2024-11-05T09:15:12+0000 lvl=info msg="Received signed execution payload from p2p" id=0x1a1afc77dd2baf713d9a9a1bfb5d8391b81116a7cef9c52b0227f6e4be3c6cc5:22004382 peer=16Uiu2HAmBDhteFRgQk98h7zTVi3NpR7fR1M8xqyi6YTdfHAMMqbj txs=143
t=2024-11-05T09:15:12+0000 lvl=info msg="Optimistically queueing unsafe L2 execution payload" id=0x1a1afc77dd2baf713d9a9a1bfb5d8391b81116a7cef9c52b0227f6e4be3c6cc5:22004382
t=2024-11-05T09:15:13+0000 lvl=info msg="Received signed execution payload from p2p" id=0xa8f0d241eb99458a07fe5532f582aa8b0eb1e7e84569ff30abd2ac66b3896393:22004383 peer=16Uiu2HAmBDhteFRgQk98h7zTVi3NpR7fR1M8xqyi6YTdfHAMMqbj txs=131
t=2024-11-05T09:15:13+0000 lvl=info msg="Optimistically queueing unsafe L2 execution payload" id=0xa8f0d241eb99458a07fe5532f582aa8b0eb1e7e84569ff30abd2ac66b3896393:22004383
t=2024-11-05T09:15:16+0000 lvl=info msg="Received signed execution payload from p2p" id=0x8a1e725f04e5d197d647521e33ba44ba70fe32b0948344a15a3bed51d8518910:22004384 peer=16Uiu2HAkxaXPeUAuAizGTKmJbRFTsmUNxui1BDeDXEyrPLH24y35 txs=132
t=2024-11-05T09:15:16+0000 lvl=info msg="Optimistically queueing unsafe L2 execution payload" id=0x8a1e725f04e5d197d647521e33ba44ba70fe32b0948344a15a3bed51d8518910:22004384
t=2024-11-05T09:15:18+0000 lvl=info msg="Received signed execution payload from p2p" id=0x4cc43c5cad9883861bbfa2e103d49b09f4b7fac44b88ae9c20fda8802d826a81:22004385 peer=16Uiu2HAm1Np89gwr77Sgfag5SRWqtB14idJFVNZZcxKWSoHeYc5B txs=140
t=2024-11-05T09:15:18+0000 lvl=info msg="Optimistically queueing unsafe L2 execution payload" id=0x4cc43c5cad9883861bbfa2e103d49b09f4b7fac44b88ae9c20fda8802d826a81:22004385
t=2024-11-05T09:15:20+0000 lvl=info msg="Received signed execution payload from p2p" id=0xf240cad3c54b9d6f19bd7a4ff3af93311b09fc8218a2641b22065b7ef3dfa77e:22004386 peer=16Uiu2HAm1Np89gwr77Sgfag5SRWqtB14idJFVNZZcxKWSoHeYc5B txs=138
t=2024-11-05T09:15:20+0000 lvl=warn msg="Failed to get payload" payload_id=0x03f56c6c6cfd92f0 payload_id=0x03f56c6c6cfd92f0 err="Unknown payload"
t=2024-11-05T09:15:20+0000 lvl=warn msg="Cannot seal block, payload ID is unknown" payloadID=0x03f56c6c6cfd92f0 payload_time=1730160007 started_time=2024-11-05T09:15:20+0000
t=2024-11-05T09:15:20+0000 lvl=warn msg="Block sealing job of derived attributes expired, job will be re-attempted." build_id=0x03f56c6c6cfd92f0 timestamp=1730160007 err="failed to seal execution payload (ID: 0x03f56c6c6cfd92f0): input error -38001: Unknown payload"
t=2024-11-05T09:15:20+0000 lvl=info msg="Optimistically queueing unsafe L2 execution payload" id=0xf240cad3c54b9d6f19bd7a4ff3af93311b09fc8218a2641b22065b7ef3dfa77e:22004386
t=2024-11-05T09:15:22+0000 lvl=info msg="Received signed execution payload from p2p" id=0x20385e8d7e9678161cdc7f05af7e1894e3b3dde6f804fbcc59497c945dc1a61c:22004387 peer=16Uiu2HAmBDhteFRgQk98h7zTVi3NpR7fR1M8xqyi6YTdfHAMMqbj txs=122
t=2024-11-05T09:15:22+0000 lvl=info msg="Optimistically queueing unsafe L2 execution payload" id=0x20385e8d7e9678161cdc7f05af7e1894e3b3dde6f804fbcc59497c945dc1a61c:22004387
t=2024-11-05T09:15:24+0000 lvl=info msg="Received signed execution payload from p2p" id=0x7fc6a8db1c8507ef71ee9560ede19ad2ae087b7eae0e46e35a034716e9f62ac8:22004388 peer=16Uiu2HAm9ekUfDrexCTJxA2eqdLsSYwNLMVLV4ZjJ6YkjEmbcyWD txs=149
t=2024-11-05T09:15:24+0000 lvl=info msg="Optimistically queueing unsafe L2 execution payload" id=0x7fc6a8db1c8507ef71ee9560ede19ad2ae087b7eae0e46e35a034716e9f62ac8:22004388
t=2024-11-05T09:15:26+0000 lvl=info msg="Received signed execution payload from p2p" id=0x768f3cd6047288385c002b3dcc611eec67577a727a82968d934cb449b1b09745:22004389 peer=16Uiu2HAm9ekUfDrexCTJxA2eqdLsSYwNLMVLV4ZjJ6YkjEmbcyWD txs=154
t=2024-11-05T09:15:26+0000 lvl=info msg="Optimistically queueing unsafe L2 execution payload" id=0x768f3cd6047288385c002b3dcc611eec67577a727a82968d934cb449b1b09745:22004389
t=2024-11-05T09:15:28+0000 lvl=info msg="Received signed execution payload from p2p" id=0x3ca3951e5849d32fa6797d5e47e5ecb5bab2fd62d27c5ba10cec843376507e1b:22004390 peer=16Uiu2HAmBDhteFRgQk98h7zTVi3NpR7fR1M8xqyi6YTdfHAMMqbj txs=196
t=2024-11-05T09:15:28+0000 lvl=info msg="Optimistically queueing unsafe L2 execution payload" id=0x3ca3951e5849d32fa6797d5e47e5ecb5bab2fd62d27c5ba10cec843376507e1b:22004390

Additional Information

No response

Feedback

No response

[DaraDoyoung]

found the issue.
my op-node config was the reason for this.
had to add these flags

    --syncmode=execution-layer
    --l2.enginekind=reth