Bug 322327

Summary:	high load while seemingly doing nothing
Product:	[Frameworks and Libraries] Akonadi	Reporter:	john Terragon <terragonjohn>
Component:	Migration	Assignee:	kdepim bugs <kdepim-bugs>
Status:	RESOLVED UNMAINTAINED
Severity:	normal
Priority:	NOR
Version:	4.10
Target Milestone:	---
Platform:	Debian unstable
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description john Terragon 2013-07-14 06:23:45 UTC

Just migrated from kmail1. Migration went well, nothing lost as far as I can tell. 
The problem is that the mysqld process is now constantly at 90%/100% cpu load, with akonadiserver trailing it at 15%. They seem not to do anything. No disk activity, the database doesn't grow larger or anything in the .local/share/akonadi dir. It seems not to be modifying anything, just stays there at 90%/100% load doing I don't know what.
kmail is responsive and it seems to receive the mail but it can't send it (so that's another thing).
One last thing: semantic search is deactivated (no need to deal with that too...)

So, let me know if there are tests I can do to pinpoint the problem and figure out what mysql is actually doing.

john



Reproducible: Always

Comment 1 john Terragon 2013-07-14 07:07:05 UTC

It turns out that there were some bugs in the mysql log.
Calling a mysql_upgrade fixed that and after restarting  akonadi (and mysql) everything is
fine.

Comment 2 john Terragon 2013-07-14 07:17:09 UTC

Spoken too soon.
Kmail lamented some kind of conflict (it showed two email side by side in a popup window).
I clicked on keep both and know  mysql has a 300% load while doing nothing, Restarting it won't do anything.

Comment 3 Denis Kurz 2016-09-24 20:31:58 UTC

This bug has only been reported for versions older than KDEPIM 4.14 (at most akonadi-1.3). Can anyone tell if this bug still present?

If noone confirms this bug for a recent version of akonadi (part of KDE Applications 15.08 or later), it gets closed in about three months.

Comment 4 Denis Kurz 2017-01-07 21:47:09 UTC

Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.0 aka 15.08), please open a new one unless it already exists. Thank you for all your input.