Akonadi: Difference between revisions
Add Akonadi troubleshoot tips, will be linked to from the Akonadi self-test dialog. |
Missed one sentence when moving from techbase. |
||
| Line 18: | Line 18: | ||
sudo aa-complain mysqld | sudo aa-complain mysqld | ||
sudo /etc/init.d/apparmor reload | sudo /etc/init.d/apparmor reload | ||
Note that you might be using Apparmor even if it does not show up in the process list. | |||
=== Environment Setup === | === Environment Setup === | ||
The Akoandi server searches for Akonadi agents and resources in the paths defined in the '''XDG_DATA_DIRS''' environment variable. If Akonadi complains about not finding agents or resources, check if this variable is set correctly. Also keep in mind that even if set in a current console session, it might not have been set when starting the server. Starting the server manually in the current console session excludes this cause. | The Akoandi server searches for Akonadi agents and resources in the paths defined in the '''XDG_DATA_DIRS''' environment variable. If Akonadi complains about not finding agents or resources, check if this variable is set correctly. Also keep in mind that even if set in a current console session, it might not have been set when starting the server. Starting the server manually in the current console session excludes this cause. | ||
Revision as of 16:37, 9 November 2008
Troubleshooting Tips
- When reporting problems with the Akonadi server, always include the comprehensive self-test report. This report can be obtained from the self-test dialog which shows up whenever the Akonadi server was unable to start successfully. You also can access this dialog via systemsettings -> Advanced -> Akonadi -> Server Configuration -> Test.
- Starting the Akonadi server manually on the command line can result in additional useful information. This can be done by running akonadictl start on a console. Similar, with akonadictl stop the Akonadi server can be stopped again.
Common Problems
Apparmor
Some distributions using Apparmor have it set up in a way that prevents Akonadi from running its internal database server. This can result in a variety of fuzzy error messages, including but not limited to the following:
- unknown error 255 when running akonadictl
- "DB error: 'Could not open required defaults file: /home/$username/.local/share/akonadi/mysql.conf"
You can solve this by running aa-complain mysqld with root privileges then reload apparmor. On KUbuntu this is:
sudo aa-complain mysqld sudo /etc/init.d/apparmor reload
Note that you might be using Apparmor even if it does not show up in the process list.
Environment Setup
The Akoandi server searches for Akonadi agents and resources in the paths defined in the XDG_DATA_DIRS environment variable. If Akonadi complains about not finding agents or resources, check if this variable is set correctly. Also keep in mind that even if set in a current console session, it might not have been set when starting the server. Starting the server manually in the current console session excludes this cause.