[NIS, NFS] akonadi fails to start

[Craig Magina]

I'll attach the log output it gave me plus the failure output from akonadi_control. I believe this is an issue due to my machine's setup. My user is a NIS user with an NFS home directory, which I believe is causing permission issues for akonadiserver. Any help in working around this would be great.

This is on a fully updated, as of 04-22-2009, Kubuntu 9.04 amd64 install.

[Harald Sitter (apachelogger)]

Hey Craig.

Please try if turning off apparmor makes akonadi start properly.
You can turn it off by issuing the following command in a terminal:
sudo /etc/init.d/apparmor stop

Even though it is possible that Akonadi/MySQL have a problem with NFS, I personally would suspect apparmor as problem.

Have a nice day :)

[Craig Magina (craig.magina)]

Thanks, akonadi_control worked after stopping apparmor. I figured it was NFS due to both my home desktop and laptop not having this issue even though they were installed using the same Kubuntu 9.04 beta CD. Is it know which apparmor rule is broken?

[Timo Aaltonen (tjaalton)]

The apparmor profile is shipped by akonadi, so please fix it.

[Thomas Ohms (tohms)]

Wouldn't say it's a bug with app armor profile as the one in package looks good to me:
@{HOME}/.local/share/akonadi/** rwk,

But the error in Craig's akonadi_control output:
stderr: "Could not open required defaults file: /h/cmagina/.local/share/akonadi//mysql.conf

See the 2 slashes?!

Otherwise: Craig what's the output of "echo $HOME"?

[Craig Magina (craig.magina)]

I noticed the double slash as well. If my memory serves me right, it was located in one of the config scripts. I removed the extra slash, but that didn't solve it.

Here is my 'echo $HOME'
 /h/cmagina

[Thomas Ohms (tohms)]

Craig, can you test the following:

Stop akonadi, reload apparmor profiles, start akonadi.

If you get same error, try 'aa-complain mysqld-akonadi', reload apparmor profiles and try to start akonadi again.

What's the result?

[Benjamin Geese (ben-8409)]

i've had the same problems as craig. although i never touched apparmor oder akondi configuration before, akonadi kept on failing to start.

disabling apparmor fixed that.
after that, i tried the steps thomas mentioned (aa-complain mysqld-akonadi, reloading apparmor profiles and then restaerting akonadi) which actually fixed the problem for me!

now even kolab works like a charms. thanks

[Thomas Ohms (tohms)]

Benjamin,
can you attach output of Akonadi logs here!?

[Jamie Strandboge (jdstrand)]

Does adjusting the @{HOME} tunable fix this for you? Please review https://wiki.ubuntu.com/DebuggingApparmor#Adjusting%20Tunables as well as the information and solution in bug #447292.

[Craig Magina (craig.magina)]

Adding my nfs mount home directory to the tunables fixed the issue.

[Joerg Delker (ubuntu-delker)]

I just bumped into this issue, too - having NFS homedirs under /shared/home.

Adjusting the apparmor tunables "home" as posted in comment #11 fixes this problem!
Thus, this isn't an akonadi issue anymore.

[Harald Sitter (apachelogger)]

So, what do we do?
This cannot be fixed by akonadi's apparmor config but must be resolved in apparmor, in case it can even be resolved some way.

Moving bug over to apparmor, in any case there is nothing akonadi can do about this.

[Jamie Strandboge (jdstrand)]

Marking Won't Fix for Jaunty

[Jamie Strandboge (jdstrand)]

Marking Fix Released since using akonadi on NFS is usable as long as the home tunable is set. In Lucid and Maverick, this tunable is adjusted on upgrade and also settable via debconf.