Akonadi Error!

When i have installed akonadi i’ve restarted opensuse and on starting the DE, the akonadi configuration has started.

But i’ve get this error:
The driver QtSQL «QMYSQL» is required from the current configuration of the akonadi server.
The following drivers are installed: QSQLITE, QMYSQL3, QMYSQL.
Make sure that required drivers are installed

I have searched in some sites but i haven’t resolved this issue.

Anyone can help me??

Thanks a lot…

  • mola89,

I am not sure if it is an error. I saw the same message, but it works fine here: Akonadi imported data when I launched Kontact.

Uwe

Do you know a good guide or how-to for install and configure akonadi, in a way that it works properly??

Thanks…

  • mola89,

in KDE4.2 it is supposed to work out of the box. So far I’m just sitting here staring at it, and that seems to work okay.
Some stuff to read is here:
http://techbase.kde.org/Projects/PIM/Akonadi

Uwe

I too experience the same issue, and could not find any useful information at the link quoted above.

I keep getting not registered with d-bus error, I am at a loss. I remember when I first used KDE 4.0, there was an icon of Akonadi in the system tray. I then could not find any use for it, so I uninstalled it.

Now in KDE 4.2 I installed again and all I get is Akonadi server not functional. It says I need to add at least one resource, but nothing suggests how.

Can anyone please shed some light into this, or perhaps confirm that at this point Akonadi is still not fully usable.

Thanks in advance!

  • hermesrules

I suggest you create a test user account to play with it. Akonadi configuration is now in the Personal Settings in KDE, under the “Advanced” tab. What you can add there seems rather self explaining to me; go check it out.

Uwe

Thanks, Uwe!

I read through a lot of forums regarding Akonadi, and what I did was to delete the akonadiserverrc file. Upon restart of the Akonadi server, everything was recreated and now works. No more complaints, no d-bus problems, and I was able to add resources.

However, when I added an imap resource, the akonadi-imap process (not sure of exact name) ate all of my cpu. For about 10 minutes every now and then, I can hardly use the computer, even the mouse becomes slow to respond. Then it all returns to normal. Moreover, I could not find a way to use that resource from Akonadi in KMail… So I removed it.

I successfully added a Google calendar as an Akonadi resource, but I have yet to figure out why it appears as read only. It crashes every time I try to add an event through KOrganizer.

Is this normal?

i have the same cpu probs after update to 4.2.86. Akonadi eats 100% cpu (with kontact and kopete). The only solution right now that works is to stop akonadi server in kde configuration…

I am sick of these kabuki dances that I have to do whenever I install an updated distro, this time SuSE 11.3. I can’t get akonadi to work hence kmail is screwed up. I do not need this. If anyone has this problem and fixed it, I would like to hear about it. Meantime, I’m looking at Thunderbird.

"
0: akonadiserver(_Z11akBacktracev+0x39) [0x40c5d9]
1: akonadiserver() [0x40cb42]
2: /lib64/libc.so.6(+0x32a60) [0x7f7d4f902a60]
3: /lib64/libc.so.6(gsignal+0x35) [0x7f7d4f9029e5]
4: /lib64/libc.so.6(abort+0x186) [0x7f7d4f903ee6]
5: /usr/lib64/libQtCore.so.4(_Z17qt_message_output9QtMsgTypePKc+0x74) [0x7f7d50ae0984]
6: akonadiserver(_ZN15FileDebugStream9writeDataEPKcx+0xab) [0x40e45b]
7: /usr/lib64/libQtCore.so.4(_ZN9QIODevice5writeEPKcx+0x77) [0x7f7d50b6bc37]
8: /usr/lib64/libQtCore.so.4(+0x103026) [0x7f7d50b74026]
9: /usr/lib64/libQtCore.so.4(_ZN11QTextStreamD1Ev+0x3b) [0x7f7d50b7cefb]
10: /usr/lib64/libakonadiprivate.so.1(_ZN6QDebugD1Ev+0x4b) [0x7f7d50f3347b]
11: /usr/lib64/libakonadiprivate.so.1(_ZN7Akonadi13AkonadiServer25startMysqlDatabaseProcessEv+0x1c3a) [0x7f7d50f3c79a]
12: /usr/lib64/libakonadiprivate.so.1(_ZN7Akonadi13AkonadiServer20startDatabaseProcessEv+0x2e8) [0x7f7d50f426f8]
13: /usr/lib64/libakonadiprivate.so.1(_ZN7Akonadi13AkonadiServerC1EP7QObject+0x76) [0x7f7d50f42b26]
14: /usr/lib64/libakonadiprivate.so.1(_ZN7Akonadi13AkonadiServer8instanceEv+0x4a) [0x7f7d50f4422a]
15: akonadiserver(main+0x217) [0x406767]
16: /lib64/libc.so.6(__libc_start_main+0xfd) [0x7f7d4f8eeb7d]
17: akonadiserver() [0x406459]
]
"
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 ‘/root/.config/akonadi/akonadiserverrc’:
%General]
Driver=QMYSQL
SizeThreshold=4096
ExternalPayload=false

[QMYSQL]
Name=akonadi
Host=
User=root
Password=75thinfmysql
Optionst=“UNIX_SOCKET=/root/.local/share/akonadi/db_misc/mysql.socket”
ServerPath=/usr/sbin/mysqld
StartServer=true
Options=“UNIX_SOCKET=/root/.local/share/akonadi/db_misc/mysql.socket”

Test 2: SUCCESS

MySQL server found.
Details: You currently have 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 locations varies depending on the distribution.

Test 3: SUCCESS

MySQL server is executable.
Details: MySQL server found: 101117 18:19:46 [Warning] ‘–skip-locking’ is deprecated and will be removed in a future release. Please use ‘–skip-external-locking’ instead.
/usr/sbin/mysqld Ver 5.1.46-log for suse-linux-gnu on x86_64 (SUSE MySQL RPM)

Test 4: SUCCESS

No current MySQL error log found.
Details: The MySQL server did not report any errors during this startup into ‘/root/.local/share/akonadi/db_data/mysql.err’.

Test 5: 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=latin1
collation_server=latin1_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=1296000

Test 6: SKIP

MySQL server custom configuration not available.
Details: The custom configuration for the MySQL server was not found but is optional.

Test 7: SUCCESS

MySQL server configuration is usable.
Details: The MySQL server configuration was found at <a href=’/root/.local/share/akonadi/mysql.conf’>/root/.local/share/akonadi/mysql.conf</a> and is readable.

File content of ‘/root/.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=latin1
collation_server=latin1_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=1296000

Test 8: 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.3.1

Test 9: ERROR

Akonadi control process not registered at D-Bus.
Details: The Akonadi control process is not registered at D-Bus which typically means it was not started or encountered a fatal error during startup.

Test 10: ERROR

Akonadi server process not registered at D-Bus.
Details: The Akonadi server process is not registered at D-Bus which typically means it was not started or encountered a fatal error during startup.

Test 11: ERROR

Nepomuk search service not registered at D-Bus.
Details: The Nepomuk search service is not registered at D-Bus which typically means it was not started or encountered a fatal error during startup.

Test 12: 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 13: 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 to.

Directory listing of ‘/usr/share/akonadi/agents’:
birthdaysresource.desktop
contactsresource.desktop
icalresource.desktop
imapresource.desktop
kabcresource.desktop
kcalresource.desktop
kolabproxyresource.desktop
localbookmarksresource.desktop
maildirresource.desktop
maildispatcheragent.desktop
mboxresource.desktop
microblog.desktop
mtdummyresource.desktop
nepomukcalendarfeeder.desktop
nepomukcontactfeeder.desktop
nepomuktagresource.desktop
nntpresource.desktop
notesresource.desktop
pop3resource.desktop
vcarddirresource.desktop
vcardresource.desktop

Environment variable XDG_DATA_DIRS is set to ‘/usr/share:/etc/opt/kde3/share:/opt/kde3/share’

Test 14: ERROR

Current Akonadi server error log found.
Details: The Akonadi server did report error during startup into <a href=’/root/.local/share/akonadi/akonadiserver.error’>/root/.local/share/akonadi/akonadiserver.error</a>.

File content of ‘/root/.local/share/akonadi/akonadiserver.error’:
"
0: akonadiserver(_Z11akBacktracev+0x39) [0x40c5d9]
1: akonadiserver() [0x40cb42]
2: /lib64/libc.so.6(+0x32a60) [0x7f5dbbdd1a60]
3: /lib64/libc.so.6(gsignal+0x35) [0x7f5dbbdd19e5]
4: /lib64/libc.so.6(abort+0x186) [0x7f5dbbdd2ee6]
5: /usr/lib64/libQtCore.so.4(_Z17qt_message_output9QtMsgTypePKc+0x74) [0x7f5dbcfaf984]
6: akonadiserver(_ZN15FileDebugStream9writeDataEPKcx+0xab) [0x40e45b]
7: /usr/lib64/libQtCore.so.4(_ZN9QIODevice5writeEPKcx+0x77) [0x7f5dbd03ac37]
8: /usr/lib64/libQtCore.so.4(+0x103026) [0x7f5dbd043026]
9: /usr/lib64/libQtCore.so.4(_ZN11QTextStreamD1Ev+0x3b) [0x7f5dbd04befb]
10: /usr/lib64/libakonadiprivate.so.1(_ZN6QDebugD1Ev+0x4b) [0x7f5dbd40247b]
11: /usr/lib64/libakonadiprivate.so.1(_ZN7Akonadi13AkonadiServer25startMysqlDatabaseProcessEv+0x1c3a) [0x7f5dbd40b79a]
12: /usr/lib64/libakonadiprivate.so.1(_ZN7Akonadi13AkonadiServer20startDatabaseProcessEv+0x2e8) [0x7f5dbd4116f8]
13: /usr/lib64/libakonadiprivate.so.1(_ZN7Akonadi13AkonadiServerC1EP7QObject+0x76) [0x7f5dbd411b26]
14: /usr/lib64/libakonadiprivate.so.1(_ZN7Akonadi13AkonadiServer8instanceEv+0x4a) [0x7f5dbd41322a]
15: akonadiserver(main+0x217) [0x406767]
16: /lib64/libc.so.6(__libc_start_main+0xfd) [0x7f5dbbdbdb7d]
17: akonadiserver() [0x406459]
]
"

Test 15: ERROR

Previous Akonadi server error log found.
Details: The Akonadi server did report error during its previous startup into <a href=’/root/.local/share/akonadi/akonadiserver.error.old’>/root/.local/share/akonadi/akonadiserver.error.old</a>.

File content of ‘/root/.local/share/akonadi/akonadiserver.error.old’:
"
0: akonadiserver(_Z11akBacktracev+0x39) [0x40c5d9]
1: akonadiserver() [0x40cb42]
2: /lib64/libc.so.6(+0x32a60) [0x7f74196b7a60]
3: /lib64/libc.so.6(gsignal+0x35) [0x7f74196b79e5]
4: /lib64/libc.so.6(abort+0x186) [0x7f74196b8ee6]
5: /usr/lib64/libQtCore.so.4(_Z17qt_message_output9QtMsgTypePKc+0x74) [0x7f741a895984]
6: akonadiserver(_ZN15FileDebugStream9writeDataEPKcx+0xab) [0x40e45b]
7: /usr/lib64/libQtCore.so.4(_ZN9QIODevice5writeEPKcx+0x77) [0x7f741a920c37]
8: /usr/lib64/libQtCore.so.4(+0x103026) [0x7f741a929026]
9: /usr/lib64/libQtCore.so.4(_ZN11QTextStreamD1Ev+0x3b) [0x7f741a931efb]
10: /usr/lib64/libakonadiprivate.so.1(_ZN6QDebugD1Ev+0x4b) [0x7f741ace847b]
11: /usr/lib64/libakonadiprivate.so.1(_ZN7Akonadi13AkonadiServer25startMysqlDatabaseProcessEv+0x1c3a) [0x7f741acf179a]
12: /usr/lib64/libakonadiprivate.so.1(_ZN7Akonadi13AkonadiServer20startDatabaseProcessEv+0x2e8) [0x7f741acf76f8]
13: /usr/lib64/libakonadiprivate.so.1(_ZN7Akonadi13AkonadiServerC1EP7QObject+0x76) [0x7f741acf7b26]
14: /usr/lib64/libakonadiprivate.so.1(_ZN7Akonadi13AkonadiServer8instanceEv+0x4a) [0x7f741acf922a]
15: akonadiserver(main+0x217) [0x406767]
16: /lib64/libc.so.6(__libc_start_main+0xfd) [0x7f74196a3b7d]
17: akonadiserver() [0x406459]
]
"

Test 16: SUCCESS

No current Akonadi control error log found.
Details: The Akonadi control process did not report any errors during its current startup.

Test 17: SUCCESS

No previous Akonadi control error log found.
Details: The Akonadi control process did not report any errors during its previous startup.

Never mind… I was logged in as “root”. when I logged in under another user, it worked. Too much time as an admin, I guess.