[OP Stack Deployment] op-node cannot sync L1 data

[DavidCoder88]

Did you check the documentation?

• Yes

Did you check for duplicate questions?

• Yes

Issue Description

1. my binary file verison：
   ubuntu@ip-162-11-21-40:/test-layer-l2-scripts/op/sequencer-node$ ../build/geth -v
   geth version 1.101408.0-stable-5c2e7586
   ubuntu@ip-162-11-21-40:/test-layer-l2-scripts/op/sequencer-node$ ../build/op-node -v
   op-node version v1.9.1-4797ddb7-1724853807

2.detail:
We set up our L2 using OP around September last year, and it has been running well, syncing L1 (Sepolia) data normally. However, in the past two days, we've encountered an issue where it can no longer sync data. We're not sure exactly when the problem started. After attempting a restart, the node starts syncing L1 data from approximately three days ago, but it soon gets stuck. Specifically, the issue occurs when syncing block 7836368, where errors begin to appear.
We dont update any configuration or starting command, except add new paramter " --l1.trustrpc=true" for op-node.
Can you help me？ tks

Logs

t=2025-03-08T06:41:00+0000 lvl=warn msg="Engine temporary error" err="temp: failed to fetch receipts of L1 block 0xf27015beb7179166439d1e3cd14d8b2445cc2012b62dea906fa219aa06c81b21:7836368 (parent: 0x214c08ac83bd017e123b2ac6ea10561aa8faf72f8aca962c5c1fef98b628115a:7836367) for L1 sysCfg update: querying block: transaction type not supported"
t=2025-03-08T06:41:01+0000 lvl=warn msg="L1 head signal indicates a possible L1 re-org" old_l1_head=0xe4f2c2345c7f10b47ec7c0c36d90791d0d339330a3f0625a6880214e610630b9:7857311 new_l1_head_parent=0xb328c5e4204d4668d3a820ecc6268b0d0f05bdd4d6e9a932d85b218ce469c245 new_l1_head=0xf33cc23973290c3838e765e46dd5937e3e04c639df1d6f0267a02116267ef1a6:7857313
t=2025-03-08T06:41:03+0000 lvl=info msg="attempting connection" peer=16Uiu2HAmMbocKv8MDVmC3VPoRzW1Li4gBssZEkAf8Es4CUQRtGDs
t=2025-03-08T06:41:08+0000 lvl=info msg="attempting connection" peer=16Uiu2HAmMbocKv8MDVmC3VPoRzW1Li4gBssZEkAf8Es4CUQRtGDs
t=2025-03-08T06:41:12+0000 lvl=warn msg="Engine temporary error" err="temp: failed to fetch receipts of L1 block 0xf27015beb7179166439d1e3cd14d8b2445cc2012b62dea906fa219aa06c81b21:7836368 (parent: 0x214c08ac83bd017e123b2ac6ea10561aa8faf72f8aca962c5c1fef98b628115a:7836367) for L1 sysCfg update: querying block: transaction type not supported"

Additional Information

No response

Feedback

No response

[DavidCoder88]

thx a lot

[imtipi]

https://docs.optimism.io/notices/pectra-changes
please upgrade your node,theres lot of update since the deploy

[Chomtana]

L1 Sepolia has a breaking Pectra upgrade. Please refer to this announcement and upgrade your L1 ETH Sepolia node.

It is strongly recommended to update to these releases on Sepolia testnet.

Geth: https://github.com/ethereum/go-ethereum/releases/tag/v1.15.5

Nethermind: https://github.com/NethermindEth/nethermind/releases/tag/1.31.4

Reth: https://github.com/paradigmxyz/reth/releases/tag/v1.2.2

Erigon: https://github.com/erigontech/erigon/releases/tag/v3.0.0-rc2

Sepolia L1 nodes that do not update are expected to fall out of sync, which may prevent batch-submission and stops L2 nodes from syncing.

[opfocus]

This is my upgrade process, but it is for reference only. Since your chain was down for a long time, maybe you should redeploy it
I upgraded my OP Stack chain (tutorials/chain，without fault-proof). I tried upgrading to the version specified in the documentation and compiled the components using the corresponding repo branch:

1. op-geth at v1.101500.0: Encountered multiple issues, one of which was an error when starting the specified op-node:

   failed to load or fetch chain config for id 42069: fetching: the method debug_chainConfig does not exist/is not available
   

   Solution: Abandoned this branch and replaced it with the optimism branch of op-geth.

2. op-node at v1.11.1: Encountered an issue where two related scale parameters were considered redundant.
   Solution: Removed the corresponding two parameters from rollup.json.

3. op-batcher at v1.11.4: Encountered the following issue:

   lvl=warn msg="Served miner_setMaxDASize" reqid=1 duration=11.22µs err="the method miner_setMaxDASize does not exist/is not available"
   

   Solution: This issue is described in a specific branch of the documentation:
   Ethereum Optimism Docs - Batcher Configuration

[opfocus]

If you think there is an acceptable answer, please mark it as the answer and close this discussion.
or you can also continue to add comments