I’m having issues trying to update/upgrade to 42.2. Akonadi gets hung up
trying to process email messages - hangs one cpu (of 8) at 100% for up to 5
minutes. The system will then simply continue or Akonadi/kmail will crash
completely. I see similar issues all the way back to 13.1 but the
occurrences are more frequent and have much greater impact with the 42.2.
The randomness is that there appears no consistent sequence of events
leading to the crash (at least none that I’ve been able to spot) after
recreating the updated system from the same base system several times.
Is there a way to force a re-index of the email database or do a manual
index of the emails?
Which Leap 42.2? – Beta ? Test
or, Release Candidate 1 Test? 1. Upgrade from KDE Plasma 5 Kontact or, from KDE4 Plasma Kontact?
[HR][/HR]IMHO, yes, the KDE folks do a pretty good job of providing migration procedures from earlier versions to the current version and, if you take a look into the Leap 42.2 discussion threads (one per Test release), you’ll notice entries which document the ability of KDE to migrate from earlier Kontact versions;
but
, the test scenarios use small sets of sample e-Mails, appointments, and so on . . .
[HR][/HR]IMHO, a serious migration of Kontact data from an earlier (Qt4) to the current (Qt5) KDE is best executed by exporting everything before the upgrade is executed; delete the old Kontact environment before the upgrade is executed; set-up the user’s Kontact environment as new (no previous data); import the Kontact data from the earlier release.
and theres’ akonadiconsole. Never got to actually using that.
In my case all emailaccounts are IMAP based. In the past I’ve seen database corruptions, which I “solved” by simply removing the account and readding it.
If it’s clear which folder contains the culprits, you can copy the folder ( to local mail ), then remove, then copy back.
>
> whonea;2797281 Wrote:
>>
>> Is there a way to force a re-index of the email database or do a manual
>> index of the emails?
>
> Akonadictl provides two options:
>
> Code:
> --------------------
>
> akonadictl fsck
> akonadictl vacuum
>
> --------------------
>
>
> and theres’ akonadiconsole. Never got to actually using that.
>
> In my case all emailaccounts are IMAP based. In the past I’ve seen
> database corruptions, which I “solved” by simply removing the account
> and readding it.
>
> If it’s clear which folder contains the culprits, you can copy the
> folder ( to local mail ), then remove, then copy back.
>
Thanks - those two operations got things stable again. Turned out to be one
particular message with a really garbled “subject” line of more than 400
characters. Most likely a corrupted data stream but I’ll see if I can
duplicate the issue so that a bug report can point to a missed data length
check somewhere.
Weird coincedence, this morning suddenly my kmail session ( active since yesterday morning ) crashed. Restarting akonadi, restarting the entire system did not help. Ran ‘akonadictl fsck’ and back to normal.
> Weird coincedence, this morning suddenly my kmail session ( active since
> yesterday morning ) crashed. Restarting akonadi, restarting the entire
> system did not help. Ran ‘akonadictl fsck’ and back to normal.
>
Mine crapped out after running alright for a day or so as well - but the
problem now is considerably more complicated as any filter or delete of
messages ties the whole system in knots. Ah, well - need an occasional
challenge to keep the elderly brain cells active. Will post anything useful
I might find.