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

Unknown signer issue resolved by resetting the database #5665

Closed
obycode opened this issue Jan 7, 2025 · 1 comment · Fixed by #5811
Closed

Unknown signer issue resolved by resetting the database #5665

obycode opened this issue Jan 7, 2025 · 1 comment · Fixed by #5811
Assignees
Milestone

Comments

@obycode
Copy link
Contributor

obycode commented Jan 7, 2025

There is some scenario in which the signer gets into a state where it is unable to keep up with the chain. When exhibiting this behavior, the signer is showing excessive disk access activity. If the database is deleted and the signer is restarted, the problem goes away.

The issue does not appear to be related purely to the size of the database, as we see healthy signers with databases larger than that of those that got stuck behind.

@obycode
Copy link
Contributor Author

obycode commented Feb 5, 2025

Some additional information: this tends to happen on restarts.

@wileyj wileyj added this to the 3.1.0.0.6 milestone Feb 5, 2025
@obycode obycode moved this from Status: 🆕 New to Status: 💻 In Progress in Stacks Core Eng Feb 6, 2025
@obycode obycode assigned hstove and unassigned obycode Feb 6, 2025
@hstove hstove linked a pull request Feb 6, 2025 that will close this issue
@hstove hstove moved this from Status: 💻 In Progress to Status: In Review in Stacks Core Eng Feb 10, 2025
@hstove hstove closed this as completed Feb 10, 2025
@github-project-automation github-project-automation bot moved this from Status: In Review to Status: ✅ Done in Stacks Core Eng Feb 10, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Status: ✅ Done
Development

Successfully merging a pull request may close this issue.

3 participants