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

Base Reth node is not syncing #7950

Closed
1 task done
tofanovskiy opened this issue Apr 28, 2024 · 8 comments
Closed
1 task done

Base Reth node is not syncing #7950

tofanovskiy opened this issue Apr 28, 2024 · 8 comments
Labels
A-networking Related to networking in general A-op-reth Related to Optimism and op-reth A-staged-sync Related to staged sync (pipelines and stages) C-bug An unexpected or incorrect behavior S-stale This issue/PR is stale and will close with no further activity

Comments

@tofanovskiy
Copy link

tofanovskiy commented Apr 28, 2024

Describe the bug

I am trying to launch Base mainnet node following your guide.

After a week of node running - it synced only 12000 blocks. What am I doing wrong?

Logs:

024-04-28T18:36:59.022057Z DEBUG jsonrpsee-server: Accepting new connection 1/500
2024-04-28T18:36:59.022410Z DEBUG jsonrpsee-server: Accepting new connection 1/500
2024-04-28T18:36:59.542218Z DEBUG jsonrpsee-server: Accepting new connection 1/500
2024-04-28T18:36:59.543343Z  INFO blockchain_tree: Block is already canonical, ignoring. block_hash=0x871f0d50446b04f880b
eb7b883afaabd9ed1e2b42acf3febad0fb31ecfb55669
2024-04-28T18:36:59.543530Z DEBUG consensus::engine: [Optimism] Allowing beacon reorg to old head fcu_head_num=13495 curr
ent_head_num=13495
2024-04-28T18:36:59.543797Z  INFO reth_node_events::node: Canonical chain committed number=13495 hash=0x871f0d50446b04f880beb7b883afaabd9ed1e2b42acf3febad0fb31ecfb55669 elapsed=791.717µs
2024-04-28T18:36:59.544126Z DEBUG consensus::engine::hooks: Next hook is not ready hook="Prune"
2024-04-28T18:37:12.267854Z  INFO reth::cli: Status connected_peers=0 freelist=364 latest_block=13495

Other question - is it possible to download somewhere snapshot for archive and use it with Reth base version?

My launch commands:

nohup op-reth node \
    --chain base \
    --rollup.sequencer-http https://sequencer.base.org \
    --http \
    --ws \
    --authrpc.port 9551 \
    --authrpc.jwtsecret /company/jwt.hex \
    --datadir /company/data &

nohup op-node \
    --network="base-mainnet" \
    --l1=https://eth-l1.company.io \
    --l1.beacon=https://lighthouse.company.io \
    --l2=http://localhost:9551 \
    --l2.jwt-secret=/company/jwt.hex \
    --rpc.addr=0.0.0.0 \
    --rpc.port=7000 \
    --log.level=debug > nohup2.out &

Using latest CLI clients. Anything I can do to make it sync faster?
Thanks a lot

Steps to reproduce

following main guide

Node logs

No response

Platform(s)

Linux (x86)

What version/commit are you on?

reth Version: 0.2.0-beta.5-dev
Commit SHA: 250da4e
Build Timestamp: 2024-04-22T13:19:08.271330192Z
Build Features: jemalloc,optimism
Build Profile: release

What database version are you on?

Current database version: 2
Local database is uninitialized

Which chain / network are you on?

mainnet

What type of node are you running?

Archive (default)

What prune config do you use, if any?

If you've built Reth from source, provide the full command you used

No response

Code of Conduct

  • I agree to follow the Code of Conduct
@tofanovskiy tofanovskiy added C-bug An unexpected or incorrect behavior S-needs-triage This issue needs to be labelled labels Apr 28, 2024
@emhane emhane added A-op-reth Related to Optimism and op-reth and removed S-needs-triage This issue needs to be labelled labels May 8, 2024
@emhane
Copy link
Member

emhane commented May 8, 2024

you could try #7500 (comment) @tofanovskiy

@emhane
Copy link
Member

emhane commented May 8, 2024

we don't have the op-reth base datadir available for download atm @gakonst @clabby

@emhane emhane added the A-staged-sync Related to staged sync (pipelines and stages) label May 8, 2024
@emhane emhane added the A-networking Related to networking in general label May 17, 2024
@emhane
Copy link
Member

emhane commented May 17, 2024

second look at this, I see you are missing the --enable-discv5-discovery flag from the op-reth command. this is enabled by default for op stack in upcoming release #8065.

@Rjected
Copy link
Member

Rjected commented May 22, 2024

@tofanovskiy is this still a problem / have you tried the above flag?

@gakonst
Copy link
Member

gakonst commented May 29, 2024

bump @tofanovskiy !

@emhane
Copy link
Member

emhane commented Jun 1, 2024

from op-node the --syncmode=execution-layer flag is missing @tofanovskiy

Copy link
Contributor

This issue is stale because it has been open for 21 days with no activity.

@github-actions github-actions bot added the S-stale This issue/PR is stale and will close with no further activity label Jun 23, 2024
Copy link
Contributor

github-actions bot commented Jul 8, 2024

This issue was closed because it has been inactive for 7 days since being marked as stale.

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Jul 8, 2024
@github-project-automation github-project-automation bot moved this from Todo to Done in Reth Tracker Jul 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-networking Related to networking in general A-op-reth Related to Optimism and op-reth A-staged-sync Related to staged sync (pipelines and stages) C-bug An unexpected or incorrect behavior S-stale This issue/PR is stale and will close with no further activity
Projects
Archived in project
Development

No branches or pull requests

4 participants