Bug 362044 - akonadi database corrupt after reboot on 15.12 (and 16.04) with mail loss after akondictl vacuum
Summary: akonadi database corrupt after reboot on 15.12 (and 16.04) with mail loss aft...
Status: RESOLVED WORKSFORME
Alias: None
Product: Akonadi
Classification: Frameworks and Libraries
Component: akonadiconsole (show other bugs)
Version: unspecified
Platform: openSUSE Linux
: NOR critical
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-04-21 16:32 UTC by kuede
Modified: 2022-11-22 05:13 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description kuede 2016-04-21 16:32:17 UTC
When starting Kontact it complains about akonadi not running correctly. The only way to repair seems to perform akonadictl fsck (twice), killing all akonadi-related processes and kontact and start Kontact again. 

All mails are redownloaded again and most folder settings are incorrect. 

Running akonadictl fsck results in removal of almost all mails from database (already completely deleted database, all cache folders and config files and set-up kontact/akonadi from start; results every time in same behaviour).  

Running aconadictl vacuum even completely deleted all mails from an IMAP server (complete mail loss).

Furthermore: clicking the details button in Kontact (when akonadi is not working correctly) does not do anything, akonadictl stop or restart don't result in any output nor stopping or restart. Only akonadictl start works.

Only remaining question for me: Did I forget to delete any data/config/storage file of akonadi/kontact that might cause this behaviour even after a "almost clean" install?

My system: Opensuse Leap 42.1, up-to date, using KDE-Applications (now running 16.04).

Reproducible: Always

Steps to Reproduce:
1. Having a running copy of Kontact
2. Reboot
3. akonadi stops working

Actual Results:  
Kontact does not work (or better: akonadi)


excerpt from akonadictl fsck output (second run):
Found unreferenced external file: /home/kuede/.local/share/akonadi/file_db_data/24/8524_r0
Found unreferenced external file: /home/kuede/.local/share/akonadi/file_db_data/19/10119_r0
Found unreferenced external file: /home/kuede/.local/share/akonadi/file_db_data/92/10792_r0
Found unreferenced external file: /home/kuede/.local/share/akonadi/file_db_data/87/9987_r0
Found unreferenced external file: /home/kuede/.local/share/akonadi/file_db_data/28/13928_r0
Found unreferenced external file: /home/kuede/.local/share/akonadi/file_db_data/13/7313_r0
Found unreferenced external file: /home/kuede/.local/share/akonadi/file_db_data/53/10753_r0
Found unreferenced external file: /home/kuede/.local/share/akonadi/file_db_data/60/12560_r0
Found unreferenced external file: /home/kuede/.local/share/akonadi/file_db_data/63/11463_r0
Found unreferenced external file: /home/kuede/.local/share/akonadi/file_db_data/93/8893_r0
Found unreferenced external file: /home/kuede/.local/share/akonadi/file_db_data/50/7850_r0
Found unreferenced external file: /home/kuede/.local/share/akonadi/file_db_data/77/12677_r0
Found unreferenced external file: /home/kuede/.local/share/akonadi/file_db_data/51/8051_r0
Found unreferenced external file: /home/kuede/.local/share/akonadi/file_db_data/82/8682_r0
Found unreferenced external file: /home/kuede/.local/share/akonadi/file_db_data/11/8511_r0
Found unreferenced external file: /home/kuede/.local/share/akonadi/file_db_data/60/10560_r0
Found unreferenced external file: /home/kuede/.local/share/akonadi/file_db_data/93/6893_r0
Found unreferenced external file: /home/kuede/.local/share/akonadi/file_db_data/80/9880_r0
Found unreferenced external file: /home/kuede/.local/share/akonadi/file_db_data/77/10677_r0
Found unreferenced external file: /home/kuede/.local/share/akonadi/file_db_data/54/8554_r0
Found unreferenced external file: /home/kuede/.local/share/akonadi/file_db_data/59/7859_r0
Found unreferenced external file: /home/kuede/.local/share/akonadi/file_db_data/81/12581_r0
Found unreferenced external file: /home/kuede/.local/share/akonadi/file_db_data/80/8880_r0
Found unreferenced external file: /home/kuede/.local/share/akonadi/file_db_data/84/11484_r0
Found unreferenced external file: /home/kuede/.local/share/akonadi/file_db_data/07/4607_r0
Found unreferenced external file: /home/kuede/.local/share/akonadi/file_db_data/75/9175_r0
Moved 1352 unreferenced files to lost+found.
Checking size treshold changes...
Found 0 parts to be moved to external files
Found 0 parts to be moved to database
Looking for dirty objects...
Collection "Search" (id: 1) has no RID.
Collection "OpenInvitations" (id: 33) has no RID.
Collection "DeclinedInvitations" (id: 34) has no RID.
Found 3 collections without RID.

Error messages in the error protocols typically say:
cannot stop inactive timer.
Akonadi ressource_XYZ does not run because "" (no text that indicate a reason)
Comment 1 Justin Zobel 2022-10-20 23:54:27 UTC
Thank you for reporting this bug in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version?

If you can reproduce the issue, please change the status to "CONFIRMED" when replying. Thank you!
Comment 2 kuede 2022-10-23 11:04:31 UTC
> If you can reproduce the issue, please change the status to "CONFIRMED" when
> replying. Thank you!

Having tried several times with newer versions thereafter, it still occurred. However, now using Kontact/KMail only irregulary, it does not seem to recur anymore.
Version used: Version 5.19.3 (21.12.3)
For me this seems ressolved for the moment.
Comment 3 Bug Janitor Service 2022-11-07 05:09:16 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 4 Bug Janitor Service 2022-11-22 05:13:04 UTC
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!