Skip to content
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

Closed
kantai opened this issue Mar 2, 2021 · 4 comments
Closed

stacks-node appears to stall during bootup in develop #2491

kantai opened this issue Mar 2, 2021 · 4 comments
Assignees
Labels

Comments

@kantai
Copy link
Member

kantai commented Mar 2, 2021

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.

@jcnelson jcnelson self-assigned this Mar 3, 2021
@jcnelson
Copy link
Member

jcnelson commented Mar 10, 2021

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.

@jcnelson
Copy link
Member

Yup, that was the problem. Confirmed that my testnet node continuously streams blocks and microblocks with the fix.

blocks-and-microblocks

jcnelson added a commit that referenced this issue Mar 10, 2021
@jcnelson
Copy link
Member

PR sent

This was referenced Mar 10, 2021
jcnelson added a commit that referenced this issue Mar 18, 2021
@kantai kantai closed this as completed in fa1178e Mar 18, 2021
@blockstack-devops
Copy link
Contributor

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.

@stacks-network stacks-network locked as resolved and limited conversation to collaborators Nov 16, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants