-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
Node v1.3.4 not syncing BAD BLOCK #2049
Comments
My docker-compose service:
My config.toml:
|
My eth.syncing:
My geth.net
|
It completely died
Help plz |
Got the same behavior on 1.3.4, reverting to 1.3.3 it moves again |
@roflganker could you help change |
Then your nodes will be broken, can not sync anymore, need to reset your environment. |
yea, but you will have problem next time, if you upgrade to v1.3.4+ |
You may need to download the fastnode snapshot and sync again: https://github.com/48Club/bsc-snapshots |
There is same issue with
after restart there is another error:
|
@gituser I think that's a different issue. If you're still facing the problem, please open a new issue |
@gituser you need to add flags |
@roflganker will
@roflganker likely, your node is in this case, need to recover your node from scratch.
I will close the issue now. |
System information
Geth version:
1.3.4
OS & Version: Linux 5.10.0-18-amd64 #1 SMP Debian 5.10.140-1 (2022-09-02) x86_64 GNU/Linux
Commit hash : -
Expected behaviour
Node syncing correctly, serving
eth_
RPCActual behaviour
Doing absolutely nothing, not syncing, serving stale data
Steps to reproduce the behaviour
Run bnbchain/bsc v1.3.4 inside docker compose
Backtrace
Additional info
The node was working correctly on 1.2.x for several months. Recently I migrated to 1.3.4 and... It was working correcly for a short time (several hours), and stuck at block 34141848.
What did I try in order to fix this:
The text was updated successfully, but these errors were encountered: