Akonadi server process not registered at DBus
Linuxguy123
linuxguy123 at gmail.com
Sat Apr 11 17:14:59 UTC 2009
On Sat, 2009-04-11 at 09:53 -0700, Craig White wrote:
> On Sat, 2009-04-11 at 10:35 -0600, Linuxguy123 wrote:
> > I get an Akonadi error message when I log into my KDE session.
> >
> > A short while after the session starts, an Akonadi window appears with a
> > list of tasks that have occurred. The first item in the list marked as
> > an error is
> >
> > "Akonadi server process not registered at D-Bus"
> >
> > Frustratingly, the Akonadi error window disappears after being visible
> > for about 10 seconds and I can't get much more information than that.
> >
> > There is a button to copy the error message(s) to the clipboard, but it
> > doesn't seem to work.
> >
> > How do I troubleshoot/fix this problem ?
> ----
> assuming that you are not running gui as root which seems to cause some
> issues with akonadia, that seemed to be an issue with early versions of
> F10/KDE but I suspect that if you open systemsettings
>
> Advanced => Akondai Configuration => Akonodai Server Configuration
>
> and then click 'Test' button, you can see what the issues are and use
> this tool to fix if necessary.
So here is what it says when I invoke the test button. It now says that
its registered with D-Bus and everything is fine. Is it a race
condition ?
Akonadi Server Self-Test Report
===============================
Test 1: SUCCESS
--------
Database driver found.
Details: The QtSQL driver 'QMYSQL' is required by your current Akonadi
server configuration.
The following drivers are installed: QSQLITE, QMYSQL3, QMYSQL.
Make sure the required driver is installed.
File content of '/home/xxx/.config/akonadi/akonadiserverrc':
[%General]
Driver=QMYSQL
[QMYSQL]
Name=akonadi
User=
Password=
Options="UNIX_SOCKET=/home/xxx/.local/share/akonadi/db_misc/mysql.socket"
ServerPath=/usr/libexec/mysqld
StartServer=true
[Debug]
Tracer=null
Test 2: SUCCESS
--------
MySQL server found.
Details: You currently have configured Akonadi to use the MySQL server
'/usr/libexec/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: 090411 11:12:31 [Warning] option
'max_join_size': unsigned value 18446744073709551615 adjusted to
4294967295
090411 11:12:31 [Warning] option 'max_join_size': unsigned value
18446744073709551615 adjusted to 4294967295
/usr/libexec/mysqld Ver 5.0.77 for redhat-linux-gnu on i386 (Source
distribution)
Test 4: WARNING
--------
MySQL server log contains warnings.
Details: The MySQL server log file '<a
href='/home/xxx/.local/share/akonadi/db_data/mysql.err'>/home/xxx/.local/share/akonadi/db_data/mysql.err</a>' contains warnings.
File content of '/home/xxx/.local/share/akonadi/db_data/mysql.err':
090411 10:28:58 InnoDB: Started; log sequence number 0 146545
090411 10:29:01 [Warning] Can't open and lock time zone table: Table
'mysql.time_zone_leap_second' doesn't exist trying to live without them
090411 10:29:01 [Note] /usr/libexec/mysqld: ready for connections.
Version: '5.0.77-log' socket:
'/home/xxx/.local/share/akonadi/db_misc/mysql.socket' port: 0 Source
distribution
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 at 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
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=8M
innodb_flush_log_at_trx_commit=2
Test 6: SUCCESS
--------
MySQL server custom configuration found.
Details: The custom configuration for the MySQL server was found and is
readable at <a
href='/etc/akonadi/mysql-local.conf'>/etc/akonadi/mysql-local.conf</a>
File content of '/etc/akonadi/mysql-local.conf':
Test 7: SUCCESS
--------
MySQL server configuration is usable.
Details: The MySQL server configuration was found at <a
href='/home/xxx/.local/share/akonadi/mysql.conf'>/home/xxx/.local/share/akonadi/mysql.conf</a> and is readable.
File content of '/home/xxx/.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 at 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
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
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 Control: running
Akonadi Server: running
Test 9: 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 10: 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 11: 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 12: SUCCESS
--------
Resource agents found.
Details: At least one resource agent has been found.
Directory listing of '/usr/share/akonadi/agents':
distlistresource.desktop
icalresource.desktop
imaplibresource.desktop
kabcresource.desktop
kcalresource.desktop
knutresource.desktop
localbookmarksresource.desktop
maildirresource.desktop
mailthreaderagent.desktop
nepomukcontactfeeder.desktop
nepomukemailfeeder.desktop
nepomuktagresource.desktop
nntpresource.desktop
strigifeeder.desktop
vcarddirresource.desktop
vcardresource.desktop
Environment variable XDG_DATA_DIRS is set to
'/usr/share/kde-settings/kde-profile/default/share:/usr/local/share:/usr/share'
Test 13: SUCCESS
--------
No current Akonadi server error log found.
Details: The Akonadi server did not report any errors during its current
startup.
Test 14: ERROR
--------
Previous Akonadi server error log found.
Details: The Akonadi server did report error during its previous startup
into <a
href='/home/xxx/.local/share/akonadi/akonadiserver.error.old'>/home/xxx/.local/share/akonadi/akonadiserver.error.old</a>.
File content of
'/home/xxx/.local/share/akonadi/akonadiserver.error.old':
Control process died, committing suicide!
Test 15: SUCCESS
--------
No current Akonadi control error log found.
Details: The Akonadi control process did not report any errors during
its current startup.
Test 16: SUCCESS
--------
No previous Akonadi control error log found.
Details: The Akonadi control process did not report any errors during
its previous startup.
More information about the users
mailing list