-
Notifications
You must be signed in to change notification settings - Fork 115
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
joystream-node: Investigate why Syncing hangs #2999
Comments
Could you perhaps share a few additional logs lines before the one above. Do you see any "Invalid justification provided" messages? If you were to restart the node does log output reach line:
And at this point you see high CPU usage? I have experienced this on some validators. If you leave it running for some time it will eventually come back to life. I suspect it is scanning the database for integrity. In the case of this node it took approx 5h..
This behavior is of course a little buggy and we know that the current version of substrate we are using for the testnet is a bit outdated and there have been some bugs related to syncing fixes in newer version. such as paritytech/substrate#8698 |
Checked logs of recently synced endpoints and found two nodes with occasional zero syncs and one that got stuck. From what i saw reasons could be
Never experiencesd that one.
This always goes through without issues and syncing picks up immediately after the restart without the need to check CPU usage. Sorry for the formatting, wish there was a way to log into a separate file with stripped color codes. stuckSync rate suddenly drops to zero, node had to be restarted manually which usualy fixes the issue. The curious question is why despite non-zero peers the node gets into a state where suddenly no more blocks are imported indefinitely.
temporary issues
unrelatedNetwork with single bootnode dies because background compilation delays block production.
|
As you can read in the #validators channel many operators have this issue at least once during a full sync run:
From my memory this did not happen / much less on the Babylon testnet.
┆Issue is synchronized with this Asana task by Unito
The text was updated successfully, but these errors were encountered: