Well after my upgrade to 12.1 Kmail2 is giving me an error.
The Akondai Personal Information Management Service is not operational
I have Googled a great deal and deleted the Akondai folders in /local/share and config and I still get the error. I cannot delete or add any resources as soon as I try the Akondai Server tries to run but cannot. Any help or advice would be much appreciated.
A test reveals the following.
Akonadi Server Self-Test Report
Test 1: SUCCESS
Database driver found.
Details: The QtSQL driver ‘QMYSQL’ is required by your current Akonadi server configuration and was found on your system.
File content of ‘/home/chris/.config/akonadi/akonadiserverrc’:
%General]
Driver=QMYSQL
[QMYSQL]
Name=akonadi
Host=
Options=“UNIX_SOCKET=/home/chris/.local/share/akonadi/socket-vox/mysql.socket”
ServerPath=/usr/sbin/mysqld
StartServer=true
[Debug]
Tracer=null
Test 2: SUCCESS
Akonadi is not running as root
Details: Akonadi is not running as a root/administrator user, which is the recommended setup for a secure system.
Test 3: SUCCESS
MySQL server found.
Details: You have currently configured Akonadi to use the MySQL server ‘/usr/sbin/mysqld’.
Make sure you have the MySQL server installed, set the correct path and ensure you have the necessary read and execution rights on the server executable. The server executable is typically called ‘mysqld’; its location varies depending on the distribution.
Test 4: SUCCESS
MySQL server is executable.
Details: MySQL server found: /usr/sbin/mysqld Ver 5.5.16 for Linux on i686 (Source distribution)
Test 5: SUCCESS
MySQL server log contains no errors.
Details: The MySQL server log file ‘<a href=’/home/chris/.local/share/akonadi/db_data/mysql.err’>/home/chris/.local/share/akonadi/db_data/mysql.err</a>’ does not contain any errors or warnings.
File content of ‘/home/chris/.local/share/akonadi/db_data/mysql.err’:
111116 23:57:44 InnoDB: The InnoDB memory heap is disabled
111116 23:57:44 InnoDB: Mutexes and rw_locks use GCC atomic builtins
111116 23:57:44 InnoDB: Compressed tables use zlib 1.2.5
111116 23:57:44 InnoDB: Initializing buffer pool, size = 80.0M
111116 23:57:44 InnoDB: Completed initialization of buffer pool
111116 23:57:44 InnoDB: highest supported file format is Barracuda.
111116 23:57:44 InnoDB: Waiting for the background threads to start
111116 23:57:45 InnoDB: 1.1.8 started; log sequence number 1701343
111116 23:57:45 [Note] /usr/sbin/mysqld: ready for connections.
Version: ‘5.5.16’ socket: ‘/home/chris/.local/share/akonadi/socket-vox/mysql.socket’ port: 0 Source distribution
Test 6: SUCCESS
MySQL server default configuration found.
Details: The default configuration for the MySQL server was found and is readable at <a href=’/etc/akonadi/mysql-global.conf’>/etc/akonadi/mysql-global.conf</a>.
File content of ‘/etc/akonadi/mysql-global.conf’:
Global Akonadi MySQL server settings,
These settings can be adjusted using $HOME/.config/akonadi/mysql-local.conf
Based on advice by Kris Köhntopp <kris@mysql.com>
[mysqld]
skip_grant_tables
skip_networking
strict query parsing/interpretation
TODO: make Akonadi work with those settings enabled
#sql_mode=strict_trans_tables,strict_all_tables,strict_error_for_division_by_zero,no_auto_create_user,no_auto_value_on_zero,no_engine_substitution,no_zero_date,no_zero_in_date,only_full_group_by,pipes_as_concat
#sql_mode=strict_trans_tables
use InnoDB for transactions and better crash recovery
default_storage_engine=innodb
case-insensitive table names, avoids trouble on windows
lower_case_table_names=1
character_set_server=utf8
collation_server=utf8_general_ci
table_cache=200
thread_cache_size=3
#log_bin=mysql-bin
#expire_logs_days=3
#sync_bin_log=0
error log file name, relative to datadir
log_error=mysql.err
log_warnings=2
log all queries, useful for debugging but generates an enormous amount of data
#log=mysql.full
log queries slower than n seconds, log file name relative to datadir (for debugging only)
#log_slow_queries=mysql.slow
#long_query_time=1
log queries not using indices, debug only, disable for production use
#log_queries_not_using_indexes=1
maximum blob size
max_allowed_packet=32M
max_connections=256
makes sense when having the same query multiple times
makes no sense with prepared statements and/or transactions
query_cache_type=0
query_cache_size=0
innodb_file_per_table=1
innodb_log_buffer_size=1M
innodb_additional_mem_pool_size=1M
messure database size and adjust
SELECT sum(data_length) as bla, sum(index_length) as blub FROM information_schema.tables WHERE table_schema not in (“mysql”, “information_schema”);
innodb_buffer_pool_size=80M
size of average write burst, keep Innob_log_waits small, keep Innodb_buffer_pool_wait_free small (see show global status like “inno%”, show global variables)
innodb_log_file_size=64M
innodb_flush_log_at_trx_commit=2
Do not drop the connection to the DB after 8 hours of inactivity
wait_timeout=31536000
[client]
default-character-set=utf8
Test 7: SKIP
MySQL server custom configuration not available.
Details: The custom configuration for the MySQL server was not found but is optional.
Test 8: SUCCESS
MySQL server configuration is usable.
Details: The MySQL server configuration was found at <a href=’/home/chris/.local/share/akonadi/mysql.conf’>/home/chris/.local/share/akonadi/mysql.conf</a> and is readable.
File content of ‘/home/chris/.local/share/akonadi/mysql.conf’:
Global Akonadi MySQL server settings,
These settings can be adjusted using $HOME/.config/akonadi/mysql-local.conf
Based on advice by Kris Köhntopp <kris@mysql.com>
[mysqld]
skip_grant_tables
skip_networking
strict query parsing/interpretation
TODO: make Akonadi work with those settings enabled
#sql_mode=strict_trans_tables,strict_all_tables,strict_error_for_division_by_zero,no_auto_create_user,no_auto_value_on_zero,no_engine_substitution,no_zero_date,no_zero_in_date,only_full_group_by,pipes_as_concat
#sql_mode=strict_trans_tables
use InnoDB for transactions and better crash recovery
default_storage_engine=innodb
case-insensitive table names, avoids trouble on windows
lower_case_table_names=1
character_set_server=utf8
collation_server=utf8_general_ci
table_cache=200
thread_cache_size=3
#log_bin=mysql-bin
#expire_logs_days=3
#sync_bin_log=0
error log file name, relative to datadir
log_error=mysql.err
log_warnings=2
log all queries, useful for debugging but generates an enormous amount of data
#log=mysql.full
log queries slower than n seconds, log file name relative to datadir (for debugging only)
#log_slow_queries=mysql.slow
#long_query_time=1
log queries not using indices, debug only, disable for production use
#log_queries_not_using_indexes=1
maximum blob size
max_allowed_packet=32M
max_connections=256
makes sense when having the same query multiple times
makes no sense with prepared statements and/or transactions
query_cache_type=0
query_cache_size=0
innodb_file_per_table=1
innodb_log_buffer_size=1M
innodb_additional_mem_pool_size=1M
messure database size and adjust
SELECT sum(data_length) as bla, sum(index_length) as blub FROM information_schema.tables WHERE table_schema not in (“mysql”, “information_schema”);
innodb_buffer_pool_size=80M
size of average write burst, keep Innob_log_waits small, keep Innodb_buffer_pool_wait_free small (see show global status like “inno%”, show global variables)
innodb_log_file_size=64M
innodb_flush_log_at_trx_commit=2
Do not drop the connection to the DB after 8 hours of inactivity
wait_timeout=31536000
[client]
default-character-set=utf8
Test 9: SUCCESS
akonadictl found and usable
Details: The program ‘/usr/bin/akonadictl’ to control the Akonadi server was found and could be executed successfully.
Result:
Akonadi 1.6.2
Test 10: SUCCESS
Akonadi control process registered at D-Bus.
Details: The Akonadi control process is registered at D-Bus which typically indicates it is operational.
Test 11: SUCCESS
Akonadi server process registered at D-Bus.
Details: The Akonadi server process is registered at D-Bus which typically indicates it is operational.
Test 12: SUCCESS
Nepomuk search service registered at D-Bus.
Details: The Nepomuk search service is registered at D-Bus which typically indicates it is operational.
Test 13: SUCCESS
Nepomuk search service uses an appropriate backend.
Details: The Nepomuk search service uses one of the recommended backends.
Test 14: SKIP
Protocol version check not possible.
Details: Without a connection to the server it is not possible to check if the protocol version meets the requirements.
Test 15: ERROR
No resource agents found.
Details: No resource agents have been found, Akonadi is not usable without at least one. This usually means that no resource agents are installed or that there is a setup problem. The following paths have been searched: ‘/usr/share/akonadi/agents’. The XDG_DATA_DIRS environment variable is set to ‘/usr/share:/etc/opt/kde3/share:/opt/kde3/share’; make sure this includes all paths where Akonadi agents are installed.
Directory listing of ‘/usr/share/akonadi/agents’:
nepomukemailfeeder.desktop
Environment variable XDG_DATA_DIRS is set to ‘/usr/share:/etc/opt/kde3/share:/opt/kde3/share’
Test 16: SUCCESS
No current Akonadi server error log found.
Details: The Akonadi server did not report any errors during its current startup.
Test 17: SUCCESS
No previous Akonadi server error log found.
Details: The Akonadi server did not report any errors during its previous startup.
Test 18: SUCCESS
No current Akonadi control error log found.
Details: The Akonadi control process did not report any errors during its current startup.
Test 19: SUCCESS
No previous Akonadi control error log found.
Details: The Akonadi control process did not report any errors during its previous startup.
See “Test 15”.
What do you get with:
ls -lh /usr/share/akonadi/agents
total 116K
-rw-r–r-- 1 root root 350 Oct 30 03:14 akonotesresource.desktop
-rw-r–r-- 1 root root 433 Oct 30 03:14 birthdaysresource.desktop
-rw-r–r-- 1 root root 261 Oct 30 03:14 calendarsearchagent.desktop
-rw-r–r-- 1 root root 367 Oct 30 03:14 contactsresource.desktop
-rw-r–r-- 1 root root 521 Oct 30 03:14 davgroupwareresource.desktop
-rw-r–r-- 1 root root 480 Oct 30 03:14 icalresource.desktop
-rw-r–r-- 1 root root 284 Oct 30 03:14 imapresource.desktop
-rw-r–r-- 1 root root 599 Oct 30 03:14 invitationsagent.desktop
-rw-r–r-- 1 root root 353 Oct 30 03:14 kabcresource.desktop
-rw-r–r-- 1 root root 476 Oct 30 03:14 kcalresource.desktop
-rw-r–r-- 1 root root 289 Oct 30 03:14 kdeaccountsresource.desktop
-rw-r–r-- 1 root root 612 Oct 30 03:14 kolabproxyresource.desktop
-rw-r–r-- 1 root root 300 Oct 30 03:14 localbookmarksresource.desktop
-rw-r–r-- 1 root root 319 Oct 30 03:14 maildirresource.desktop
-rw-r–r-- 1 root root 268 Oct 30 03:14 maildispatcheragent.desktop
-rw-r–r-- 1 root root 305 Oct 30 03:14 mboxresource.desktop
-rw-r–r-- 1 root root 325 Oct 30 03:14 microblog.desktop
-rw-r–r-- 1 root root 306 Oct 30 03:14 mixedmaildirresource.desktop
-rw-r–r-- 1 root root 357 Oct 30 03:14 mtdummyresource.desktop
-rw-r–r-- 1 root root 339 Oct 30 03:14 nepomukcalendarfeeder.desktop
-rw-r–r-- 1 root root 354 Oct 30 03:14 nepomukcontactfeeder.desktop
-rw-r–r-- 1 root root 322 Oct 30 03:27 nepomukemailfeeder.desktop
-rw-r–r-- 1 root root 355 Oct 30 03:14 nepomuktagresource.desktop
-rw-r–r-- 1 root root 306 Oct 30 03:14 nntpresource.desktop
-rw-r–r-- 1 root root 316 Oct 30 03:14 notesresource.desktop
-rw-r–r-- 1 root root 574 Oct 30 03:14 openxchangeresource.desktop
-rw-r–r-- 1 root root 283 Oct 30 03:14 pop3resource.desktop
-rw-r–r-- 1 root root 295 Oct 30 03:14 vcarddirresource.desktop
-rw-r–r-- 1 root root 308 Oct 30 03:14 vcardresource.desktop
This thing is driving me nuts.
I don’t know how I got it working but I did finally. In The Resource I can add my address book but cannot remove the read only attribute so I can use it. I mean I uncheck it and try to use it as standard but the attribute comes back? Anyone got any ideas?
> Any help or advice would be much appreciated.
i think all you needed to do was have patience…and a lot of it…see
the post i just made to http://forums.opensuse.org/showthread.php?t=467857
–
DD http://gplus.to/DenverD
openSUSE®, the “German Automobiles” of operating systems
You might be right I am not a patient person. I did however get everything sorted out and now I have my system running just like before. I would like to sincerely thank everyone here who offered advice and help. As I said before one of the biggest reasons to stick with a distro is the community and openSUSE has a great community.