Ubuntu
akonadi package

Akonadi personal information management service not operational after upgrading

Bug #1448345 reported by Michael Lynch
32
This bug affects 6 people
Affects Status Importance Assigned to Milestone
akonadi (Ubuntu)
Confirmed
Medium
Unassigned

Bug Description

Last night, I upgraded from Ubuntu 14.10 to Ubuntu 15.04.
Upon logging in, I found that I no longer have the KDE Plasma desktop available.
Then, when trying to open Kontact, I got the following error message: "The Akonadi personal information management service is not operational."

I was able to reinstall the Plasma desktop, and it seems to be working well, but the problem with Kontact is persisting.
Below is the report. Please advise what steps I can take; I rely quite heavily on data in Kontact, which at this time I am unable to access easily.

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/michael/.config/akonadi/akonadiserverrc':
[%General]
Driver=QMYSQL

[QMYSQL]
Name=akonadi
Host=
Options="UNIX_SOCKET=/tmp/akonadi-michael.D0cxKV/mysql.socket"
ServerPath=/usr/sbin/mysqld-akonadi
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-akonadi'.
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.6.24-0ubuntu2 for debian-linux-gnu on x86_64 ((Ubuntu))

Test 5: ERROR
--------

MySQL server log contains errors.
Details: The MySQL server error log file &apos;<a href='/home/michael/.local/share/akonadi/db_data/mysql.err'>/home/michael/.local/share/akonadi/db_data/mysql.err</a>&apos; contains errors.

File content of '/home/michael/.local/share/akonadi/db_data/mysql.err':
2015-04-24 19:15:57 25465 [Note] Plugin 'FEDERATED' is disabled.
2015-04-24 19:15:57 7fb52b594740 InnoDB: Warning: Using innodb_additional_mem_pool_size is DEPRECATED. This option may be removed in future releases, together with the option innodb_use_sys_malloc and with the InnoDB's internal memory allocator.
2015-04-24 19:15:57 25465 [Note] InnoDB: Using atomics to ref count buffer pool pages
2015-04-24 19:15:57 25465 [Note] InnoDB: The InnoDB memory heap is disabled
2015-04-24 19:15:57 25465 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2015-04-24 19:15:57 25465 [Note] InnoDB: Memory barrier is not used
2015-04-24 19:15:57 25465 [Note] InnoDB: Compressed tables use zlib 1.2.8
2015-04-24 19:15:57 25465 [Note] InnoDB: Using Linux native AIO
2015-04-24 19:15:57 25465 [Note] InnoDB: Using CPU crc32 instructions
2015-04-24 19:15:57 25465 [Note] InnoDB: Initializing buffer pool, size = 80.0M
2015-04-24 19:15:57 25465 [Note] InnoDB: Completed initialization of buffer pool
2015-04-24 19:15:57 25465 [Note] InnoDB: Highest supported file format is Barracuda.
2015-04-24 19:15:57 25465 [Note] InnoDB: The log sequence numbers 694421054 and 694421054 in ibdata files do not match the log sequence number 791222025 in the ib_logfiles!
2015-04-24 19:15:57 25465 [Note] InnoDB: Database was not shutdown normally!
2015-04-24 19:15:57 25465 [Note] InnoDB: Starting crash recovery.
2015-04-24 19:15:57 25465 [Note] InnoDB: Reading tablespace information from the .ibd files...
2015-04-24 19:15:57 25465 [Note] InnoDB: Restoring possible half-written data pages
2015-04-24 19:15:57 25465 [Note] InnoDB: from the doublewrite buffer...
23:15:57 UTC - mysqld got signal 11 ;
This could be because you hit a bug. It is also possible that this binary
or one of the libraries it was linked against is corrupt, improperly built,
or misconfigured. This error can also be caused by malfunctioning hardware.
We will try our best to scrape up some info that will hopefully help
diagnose the problem, but since we have already crashed,
something is definitely wrong and this may fail.

key_buffer_size=16384
read_buffer_size=131072
max_used_connections=0
max_threads=256
thread_count=0
connection_count=0
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 101584 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x0
Attempting backtrace. You can use the following information to find out
where mysqld died. If you see no messages after this, something went
terribly wrong...
stack_bottom = 0 thread_stack 0x40000
/usr/sbin/mysqld(my_print_stacktrace+0x3b)[0x8e09db]
/usr/sbin/mysqld(handle_fatal_signal+0x36a)[0x64338a]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x10d10)[0x7fb52a736d10]
/usr/sbin/mysqld[0xa9d1c1]
/usr/sbin/mysqld[0xa9ea18]
/usr/sbin/mysqld[0xa0fa20]
/usr/sbin/mysqld[0x94d274]
/usr/sbin/mysqld(_Z24ha_initialize_handlertonP13st_plugin_int+0x48)[0x57da08]
/usr/sbin/mysqld[0x6d27c5]
/usr/sbin/mysqld(_Z11plugin_initPiPPci+0x868)[0x6d8f08]
/usr/sbin/mysqld(_Z11mysqld_mainiPPc+0x925)[0x575a05]
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf0)[0x7fb529d65a40]
/usr/sbin/mysqld(_start+0x29)[0x569eb9]
The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
information that should help you find out what is causing the crash.

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 <email address hidden>
#
[mysqld]

# 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

# DEBUGGING:
# 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
#
# mesure database size and adjust innodb_buffer_pool_size
# SELECT sum(data_length) as bla, sum(index_length) as blub FROM information_schema.tables WHERE table_schema not in ("mysql", "information_schema");

# NOTES:
# Keep Innob_log_waits and keep Innodb_buffer_pool_wait_free small (see show global status like "inno%", show global variables)

#expire_logs_days=3

#sync_bin_log=0

# Use UTF-8 encoding for tables
character_set_server=utf8
collation_server=utf8_general_ci

# use InnoDB for transactions and better crash recovery
default_storage_engine=innodb

# memory pool InnoDB uses to store data dictionary information and other internal data structures (default:1M)
# Deprecated in MySQL >= 5.6.3
innodb_additional_mem_pool_size=1M

# memory buffer InnoDB uses to cache data and indexes of its tables (default:128M)
# Larger values means less I/O
innodb_buffer_pool_size=80M

# Create a .ibd file for each table (default:0)
innodb_file_per_table=1

# Write out the log buffer to the log file at each commit (default:1)
innodb_flush_log_at_trx_commit=2

# Buffer size used to write to the log files on disk (default:1M for builtin, 8M for plugin)
# larger values means less I/O
innodb_log_buffer_size=1M

# Size of each log file in a log group (default:5M) larger means less I/O but more time for recovery.
innodb_log_file_size=64M

# # error log file name, relative to datadir (default:hostname.err)
log_error=mysql.err

# print warnings and connection errors (default:1)
log_warnings=2

# Convert table named to lowercase
lower_case_table_names=1

# Maximum size of one packet or any generated/intermediate string. (default:1M)
max_allowed_packet=32M

# Maximum simultaneous connections allowed (default:100)
max_connections=256

# The two options below make no sense with prepared statements and/or transactions
# (make sense when having the same query multiple times)

# Memory allocated for caching query results (default:0 (disabled))
query_cache_size=0

# Do not cache results (default:1)
query_cache_type=0

# Do not use the privileges mechanisms
skip_grant_tables

# Do not listen for TCP/IP connections at all
skip_networking

# The number of open tables for all threads. (default:64)
table_open_cache=200

# How many threads the server should cache for reuse (default:0)
thread_cache_size=3

# wait 365d before dropping the DB connection (default:8h)
wait_timeout=31536000

# We use InnoDB, so don't let MyISAM eat up memory
key_buffer_size=16K

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

File content of '/home/michael/.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 <email address hidden>
#
[mysqld]

# 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

# DEBUGGING:
# 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
#
# mesure database size and adjust innodb_buffer_pool_size
# SELECT sum(data_length) as bla, sum(index_length) as blub FROM information_schema.tables WHERE table_schema not in ("mysql", "information_schema");

# NOTES:
# Keep Innob_log_waits and keep Innodb_buffer_pool_wait_free small (see show global status like "inno%", show global variables)

#expire_logs_days=3

#sync_bin_log=0

# Use UTF-8 encoding for tables
character_set_server=utf8
collation_server=utf8_general_ci

# use InnoDB for transactions and better crash recovery
default_storage_engine=innodb

# memory pool InnoDB uses to store data dictionary information and other internal data structures (default:1M)
# Deprecated in MySQL >= 5.6.3
innodb_additional_mem_pool_size=1M

# memory buffer InnoDB uses to cache data and indexes of its tables (default:128M)
# Larger values means less I/O
innodb_buffer_pool_size=80M

# Create a .ibd file for each table (default:0)
innodb_file_per_table=1

# Write out the log buffer to the log file at each commit (default:1)
innodb_flush_log_at_trx_commit=2

# Buffer size used to write to the log files on disk (default:1M for builtin, 8M for plugin)
# larger values means less I/O
innodb_log_buffer_size=1M

# Size of each log file in a log group (default:5M) larger means less I/O but more time for recovery.
innodb_log_file_size=64M

# # error log file name, relative to datadir (default:hostname.err)
log_error=mysql.err

# print warnings and connection errors (default:1)
log_warnings=2

# Convert table named to lowercase
lower_case_table_names=1

# Maximum size of one packet or any generated/intermediate string. (default:1M)
max_allowed_packet=32M

# Maximum simultaneous connections allowed (default:100)
max_connections=256

# The two options below make no sense with prepared statements and/or transactions
# (make sense when having the same query multiple times)

# Memory allocated for caching query results (default:0 (disabled))
query_cache_size=0

# Do not cache results (default:1)
query_cache_type=0

# Do not use the privileges mechanisms
skip_grant_tables

# Do not listen for TCP/IP connections at all
skip_networking

# The number of open tables for all threads. (default:64)
table_open_cache=200

# How many threads the server should cache for reuse (default:0)
thread_cache_size=3

# wait 365d before dropping the DB connection (default:8h)
wait_timeout=31536000

# We use InnoDB, so don't let MyISAM eat up memory
key_buffer_size=16K

[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.13.0

Test 10: 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 11: 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 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/plasma:/usr/local/share/:/usr/share/'; make sure this includes all paths where Akonadi agents are installed.

Directory listing of '/usr/share/akonadi/agents':
akonadibalooindexingagent.desktop
akonadinepomukfeederagent.desktop
akonotesresource.desktop
archivemailagent.desktop
birthdaysresource.desktop
contactsresource.desktop
davgroupwareresource.desktop
facebookresource.desktop
folderarchiveagent.desktop
followupreminder.desktop
googlecalendarresource.desktop
googlecontactsresource.desktop
icaldirresource.desktop
icalresource.desktop
imapresource.desktop
invitationsagent.desktop
kabcresource.desktop
kalarmdirresource.desktop
kalarmresource.desktop
kcalresource.desktop
kdeaccountsresource.desktop
kolabproxyresource.desktop
kolabresource.desktop
localbookmarksresource.desktop
maildirresource.desktop
maildispatcheragent.desktop
mailfilteragent.desktop
mboxresource.desktop
migrationagent.desktop
mixedmaildirresource.desktop
mtdummyresource.desktop
newmailnotifieragent.desktop
nntpresource.desktop
notesagent.desktop
notesresource.desktop
openxchangeresource.desktop
pop3resource.desktop
sendlateragent.desktop
vcarddirresource.desktop
vcardresource.desktop

Environment variable XDG_DATA_DIRS is set to '/usr/share/plasma:/usr/local/share/:/usr/share/'

Test 14: ERROR
--------

Current Akonadi server error log found.
Details: The Akonadi server reported errors during its current startup. The log can be found in <a href='/home/michael/.local/share/akonadi/akonadiserver.error'>/home/michael/.local/share/akonadi/akonadiserver.error</a>.

File content of '/home/michael/.local/share/akonadi/akonadiserver.error':
Database process exited unexpectedly during initial connection!
executable: "/usr/sbin/mysqld-akonadi"
arguments: ("--defaults-file=/home/michael/.local/share/akonadi/mysql.conf", "--datadir=/home/michael/.local/share/akonadi/db_data/", "--socket=/tmp/akonadi-michael.D0cxKV/mysql.socket")
stdout: ""
stderr: "2015-04-24 19:15:57 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
2015-04-24 19:15:57 0 [Note] /usr/sbin/mysqld (mysqld 5.6.24-0ubuntu2) starting as process 25465 ...
"
exit code: 1
process error: "Process operation timed out"
"[
0: akonadiserver() [0x418c8a]
1: akonadiserver() [0x418f04]
2: /lib/x86_64-linux-gnu/libc.so.6(+0x352f0) [0x7fc2d06e92f0]
3: /lib/x86_64-linux-gnu/libc.so.6(gsignal+0x37) [0x7fc2d06e9267]
4: /lib/x86_64-linux-gnu/libc.so.6(abort+0x16a) [0x7fc2d06eaeca]
5: /usr/lib/x86_64-linux-gnu/libQtCore.so.4(_Z17qt_message_output9QtMsgTypePKc+0x12a) [0x7fc2d1f13a8a]
6: akonadiserver() [0x41ad0d]
7: /usr/lib/x86_64-linux-gnu/libQtCore.so.4(_ZN9QIODevice5writeEPKcx+0x8a) [0x7fc2d1fb330a]
8: /usr/lib/x86_64-linux-gnu/libQtCore.so.4(+0x121155) [0x7fc2d1fc3155]
9: /usr/lib/x86_64-linux-gnu/libQtCore.so.4(_ZN11QTextStreamD1Ev+0x31) [0x7fc2d1fcbab1]
10: akonadiserver() [0x48235e]
11: akonadiserver() [0x41b90f]
12: akonadiserver() [0x41dff8]
13: akonadiserver() [0x4e2e49]
14: /usr/lib/x86_64-linux-gnu/libQtCore.so.4(_ZN7QObject5eventEP6QEvent+0x1e1) [0x7fc2d2042891]
15: /usr/lib/x86_64-linux-gnu/libQtCore.so.4(_ZN16QCoreApplication14notifyInternalEP7QObjectP6QEvent+0x8d) [0x7fc2d202917d]
16: /usr/lib/x86_64-linux-gnu/libQtCore.so.4(_ZN23QCoreApplicationPrivate16sendPostedEventsEP7QObjectiP11QThreadData+0x231) [0x7fc2d202ca21]
17: /usr/lib/x86_64-linux-gnu/libQtCore.so.4(+0x1b669e) [0x7fc2d205869e]
18: /lib/x86_64-linux-gnu/libglib-2.0.so.0(g_main_context_dispatch+0x24d) [0x7fc2cfdb1c3d]
19: /lib/x86_64-linux-gnu/libglib-2.0.so.0(+0x49f20) [0x7fc2cfdb1f20]
20: /lib/x86_64-linux-gnu/libglib-2.0.so.0(g_main_context_iteration+0x2c) [0x7fc2cfdb1fcc]
21: /usr/lib/x86_64-linux-gnu/libQtCore.so.4(_ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE+0x7e) [0x7fc2d205880e]
22: /usr/lib/x86_64-linux-gnu/libQtCore.so.4(_ZN10QEventLoop13processEventsE6QFlagsINS_17ProcessEventsFlagEE+0x41) [0x7fc2d2027cd1]
23: /usr/lib/x86_64-linux-gnu/libQtCore.so.4(_ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE+0x1a5) [0x7fc2d2028035]
24: /usr/lib/x86_64-linux-gnu/libQtCore.so.4(_ZN16QCoreApplication4execEv+0x99) [0x7fc2d202dab9]
25: akonadiserver() [0x4131b5]
26: /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf0) [0x7fc2d06d4a40]
27: akonadiserver(_start+0x29) [0x413be9]
]
"

Test 15: ERROR
--------

Previous Akonadi server error log found.
Details: The Akonadi server reported errors during its previous startup. The log can be found in <a href='/home/michael/.local/share/akonadi/akonadiserver.error.old'>/home/michael/.local/share/akonadi/akonadiserver.error.old</a>.

File content of '/home/michael/.local/share/akonadi/akonadiserver.error.old':
Database process exited unexpectedly during initial connection!
executable: "/usr/sbin/mysqld-akonadi"
arguments: ("--defaults-file=/home/michael/.local/share/akonadi/mysql.conf", "--datadir=/home/michael/.local/share/akonadi/db_data/", "--socket=/tmp/akonadi-michael.D0cxKV/mysql.socket")
stdout: ""
stderr: "2015-04-24 19:15:56 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
2015-04-24 19:15:56 0 [Note] /usr/sbin/mysqld (mysqld 5.6.24-0ubuntu2) starting as process 25451 ...
"
exit code: 1
process error: "Process operation timed out"
"[
0: akonadiserver() [0x418c8a]
1: akonadiserver() [0x418f04]
2: /lib/x86_64-linux-gnu/libc.so.6(+0x352f0) [0x7f1f9e9192f0]
3: /lib/x86_64-linux-gnu/libc.so.6(gsignal+0x37) [0x7f1f9e919267]
4: /lib/x86_64-linux-gnu/libc.so.6(abort+0x16a) [0x7f1f9e91aeca]
5: /usr/lib/x86_64-linux-gnu/libQtCore.so.4(_Z17qt_message_output9QtMsgTypePKc+0x12a) [0x7f1fa0143a8a]
6: akonadiserver() [0x41ad0d]
7: /usr/lib/x86_64-linux-gnu/libQtCore.so.4(_ZN9QIODevice5writeEPKcx+0x8a) [0x7f1fa01e330a]
8: /usr/lib/x86_64-linux-gnu/libQtCore.so.4(+0x121155) [0x7f1fa01f3155]
9: /usr/lib/x86_64-linux-gnu/libQtCore.so.4(_ZN11QTextStreamD1Ev+0x31) [0x7f1fa01fbab1]
10: akonadiserver() [0x48235e]
11: akonadiserver() [0x41b90f]
12: akonadiserver() [0x41dff8]
13: akonadiserver() [0x4e2e49]
14: /usr/lib/x86_64-linux-gnu/libQtCore.so.4(_ZN7QObject5eventEP6QEvent+0x1e1) [0x7f1fa0272891]
15: /usr/lib/x86_64-linux-gnu/libQtCore.so.4(_ZN16QCoreApplication14notifyInternalEP7QObjectP6QEvent+0x8d) [0x7f1fa025917d]
16: /usr/lib/x86_64-linux-gnu/libQtCore.so.4(_ZN23QCoreApplicationPrivate16sendPostedEventsEP7QObjectiP11QThreadData+0x231) [0x7f1fa025ca21]
17: /usr/lib/x86_64-linux-gnu/libQtCore.so.4(+0x1b669e) [0x7f1fa028869e]
18: /lib/x86_64-linux-gnu/libglib-2.0.so.0(g_main_context_dispatch+0x24d) [0x7f1f9dfe1c3d]
19: /lib/x86_64-linux-gnu/libglib-2.0.so.0(+0x49f20) [0x7f1f9dfe1f20]
20: /lib/x86_64-linux-gnu/libglib-2.0.so.0(g_main_context_iteration+0x2c) [0x7f1f9dfe1fcc]
21: /usr/lib/x86_64-linux-gnu/libQtCore.so.4(_ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE+0x7e) [0x7f1fa028880e]
22: /usr/lib/x86_64-linux-gnu/libQtCore.so.4(_ZN10QEventLoop13processEventsE6QFlagsINS_17ProcessEventsFlagEE+0x41) [0x7f1fa0257cd1]
23: /usr/lib/x86_64-linux-gnu/libQtCore.so.4(_ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE+0x1a5) [0x7f1fa0258035]
24: /usr/lib/x86_64-linux-gnu/libQtCore.so.4(_ZN16QCoreApplication4execEv+0x99) [0x7f1fa025dab9]
25: akonadiserver() [0x4131b5]
26: /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf0) [0x7f1f9e904a40]
27: akonadiserver(_start+0x29) [0x413be9]
]
"

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.

Revision history for this message
Ubuntu Foundations Team Bug Bot (crichton) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage. You might also ask for help in the #ubuntu-bugs irc channel on Freenode.

To change the source package that this bug is filed about visit https://bugs.launchpad.net/ubuntu/+bug/1448345/+editstatus and add the package name in the text box next to the word Package.

[This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.]

tags: added: bot-comment
Revision history for this message
Michael Lynch (lynchm0965) wrote :

Probably involves the entire KDE plasma desktop, but the error message that initiated this request specifically mentioned Akonadi.

affects: ubuntu → akonadi (Ubuntu)
Revision history for this message
Phil Thane (phil-pthane) wrote :

Me too. I haven't checked every line above, but similar symptoms. Plasma appeared to work OK at first, but Kontact failed with error message about Akonadi. Then Plasma crashed and will not restart despite reboots. had to install LXDE from terminal to continue using machine.

Brian Murray (brian-murray)
tags: added: vivid
Revision history for this message
cardonator (bcardon) wrote :

I am having the same problem. It appears that the file:

$HOME/.local/share/akonadi/mysql.conf

is not set up properly. I have been using 15.04 since Beta 1 and this only started happening in the RC right before release.

The first error (about TIMESTAMP) could be resolved by adding

explicit_defaults_for_timestamp = 1

to the config file mentioned above.

Afterwards, it seems like mysql dumping out output is causing a problem as I get this in the log:

stderr: "2015-05-11 10:40:48 0 [Note] /usr/sbin/mysqld (mysqld 5.6.24-0ubuntu2) starting as process 3635 ...
"

And then akonadiserver fails to launch.

I am stumped. I'm not sure how to prevent output on starting the mysql server.

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in akonadi (Ubuntu):
status: New → Confirmed
Alberto Salvia Novella (es20490446e)
Changed in akonadi (Ubuntu):
importance: Undecided → Medium
Revision history for this message
CaCO3 (caco3) wrote :
Download full text (19.1 KiB)

I also have this issue.
After applying the fix from comment #4, it fails on test #10:
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.

I also upgraded from Kubuntu 14.10 to 15.04 (Beta 2 approx. a month ago)

Full log:
-------------------------------------------------------
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/gruinelli/.config/akonadi/akonadiserverrc':
[%General]
Driver=QMYSQL

[QMYSQL]
Name=akonadi
Host=
Options="UNIX_SOCKET=/tmp/akonadi-gruinelli.JUJrye/mysql.socket"
ServerPath=/usr/sbin/mysqld-akonadi
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-akonadi'.
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.6.24-0ubuntu2 for debian-linux-gnu on x86_64 ((Ubuntu))

Test 5: SUCCESS
--------

No current MySQL error log found.
Details: The MySQL server did not report any errors during this startup. The log can be found in '/home/gruinelli/.local/share/akonadi/db_data/mysql.err'.

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 <email address hidden>
#
[mysqld]

# 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

# DEBUGGING:
# 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
#
# mesure database size and adjust innodb_buffer_pool_size
# SELECT sum(data_length) as bla, sum(index_length) as blub FROM information_schema.tables...

Revision history for this message
Magnus Holmgren (holmgren) wrote :

Same here. Fortunately, MariaDB (packages mariadb-server-core-10.0 and mariadb-client-core-10.0, but the client package might not need to be substiuted) seems to work as a perfect replacement.

Revision history for this message
Robert Koebner (mockbeggars) wrote :

Can anyone resolve the problem of being locked out of kaddress? As above users have remarked, this problem has only arisen as a result of updating from 14.10 to 15.04. The error log I get is attached - I think it's exactly the same as experienced by others. Losing access to addresses is becoming more serious than just inconvenient!

Revision history for this message
Richard Johnson (rmchard) wrote :

This seems to be related to this bug: https://bugs.launchpad.net/ubuntu/+source/akonadi/+bug/1445383

akonadi needs mariadb (not newer mySql) to start up. Other things might be involved too. Since akonadi gets used by address book, the notes, kmail, PIM, etc. any problem there will bleed over.

Hopefully some of the info there will fix your specific issue.

Revision history for this message
Chris Bartram (yorkie-archive) wrote :

I've just installed the latest version of Lubuntu to try it out on my very slow 10-year-old machine. Trying to launch Korganiser brings up this bug (which seems to have been around for several years) saying that the Akonadi PIM service is not operational. I've used Korganiser on Linux Mint for a couple of years but I'm really not tech-savvy. (I'm very old . . . and a bit stupid . . .)

Wolfi323 suggested in another thread, to try typing "~$ akonadictl start" into terminal : it didn't work. Elsewhere I've seen instruction to create a directory "/var/lib/mysql-files" : how do I do that? Is there a way to do that by typing some instructions into a terminal? If so, please make it as simple as possible - "copy and paste" is about as savvy as I can manage.

Revision history for this message
Rik Mills (rikmills) wrote : Re: [Bug 1448345] Re: Akonadi personal information management service not operational after upgrading

On 23/07/17 17:43, Chris Bartram wrote:
> Elsewhere I've seen instruction
> to create a directory "/var/lib/mysql-files" : how do I do that? Is
> there a way to do that by typing some instructions into a terminal? If
> so, please make it as simple as possible - "copy and paste" is about as
> savvy as I can manage.
>

sudo mkdir /var/lib/mysql-files

Revision history for this message
Chris Bartram (yorkie-archive) wrote :

Yay! It's working! Thank you, Rik Mills.

Revision history for this message
Bruce Lerner (1-bruce) wrote :

creating the mysql-files directory (sudo mkdir /var/lib/mysql-files) resolved the issue for me also

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.