-
Notifications
You must be signed in to change notification settings - Fork 45
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
BSC Chapel Archive stuck with [2/9 Headers] No block headers to write on different blocks #603
Comments
+1 |
Could you please show the logs from when the node started? |
Full log from the node start, with |
Try it and show me the logs.
|
It tests fine on my local. I'm not sure why it can't find any peers. Seems no error. |
full logs after running this attached: logs-bsc-chapel-02.txt |
@blxdyx do you mind sharing the flags/parameters on your test node? Also, do you happen to have any static peers we could use? |
Actually we have hard code the static node. |
Bsc have a tool to test, could you check with this in your device:
|
System information
Erigon version: erigon version 1.3.0-beta1-95aaa15alogs
OS & Version: Linux Kubernetes
Erigon Command (with flags/config)
Consensus Layer
Consensus Layer Command (with flags/config)
N/A
Chain/Network
BSC Chapel
Expected behaviour
Erigon should sync properly and write block headers.
Actual behaviour
Facing No block headers issue on different blocks
Steps to reproduce the behaviour
Steps to troubleshoot
Sometimes this helped, but eventually, the node stopped syncing at stage 2 with different block
Backtrace
The text was updated successfully, but these errors were encountered: