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

Bor sync stuck at block 54875999 #1210

Closed
zyx0355 opened this issue Apr 7, 2024 · 5 comments
Closed

Bor sync stuck at block 54875999 #1210

zyx0355 opened this issue Apr 7, 2024 · 5 comments
Assignees
Labels

Comments

@zyx0355
Copy link

zyx0355 commented Apr 7, 2024

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:
a48abc49f5884eb063e768157fc9022

The situation of bor client is as follows:
8055eefe0e3ba8aacbb16dda44a5f4c

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.
95a127267a87a14029763e13a6b9916
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.

@zyx0355
Copy link
Author

zyx0355 commented Apr 9, 2024

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.
@ameerrah

@zyx0355
Copy link
Author

zyx0355 commented Apr 9, 2024

Do you have any other solutions?

@manav2401
Copy link
Contributor

manav2401 commented Apr 18, 2024

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!

Copy link

github-actions bot commented May 3, 2024

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.

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

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants
@manav2401 @zyx0355 and others