<html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /></head><body style='font-size: 10pt; font-family: Verdana,Geneva,sans-serif'>
<p>Hello David,</p>
<p>(sorry for the formatting, this is sent from webmail)</p>
<p>I'm not familiar with a good workaround but am familiar with the struggles of cleaning up Akonadi. I've done it often and it is never easy.</p>
<p>In fact since a week, akonadi refuses to start. It gives this error:</p>
<p>===</p>
<p><span style="font-family: monospace;"><span style="color: #000000; background-color: #ffffff;">Error : Table 'akonadi.pimitemtable' doesn't exist in engine </span><br />status : Operation failed<br /></span>===</p>
<p>There are reports that this is caused by a MariaDB update, but I'm not sure about that, because I'm on <span style="font-family: monospace;"><span style="color: #000000; background-color: #ffffff;">mariadb-server-10.5.11</span> with <span style="color: #000000; background-color: #ffffff;">mariadb-connector-c-3.1.13</span>, not libmariadb 3.2.<br /></span></p>
<p> https://old.reddit.com/r/kde/comments/p5d4bc/kmail_completely_broken/</p>
<p>akonadictl fsck will not run because akonadi is not running: a catch 22 situation.</p>
<p>So, while this is no help to you, I would like to say that the documentation work is much appreciated!</p>
<p>Jos</p>
<p><br /></p>
<p id="reply-intro">David Bryant schreef op 2021-08-15 17:33:</p>
<blockquote type="cite" style="padding: 0 0.4em; border-left: #1010ff 2px solid; margin: 0">
<div class="pre" style="margin: 0; padding: 0; font-family: monospace">I'm currently working on Chapter 7 ("Troubleshooting") of the KMail <br />documentation. It's almost done, except for some advice on dealing with <br />"dirty" items in the akonadi/mysql database files.<br /><br />This problem is documented as a bug: <a href="https://bugs.kde.org/show_bug.cgi?" target="_blank" rel="noopener noreferrer">https://bugs.kde.org/show_bug.cgi?</a><br />id=436550 I have a workaround, but it's quite laborious.<br /><br />The problem is present if and when one obtains terminal output like this.<br /><br />~ $ akonadictl fsck 2>&1 | grep ^Found<br />Found 5 external files.<br />Found 5 external parts.<br />Found no unreferenced external files.<br />Found 0 parts to be moved to external files<br />Found 0 parts to be moved to database<br />Found 6 collections without RID.<br />Found 3 items without RID.<br />Found 3001 dirty items.<br />~ $<br /><br />From time to time akonadictl reports 1 dirty item, which KMail/akonadi is <br />apparently able to patch up somehow. But when I (some way or another) got <br />bitten by ~3,000 dirty items last April, KMail became practically unuseable <br />(lots of messages could not be accessed, although they were displayed in the <br />Message List).<br /><br />Anyway, I'm hoping some clever programmer out there can think of an easier way <br />to fix this problem (when it occurs) than the method I devised. I backed up all <br />my email messages, deleted everything from the ~/.local/share/local-mail/ <br />directory, then started KMail. Akonadi erased all its DB files when it synced <br />with an empty tree. That eliminated the "dirty" items. Then I closed KMail & <br />akonadi and restored the backup copy of all my messages. When I restarted <br />KMail, akonadi rebuilt the mysql DB files cleanly. But I lost some auxiliary <br />information (special folder properties, for instance), and some of my mail <br />filter rules had to be reconstructed. So it was a lot of work. Is there a <br />simpler way to fix the "dirty" items when they arrive en masse?<br /><br />Thanks. Any and all suggestions are welcome.</div>
</blockquote>
<p><br /></p>
</body></html>