[opensuse-factory] Akonadi crashes and crashes...
Hi! Is it only me or does anybody else suffer constant akonadi crashes on a current TW? Just now in the bottom line of kmail I got the message: "Unable to fetch item from backend (collection -1): Unable to retrieve item from resource: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken." And thousands of complaints: »org.kde.pim.akonadicore: Got a stale notification for an item which was already removed. 152705 "" « Restarting akonadi helps for a short period of time, seconds, maybe minutes. Then again mails won't be filtered or displayed, kmail fetches at random messages from server, which have already been downloaded at least once. Akonadi was working exactly until the TW update 20161217. I'd be very glad if somebody could do some maintenance. Regards, Alexander -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On dimanche, 8 janvier 2017 21.21:20 h CET AW wrote:
Hi!
Is it only me or does anybody else suffer constant akonadi crashes on a current TW? Just now in the bottom line of kmail I got the message: "Unable to fetch item from backend (collection -1): Unable to retrieve item from resource: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken."
And thousands of complaints:
»org.kde.pim.akonadicore: Got a stale notification for an item which was already removed. 152705 "" «
Restarting akonadi helps for a short period of time, seconds, maybe minutes. Then again mails won't be filtered or displayed, kmail fetches at random messages from server, which have already been downloaded at least once.
Akonadi was working exactly until the TW update 20161217.
I'd be very glad if somebody could do some maintenance.
Regards,
Alexander Work like a charm here (TW 20170104) linked to a shared postgresql db.
did you try to after a login go to konsole akonadictl status (should show running) akonadictl fsck akonadictl vacuum (long) akonadictl stop akonadictl start you could also add -v to have a bit more verbose message. -- Bruno Friedmann Ioda-Net Sàrl www.ioda-net.ch Bareos Partner, openSUSE Member, fsfe fellowship GPG KEY : D5C9B751C4653227 irc: tigerfoot -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Sunday, 8 January 2017 21:21:20 CET AW wrote:
And thousands of complaints:
»org.kde.pim.akonadicore: Got a stale notification for an item which was already removed. 152705 "" «
does it show 'merge conflicts' when you press the (up arrow near the blue updating bar whilst updating?) im on imap, i moved some post from one folder to another, after that i ended up with this bug https://bugs.kde.org/show_bug.cgi?id=338658 (which has just been solved). -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Mine just says "The Akonadi personal information management service is not operational" when I launch KMail on my desktop. I had already deleted the Akonadi files and redownloaded the emails, but the problem returned. I am using KMail on my laptop which is not showing the issue at present which only showed the CPU hogging issue. On Sunday, 8 January 2017 21:52:00 CST nicholas wrote:
On Sunday, 8 January 2017 21:21:20 CET AW wrote:
And thousands of complaints:
»org.kde.pim.akonadicore: Got a stale notification for an item which was already removed. 152705 "" «
does it show 'merge conflicts' when you press the (up arrow near the blue updating bar whilst updating?) im on imap, i moved some post from one folder to another, after that i ended up with this bug https://bugs.kde.org/show_bug.cgi?id=338658 (which has just been solved). -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Sunday, January 8, 2017 9:21:20 PM MST AW wrote:
Is it only me or does anybody else suffer constant akonadi crashes on a current TW?
Not sure if your issue is the same as mine but finally got my setup functional again... None of the akonadictl commands I ran did anything to help. I finally deleted the socket stuff: rm -rf ~/.local/share/akonadi/socket* rm -rf /tmp/akonadi* And then had kmail start the akonadi stuff and it works again... -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Sunday, 8 January 2017 13:58:48 GMT Warren Stockton wrote:
On Sunday, January 8, 2017 9:21:20 PM MST AW wrote:
Is it only me or does anybody else suffer constant akonadi crashes on a current TW?
Not sure if your issue is the same as mine but finally got my setup functional again...
None of the akonadictl commands I ran did anything to help.
I finally deleted the socket stuff: rm -rf ~/.local/share/akonadi/socket* rm -rf /tmp/akonadi*
And then had kmail start the akonadi stuff and it works again...
I've had to do something similar a couple of times lately (in my case just removing a mysql.socket file in /tmp did the trick). Just another ordinary day in the life of a kmail user... Regards, Huw
Op dinsdag 10 januari 2017 18:40:50 schreef huw:
On Sunday, 8 January 2017 13:58:48 GMT Warren Stockton wrote:
On Sunday, January 8, 2017 9:21:20 PM MST AW wrote:
Is it only me or does anybody else suffer constant akonadi crashes on a current TW?
Not sure if your issue is the same as mine but finally got my setup functional again...
None of the akonadictl commands I ran did anything to help.
I finally deleted the socket stuff: rm -rf ~/.local/share/akonadi/socket* rm -rf /tmp/akonadi*
And then had kmail start the akonadi stuff and it works again...
I've had to do something similar a couple of times lately (in my case just removing a mysql.socket file in /tmp did the trick).
Just another ordinary day in the life of a kmail user...
Regards, Huw
Same with me on Tumbleweed. Will try the socket trick. I read about a recent solution in bugzilla of KDE, can't currently find the link. Hopefully this will soon arrive in Tumbleweed. But I fear this is not the only problem. -- fr.gr. member openSUSE Freek de Kruijf -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Op woensdag 11 januari 2017 12:29:18 CET schreef Freek de Kruijf:
Op dinsdag 10 januari 2017 18:40:50 schreef huw:
On Sunday, 8 January 2017 13:58:48 GMT Warren Stockton wrote:
On Sunday, January 8, 2017 9:21:20 PM MST AW wrote:
Is it only me or does anybody else suffer constant akonadi crashes on a current TW?
Not sure if your issue is the same as mine but finally got my setup functional again...
None of the akonadictl commands I ran did anything to help.
I finally deleted the socket stuff: rm -rf ~/.local/share/akonadi/socket* rm -rf /tmp/akonadi*
And then had kmail start the akonadi stuff and it works again...
I've had to do something similar a couple of times lately (in my case just removing a mysql.socket file in /tmp did the trick).
Just another ordinary day in the life of a kmail user...
Regards, Huw
Same with me on Tumbleweed. Will try the socket trick. I read about a recent solution in bugzilla of KDE, can't currently find the link. Hopefully this will soon arrive in Tumbleweed. But I fear this is not the only problem.
I don't see crashes. I do see akonadi not starting after a cold boot. Removing only the mysql.socket from /tmp/akonadi-$USER.#hash/ and 'akonadictl start' returns a working akonadi. A reboot doesn't have this issue. I'll post the output after a cold boot. -- Gertjan Lettink, a.k.a. Knurpht openSUSE Board Member openSUSE Forums Team -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Op woensdag 11 januari 2017 14:08:03 schreef Knurpht - Gertjan Lettink:
Op woensdag 11 januari 2017 12:29:18 CET schreef Freek de Kruijf:
Op dinsdag 10 januari 2017 18:40:50 schreef huw:
On Sunday, 8 January 2017 13:58:48 GMT Warren Stockton wrote:
On Sunday, January 8, 2017 9:21:20 PM MST AW wrote:
Is it only me or does anybody else suffer constant akonadi crashes on a current TW?
Not sure if your issue is the same as mine but finally got my setup functional again...
None of the akonadictl commands I ran did anything to help.
I finally deleted the socket stuff: rm -rf ~/.local/share/akonadi/socket* rm -rf /tmp/akonadi*
And then had kmail start the akonadi stuff and it works again...
I've had to do something similar a couple of times lately (in my case just removing a mysql.socket file in /tmp did the trick).
Just another ordinary day in the life of a kmail user...
Regards, Huw
Same with me on Tumbleweed. Will try the socket trick. I read about a recent solution in bugzilla of KDE, can't currently find the link. Hopefully this will soon arrive in Tumbleweed. But I fear this is not the only problem. I don't see crashes. I do see akonadi not starting after a cold boot. Removing only the mysql.socket from /tmp/akonadi-$USER.#hash/ and 'akonadictl start' returns a working akonadi. A reboot doesn't have this issue. I'll post the output after a cold boot.
These crashes are a result of certain circumstances/actions that are performed. In my case I have several IMAP servers (5) configured, 1 GMail and 4 dovecot servers. When I move a message from the GMail inbox to a specific folder on a large dovecot server with about 200 folders and thousands of messages I see a crash of akonadiserver. Not always. Furthermore I quite often have a stall of KMail after deleting several messages in an inbox. I have to finish kontact and start it again to be able to continue. Sometimes I need to use akonadictl stop and start. Will see if in that case removing the sockets will help too. Apparently I have been lucky that despite all this trouble I never have lost any message on my IMAP servers. -- fr.gr. member openSUSE Freek de Kruijf -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Sun, 8 Jan 2017, at 14:58, Warren Stockton wrote:
I finally deleted the socket stuff: rm -rf ~/.local/share/akonadi/socket* rm -rf /tmp/akonadi*
And then had kmail start the akonadi stuff and it works again...
My setup seems to be working again after this. Running Kontact from the terminal does show multiple entries along the following lines: org.kde.pim.akonadicore: Got a stale notification for an item which was already removed. 128489 "" Is this something I should be concerned about? -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Sunday, 8 January 2017 21:21:20 GMT AW wrote:
Hi!
Is it only me or does anybody else suffer constant akonadi crashes on a current TW? Just now in the bottom line of kmail I got the message: "Unable to fetch item from backend (collection -1): Unable to retrieve item from resource: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken."
And thousands of complaints:
»org.kde.pim.akonadicore: Got a stale notification for an item which was already removed. 152705 "" «
Restarting akonadi helps for a short period of time, seconds, maybe minutes. Then again mails won't be filtered or displayed, kmail fetches at random messages from server, which have already been downloaded at least once.
Akonadi was working exactly until the TW update 20161217.
I'd be very glad if somebody could do some maintenance.
Regards,
Alexander You are not alone, i reported this before Christmas, the developer responded to say he was aware and would try and resolve it over the christmas period but nothing so far.
-- opensuse:tumbleweed:20170104 Qt: 5.7.1 KDE Frameworks: 5.29.0 KDE Plasma: 5.8.5 kwin5-5.8.5-172.1.x86_64 Kernel: 4.9.0-2-default Nouveau: 1.0.13_2.1 -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
participants (9)
-
AW -
Bruno Friedmann -
Chan Ju Ping -
Freek de Kruijf -
huw -
ianseeks -
Knurpht - Gertjan Lettink -
nicholas -
Warren Stockton