Skip to content

Sync error after fusaka upgrdae #261

@Hizitok

Description

@Hizitok

Describe the bug

After fusaka upgrade, base-reth-node have unexpected error and info logs.

Node logs

2025-12-07T06:04:57.785625Z  INFO added flashblock to processing queue block_number=34339139 flashblock_index=4
2025-12-07T06:04:57.785695Z  INFO waiting for first Flashblock
2025-12-07T06:04:58.072890Z  INFO Received block from consensus engine number=34339139 hash=0x0664d37044f2839bdfd1bbf976f28b72723b2028ca420fca08bbff7c96bba321
2025-12-07T06:04:58.101654Z  INFO Executed block range start=33064261 end=33068873 throughput="781.80Mgas/second"
2025-12-07T06:04:58.139323Z  INFO added flashblock to processing queue block_number=34339140 flashblock_index=0
2025-12-07T06:04:58.139422Z ERROR could not process Flashblock error=Failed to extract header for canonical block number 34339139. This can be ignored if the node has recently restarted, restored from a snapshot or is still syncing.
2025-12-07T06:04:58.144446Z  INFO added flashblock to processing queue block_number=34339140 flashblock_index=1
2025-12-07T06:04:58.144504Z  INFO waiting for first Flashblock
2025-12-07T06:04:58.285113Z  INFO added flashblock to processing queue block_number=34339140 flashblock_index=2
2025-12-07T06:04:58.285185Z  INFO waiting for first Flashblock
2025-12-07T06:04:58.531711Z  INFO added flashblock to processing queue block_number=34339140 flashblock_index=3
2025-12-07T06:04:58.531790Z  INFO waiting for first Flashblock
2025-12-07T06:04:58.781282Z  INFO added flashblock to processing queue block_number=34339140 flashblock_index=4
2025-12-07T06:04:58.781360Z  INFO waiting for first Flashblock

it still get error after a 24-hour syncing, so I'm not sure if it is normal or not.

and, eth_syncing method to rpc to get sync status returns:

$ curl -X POST http://localhost:18547 \
     -H "Content-Type: application/json" \
     -d '{
           "jsonrpc": "2.0",
           "method": "eth_syncing",
           "params": [],
           "id": 1
         }'
{"jsonrpc":"2.0","id":1,"result":{"startingBlock":"0x0","currentBlock":"0x0","highestBlock":"0x0","warpChunksAmount":null,"warpChunksProcessed":null,"stages":[{"name":"AccountHashing","block":"0x0"},{"name":"Bodies","block":"0x20be4b4"},{"name":"Era","block":"0x0"},{"name":"Execution","block":"0x202216f"},{"name":"Finish","block":"0x0"},{"name":"Headers","block":"0x20be4b4"},{"name":"IndexAccountHistory","block":"0x0"},{"name":"IndexStorageHistory","block":"0x0"},{"name":"MerkleChangeSets","block":"0x0"},{"name":"MerkleExecute","block":"0x0"},{"name":"MerkleUnwind","block":"0x0"},{"name":"Prune","block":"0x0"},{"name":"PruneSenderRecovery","block":"0x0"},{"name":"SenderRecovery","block":"0x20be4b4"},{"name":"StorageHashing","block":"0x0"},{"name":"TransactionLookup","block":"0x0"}]}}

Platform(s)

Operating System: AlmaLinux 9.6 (Sage Margay)
CPE OS Name: cpe:/o:almalinux:almalinux:9::baseos
Kernel: Linux 5.14.0-503.33.1.el9_5.x86_64
Architecture: x86-64
Firmware Version: 2.18.1

Container Type

Not running in a container

What version/commit are you on?

Base Reth Node Version: 1.9.3-dev
Commit SHA: 27a8c0f5a6dfb27dea84c5751776ecabdd069646
Build Timestamp: 2025-12-07T04:29:55.765965866Z
Build Features: jemalloc,otlp
Build Profile: release

op-node version v1.16.3-478b8bda-1764819032

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions