Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Cannot sync from latest snapshot #2545

Open
insider89 opened this issue Aug 1, 2024 · 0 comments
Open

Cannot sync from latest snapshot #2545

insider89 opened this issue Aug 1, 2024 · 0 comments

Comments

@insider89
Copy link

Describe the bug
Try to sync the Arbitrum nitro from with the command:

 - --init.url=https://snapshot.arbitrum.foundation/sepolia/nitro-pruned.tar
        - --parent-chain.connection.url=http://sepolia-1-erigon-rpc.sepolia.svc.cluster.local:8545
        - --parent-chain.blob-client.beacon-url=http://sepolia-1-erigon-rpc.sepolia.svc.cluster.local:5052
        - --chain.id=421614
        - --http.api=net,web3,eth,debug,arb
        - --http.corsdomain=*
        - --http.addr=0.0.0.0
        - --http.vhosts=*
        - --ws.addr=0.0.0.0
        - --ws.api=net,web3,eth,debug,arb
        - --ws.origins=*
        - --init.download-path=/home/user/.arbitrum/nitro-pruned.tar

Got an error:

err="failed to get blobs: error fetching blobs in 6227045 l1 block: expected at least 3 blobs for slot 5343747 but only got 0"

Running on the latest image: docker.io/offchainlabs/nitro-node:v3.1.0-7d1d84c

To Reproduce
Steps to reproduce the behavior:
Running the Arbitrum nitro with the configuration above.

Expected behavior
Node sync

Additional context
Trying to use beacon node from chainstack, but got the same result.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant