stuck on fetching blob sidecars

[sahfd4eiugf]

Seems this is a recurrent issue with OP node.

My personal lighthouse beacon did not work, but even after trying every single RPC on this list https://eth-clients.github.io/checkpoint-sync-endpoints/ , nothing fixes this error and I can never achieve a full sync.

lvl=warn msg="Engine temporary error" err="derivation failed: temp: failed to fetch blobs: failed to get blob sidecars for L1BlockRef 0x5eaee30a2dc126cb088e37c5e23fd5177ff239e046311c55472b4c379da458d3:21164365: failed to fetch blob sidecars for slot 10375261 block 0x5eaee30a2dc126cb088e37c5e23fd5177ff239e046311c55472b4c379da458d3:21164365: #returned blobs(0) != #requested blobs(5)

[leo-chorus-one]

Hi. We are encountering the same issue:

lvl=warn msg="Engine temporary error" err="derivation failed: temp: failed to fetch blobs: failed to get blob sidecars for L1BlockRef 0x36825190eb3aa9c0574ed38aabbec9327269497dc88c5f3b3050a4341470d04d:21165243: failed to fetch blob sidecars for slot 10376146 block 0x36825190eb3aa9c0574ed38aabbec9327269497dc88c5f3b3050a4341470d04d:21165243: #returned blobs(0) != #requested blobs(5)".

So it’s another slot, but very close: ours 10376146 is and yours is 10375261, both on November 11th 2024. We are currently trying with another snapshot that we got for another of our working nodes.

We were starting from snapshot base-mainnet-reth-1735705102.tar.zst dated from Wed 01 Jan 2025 04:18:22 UTC. Was was the snapshot you tried @sahfd4eiugf ?

[leo-chorus-one]

@sahfd4eiugf using our own snapshot from another node did work for us, so it seems indeed that there is an issue with the upstream snapshots.

[sahfd4eiugf]

I used base-mainnet-reth-1735445925.tar.zst

What L1 beacon node are you using? Your own Lighthouse/Prysm?

[banky]

@sahfd4eiugf it looks like the base snapshot file is outdated even though the timestamp is recent. using the snapshot base-mainnet-reth-1736309898.tar.zst, my node starts syncing from 22287794 (2 months ago). when you start up from the snapshot, what block does your node start syncing from? we might be encountering the same issue