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

OP-reth problem with beacon #366

Open
gamebak opened this issue Dec 11, 2024 · 1 comment
Open

OP-reth problem with beacon #366

gamebak opened this issue Dec 11, 2024 · 1 comment

Comments

@gamebak
Copy link

gamebak commented Dec 11, 2024

Hello,
I'm using op-reth, I downloaded the archive you provided on the website and I've waited for a few days to sync but to no luck. It went from 39k minutes to 34k in the past few days, but I noticed that I was stuck now.

Inspecting the docker I noticed this:

[+] Running 2/0
 ✔ Container node-execution-1  Created                                                                                                                                                     0.0s 
 ✔ Container node-node-1       Created                                                                                                                                                     0.0s 
Attaching to execution-1, node-1
node-1       | waiting for execution client to be ready
execution-1  | ts=2024-12-11T00:26:45.442549286Z level=error target=engine::jwt-validator message="Invalid JWT: Authorization header is missing or invalid"
node-1       | t=2024-12-11T00:26:45+0000 lvl=warn msg="Unknown env var" prefix=OP_NODE env_var="OP_NODE_L2_ENGINE_AUTH_RAW=688f5d737bad920bdfb2fc2f488d6b6209eebda1dae949a8de91398d932c517a"
node-1       | t=2024-12-11T00:26:45+0000 lvl=info msg="Rollup Config" l2_chain_id=8453 l2_network=Base l1_chain_id=1 l1_network=mainnet l2_start_time=1686789347 l2_block_hash=0xf712aa9241cc24369b143cf6dce85f0902a9731e70d66818a3a5845b296c73dd l2_block_number=0 l1_block_hash=0x5c13d307623a926cd31415036c8b7fa14572f9dac64528e857a470511fc30771 l1_block_number=17481768 regolith_time="@ genesis" canyon_time="@ 1704992401 ~ Thu Jan 11 17:00:01 UTC 2024" delta_time="@ 1708560000 ~ Thu Feb 22 00:00:00 UTC 2024" ecotone_time="@ 1710374401 ~ Thu Mar 14 00:00:01 UTC 2024" fjord_time="@ 1720627201 ~ Wed Jul 10 16:00:01 UTC 2024" granite_time="@ 1726070401 ~ Wed Sep 11 16:00:01 UTC 2024" holocene_time="(not configured)" interop_time="(not configured)" alt_da=false
node-1       | t=2024-12-11T00:26:45+0000 lvl=info msg="Initializing rollup node" version=v1.10.0-910c9ade-1732025300
node-1       | t=2024-12-11T00:27:01+0000 lvl=error msg="Error initializing the rollup node" err="failed to check L1 Beacon API version: operation failed permanently after 5 attempts: failed request with status 400: {\"jsonrpc\":\"2.0\",\"id\":null,\"error\":{\"code\":-32600,\"message\":\"Invalid json request\"}}"
node-1       | t=2024-12-11T00:27:01+0000 lvl=crit msg="Application failed" message="failed to setup: unable to create the rollup node: failed to check L1 Beacon API version: operation failed permanently after 5 attempts: failed request with status 400: {\"jsonrpc\":\"2.0\",\"id\":null,\"error\":{\"code\":-32600,\"message\":\"Invalid json request\"}}"
node-1 exited with code 1

I have changed the beacon trying 3 other providers but to no luck, I get the same error.
Is there a solution for something like this or I'm just doomed to not get a node up and running?

@nautel2000
Copy link

good

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

2 participants