Skip to main content

How to solve issues with a corrupt eXist-db ?

Maxime avatar
Written by Maxime
Updated over 3 weeks ago

Question

The eXist-db being used by LiveDocs is corrupt. How can I solve this without losing any data?

Answer

These are the steps you need to perform :

  • Stop the eXist service

  • Stop the Scriptura Frontend service

  • Rename the eXist data folder (C:\eXist-db\webapp\WEB-INF\data) for example to data.backup

  • Start the eXist-db service, a new data folder will be created with a blank database

  • Reset the Admin password for the new eXist-db

    • Log into the eXist-db UI (http://localhost:8080/) with the deault admin user (empty password)

    • Via collections, browse to /db/system/security/exist/accounts/admin.xml

    • Set the password in plain text (<password>example</password>)

  • Start the Scriptura Frontend service

  • Browse to the LiveDocs page

    • the call will block and the Frontend server will fill the cache and the eXist-db again

    • Note : this can take a very long time as all resources need to be synced from the Resource server to eXist-db

Did this answer your question?