-
Notifications
You must be signed in to change notification settings - Fork 2.6k
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] snarkOS sometimes stops syncing #2916
Comments
This looks like a bug I fixed here: https://github.com/AleoHQ/snarkOS/pull/2903. Can you try with that branch? |
oops, didn't notice the incomplete title. I'm not even sure if I can reproduce this issue before that pr is merged as it only happens randomly (and really sporadically), and because of #2917 I'm reluctant to do further modifications to my running node now as it directly affects my explorer. That said, probably the stray |
I understand. That said, the PR should be up-to-date with testnet3 and only adds 1 relatively simple commit. |
related syncing problem #2910 |
Is this still relevant? Should be related to https://github.com/AleoHQ/snarkOS/issues/2978 |
🐛 Bug Report
My node sometimes will stop syncing without any warning. Here's the log:
Unfortunately I've just removed some additional debug logs when investigating another potential issue so I'm not sure why the node stopped to process the block responses (assuming I do have received responses here).
Note that my node is connected to 80+ other nodes and if you look carefully the block sync interval is also adjusted, so officially it's out of specs right now (cli doesn't have options for specifying max peers).
Also sadly I can't use verbosity 5 and run the node until it happens again, it's way too noisy as I have too many connected nodes here, and reproducing this might take weeks.
BTW, when I was investigating "another potential issue" I found that the sync module sometimes would leave some stray block responses in the
responses
map inBlockSync
struct in unknown circumstances. Not sure if it's related.Steps to Reproduce
Not exactly sure.
Expected Behavior
The node should sync.
Your Environment
The text was updated successfully, but these errors were encountered: