-
Notifications
You must be signed in to change notification settings - Fork 474
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
Bor sync stuck at block 54875999 #1210
Comments
Hello, no error occurred on my side, but the bor client just kept looking for peer nodes, but peercount=0, and could never find a good peer node, resulting in data being unable to be synchronized. |
Do you have any other solutions? |
Hi @zyx0355, I believe you're running on a very old bor version. Could you please upgrade it and let us know how it goes? As there was a HF few weeks back, it might be the reason for bor stuck at some block. Thanks! |
This issue is stale because it has been open 14 days with no activity. Remove stale label or comment or this will be closed in 14 days. |
This issue was closed because it has been stalled for 28 days with no activity. |
Hello, my current bor client is also stuck in a certain block. The block is 54875999. I rolled back the bor client blocks to 500, 2000, and 15000 and still the problem has not been solved.
My client situation is as follows:
bor version 1.1.0 and heimdall v1.0.3
The situation of heimdall is as follows:
The situation of bor client is as follows:
When the bor client just started, it kept looking for peer nodes. After that, the following situation would always occur, and the data could not be synchronized forward.
I tried rolling back the bor client:
$ bor attach ~/.bor/data/bor.ipc`
debug.setHead("0x3451cc7")
I tried going back 500, 1000, and 15000 blocks, but the final data block was stuck at block 54875999, and the data could not be synchronized forward.
The text was updated successfully, but these errors were encountered: