akonadi wont start

[snerk]

im having the same old problems again after upgrading to kde 4.12 from the backports ppa
see this screenshot http://i.imgur.com/6zErn3z.png
i had the same problem after upgrading to 4.11, then installing qt4-default & libqt4-dev from backports ppa did the trick, but not this time

i also tried
rm -rfv ~/.config/akonadi/*
rm -rfv ~/.local/share/akonadi/*
rm -rfv ~/.kde/share/config/akonadi*
but that did nothing..help?

[SteveRiley]

Please open a console window and run

akonadictl start

Paste the output here.

[snerk]

hi, here it is

akonadictl start
Unable to register service as "org.freedesktop.Akonadi.Control.lock" Maybe it's already running?
"[
0: /usr/bin/akonadi_control() [0x427f77]
1: /usr/bin/akonadi_control() [0x4281d2]
2: /lib/x86_64-linux-gnu/libc.so.6(+0x36ff0) [0x7f131efceff0]
3: /lib/x86_64-linux-gnu/libc.so.6(gsignal+0x37) [0x7f131efcef77]
4: /lib/x86_64-linux-gnu/libc.so.6(abort+0x148) [0x7f131efd25e8]
5: /usr/lib/x86_64-linux-gnu/libQtCore.so.4(_Z17qt_message_output9QtMsgTypePKc+ 0x102) [0x7f1320008912]
6: /usr/bin/akonadi_control() [0x429ecd]
7: /usr/lib/x86_64-linux-gnu/libQtCore.so.4(_ZN9QIODevice5writeEPKcx+0xb0) [0x7f13200a3020]
8: /usr/lib/x86_64-linux-gnu/libQtCore.so.4(+0x1183ad) [0x7f13200b03ad]
9: /usr/lib/x86_64-linux-gnu/libQtCore.so.4(_ZN11QTextStreamD1Ev+0x33) [0x7f13200b8f93]
10: /usr/bin/akonadi_control() [0x40c8e9]
11: /usr/bin/akonadi_control() [0x40938d]
12: /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf5) [0x7f131efb9de5]
13: /usr/bin/akonadi_control() [0x40967f]
]
"
Error: akonadi_control was started but didn't register at D-Bus session bus.
Make sure your system is set up correctly!

[oshunluvr]

https://bugs.kde.org/show_bug.cgi?id=326480

From the above link:

Killing akonadi_control, akonadiserver and mysqld processes and restarting akonadi afterwards let akonadi run fine until the next reboot

[snerk]

yep
pkill akonadi_control
pkill akonadiserver
akonadictl start
works

[oshunluvr]

This bug appears unresolved at the moment. You might want to make a script file to run after you log in as a workaround. Add a delay at the beginning and before the akonadictl start.

[snerk]

This bug appears unresolved at the moment. You might want to make a script file to run after you log in as a workaround. Add a delay at the beginning and before the akonadictl start.

already done but thanks for suggestion

[oshunluvr]

Great minds!

[SteveRiley]

Weird and random bug there.

On my machine, Akonadi never starts at boot. Or at least I think it doesn't. The evidence is that after booting, when I open KMail, the window is darkened and some text in the window informs me that Akonadi is starting. I suppose this is why I've not encountered the timing issue? Because by the time I open KMail, dbus has already got its lazy self started.

[royleith]

I wanted to use KOrganiser, but could not start Akonadi. The first reported error was that the error log file was in place, but could not be opened. I resolved that by changing the permissions of .local to user.

That leaves me with three errors I cannot resolve;

Akonadi control process not registered at D-Bus.

Akonadi server process not registered at D-Bus.

No resource agents found.

I tried the above stop service and restart and got the following;

roy@nettop:~$ akonadictl start
roy@nettop:~$ Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QStr ing,QString,QString)
Cannot remove old log file - running on a readonly filesystem maybe?
QIODevice:utChar: Closed device
"[
0: akonadiserver() [0x419828]
1: akonadiserver() [0x419ab2]
2: /lib/x86_64-linux-gnu/libc.so.6(+0x36ff0) [0x7f347d943ff0]
3: /lib/x86_64-linux-gnu/libc.so.6(gsignal+0x37) [0x7f347d943f77]
4: /lib/x86_64-linux-gnu/libc.so.6(abort+0x148) [0x7f347d9475e8]
5: /usr/lib/x86_64-linux-gnu/libQtCore.so.4(_Z17qt_message_output9QtMsgTypePKc+ 0x102) [0x7f347f426912]
6: /usr/lib/x86_64-linux-gnu/libQtCore.so.4(+0x70c79) [0x7f347f426c79]
7: /usr/lib/x86_64-linux-gnu/libQtCore.so.4(_Z6qFatalPKcz+0x94) [0x7f347f427484]
8: akonadiserver() [0x41b344]
9: akonadiserver() [0x41510b]
10: akonadiserver() [0x4125cb]
11: /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf5) [0x7f347d92ede5]
12: akonadiserver() [0x412ff8]
]
"
ProcessControl: Application 'akonadiserver' returned with exit code 255 (Unknown error)
Cannot remove old log file - running on a readonly filesystem maybe?
QIODevice:utChar: Closed device
"[
0: akonadiserver() [0x419828]
1: akonadiserver() [0x419ab2]
2: /lib/x86_64-linux-gnu/libc.so.6(+0x36ff0) [0x7f1955bf7ff0]
3: /lib/x86_64-linux-gnu/libc.so.6(gsignal+0x37) [0x7f1955bf7f77]
4: /lib/x86_64-linux-gnu/libc.so.6(abort+0x148) [0x7f1955bfb5e8]
5: /usr/lib/x86_64-linux-gnu/libQtCore.so.4(_Z17qt_message_output9QtMsgTypePKc+ 0x102) [0x7f19576da912]
6: /usr/lib/x86_64-linux-gnu/libQtCore.so.4(+0x70c79) [0x7f19576dac79]
7: /usr/lib/x86_64-linux-gnu/libQtCore.so.4(_Z6qFatalPKcz+0x94) [0x7f19576db484]
8: akonadiserver() [0x41b344]
9: akonadiserver() [0x41510b]
10: akonadiserver() [0x4125cb]
11: /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf5) [0x7f1955be2de5]
12: akonadiserver() [0x412ff8]
]
"
ProcessControl: Application 'akonadiserver' returned with exit code 255 (Unknown error)
Cannot remove old log file - running on a readonly filesystem maybe?
QIODevice:utChar: Closed device
"[
0: akonadiserver() [0x419828]
1: akonadiserver() [0x419ab2]
2: /lib/x86_64-linux-gnu/libc.so.6(+0x36ff0) [0x7f6ee586eff0]
3: /lib/x86_64-linux-gnu/libc.so.6(gsignal+0x37) [0x7f6ee586ef77]
4: /lib/x86_64-linux-gnu/libc.so.6(abort+0x148) [0x7f6ee58725e8]
5: /usr/lib/x86_64-linux-gnu/libQtCore.so.4(_Z17qt_message_output9QtMsgTypePKc+ 0x102) [0x7f6ee7351912]
6: /usr/lib/x86_64-linux-gnu/libQtCore.so.4(+0x70c79) [0x7f6ee7351c79]
7: /usr/lib/x86_64-linux-gnu/libQtCore.so.4(_Z6qFatalPKcz+0x94) [0x7f6ee7352484]
8: akonadiserver() [0x41b344]
9: akonadiserver() [0x41510b]
10: akonadiserver() [0x4125cb]
11: /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf5) [0x7f6ee5859de5]
12: akonadiserver() [0x412ff8]
]
"
ProcessControl: Application 'akonadiserver' returned with exit code 255 (Unknown error)
Cannot remove old log file - running on a readonly filesystem maybe?
QIODevice:utChar: Closed device
"[
0: akonadiserver() [0x419828]
1: akonadiserver() [0x419ab2]
2: /lib/x86_64-linux-gnu/libc.so.6(+0x36ff0) [0x7f85afbe1ff0]
3: /lib/x86_64-linux-gnu/libc.so.6(gsignal+0x37) [0x7f85afbe1f77]
4: /lib/x86_64-linux-gnu/libc.so.6(abort+0x148) [0x7f85afbe55e8]
5: /usr/lib/x86_64-linux-gnu/libQtCore.so.4(_Z17qt_message_output9QtMsgTypePKc+ 0x102) [0x7f85b16c4912]
6: /usr/lib/x86_64-linux-gnu/libQtCore.so.4(+0x70c79) [0x7f85b16c4c79]
7: /usr/lib/x86_64-linux-gnu/libQtCore.so.4(_Z6qFatalPKcz+0x94) [0x7f85b16c5484]
8: akonadiserver() [0x41b344]
9: akonadiserver() [0x41510b]
10: akonadiserver() [0x4125cb]
11: /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf5) [0x7f85afbccde5]
12: akonadiserver() [0x412ff8]
]
"
ProcessControl: Application 'akonadiserver' returned with exit code 255 (Unknown error)
"akonadiserver" crashed too often and will not be restarted!

I have also received errors saying that the akonadi start was by user and not root. Starting as a sudoer gave similar results. If anyone can point me in the right direction, please do. Otherwise, it is back to my paper diary.

I use Thunderbird, which is why I never found out that KMail is also broken by Akonadi not starting.

[SteveRiley]

You should never run Akonadi as root -- that could be part of the problem.

As I just wrote in another thread here, Akonadi problems can sometimes be more easily diagnosed by folks at the KDE Forums. A number of Akonadi experts hang out there.

[kubicle]

You should never run Akonadi as root -- that could be part of the problem.

And it most certainly is, never start akonadi with sudo, it is meant to run as user. If you start akonadi with sudo, it can cause various akonadi related files in ~/.local and ~/.config (for example) to become owned by root (since the akonadi process will be running as root as it writes/modifies the files, but $HOME still points to the user's home directory), and if you later start akonadi as a user, the akonadi process does not have write access (depending on the permissions, possibly not even read access) to the files owned by root, hence:

Cannot remove old log file - running on a readonly filesystem maybe?

The first step is to reown your home folder files to your user:

sudo chown -R $(id -u):$(id -g) $HOME

Also, if you don't mind starting your akonadi configs afresh, I would recommend checking/removing akonadi related files in case starting akonadi with sudo has messed up the sockets as well. You could do the same thing mentioned in the first post of this thread:

rm -rfv ~/.config/akonadi/*
rm -rfv ~/.local/share/akonadi/*
rm -rfv ~/.kde/share/config/akonadi*

EDIT: probably better to also remove:

rm -rfv ~/.kde/share/apps/akonadi*

To start with a fresh configuration

[royleith]

In my defence, I only resorted to root when I was not able to restart akonadi as user.

I removed all the files you suggested and then stopped and started the service. I got warnings about setting the root and user mysql passwords, but the bin command was not installed in /usr.

I stopped and restarted akonadi and it seemed to start OK. KOrganiser launched with no problems. I have not formatted the home partition for several Kubuntu releases, now. I may have had permission errors from several issues ago. I know it is not a new problem for me with other programs including Wine.

I have not checked to ensure that akonadi starts on reboot, but, thanks to the help on this thread, I have an effective work-around.

Cheers

[kubicle]

In my defence, I only resorted to root when I was not able to restart akonadi as user.

Sure, I wasn't suggesting there wasn't a problem with your akonadi configs before, just that running akonadi with sudo will not fix those issues, and will create additional ownership issues on top of the original issues (effectively making things worse rather than better).