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

Starting with wrong option in config.ini creates a corrupte state file #154

Closed
matthewdarwin opened this issue May 17, 2024 · 5 comments
Closed

Comments

@matthewdarwin
Copy link

Start nodeos with producer-threads = 4, which is invalid for this release. Restart nodeos after removing that option, and you end up with this mess:

May 17 13:32:18 spring1-bp203 nodeos[512]: error 2024-05-17T13:32:18.982 nodeos    main.cpp:217                  main                 ] 3060005 bad_database_version_exception: Database is an unknown or unsupported version
May 17 13:32:18 spring1-bp203 nodeos[512]: state database version pre-dates versioning, please restore from a compatible snapshot or replay!
May 17 13:32:18 spring1-bp203 nodeos[512]:     {}
May 17 13:32:18 spring1-bp203 nodeos[512]:     nodeos  controller.cpp:1859 validate_db_version
May 17 13:32:18 spring1-bp203 nodeos[512]: rethrow
May 17 13:32:18 spring1-bp203 nodeos[512]:     {}
May 17 13:32:18 spring1-bp203 nodeos[512]:     nodeos  chain_plugin.cpp:1097 plugin_initialize

Nodeos should not create a corrupt state database.

@heifner
Copy link
Member

heifner commented May 17, 2024

Potentially related to #138

@matthewdarwin
Copy link
Author

Yes, I'm using block-log-retain-blocks = 0

@heifner
Copy link
Member

heifner commented May 17, 2024

Is it possible you had an old data-dir/state/ directory from a different version of nodeos?

@heifner
Copy link
Member

heifner commented May 17, 2024

Did you happen to run with main before using release/1.0-beta1 ?

@bhazzard bhazzard removed the triage label Oct 17, 2024
@bhazzard
Copy link

We haven't been able to reproduce this.

@bhazzard bhazzard closed this as not planned Won't fix, can't repro, duplicate, stale Oct 17, 2024
@github-project-automation github-project-automation bot moved this from Todo to Done in Team Backlog Oct 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Done
Development

No branches or pull requests

4 participants