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

FAQ: Solution For Common Issues #41

Open
calmbeing opened this issue Apr 26, 2023 · 10 comments
Open

FAQ: Solution For Common Issues #41

calmbeing opened this issue Apr 26, 2023 · 10 comments

Comments

@calmbeing
Copy link

calmbeing commented Apr 26, 2023

Rationale

For some common issue encountered, such as the follows:

  • No block header/body write.
  • Body download speed is slow
  • Database is too large for current system

Solution

Please try to specify these flags in the command line for starting node:

  • --p2p.protocol=68(bsc remove 66&67 after v1.4.x)
  • --db.pagesize=16k

Also, for some cases that now work especially in reboot scenario, it'll help to unwind some blocks:

  1. Stop erigon node
  2. run make integration
  3. run ./build/bin/integration stage_exec --datadir ./data/ --chain bsc --unwind 10
  4. Start erigon node

FAQs

Q1: mdbx_env_open: MDBX_TOO_LARGE? refer: #38

Q2: Any suggested start up command line?

Here is our command line to start on BSC Mainnet, you can use on your need.

Note: we have plenty SSD disk storage to support archive node, which is 14TB, so we set --db.pagesize=16k for fast DB performance. You may configure it according to your device setting.

./erigon --bodies.cache=214748364800 --batchSize=4096M --txpool.disable --metrics.addr=0.0.0.0 --log.console.verbosity=eror --log.dir.verbosity=dbug --http --ws --http.api=web3,net,eth,debug,trace,txpool,admin --http.addr=0.0.0.0 --db.pagesize=16k --datadir ${workspace}/data --private.api.addr=localhost:9090 --chain=bsc --metrics 

Q3: OOM Crash?

Try not specify the body cache and batch size: --bodies.cache=214748364800 --batchSize=4096M.
These 2 flags will bring heavy to RAM caches. Similar issue: #39

Q4: For The Lagging Sync Issue, pls refer: #51

Q5: Log with "DumpBlocks: DumpHeaders: header missed in db:"

It won't affect sync. Two way to fix it.

  1. Remove datadir/downloader and datadir/snapshots/prohibit_new_downloads.lock
  2. integration stage_headers —reset

Q6: Wrong totalDifficult in eth_getBlockByNumber.

Stop erigon and ./integration stage_headers --reset --chain=bsc --datadir=yourdata will fix.

@blxdyx
Copy link
Collaborator

blxdyx commented Apr 26, 2023

No block header write. you could try this:

integration state_stages --unwind=20 --chain=bsc --datadir=/path
integration stage_headers --unwind=20 --chain=bsc --datadir=/path

@blxdyx blxdyx unpinned this issue Apr 27, 2023
@Denis-score
Copy link

Since yesterday, it's still complicated to be live sync with erigon. I always have 50-100 blocks of delay. Anyone have an idea ?

@harveyff
Copy link

Since yesterday, it's still complicated to be live sync with erigon. I always have 50-100 blocks of delay. Anyone have an idea ?

One week ago, I was also behind by dozens of blocks. Since one week ago, I have been behind by 2000 blocks, and it is getting slower and slower. Without any ideas, it can no longer provide services for the production environment.

@setunapo setunapo changed the title Solution for some common problem and issue [FAQ] Solution for some common problem and issue May 5, 2023
@setunapo setunapo changed the title [FAQ] Solution for some common problem and issue FAQ: Solution for some common problem and issue May 5, 2023
@setunapo setunapo pinned this issue May 5, 2023
@setunapo setunapo changed the title FAQ: Solution for some common problem and issue FAQ: Solution For Common Issues May 5, 2023
@github-actions
Copy link

This issue is stale because it has been open for 40 days with no activity. Remove stale label or comment, or this will be closed in 7 days.

@github-actions github-actions bot added the Stale label Aug 21, 2023
@github-actions
Copy link

This issue was closed because it has been stalled for 7 days with no activity.

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Aug 28, 2023
@blxdyx blxdyx reopened this Aug 28, 2023
@github-actions github-actions bot removed the Stale label Aug 29, 2023
@github-actions
Copy link

This issue is stale because it has been open for 40 days with no activity. Remove stale label or comment, or this will be closed in 7 days.

@github-actions github-actions bot added the Stale label Oct 22, 2023
@github-actions
Copy link

This issue was closed because it has been stalled for 7 days with no activity.

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Oct 30, 2023
@blxdyx blxdyx reopened this Jan 17, 2024
@github-actions github-actions bot removed the Stale label Jan 18, 2024
@du5
Copy link

du5 commented Jan 22, 2024

214748364800 bytes = 200 gigabytes

The default value should be 256 megabyte, I think this parameter can be set to about 4G. There is no comparison with physical memory in the code. 200G seems to easily exceed the user's memory size.

Copy link

github-actions bot commented Mar 3, 2024

This issue is stale because it has been open for 40 days with no activity. Remove stale label or comment, or this will be closed in 7 days.

@github-actions github-actions bot added the Stale label Mar 3, 2024
Copy link

This issue was closed because it has been stalled for 7 days with no activity.

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

5 participants