Hallo,
seit dem Update auf die neue Version von MariaDB lässt sich Akonadi nicht mehr starten.
MariaDB gibt folgende Meldungen aus:
2014-07-15 10:03:49 7f39f4d0a780 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.
140715 10:03:49 [Note] InnoDB: Using mutexes to ref count buffer pool pages
140715 10:03:49 [Note] InnoDB: The InnoDB memory heap is disabled
140715 10:03:49 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
140715 10:03:49 [Note] InnoDB: Compressed tables use zlib 1.2.8
140715 10:03:49 [Note] InnoDB: Using Linux native AIO
140715 10:03:49 [Note] InnoDB: Using CPU crc32 instructions
140715 10:03:49 [Note] InnoDB: Initializing buffer pool, size = 80.0M
140715 10:03:49 [Note] InnoDB: Completed initialization of buffer pool
140715 10:03:49 [Note] InnoDB: Highest supported file format is Barracuda.
140715 10:03:49 [Note] InnoDB: The log sequence numbers 51479303 and 51479303 in ibdata files do not match the log sequence number 123350298 in the ib_logfiles!
140715 10:03:49 [Note] InnoDB: Database was not shutdown normally!
140715 10:03:49 [Note] InnoDB: Starting crash recovery.
140715 10:03:49 [Note] InnoDB: Reading tablespace information from the .ibd files...
140715 10:03:49 [Note] InnoDB: Restoring possible half-written data pages
140715 10:03:49 [Note] InnoDB: from the doublewrite buffer...
140715 10:03:49 [ERROR] 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.
To report this bug, see http://kb.askmonty.org/en/reporting-bugs
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.
Server version: 10.0.12-MariaDB
key_buffer_size=16384
read_buffer_size=131072
max_used_connections=0
max_threads=258
thread_count=0
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 566740 K bytes of memory
Hope that's ok; if not, decrease some variables in the equation.
Thread pointer: 0x0x0
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 = 0x0 thread_stack 0x48000
/usr/bin/mysqld(my_print_stacktrace+0x3d)[0xb9cc5d]
/usr/bin/mysqld(handle_fatal_signal+0x345)[0x70cc25]
/usr/lib/libpthread.so.0(+0xf4b0)[0x7f39f40634b0]
/usr/bin/mysqld[0x9d3a59]
/usr/bin/mysqld[0x9d5c63]
/usr/bin/mysqld[0x9354d5]
/usr/bin/mysqld[0x86edab]
/usr/bin/mysqld(_Z24ha_initialize_handlertonP13st_plugin_int+0x64)[0x70edd4]
/usr/bin/mysqld[0x5c3bf3]
/usr/bin/mysqld(_Z11plugin_initPiPPci+0x558)[0x5c4a08]
/usr/bin/mysqld[0x529ba0]
/usr/bin/mysqld(_Z11mysqld_mainiPPc+0x5ad)[0x52dcad]
/usr/lib/libc.so.6(__libc_start_main+0xf0)[0x7f39f2e30000]
/usr/bin/mysqld[0x5225b1]
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.
Das Akonadi Fehlerprotokoll ist:
Database process exited unexpectedly during initial connection!
executable: "/usr/bin/mysqld"
arguments: ("--defaults-file=/home/joju/.local/share/akonadi/mysql.conf", "--datadir=/home/joju/.local/share/akonadi/db_data/", "--socket=/tmp/akonadi-joju.AlTu4T/mysql.socket")
stdout: ""
stderr: ""
exit code: 1
process error: "Unknown error"
"[
0: akonadiserver(_Z11akBacktracev+0x37) [0x45d8e7]
1: akonadiserver() [0x45db39]
2: /usr/lib/libc.so.6(+0x33df0) [0x7f99e855bdf0]
3: /usr/lib/libc.so.6(gsignal+0x37) [0x7f99e855bd67]
4: /usr/lib/libc.so.6(abort+0x148) [0x7f99e855d118]
5: /usr/lib/libQtCore.so.4(_Z17qt_message_output9QtMsgTypePKc+0x5f) [0x7f99e9d549ff]
6: akonadiserver(_ZN15FileDebugStream9writeDataEPKcx+0x9d) [0x45fd0d]
7: /usr/lib/libQtCore.so.4(_ZN9QIODevice5writeEPKcx+0xb0) [0x7f99e9def560]
8: /usr/lib/libQtCore.so.4(+0x11ac2d) [0x7f99e9dfec2d]
9: /usr/lib/libQtCore.so.4(_ZN11QTextStreamD1Ev+0x31) [0x7f99e9e07811]
10: akonadiserver(_ZN6QDebugD1Ev+0x39) [0x457e39]
11: akonadiserver(_ZN7Akonadi6Server13DbConfigMysql19startInternalServerEv+0x1de1) [0x5096c1]
12: akonadiserver(_ZN7Akonadi6Server13AkonadiServer20startDatabaseProcessEv+0xd7) [0x4607e7]
13: akonadiserver(_ZN7Akonadi6Server13AkonadiServer4initEv+0xa7) [0x4631b7]
14: /usr/lib/libQtCore.so.4(_ZN7QObject5eventEP6QEvent+0x24e) [0x7f99e9e796ae]
15: /usr/lib/libQtCore.so.4(_ZN16QCoreApplication14notifyInternalEP7QObjectP6QEvent+0x6d) [0x7f99e9e6158d]
16: /usr/lib/libQtCore.so.4(_ZN23QCoreApplicationPrivate16sendPostedEventsEP7QObjectiP11QThreadData+0x1ed) [0x7f99e9e646dd]
17: /usr/lib/libQtCore.so.4(+0x1aa9e3) [0x7f99e9e8e9e3]
18: /usr/lib/libglib-2.0.so.0(g_main_context_dispatch+0x254) [0x7f99e7c30b84]
19: /usr/lib/libglib-2.0.so.0(+0x48dc8) [0x7f99e7c30dc8]
20: /usr/lib/libglib-2.0.so.0(g_main_context_iteration+0x2c) [0x7f99e7c30e6c]
21: /usr/lib/libQtCore.so.4(_ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE+0x65) [0x7f99e9e8e2a5]
22: /usr/lib/libQtCore.so.4(_ZN10QEventLoop13processEventsE6QFlagsINS_17ProcessEventsFlagEE+0x2f) [0x7f99e9e6015f]
23: /usr/lib/libQtCore.so.4(_ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE+0x175) [0x7f99e9e60455]
24: /usr/lib/libQtCore.so.4(_ZN16QCoreApplication4execEv+0x89) [0x7f99e9e65719]
25: akonadiserver(main+0x1c7) [0x457497]
26: /usr/lib/libc.so.6(__libc_start_main+0xf0) [0x7f99e8548000]
27: akonadiserver() [0x457be8]
]
"
Hat jemand eine Idee, wie ich den Fehler beheben kann?
Viele Grüße