-
Notifications
You must be signed in to change notification settings - Fork 524
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
Acala mainnet stuck on finalized block #5446885 #2774
Comments
I see a few message like Example:
|
Does a restart help? |
Do you still have the database around? Restarting with debug or even trace logs might reveal what is going on.
Trace for everything is likely to spammy, but only for sync should work:
|
I will enable that level of logging if I see this or any other issues. Thanks |
I didn't see this issue again. Closing for now. |
Describe the bug
A new acala mainnet node, which has been syncing from genesis, is stuck on finalized block #5446885
Expected Behavior
Sync from genesis till the latest block without issues.
Current Behavior
Suck on finalized block #5446885.
Steps to Reproduce
Additional context
The text was updated successfully, but these errors were encountered: