Tumbleweed snapshot 20210108 -- akonadi issues
Hi, I installed the latest snapshot 20210108 and after reboot akonadi run amok. Since I need a working E-mailsystem, I made zypper rollback the installation and -- because the database repair was beyond my skills (akonadictl vacuum and fsck didn't solve the issue) -- I deleted ~/.config/akonadi and ~/.local/ share/akonadi and replaced them with a backup. Sorry Simon, no bugreport possible. Somebody else hit by this? Regards, Alexander
Am Dienstag, 12. Januar 2021, 00:10:15 CET schrieb Jason Craig:
Hi! From memory: akonadi couldn't open the database and gave error messages, like deprecated signals, database crashed unexpectedly... Restarting akonadi (akonadictl restart) triggered hundreds of warnings, kmail crashing and unable to display the content of emails. Doing that for more than 15 minutes and eating all the CPU. I just had a look into the backup: ./local/akonadi had a size over 32 GB. According to the suggestion of Axel Braun I switched to PostgreSQL. Right now the database has a weight of ca. 5 GB, but I doubt that it has digested the archive of the last two decades already. We'll see... It was a very fortunate decision by the akonadi people to have database and mails stored on different locations. Nothing got lost. I installed the newest TW snapshots and all is well again. As long as you don't read the news. -- Alexander
Am Dienstag, 12. Januar 2021, 10:56:21 CET schrieb AW:
Well, it was a statement how I run akonadi, not a recommendation. You need to be aware that each postgres version change (13.x -> 14) requires database conversion: https://userbase.kde.org/Akonadi/Postgres_update Cheers Axel
Am Dienstag, 12. Januar 2021, 00:10:15 CET schrieb Jason Craig:
Hi! From memory: akonadi couldn't open the database and gave error messages, like deprecated signals, database crashed unexpectedly... Restarting akonadi (akonadictl restart) triggered hundreds of warnings, kmail crashing and unable to display the content of emails. Doing that for more than 15 minutes and eating all the CPU. I just had a look into the backup: ./local/akonadi had a size over 32 GB. According to the suggestion of Axel Braun I switched to PostgreSQL. Right now the database has a weight of ca. 5 GB, but I doubt that it has digested the archive of the last two decades already. We'll see... It was a very fortunate decision by the akonadi people to have database and mails stored on different locations. Nothing got lost. I installed the newest TW snapshots and all is well again. As long as you don't read the news. -- Alexander
Am Dienstag, 12. Januar 2021, 10:56:21 CET schrieb AW:
Well, it was a statement how I run akonadi, not a recommendation. You need to be aware that each postgres version change (13.x -> 14) requires database conversion: https://userbase.kde.org/Akonadi/Postgres_update Cheers Axel
participants (3)
-
AW -
Axel Braun -
Jason Craig