Bug 288605 - Mail Dispatcher Agent went offline for unknown reason
Summary: Mail Dispatcher Agent went offline for unknown reason
Status: RESOLVED UNMAINTAINED
Alias: None
Product: Akonadi
Classification: Frameworks and Libraries
Component: Mail Dispatcher Agent (show other bugs)
Version: 4.7
Platform: Ubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-12-09 22:18 UTC by Alexander van Loon
Modified: 2017-01-07 22:24 UTC (History)
6 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Alexander van Loon 2011-12-09 22:18:04 UTC
Version:           4.7 (using KDE 4.7.3) 
OS:                Linux

With Akonadi 1.6.2 and KMail 4.7.3 KMail I experienced this twice now two days ago and today. I don't remember changing anything with package updates or in configuration regarding Akonadi or KMail. What happened is that when I sent an e-mail in KMail it wasn't sent, but it was just placed in the Outbox, doing nothing there.

After a Google query I found this – https://bbs.archlinux.org/viewtopic.php?id=129839 – advice. I opened the Akonadi console, noticed the Mail Dispatcher Agent being offline for some reason. Toggling it back to online fixed it immediately, the e-mail was sent. My conclusion is that the MDA went offline by itself for some reason I can't fathom. Not sure if I can reproduce this, but if there are logs of some kind I'd be happy to provide them.

Reproducible: Didn't try

Steps to Reproduce:
No idea as I said, but maybe someone who does have an idea might find this bugreport and realize more people are affected.


Expected Results:  
The MDA should never go offline in such a sneaky manner without the user being aware of it, KMail gave me no error message at all and I had no idea what was wrong.
Comment 1 Mathias Homann 2012-12-23 23:03:38 UTC
I'm having the same issues in KDE 4.9.4 here. After a few hours of working with my computer the mail dispatcher simply stops working and needs to be restarted.
Comment 2 piedro 2013-07-01 10:08:49 UTC
I have a similar problem with KDE 4.10.4 -  the mail dispatcher agent is shown allright and online in the Akonadi console but it doesn't work. I have to manually restart the agent (i do that in akonadi console "restart agent") and it works again ... 

IMHO this is again a seríous problem - mail that has been sent stuck in the outbox is a real show stopper ... 

p.
Comment 3 piedro 2013-07-24 12:07:53 UTC
Plz, can someone confirm this? I run KDE on Arch, it's version 4.10.5. This bug is not random: 

Anytime I leave my box running for more than a day (this is an estimate) the akonadi agent has to be restarted. And, by the way, this is true for: 

- mail dipatcher agent 
- mail filter agent (filtering always stops at a certain runtime) 
- local notes (for kjots: it stops showing the notes altogether and has to be restarted to work again) 
- ... there may be more but these are the agents I use mostly use 

Years ago I had a similar problem. That had to do with the missing entry "wait_timeout=31536000" in the mysql.conf. But now I checked in the folder "~/.local/share/akonadi" - the file "mysql.conf is present and has the above entry. 

thx for reading, 
piedro
Comment 4 Salvo "LtWorf" Tomaselli 2014-07-11 07:17:22 UTC
I am having the same problem now.
Comment 5 Salvo "LtWorf" Tomaselli 2014-07-11 07:18:08 UTC
Actually, maybe it's different since my one refuses to go online.
Comment 6 Denis Kurz 2016-09-24 20:45:13 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 7 Denis Kurz 2017-01-07 22:24:40 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.