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

Can't fetch the block tip using op-reth for base mainnet #9053

Closed
Quertyy opened this issue Jun 24, 2024 · 1 comment
Closed

Can't fetch the block tip using op-reth for base mainnet #9053

Quertyy opened this issue Jun 24, 2024 · 1 comment
Labels
A-op-reth Related to Optimism and op-reth C-bug An unexpected or incorrect behavior S-needs-investigation This issue requires detective work to figure out what's going wrong

Comments

@Quertyy
Copy link
Contributor

Quertyy commented Jun 24, 2024

Describe the bug

I'm trying to sync a base mainnet archive node using op-reth. I first used a normal sync with op-node, after 5 days I got about 5M blocks synced, but the sync speed was really slowing down. So I searched in the reth telegram channel to see if anyone had been able to synchronize faster, and found that it was possible to use the --debug.tip flag. The users specified that it was necessary to test the hash of several blocks before being able to synchronize, but for my part none of them worked, even after waiting a whole night. The sync is stuck on: Fetching tip block from the network.

Steps to reproduce

  1. Get access to an reth mainnet archive node
  2. Run op-reth:
    op-reth node --chain base --rollup.sequencer-http https://sequencer.base.org --http --ws --http.api eth,debug,trace --ws.api eth,debug,trace --authrpc.port 9551 --authrpc.jwtsecret /data/base/secrets/jwt.hex --port 30303 --http.port 8547 --ws.port 8548 --datadir /data/base/execution --metrics 0.0.0.0:9001 --http.addr 0.0.0.0 --ws.addr 0.0.0.0 --enable-discv5-discovery --discovery.v5.port 30304 --debug.tip "0xf976207a3f98e8ae6752e632b4f2b04f564862fc0932574b9c01b26888c41f5f"

Node logs

2024-06-24T12:40:14.859732Z  INFO Initialized tracing, debug log directory: /home/ethereum/.cache/reth/logs/base
2024-06-24T12:40:14.861169Z  INFO Starting reth version="1.0.0-rc.2-dev (7bfc604a1)"
2024-06-24T12:40:14.861859Z  INFO Opening database path="/data/base/execution/db"
2024-06-24T12:40:14.961487Z  INFO Configuration loaded path="/data/base/execution/reth.toml"
2024-06-24T12:40:14.971617Z  INFO Verifying storage consistency.
2024-06-24T12:40:15.107919Z  INFO Unwinding static file segment. segment=Transactions from=5328841 to=0
2024-06-24T12:40:15.175601Z  INFO Unwinding static file segment. segment=Receipts from=5328841 to=0
2024-06-24T12:40:15.175633Z  INFO Database opened
2024-06-24T12:40:15.175640Z  INFO Starting metrics endpoint addr=0.0.0.0:9001
2024-06-24T12:40:15.175783Z  INFO
Pre-merge hard forks (block based):
- Frontier                         @0
- Homestead                        @0
- Tangerine                        @0
- SpuriousDragon                   @0
- Byzantium                        @0
- Constantinople                   @0
- Petersburg                       @0
- Istanbul                         @0
- MuirGlacier                      @0
- Berlin                           @0
- London                           @0
- ArrowGlacier                     @0
- GrayGlacier                      @0
- Bedrock                          @0
Merge hard forks:
- Paris                            @0 (network is known to be merged)
Post-merge hard forks (timestamp based):
- Regolith                         @0
- Shanghai                         @1704992401
- Canyon                           @1704992401
- Cancun                           @1710374401
- Ecotone                          @1710374401
- Fjord                            @1720627201
2024-06-24T12:40:15.263877Z  INFO Transaction pool initialized
2024-06-24T12:40:15.263996Z  INFO Loading saved peers file=/data/base/execution/known-peers.json
2024-06-24T12:40:15.265165Z  INFO Fetching tip block from the network. tip=Hash(0xf976207a3f98e8ae6752e632b4f2b04f564862fc0932574b9c01b26888c41f5f)


### Platform(s)

Linux (x86)

### What version/commit are you on?

reth Version: 1.0.0-rc.2-dev
Commit SHA: 7bfc604
Build Timestamp: 2024-06-19T04:20:46.851673219Z
Build Features: jemalloc,optimism
Build Profile: maxperf


### What database version are you on?

Current database version: 2
Local database is uninitialized


### Which chain / network are you on?

Base mainnet

### What type of node are you running?

Archive (default)

### What prune config do you use, if any?

_No response_

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

RUSTFLAGS="-C target-cpu=native" make install-op

### Code of Conduct

- [X] I agree to follow the Code of Conduct
@Quertyy Quertyy added C-bug An unexpected or incorrect behavior S-needs-triage This issue needs to be labelled labels Jun 24, 2024
@shekhirin shekhirin added A-op-reth Related to Optimism and op-reth S-needs-investigation This issue requires detective work to figure out what's going wrong and removed S-needs-triage This issue needs to be labelled labels Jun 24, 2024
@Quertyy Quertyy changed the title Can't find the block tip using op-reth for base mainnet Can't fetch the block tip using op-reth for base mainnet Jun 24, 2024
@Rjected
Copy link
Member

Rjected commented Jun 24, 2024

Should be fixed in #9058, which will be released with 1.0, so closing this!

@Rjected Rjected closed this as completed Jun 24, 2024
@github-project-automation github-project-automation bot moved this from Todo to Done in Reth Tracker Jun 24, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-op-reth Related to Optimism and op-reth C-bug An unexpected or incorrect behavior S-needs-investigation This issue requires detective work to figure out what's going wrong
Projects
Archived in project
Development

No branches or pull requests

3 participants