-
Notifications
You must be signed in to change notification settings - Fork 993
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 stuck on a block #1639
Comments
I wonder if there is a deadlock involved there like @garyyu identified yesterday. |
I highly suspect this is an old build. @quentinlesceller Could you share me the whole log file? just paste a link here or send from Gitter 😄 |
Okay it just happened again and here is the full log. it's a 154 mb file. |
Indeed this could be another dead lock case remaining.
|
Let me know if you want more logs. It is happening to me fairly regularly (every 16 hours or so) on a non mining node. |
This case is quite difficult, more logs will not help anymore. That fixed dead lock case is relatively easy because it can 100% reproduce, but this one not easy to reproduce, I observe on 2 nodes for whole day and no happening. I'm working on a tool now, but still need some time, and once it's ready, I need your help to test on your this node. |
Sure. |
Please check if this is fixed by #1657 I was stuck at height 95045 before and just got synced with latest build... |
Unfortunately still stuck 60 blocks behind on archival node. |
Hopefully fixed, or at least a similar issue will be different enough to warrant its own issue. |
Non mining node stuck on block 120,766. Running 4d2cbe6.
Attaching the grin-server.log: grin-crash.log
After that only the monitor peers thread appears to be running.
The text was updated successfully, but these errors were encountered: