-
Notifications
You must be signed in to change notification settings - Fork 673
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
stacks-node
appears to stall during bootup in develop
#2491
Comments
I think I've figured out why this is -- the relayer isn't waking up the chains coordinator when it receives a confirmed microblock stream, and nothing else. This happens more often than not, and really should be the cause of a wake-up event because the arrival of confirmed microblocks can render already-downloaded Stacks blocks processable. The current code erroneously uses either the arrival of a Stacks block or an unconfirmed microblock, but ignores the arrival of confirmed microblocks. Will send a PR once my testnet node finishes sync'ing. |
PR sent |
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
This impacted the Xenon miner running an
atlas+develop
branch: the node appeared to stall during bootup due to "nack"s received from the miner's bootstrap node. The miner was able to be nudged out of this state using the chain pusher tool, but there's likely a bug somewhere here that needs to be addressed.The text was updated successfully, but these errors were encountered: