Summary: | akonadi loses connection with IMAP server after suspend (but not only, DB error too) | ||
---|---|---|---|
Product: | [Frameworks and Libraries] Akonadi | Reporter: | yves.caniou |
Component: | IMAP resource | Assignee: | kdepim bugs <kdepim-bugs> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | asturm, dilfridge, dvratil, matija, miso, muesli |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Gentoo Packages | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
yves.caniou
2018-08-09 13:17:53 UTC
I had to stop akonadi each time I loggued on my computer, like returning from suspend mode (is it normal that akonadi restarts after suspend if it was stopped beforehands?). If I did not stop it, I realized that the computer turned slow, making a lot of swap. It turned out that akonadi requires a lot of swap space which is encrypted on my computer, thus wasting a lot of cpu too. Gentoo proposed upgrades for akonadi, so: Akonadi is v18.04.3 I gave a try to fsck and vacuum, with a renice 19, and see what happens. fsck lasted a few hours. Revealed many errors. vacuum is now sticked to "optimizing table CollectionTable..." since ~3days. No cpu, and akonadiserver is using more than 27.1GB of memory -> "vacuuming database that'll take some time and require a lot of temporary disk space..." should say that one should had some Gigs to its swap space (I thought /tmp space would be ok. It's not). How long is "some time"? There's nothing on the activity of vacuum... In addition, i tried kmail: - kmail lost contact with two smtp servers (M$ and linux) but says it still manages another one and local mails. - Trying send a mail results in a error message (partly in french, so translated): "There have been problems trying to put the message in sending: unable to append item flags." It's been several months now. What can I do? Same here, happy to provide more logs. Restarting the akonadiserver only lasts for a few minutes here, then I'm back to square 1. I seem to be getting the same issue on NixOS with Akonadi 18.12.3. Currently running `akonadictl fsck && akonadictl vacuum` and it’s been an hour at least already. I suspect that this might be related to (and fixed by): https://phabricator.kde.org/D21455 My current workaround is to kill kmail, set the IMAP resource in Akonadi Console as Offline, and use Trojita until this gets fixed. Hope that helps at least a bit. There seem to be multiple issues mixed in here: 1) Multiple Merge Candidates error (bug #338658) - we will have automatic recovery in 19.08 release. 2) Transaction timeout/deadlock - this should be fixed in 19.04 already through various fixes from David. 3) SQL error when running akonadictl fsck - fixed in 18.08.3 (commit 89727ad4da4d) 4) IMAP/SMTP getting stuck - this should mostly be fixed in 19.04 by the transaction timeout fixes 5) akonadi fsck/vacuum running while database is in use - there's a task for that (https://phabricator.kde.org/T9753) Note that vacuum never fixes anything (it's just supposed to optimize the database for index performance and storage size) and fsck is not a solution to unstuck Akonadi if it stops syncing. All in all, I think this can be closed, if you hit any of the described issues, please file separate bug reports. |