-
Notifications
You must be signed in to change notification settings - Fork 489
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 upgrade version 1.4.0 is out of sync #1334
Comments
we found this issue too in amoy testnet |
Is there any solution? |
Hi, Iam a node operator, am also facing the same issue in one of my polygon node. have you been able to a find a solution for this? Thanks. ep 19 00:50:15 polygon-sentry-01 bor[706971]: INFO [09-19|00:50:15.856] Commit Interrupt. Pre-committing the current block block=61,984,255 |
We're also seeing exactly the same behavior as described, we've just upgraded to v1.4.1 and that hasn't made any difference. |
Yes, I updated to v1.4.1 version but same errors. it worked fine for 30 minutes to an hour, but then I started encountering the error mentioned above. |
I upgraded two nodes in total, and each node had the same problem. The first node automatically recovered after running for a few days, but the other node still had the same problem |
our node have been normal after a few hours, and in that time i have tried to remove the node key info, but i don't know if it makes the node normally. |
Hi, Can you please follow the steps mentioned below. it will work. i tried the same way.
After making the changes, please restart the node and wait for sometime for the node to catch. Make sure you are on latest bor version v1.4.1. like below [p2p] Thanks. |
I do this and it's still stuck After one night, the block automatically caught up |
Hello, I was having exact same issues when trying to sync from snapshot. Thought there might be an issue with the snapshot, pruned all bor data. Delete bor. Reinstalled bor v1.4.1. Started syncing from the scratch. Nothing at all. Cannot connect to a single peer. Getting following error
|
@yuanwj210 please elaborate: do you mean that you had the same syncing issue as described, and that eventually it went away by itself? |
faces the same issue as well with Bor nodes on version v1.4.1. It seems to resolved after some time but keeps happening making the node go in and out of sync. Any fixes / cause of the issue yet? |
facing exactly the same issue. |
+1 |
the same issue |
the same issue bot 1.4.1 |
This seems to be because of the lack of peers. What is the peer count in the node? For Mainnet, can you try using this config option to get connected to more peers?
|
Thank you @ssandeep. |
It works like a charm. |
After adding DNS, I still can't keep up, and I get stuck every time I keep up |
@yuanwj210 - did you restart your node after updating the config file? |
How do I check how many peers are connected? Every time the node catches up with the latest block, it reports the following error, which can not be repaired? It is very inexplicable |
Hey @yuanwj210 you can find out the number of peers using |
Bor Version: v1.4.0
Description
The bor log keeps outputting Whitelisting milestone deferred. When bor is restarted, it will catch up with the latest block and then get stuck at Whitelisting milestone deferred.
Logs
The text was updated successfully, but these errors were encountered: