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.

Sign up for GitHub

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

Jump to bottom

Backport Exit nodeos if fork_db is corrupted and lib cannot advance #289

Closed
heifner opened this issue May 21, 2022 · 0 comments · Fixed by #311
Closed

Backport Exit nodeos if fork_db is corrupted and lib cannot advance #289

heifner opened this issue May 21, 2022 · 0 comments · Fixed by #311
Assignees
@ndcgundlach
Labels
3.1 Candidates OCI OCI working this issue...

Comments

@heifner
Copy link
Member

heifner commented May 21, 2022

EOSIO/eos#10140 reports that nodeos gets stuck after restart due to a corrupt forkdb. When this happens, log_irreversible keeps throwing the same exception whenever it executes. The solution is to exit nodeos. Log detailed information to help future debugging.

EOSIO/eos#10170
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@ndcgundlach ndcgundlach

Labels
3.1 Candidates OCI OCI working this issue...
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Backported exit on fork_db corrupted eosnetworkfoundation/mandel
2 participants
@heifner @ndcgundlach