Phone Lines icon GFI Support

Articles in this section

See more

Fixing Corrupt .journal.db With SQLite Error

Author: Vladyslav Velychko Updated

Overview

The following error string appears in the Error Logs:

[11/May/2012 10:13:33] SQLiteDbWriteCache.h: [Mail Path]/[Domain]/[Username]/.journal.db: runVacuum - SQLite error: code 11, error SQLITE_CORRUPT[11]: database disk image is malformed

This article provides instructions on how to resolve the above error.

Note: The error does not cause any issues with respect to the user's access or the functionality of the software.

Root Cause

This result code indicates that the database file .journal.db is corrupt. The database becomes corrupt when a rogue process opens a database file or journal and writes malformed data into the middle of it. There is not much that can be done about these kinds of problems, and it does not cause the user any issues. However, it can fill the error logs with many lines of the same error. 

 

Resolution

  1. Stop Kerio Connect.

  2. Open a File Explorer.

  3. Navigate to the Kerio Store folder. The default paths for various Operating Systems are listed below:

    • Windows: C:\Program Files\Kerio\MailServer\Store\Mail

    • Mac: /usr/local/kerio/mailserver/store/mail

    • Linux: /opt/kerio/mailserver/store/mail

  4. Open the affected user folder (i.e. [domain.com]/[username])

  5. Delete the file .journal.db.

    113.png

  6. Start Kerio Connect.

 

Confirmation

The file .journal.db rebuilds itself, usually instantly, but sometimes it can take a while. The rebuilding of this file should not affect the users' ability to use their email accounts. View the error logs again, and the error string should no longer appear.

 

Back to Top