-
Notifications
You must be signed in to change notification settings - Fork 111
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
Bedrock Init Error #75
Comments
Receiving same error and l2geth container is stuck after "verifier loop" ++ config bedrock/mainnet/ready
|
same issue |
@zainirfan13 @germashevanton You may want to use the following docker image until the issue gets resolved:
I have used the above docker config and the node is up now. |
How to setup .env for bedrock mainnet? |
Just rename the
You can leave the other options to its default value. It takes around 2 hours (depending on your Internet connection speed) to complete the node bootstrap. |
the same issue too, It feels like this simple project is getting more and more complicated |
Will this serve as a optimism node or I will have to run the other containers of simple-optimism-node ? with it ? Thanks a lot |
INFO [06-09|14:06:38.733] Generating state snapshot root=bfe2b0..c2d21c in=d8fa7c..bcf59f at=c33c46..e17f8a accounts=108,313 slots=7,429,828 storage=593.81MiB dangling=0 elapsed=2m40.002s eta=28.775s These are the logs i see when i ran the docker of https://github.com/CryptoManufaktur-io/optimism-docker/tree/main @raviprrasadcg |
@zainirfan13 The above output is expected. It takes lot of time to complete the process. I was in touch with the Optimism user group in the Discord and they suggested me to turn off the snapshot process temporarily to speed up the process:
So, I have added the following in the env:
and restarted the containers. |
@raviprrasadcg after following you instruction
|
You need to wait for sometime. It'll start downloading the chain segments. |
For those who are still struggling to run the mainnet node, I managed to run the node by pulling the latest code on branch I followed the README.md and did the required changes. One thing more I did was add "restart: unless-stopped" in the docker-compose.yml file for "bedrock-init:" because it kept on loosing connection when download bedrock.tar snapshot which was about 400 GB. Luckily it resumed everytime the docker of bedrock init restarted, I was able to download it in 3 to 4 hours. The JSONRPC port is 9993 and ws port is 9994 by default. |
I do it,but node has not been synced for 12 hours. |
@luoxiandong The above process took me around 2 days and 15 hours to complete. |
tks! |
Can you please help with detailed steps on how you used the CryptoNamufactur repo to get the node up? Thanks in advance |
Hi, my fork has fixed this issue and uses an official snapshot. Check out https://github.com/Chomtana/simple-optimism-node/tree/main/scripts Pull request #97 |
Closed by #97 |
Receiving the following error while starting the Docker containers:
bedrock-init_1 | ++ echo ''
bedrock-init_1 | + BEDROCK_FLAG=
bedrock-init_1 | + '[' '' == true ']'
bedrock-init_1 | + echo 'Bedrock flag not set, waiting...'
bedrock-init_1 | + sleep 60
bedrock-init_1 | Bedrock flag not set, waiting...
The text was updated successfully, but these errors were encountered: