If Parity doesn't close properly, I get the following error and have to resynch the entire chain again...

thread '' panicked at 'Error opening state db: Failed to create rocksdb directory: Error { repr: Os { code: 17, message: "File exists" } }', util/src/journaldb/archivedb.rs:49 note: Run with RUST_BACKTRACE=1 for a backtrace.

Has anyone got a better solution to recover in these instances?

  • I had a similar issue with failed database version migration. I never found out a solution other than removing the whole corrupted DB.
    – q9f
    Oct 7, 2016 at 19:39


Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Browse other questions tagged or ask your own question.