-
Notifications
You must be signed in to change notification settings - Fork 718
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
[BUG] - Mainnet Node stops syncing altogether after encountering an invalid block #4236
Comments
It is getting more frequent
|
This looks to be the same issue as #4228, which is fixed by IntersectMBO/cardano-ledger#2936 |
Is your node configured to talk to many peers or just one? My initial suspicion about a node appearing "stuck" is that it now has no peers to talk to, because it temporarily banned the one it received a bad block from. Restarting the node would have the effect that it forgets the temporary bans. If it's only configured to talk to one other peer then after banning that one peer, it'd have none. Public relays on mainnain should of course be configured to talk to many other public relays. |
@mesudip based on the above feedback, can we close this issue? |
I've not yet encountered this issue after updating the node to new version. I am closing this. |
External
Our mainnet node stopped syncing after this same error message twice
When it first appeared we were on node version
1.31.0
. Then we upgraded to1.34.1
and the issue was seen again after 4 days.Current Solution
Restarting the node solves the sync issue and it quickly catch ups to the latest tip.
Node Log
The text was updated successfully, but these errors were encountered: