Summary: | KMail doesn´t respond: ItemRetrieverException : Unable to retrieve item from resource | ||
---|---|---|---|
Product: | [Frameworks and Libraries] Akonadi | Reporter: | Martin Steigerwald <Martin> |
Component: | server | Assignee: | kdepim bugs <kdepim-bugs> |
Status: | RESOLVED WORKSFORME | ||
Severity: | normal | CC: | dvratil, luisfe |
Priority: | NOR | ||
Version: | 4.10 | ||
Target Milestone: | --- | ||
Platform: | Debian unstable | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: | |||
Attachments: | xsession-errors of the last occurence of this slow responding in KMail after triggering POP3 retrieval |
Description
Martin Steigerwald
2013-04-13 09:48:14 UTC
Created attachment 78858 [details]
xsession-errors of the last occurence of this slow responding in KMail after triggering POP3 retrieval
Usernames of POP3 replaced by nothing.
Secondary issues seen in ~/.xsession-errors: Bug 318283 - KMail/libakonadi: Got a stale notification for an item which was already removed Bug 318284 - Messages like 'Payload file "[…].local/share/akonadi/file_db_data/797210_r0" is missing, trying to recover.' According to akonadiconsole in those circumstances often my biggest maildir resource lichtvoll stalls synchronization at some random folder. It then sits there for minutes to come, even if its just a smaller folder it got stuck at. Thus I suspect a communication issue between the different components involved. Also adding versions of dbus packages to the mix: martin@merkaba:~> apt-show-versions | grep "dbus" dbus/sid uptodate 1.6.8-1 dbus-x11/sid uptodate 1.6.8-1 libdbus-1-3/sid uptodate 1.6.8-1 libdbus-1-dev/sid uptodate 1.6.8-1 libdbus-c++-1-0/sid uptodate 0.9.0-6 libdbus-glib-1-2/sid uptodate 0.100.2-1 libdbusmenu-glib4/sid uptodate 0.6.2-1 libdbusmenu-qt2/sid uptodate 0.9.0-1 libkdepimdbusinterfaces4 4:4.10.2-0r4 installed: No available version in archive libnet-dbus-perl/sid uptodate 1.0.0-2 libqt4-dbus/sid uptodate 4:4.8.2+dfsg-11 libqtdbus4/sid uptodate 4:4.8.2+dfsg-11 libsmokeqtdbus4-3/sid uptodate 4:4.8.4-1 python-dbus/sid uptodate 1.1.1-1 python-dbus-dev/sid uptodate 1.1.1-1 python-qt4-dbus/sid uptodate 4.9.3-4 qdbus/sid uptodate 4:4.8.2+dfsg-11 Maybe these deadlocks with some MySQL queries are also related: martin@merkaba:~/KDE/Bugs/318281 KMail doesn´t respond: ItemRetrieverException : Unable to retrieve item from resource> xzgrep -i "dead" xsession-errors.txt.xz Error during executing query "UPDATE PimItemTable SET atime = :0 WHERE ( ( PimItemTable.id = :1 ) )" : "Deadlock found when trying to get lock; try restarting transaction QMYSQL3: Unable to execute statement" [… some PlaneShift game client related messages …] Error during executing query "UPDATE PimItemTable SET atime = :0 WHERE ( ( PimItemTable.id = :1 ) )" : "Deadlock found when trying to get lock; try restarting transaction QMYSQL3: Unable to execute statement" MySQL has been at 100% during that POP 3 download but it often uses more than that. Dunno whether there has been something going on single-threadedly. I have mytop and mysql client installed and can try to have a closer look at whats going on. One of those is also in the shortened xsession-errors-edited.txt I attached. I am hesitant to attach the whole xsession-errors.txt cause Akonadi Nepomuk Feeder or probably some other component as well puts lots of private informations in it, included complete mail text which just don´t have anything to do in this file. Anyway version of MySQL packages involved: martin@merkaba:~> apt-show-versions | grep mysql akonadi-backend-mysql/experimental uptodate 1.9.1-2 kexi-mysql-driver/sid uptodate 1:2.4.4-3 libdbd-mysql-perl/sid uptodate 4.021-1+b1 libmysqlclient-dev/sid uptodate 5.5.30+dfsg-1 libmysqlclient18/sid uptodate 5.5.30+dfsg-1 libqt4-sql-mysql/sid uptodate 4:4.8.2+dfsg-11 mysql-client/sid uptodate 5.5.30+dfsg-1 mysql-client-5.5/sid uptodate 5.5.30+dfsg-1 mysql-common/sid uptodate 5.5.30+dfsg-1 mysql-server-core-5.5/sid uptodate 5.5.30+dfsg-1 python-mysqldb/sid uptodate 1.2.3-2 I can confirm this behavior with kde master compiled over debian stable. Does this still happen to you? If you can still reproduce the database deadlock, when it happens again, please do the following: Open Akonadi Console and in DB Console tab, run "SHOW ENGINE INNODB STATUS". This should reveal what queries are deadlocking and we can optimize them to avoid this happening in future. Dan, I don´t seem to see this anymore with KMail 4.12.2 and Akonadi 1.11.0 – Akonadi still isn´t exactly very responsive while doing stuff in the background (see bug #331848), but that ItemRetrieverException does not seem to appear anymore: martin@merkaba:~> ls -lh .xsession-errors -rw------- 1 martin martin 1,5M Mär 7 14:19 .xsession-errors martin@merkaba:~> grep -i "Did not receive a reply" .xsession-errors martin@merkaba:~#1> grep -i "ItemRetrieverException" .xsession-errors Thus closing. Luisfe, if you still see it, please reopen. Thanks, Martn |