Arbitrum One Nitro not synced correctly with mainnet . Docker image: offchainlabs/nitro-node:v2.3.3-6a1c1a7 #2212
Comments
|
Hi, this looks like an issue with your Prysm node not having the blobs. Please upgrade your Prysm node to the latest release, currently 5.0.2 as it contains fixes related to blob handling: https://github.com/prysmaticlabs/prysm/releases Also take a look at this issue, I think you need to enable the backfill flags: prysmaticlabs/prysm#13783 |
My question is this “failed to get blobs: expected at least 6 blobs for slot 8633650 but only got 0"” |
|
INFO [04-11|01:18:25.247] latest assertion not yet in our node staker=0x0000000000000000000000000000000000000000 assertion=13092 state="{BlockHash:0x1aa5ab7a54c9cb55eac61213665266ea38baca7efba59f73788d22b113c2638b SendRoot:0x55cf415773b9e2c845f63a906c665e03a1ca781bd3f7fe41e3838738c5fba678 Batch:586040 PosInBatch:448}" |
|
@ZYS980327 Are you running your prysm node with |
I used this flag --enable-experimental-backfill=true, and my prysm printed "Backfill batches processed" batchedRemaining=270233 importable=2 imported=2 prefix=backfill, but docker started that Nitro image still reports error INFO [04-11|06:43:31.214] latest assertion not yet in our node staker=0x0000000000000000000000000000000000000000 assertion=13098 state="{BlockHash: 0xd76b38002d04388b9021a3299ecec567ffb8862f8e92daf6ec8beb076869aeba SendRoot:0x38eba7af4bd8e46ca9c9498924b14a2b2e5e51817f817ba2f070ef35d4ed7cf6 Batch:586123 PosInBatch:0} " |
docker run -d --privileged --rm -it -v /usr/local/nitro-snap/:/usr/local/nitro-snap/ -p 0.0.0.0:8567:8567 -p 0.0.0.0:8568:8568 offchainlabs/nitro-node:v2.3.2-064fa11 --parent-chain.connection.url http://10.150.20.11:8545 --chain.id=42161 --parent-chain.blob-client.beacon-url=http://10.150.20.11:3500 --http.api=net,web3,eth,arb,debug --http.corsdomain=* --http.addr=0.0.0.0 --http.vhosts=* --init.url="file:///usr/local/nitro-snap/nitro-pruned.tar" --execution.tx-lookup-limit=0 |
|
@ZYS980327 Is your prysm node syncing ? what are its current logs |
|
INFO [04-11|06:38:29.783] latest assertion not yet in our node staker=0x0000000000000000000000000000000000000000 assertion=13098 state="{BlockHash:0xd76b38002d04388b9021a3299ecec567ffb8862f8e92daf6ec8beb076869aeba SendRoot:0x38eba7af4bd8e46ca9c9498924b14a2b2e5e51817f817ba2f070ef35d4ed7cf6 Batch:586123 PosInBatch:0}"
|
|
@nisdas 我认为硝基应该没问题 |
|
Those are nitro logs, can you show prysm logs ? |
|
@nisdas time="2024-04-11 14:51:31" level=info msg="Backfill batches processed" batchesRemaining=270105 importable=1 imported=1 prefix=backfill time="2024-04-11 14:51:31" level=warning msg="Attestation is too old to broadcast, disscarding it" attestationSlot=8832818 currentSlot=8832858 prefix=p2p |
|
@nisdas Most of it is broadcasting something that was rejected, and there are also some backfill logs and sync logs |
|
@nisdas ./prysm.sh beacon-chain --execution-endpoint=http://localhost:8551 --jwt-secret=/usr/local/prysm/jwt.hex --datadir /data/prysm-data/ --accept-terms-of-use=true --checkpoint-sync-url=https://beaconstate.info --genesis-beacon-api-url=https://beaconstate.info --grpc-gateway-host 10.150.20.11 --grpc-gateway-port 3500 --enable-experimental-backfill=true --accept-terms-of-use --backfill-oldest-slot=0 |
|
@ZYS980327 which version is this ? for prysm |
|
Can you try running |
|
@nisdas I think it should be the latest version 5.0.3, I've restarted it several times |
|
Can you paste more logs for prysm if possible ? A text file is fine, so that we can see why it is still stuck |
|
Ok nevermind, I understand it now. The block you are requesting has blobs which have already been pruned(18 day period) This is because of this: |
|
@nisdas I started two nitros, both of which were createblock at the beginning, and then there were no more |
|
Hey @ZYS980327 when did you start your nitro nodes ? Was this of the time at the fork. A nitro node running for a while should not be requesting expired blobs afaik |
|
@nisdas One was launched yesterday and just now |
|
Was this running with an old snapshot ? |
|
Nitro is requesting already expired blobs , so it is difficult to get this from the beacon p2p network. Possibly why prysm can't provide them |
|
@nisdas Okay, thank you, it may be caused by the Ethereum hard fork, the nitro snapshot is before the fork, and the nitro reception didn't get the data before the slot before requesting the prysm node, so it's stuck here, is that what it means? |
|
@ZYS980327 Yeah that will be an issue, the snapshot needs to be within the last 18 days otherwise nitro will be requesting already expired blob data from prysm. |
|
@nisdas This snapshot should be before the Cancun upgrade, I don't know if the official update snapshot |
|
@ZYS980327 Can you try fetching the snapshot again to see if it helps ? |
|
@nisdas Okay, but it will take some time to download and run the snapshot, and please come to this page in two days, and I will send some information about the new snapshot, thanks |
|
Sure thing, let us know if it works fine after @ZYS980327 |
|
@nisdas I downloaded yesterday the snapshot and i'm having this issue |
|
Can you reopen this @nisdas ? |
|
@nisdas Even though I downloaded a new snapshot, it still doesn't work, and node sync doesn't get blobs |
|
having the same issue |
Describe the bug
The chain is not sync when I run with docker
These are some logs :
INFO [04-01|02:36:54.769] catching up to chain batches localBatches=582,290 target=582,752
WARN [04-01|02:36:54.778] error reading inbox err="failed to get blobs: error fetching blobs in 19501975 l1 block: error calling beacon client in blobSidecars: response returned with status 404 Not Found, want 200 OK. body: {"message":"Block not found: block not found: no block roots at slot 8702476","code":404}"
To Reproduce
Steps to reproduce the behavior:
docker run -v /home/bitcoin/Arbitrum/data:/home/user/.arbitrum --restart=always --name="ArbitrumOneNitro" -d
--shm-size=128G --memory=256G --ulimit nofile=1024000:1024000
--net=mynetwork --ip=10.xxx.1.xx -p 10.xxx.1.1:8547:8547 -p 10.xxx.1.1:8548:8548 offchainlabs/nitro-node:v2.3.3-6a1c1a7 --parent-chain.connection.url http://10.xxx.1.1:8545
--parent-chain.blob-client.beacon-url=http://10.xxx.1.1:3500
--chain.id=42161 --http.api=net,web3,eth --http.corsdomain=* --http.addr=0.0.0.0 --http.vhosts=* --init.url="https://snapshot.arbitrum.foundation/arb1/nitro-pruned.tar"
My L1 works well with latest block. We use Prysm version 5.0.0 for beacon chain , the firewall already set to connect well to both beacon rpc and L1 RPC
The text was updated successfully, but these errors were encountered: