Bug 397979 - akonadi,permanently, disk write, a mean of 1.2 Mb
Summary: akonadi,permanently, disk write, a mean of 1.2 Mb
Status: REPORTED
Alias: None
Product: Akonadi
Classification: Frameworks and Libraries
Component: general (show other bugs)
Version: 5.7.3
Platform: openSUSE Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords: triaged
Depends on:
Blocks:
 
Reported: 2018-08-28 10:12 UTC by Philippe ROUBACH
Modified: 2019-03-09 10:27 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
iotop log (321.68 KB, image/png)
2018-08-28 10:12 UTC, Philippe ROUBACH
Details
sdc4 write acess (78.36 KB, image/png)
2018-08-28 10:13 UTC, Philippe ROUBACH
Details
akonadi consumes 25 % cpu power (85.39 KB, image/png)
2018-09-06 15:05 UTC, Philippe ROUBACH
Details
akonadi log (507.85 KB, image/png)
2018-09-26 12:58 UTC, Philippe ROUBACH
Details
the mbox account (90.04 KB, image/png)
2018-10-04 06:30 UTC, Philippe ROUBACH
Details
akonadi start log (305.10 KB, image/png)
2018-10-04 07:03 UTC, Philippe ROUBACH
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Philippe ROUBACH 2018-08-28 10:12:29 UTC
Created attachment 114651 [details]
iotop log

opensuse leap 42.3, leap 15

permanently whole day from start to shutdown
akonadi writes to disk.

mean size of the access : 1.2 Mb

see captures
Comment 1 Philippe ROUBACH 2018-08-28 10:13:30 UTC
Created attachment 114652 [details]
sdc4 write acess
Comment 2 Philippe ROUBACH 2018-08-28 10:29:48 UTC
other info : this occurs every day
Comment 3 Philippe ROUBACH 2018-09-06 15:05:40 UTC
Created attachment 114813 [details]
akonadi consumes 25 % cpu power

when akonadi stops making numerous disk accesses after several days
then
akonadi consumes 25 % cpu power
Comment 4 Philippe ROUBACH 2018-09-06 15:07:51 UTC
akonadi consumes 25 % cpu power during several hours for example from five pm to 12 pm
Comment 5 Daniel Vrátil 2018-09-24 15:42:31 UTC
I need some debug output from Akonadi, otherwise I can't even guess what's going on.

Enable logging and restart Akonadi from terminal:

export QT_LOGGING_RULES="*=true;qt_*=false"
akonadictl restart


You should be seeing more than plenty of messages, you may want to redirect them to a file.
Comment 6 Philippe ROUBACH 2018-09-26 12:58:36 UTC
Created attachment 115247 [details]
akonadi log

result of

export QT_LOGGING_RULES="*=true;qt_*=false"
akonadictl restart
Comment 7 Daniel Vrátil 2018-10-01 17:55:46 UTC
Looks like Item retrieval ended up in an endless loop.

My first suspicion, since this is a maildir resource, is that the journal log got corrupted or contains some wrong information, so let's try this:

akonadictl stop
mv ~/.config/akonadi/agent_config_akonadi_maildir_resource_0_changes.dat{,.bkp}
akonadictl start

This will rename the resource's journal file, so a new one will be created on start. This /may/ mean the changes you did that were stuck in the file (like marking an email as read or moving it to another folder) will be lost, but at least we will know what's wrong.

If it does not help, we'll try to debug it further.
Comment 8 Philippe ROUBACH 2018-10-03 06:04:47 UTC
problem still there.

this problem occurs after an update from 42.3 to 15 by updating the system partition and keeping the home partition
Comment 9 Christophe Marin 2018-10-03 17:46:45 UTC
is one of the messages empty? no title, no body (eg: an empty subscription mail to a mailing list)
Comment 10 Philippe ROUBACH 2018-10-04 06:30:23 UTC
Created attachment 115402 [details]
the mbox account

i get 2 imap4 accounts and one mbox cacount

the mbox account contents is a file named "roubach" with a size of 0 byte.

perhaps this is a problem.
Comment 11 Philippe ROUBACH 2018-10-04 07:03:32 UTC
Created attachment 115403 [details]
akonadi start log

there are some problems when akonadi starts

...
Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
...
Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
QDBusConnection: name 'org.freedesktop.Akonadi.Control' had owner '' but we thought it was ':1.250'
...
org.kde.pim.akonadiplugin_indexer: unknown term  "birthday"
org.kde.pim.akonadiplugin_indexer: unknown term  "birthday"
org.kde.pim.akonadicontrol: "AgentManager::agentInstanceSynchronizeCollection"  Agent instance  "akonadi_imap_resource_0"  has no resource interface!
org.kde.pim.akonadiserver: "Cannot connect to agent instance with identifier 'akonadi_imap_resource_0', error message: ''"
org.kde.pim.akonadiplugin_indexer: unknown term  "birthday"
org.kde.pim.akonadiplugin_indexer: unknown term  "birthday"
org.kde.pim.akonadiplugin_indexer: unknown term  "birthday"
org.kde.pim.akonadiplugin_indexer: unknown term  "birthday"
org.kde.kgapi: Unauthorized. Access token has expired or is invalid.
KGAPI2::ContactsGroupFetchJob(0x56087b5d24c0) "Authentification non valable."
org.kde.kgapi: Unauthorized. Access token has expired or is invalid.
KGAPI2::CalendarFetchJob(0x556cbadc64c0) "Authentification non valable."
org.kde.kgapi: Requested resource does not exist anymore.
Comment 12 Philippe ROUBACH 2018-10-04 07:42:39 UTC
(In reply to Philippe ROUBACH from comment #8)
> problem still there.
> 
> this problem occurs after an update from 42.3 to 15 by updating the system
> partition and keeping the home partition

i forget: this is opensuse 42.3 and opensuse 15.0
Comment 13 Andrew Crouthamel 2018-10-21 05:01:27 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 14 Philippe ROUBACH 2018-10-21 07:52:08 UTC
(In reply to Andrew Crouthamel from comment #13)
> Dear Bug Submitter,
> 
> This bug has been in NEEDSINFO status with no change for at least
> 15 days. Please provide the requested information as soon as
> possible and set the bug status as REPORTED. Due to regular bug
> tracker maintenance, if the bug is still in NEEDSINFO status with
> no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
> due to lack of needed information.
> 
> For more information about our bug triaging procedures please read the
> wiki located here:
> https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging
> 
> If you have already provided the requested information, please
> mark the bug as REPORTED so that the KDE team knows that the bug is
> ready to be confirmed.
> 
> Thank you for helping us make KDE software even better for everyone!

i supplied the info in my comments
Comment 15 Philippe ROUBACH 2018-10-21 07:56:25 UTC
(In reply to Christophe Giboudeaux from comment #9)
> is one of the messages empty? no title, no body (eg: an empty subscription
> mail to a mailing list)

i have thousands messages. it's impossible to know this.
Comment 16 Philippe ROUBACH 2018-11-24 11:36:52 UTC
openSuse leap 15.0 Argon

Argon is a version with always last kde app, kde framework, plasma

kde app 18.08.3
kde framework 5.52.0
plasma 5.14.3
Qt 5.11.2

i created:
2 imap account
1 google contact adressbook
1 google calendar

no local addressbook or calendar
local mail folders are the default ones and are empty

result : same problem

hypothesis : this is not a data problem but a software problem. imap or google engines ?
Comment 17 Philippe ROUBACH 2018-12-27 09:43:56 UTC
since i disable indexation of spam folder there is no more problem.

i assume indexation process can't treat some kind of spam mail.
Comment 18 Philippe ROUBACH 2019-02-12 15:49:49 UTC
after experiments i would say :

problem is around:
- too many messages in local trash box and/or spam box
- indexation about local trash box and/or spam box

i inactivated indexation of local trash box and spam box
and
i limited the life of mail to 30 days

then no more problem
Comment 19 Philippe ROUBACH 2019-03-09 10:27:44 UTC
i activated again for 2 weeks indexation. no problem.

i assume to many mails leads to an indexation problem.