-
Notifications
You must be signed in to change notification settings - Fork 429
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
Initialization of the DB fails #2416
Comments
possibly related to this |
attached is the logfile for using nitro-pruned.tar file |
I added a stack dump when the warning is shown:
go-ethereum/core/rawdb/chain_iterator.go , line 146 the resulting stack dump is attached for further investigation |
Could you check if following the strategy described here solves the issue? |
I'm having the same issue, and I'm not using the My node fails to sync and shows:
I tried with a couple of providers and my own L1 node, but no luck. |
I start my node with the following command:
Before starting the node, I copy the following files from image: offchainlabs/nitro-node:v3.0.3-3ecd01e
or you can try this:
or you may redownload the nitro-pruned.tar, for it might be updated already since your last download, the sha256sum has been changed.
and you must pay attention to your l1 consensus client start param --enable-experimental-backfill=true:
Hope it will help~~~ |
Whenever I try to initialize with existing DB (either nitro-pruned.tar or nitro-genesis.tar) I am getting weird errors of EOF type. What is the problem here? (I downloaded the files from your snapshot website) Checksum is fine. Version 3.0.2 , compiled from sources.
Log file attached
![arbitrum-init](https://private-user-images.githubusercontent.com/1125368/341511808-ded8d307-d93d-4dcc-b76b-cce177863276.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MjYxNDg2MTgsIm5iZiI6MTcyNjE0ODMxOCwicGF0aCI6Ii8xMTI1MzY4LzM0MTUxMTgwOC1kZWQ4ZDMwNy1kOTNkLTRkY2MtYjc2Yi1jY2UxNzc4NjMyNzYucG5nP1gtQW16LUFsZ29yaXRobT1BV1M0LUhNQUMtU0hBMjU2JlgtQW16LUNyZWRlbnRpYWw9QUtJQVZDT0RZTFNBNTNQUUs0WkElMkYyMDI0MDkxMiUyRnVzLWVhc3QtMSUyRnMzJTJGYXdzNF9yZXF1ZXN0JlgtQW16LURhdGU9MjAyNDA5MTJUMTMzODM4WiZYLUFtei1FeHBpcmVzPTMwMCZYLUFtei1TaWduYXR1cmU9NWVjODNmZWZkYTkzZDE1ZmJjODliNzAwZmYwM2EzY2QyOTI2ZjA2MDc1NTA3YTU5ZmQ2NDIzNzBiZjhkNWI1NSZYLUFtei1TaWduZWRIZWFkZXJzPWhvc3QmYWN0b3JfaWQ9MCZrZXlfaWQ9MCZyZXBvX2lkPTAifQ.3KzQfLdgqKoo3LC2eAHiphuzWPtPfeyFm9UDKX2s2q0)
nohup.txt
The text was updated successfully, but these errors were encountered: