[kde-freebsd] Akonadi Server crashes upon start-up

[Jerry]

FreeBSD-8 / amd64 with KDE4

I just installed KDE. Everything appears to be working correctly with
the exception of the 'Akonadi Server'. It crashed immediatey upon
start-up. There is an 'akonadiserver.core' created. Below is a copy of
the report created when the server crashes. I am unable to figure out
how to go about correcting the problem.


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/gerard/.config/akonadi/akonadiserverrc':
[%General]
Driver=QMYSQL
SizeThreshold=4096
ExternalPayload=false

[QMYSQL]
Name=akonadi
Host=localhost
User=gerard
Password=blacktop
Options="UNIX_SOCKET=/home/gerard/.local/share/akonadi/db_misc/mysql.socket"
ServerPath=/usr/local/bin/mysqld_safe
StartServer=true

[QPSQL]
Name=akonadi
Host=
User=
Password=
Port=5432


Test 2:  SUCCESS
--------

MySQL server found.
Details: You currently have configured Akonadi to use the MySQL server
'/usr/local/bin/mysqld_safe'. 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:
cat: /var/db/mysql/scorpio.seibercom.net.pid: Permission denied
rm: /var/db/mysql/scorpio.seibercom.net.pid: Permission denied 100514
06:46:34 mysqld_safe Fatal error: Can't remove the pid
file: /var/db/mysql/scorpio.seibercom.net.pid Please remove it manually
and start /usr/local/bin/mysqld_safe again; mysqld daemon not started
/usr/local/bin/mysqld_safe: cannot
create /var/db/mysql/scorpio.seibercom.net.err: Permission denied
100514 06:46:34 mysqld_safe Logging to
'/var/db/mysql/scorpio.seibercom.net.err'.


Test 4:  SUCCESS
--------

No current MySQL error log found.
Details: The MySQL server did not report any errors during this startup
into '/home/gerard/.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='/usr/local/kde4/share/config/akonadi/mysql-global.conf'>/usr/local/kde4/share/config/akonadi/mysql-global.conf</a>.

File content of
'/usr/local/kde4/share/config/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
(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



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='/home/gerard/.local/share/akonadi/mysql.conf'>/home/gerard/.local/share/akonadi/mysql.conf</a>
and is readable.

File content of '/home/gerard/.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/local/kde4/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:  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 12:  SUCCESS
--------

Nepomuk search service uses an appropriate backend. 
Details: The Nepomuk search service uses one of the recommended
backends.

Test 13:  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 14:  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/local/kde4/share/akonadi/agents'. The
XDG_DATA_DIRS environment variable is set to
'/usr/local/kde4/share::/usr/share:/usr/local/share:/usr/local/share/gnome',
make sure this includes all paths where Akonadi agents are installed to.

Directory listing of '/usr/local/kde4/share/akonadi/agents':
birthdaysresource.desktop
contactsresource.desktop
icalresource.desktop
imapresource.desktop
kabcresource.desktop
kcalresource.desktop
knutresource.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/local/kde4/share::/usr/share:/usr/local/share:/usr/local/share/gnome'

Test 15:  SUCCESS
--------

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

Test 16:  SUCCESS
--------

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

Test 17:  SUCCESS
--------

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

Test 18:  SUCCESS
--------

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

-- 
Jerry
KDE-FreeBSD.user at seibercom.net

Disclaimer: off-list followups get on-list replies or get ignored.
Please do not ignore the Reply-To header.
__________________________________________________________________