-
Notifications
You must be signed in to change notification settings - Fork 391
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
Node syncing blocks gets stuck #781
Comments
@shunsukew how easy is that to reproduce? Is it always the same block that fails? |
It is relatively easy, I'd say it's more difficult to sync without getting this so far. |
Can you please give me the exact cli flags you are using to reproduce this? |
This is cli frags using right now.
|
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 7 days. |
BTW, I fixed this issue now. Or better, worked around it. |
Thank you so much! |
Description
Astar/Shiden node gets stuck syncing blocks at particular block numbers when syncing node from scratch (0 block).
This happens at a certain rate (sometimes happens, sometimes not) and stuck block numbers are usually different.
Deleting entire parachain db (
{base path}/chains/astar
or{base path}/chains/shiden
) works as a workaround, but we need to find out why this syncing error happens in the first place.Steps to Reproduce
Expected vs. Actual Behavior
Expected
Node can sync to the latest block without an issue
Actual
Block syncing gets stuck sometimes with below error.
Environment
The text was updated successfully, but these errors were encountered: