base full node can't sync block

[zhy827827]

reth 1.5.0

/opt/rockx/base/bin/op-reth node -vvv --datadir=/opt/rockx/base/reth --log.stdout.format log-fmt --ws --ws.origins=* --ws.addr=0.0.0.0 --ws.port=28546 --ws.api=debug,eth,net,txpool --http --http.corsdomain=* --http.addr=0.0.0.0 --http.port=28545 --http.api=debug,eth,net,txpool --authrpc.addr=0.0.0.0 --authrpc.port=8555 --authrpc.jwtsecret=/opt/rockx/base/secrets/engine-auth-jwt --metrics=0.0.0.0:16060 --chain base --rpc.gascap 300000000 --full --rollup.sequencer-http=https://mainnet-sequencer.base.org --rollup.disable-tx-pool-gossip --port 30333

base-node: op-node version v1.13.4

op-node logs:

 lvl=warn msg="Engine temporary error" err="temp: failed to fetch receipts of L1 block 0xbe41c4af3edad65815bf81984d76475c70b8b620db26a187c2ffd34717011860:22831493 (parent: 0xc51f1e2fc66d75faed4609a64f21cfa684f38ae92205a95afbca5529d84914bd:22831492) for L1 sysCfg update: failed to fetch list of receipts: expected receipt root 0x3df4078a0f9d3327da1a9c383ae22f1e40cd58ef5f5a53b75c29a172337c8fd7 but computed 0xc030af83cd6f98d8daa9556ceded83f64a808561ce231146e141144d0c2f6376 from retrieved receipts"



Jul 03 03:09:25 rockx-mainnet-access-mix-ca-09 bash[3975012]: t=2025-07-03T03:09:25+0000 lvl=info msg="Optimistically queueing unsafe L2 execution payload" id=0x63935a3e0ef0e4677e0cc324c0a84e76e6506e5a7000853a3ca3dd15ac7291af:32361409
Jul 03 03:09:27 rockx-mainnet-access-mix-ca-09 bash[3975012]: t=2025-07-03T03:09:27+0000 lvl=info msg="Optimistically queueing unsafe L2 execution payload" id=0x3f291139c6246d2e29e197ad063d16ffaef3733725691661743e74dbfad6b2a5:32361410
Jul 03 03:09:29 rockx-mainnet-access-mix-ca-09 bash[3975012]: t=2025-07-03T03:09:29+0000 lvl=info msg="Optimistically queueing unsafe L2 execution payload" id=0xd8ad1611d6f2a3329815092f5f148ef6d50577658e3693931df9d226fc982813:32361411
Jul 03 03:09:31 rockx-mainnet-access-mix-ca-09 bash[3975012]: t=2025-07-03T03:09:31+0000 lvl=info msg="Optimistically queueing unsafe L2 execution payload" id=0x8fa78c866837f81817dd49d0d3862f608cea1cda91221207d16c4aa3bac5593c:32361412
Jul 03 03:09:33 rockx-mainnet-access-mix-ca-09 bash[3975012]: t=2025-07-03T03:09:33+0000 lvl=info msg="Optimistically queueing unsafe L2 execution payload" id=0x1bd870632304408eba76c1fbf960f0ac4d3150c39a3b6ec4dbdd2868f6f366a2:32361413
Jul 03 03:09:34 rockx-mainnet-access-mix-ca-09 bash[3975012]: t=2025-07-03T03:09:34+0000 lvl=warn msg="Engine temporary error" err="temp: failed to fetch receipts of L1 block 0xbe41c4af3edad65815bf81984d76475c70b8b620db26a187c2ffd34717011860:22831493 (parent: 0xc51f1e2fc66d75faed4609a64f21cfa684f38ae92205a95afbca5529d84914bd:22831492) for L1 sysCfg update: failed to fetch list of receipts: expected receipt root 0x3df4078a0f9d3327da1a9c383ae22f1e40cd58ef5f5a53b75c29a172337c8fd7 but computed 0xc030af83cd6f98d8daa9556ceded83f64a808561ce231146e141144d0c2f6376 from retrieved receipts"
Jul 03 03:09:35 rockx-mainnet-access-mix-ca-09 bash[3975012]: t=2025-07-03T03:09:35+0000 lvl=info msg="Optimistically queueing unsafe L2 execution payload" id=0x6df3fe1c2c696f00f819095ec8b8437f4e18a294af38fb551e74c928144eb5c2:32361414
Jul 03 03:09:37 rockx-mainnet-access-mix-ca-09 bash[3975012]: t=2025-07-03T03:09:37+0000 lvl=info msg="Optimistically queueing unsafe L2 execution payload" id=0xa9ca75c2d1f71948d779bed05e442b3b0075b4a85feebb32fcc8d36d104307ee:32361415
Jul 03 03:09:39 rockx-mainnet-access-mix-ca-09 bash[3975012]: t=2025-07-03T03:09:39+0000 lvl=info msg="Optimistically queueing unsafe L2 execution payload" id=0xba4381060a5bb7afe449da100f4416fdb5d0c11f1cb62175ed818dbbb1f9e701:32361416

reth logs:

 level=warn target=reth_node_events::node message="Beacon client online, but no consensus updates received for a while. This may be because of a reth error, or an error in the beacon client! Please investigate reth and beacon client logs!" period=1148.223583924s


Jul 03 03:42:09 rockx-mainnet-access-mix-ca-09 sh[3975617]: ts=2025-07-03T03:42:09.975909711Z level=info target=reth::cli message=Status connected_peers=33 latest_block=32339469
Jul 03 03:42:34 rockx-mainnet-access-mix-ca-09 sh[3975617]: ts=2025-07-03T03:42:34.976275213Z level=info target=reth::cli message=Status connected_peers=33 latest_block=32339469
Jul 03 03:42:56 rockx-mainnet-access-mix-ca-09 sh[3975617]: ts=2025-07-03T03:42:56.974209378Z level=warn target=reth_node_events::node message="Beacon client online, but no consensus updates received for a while. This may be because of a reth error, or an error in the beacon client! Please investigate reth and beacon client logs!" period=1148.223583924s
Jul 03 03:42:59 rockx-mainnet-access-mix-ca-09 sh[3975617]: ts=2025-07-03T03:42:59.97526961Z level=info target=reth::cli message=Status connected_peers=33 latest_block=32339469
Jul 03 03:43:24 rockx-mainnet-access-mix-ca-09 sh[3975617]: ts=2025-07-03T03:43:24.975535898Z level=info target=reth::cli message=Status connected_peers=35 latest_block=32339469
Jul 03 03:43:49 rockx-mainnet-access-mix-ca-09 sh[3975617]: ts=2025-07-03T03:43:49.975894247Z level=info target=reth::cli message=Status connected_peers=36 latest_block=32339469
Jul 03 03:44:14 rockx-mainnet-access-mix-ca-09 sh[3975617]: ts=2025-07-03T03:44:14.976034736Z level=info target=reth::cli message=Status connected_peers=36 latest_block=32339469

how to fix this issues??

[meyer9]

Hey @zhy827827 , you need to make sure the consensus layer client (op-node) is running also. It seems like only the EL node is running right now. Will close this for now, but feel free to post on Discord if you run into more issues.