Zarafa -MySQL startet nicht mehr?!?

german

#1

Hallo Leute,
mein mysql Dienst startet nach einem Absturz nicht mehr. Ich bekomme im Syslog folgende Fehlermeldung:
Was kann ich tun???

Mar 17 19:44:06 ucs mysqld: 150317 19:44:06 InnoDB: Compressed tables use zlib 1.2.7
Mar 17 19:44:06 ucs mysqld: 150317 19:44:06 InnoDB: Using Linux native AIO
Mar 17 19:44:06 ucs mysqld: 150317 19:44:06 InnoDB: Initializing buffer pool, size = 128.0M
Mar 17 19:44:06 ucs mysqld: 150317 19:44:06 InnoDB: Completed initialization of buffer pool
Mar 17 19:44:06 ucs mysqld: 150317 19:44:06 InnoDB: highest supported file format is Barracuda.
Mar 17 19:44:06 ucs mysqld: InnoDB: 1 transaction(s) which must be rolled back or cleaned up
Mar 17 19:44:06 ucs mysqld: InnoDB: in total 4 row operations to undo
Mar 17 19:44:06 ucs mysqld: InnoDB: Trx id counter is 95A100
Mar 17 19:44:06 ucs mysqld: InnoDB: Cleaning up trx with id 9557F1
Mar 17 19:44:06 ucs mysqld: 150317 19:44:06  InnoDB: Waiting for the background threads to start
Mar 17 19:44:07 ucs mysqld: 150317 19:44:07 InnoDB: 5.5.40 started; log sequence number 6952755294
Mar 17 19:44:07 ucs mysqld: 150317 19:44:07 [Note] Server hostname (bind-address): '127.0.0.1'; port: 3306
Mar 17 19:44:07 ucs mysqld: 150317 19:44:07 [Note]   - '127.0.0.1' resolves to '127.0.0.1';
Mar 17 19:44:07 ucs mysqld: 150317 19:44:07 [Note] Server socket created on IP: '127.0.0.1'.
Mar 17 19:44:07 ucs mysqld: 150317 19:44:07  InnoDB: Assertion failure in thread 139963481757440 in file trx0purge.c line 840
Mar 17 19:44:07 ucs mysqld: InnoDB: Failing assertion: purge_sys->purge_trx_no <= purge_sys->rseg->last_trx_no
Mar 17 19:44:07 ucs mysqld: InnoDB: We intentionally generate a memory trap.
Mar 17 19:44:07 ucs mysqld: InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
Mar 17 19:44:07 ucs mysqld: InnoDB: If you get repeated assertion failures or crashes, even
Mar 17 19:44:07 ucs mysqld: InnoDB: immediately after the mysqld startup, there may be
Mar 17 19:44:07 ucs mysqld: InnoDB: corruption in the InnoDB tablespace. Please refer to
Mar 17 19:44:07 ucs mysqld: InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
Mar 17 19:44:07 ucs mysqld: InnoDB: about forcing recovery.
Mar 17 19:44:07 ucs mysqld: 18:44:07 UTC - mysqld got signal 6 ;
Mar 17 19:44:07 ucs mysqld: This could be because you hit a bug. It is also possible that this binary
Mar 17 19:44:07 ucs mysqld: or one of the libraries it was linked against is corrupt, improperly built,
Mar 17 19:44:07 ucs mysqld: or misconfigured. This error can also be caused by malfunctioning hardware.
Mar 17 19:44:07 ucs mysqld: We will try our best to scrape up some info that will hopefully help
Mar 17 19:44:07 ucs mysqld: diagnose the problem, but since we have already crashed,
Mar 17 19:44:07 ucs mysqld: something is definitely wrong and this may fail.
Mar 17 19:44:07 ucs mysqld:
Mar 17 19:44:07 ucs mysqld: key_buffer_size=16777216
Mar 17 19:44:07 ucs mysqld: read_buffer_size=131072
Mar 17 19:44:07 ucs mysqld: max_used_connections=0
Mar 17 19:44:07 ucs mysqld: max_threads=151
Mar 17 19:44:07 ucs mysqld: thread_count=0
Mar 17 19:44:07 ucs mysqld: connection_count=0
Mar 17 19:44:07 ucs mysqld: It is possible that mysqld could use up to
Mar 17 19:44:07 ucs mysqld: key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 346700 K  bytes of memory
Mar 17 19:44:07 ucs mysqld: Hope that's ok; if not, decrease some variables in the equation.
Mar 17 19:44:07 ucs mysqld:
Mar 17 19:44:07 ucs mysqld: Thread pointer: 0x0
Mar 17 19:44:07 ucs mysqld: Attempting backtrace. You can use the following information to find out
Mar 17 19:44:07 ucs mysqld: where mysqld died. If you see no messages after this, something went
Mar 17 19:44:07 ucs mysqld: terribly wrong...
Mar 17 19:44:07 ucs mysqld: stack_bottom = 0 thread_stack 0x30000
Mar 17 19:44:07 ucs mysqld: 150317 19:44:07 [Note] Event Scheduler: Loaded 0 events
Mar 17 19:44:07 ucs mysqld: /usr/sbin/mysqld(my_print_stacktrace+0x29)[0x7f4bdc9e10b9]
Mar 17 19:44:07 ucs mysqld: 150317 19:44:07 [Note] /usr/sbin/mysqld: ready for connections.
Mar 17 19:44:07 ucs mysqld: Version: '5.5.40-0.14.201502051002-log'  socket: '/var/run/mysqld/mysqld.sock'  port: 3306  (Univention)
Mar 17 19:44:07 ucs mysqld: /usr/sbin/mysqld(handle_fatal_signal+0x3d8)[0x7f4bdc8c8418]
Mar 17 19:44:07 ucs mysqld: /lib/x86_64-linux-gnu/libpthread.so.0(+0xf0a0)[0x7f4bdc0760a0]
Mar 17 19:44:07 ucs mysqld: /lib/x86_64-linux-gnu/libc.so.6(gsignal+0x35)[0x7f4bda906165]
Mar 17 19:44:07 ucs mysqld: /lib/x86_64-linux-gnu/libc.so.6(abort+0x180)[0x7f4bda9093e0]
Mar 17 19:44:07 ucs mysqld: /usr/sbin/mysqld(+0x5e14d5)[0x7f4bdca864d5]
Mar 17 19:44:07 ucs mysqld: /usr/sbin/mysqld(+0x5e18d9)[0x7f4bdca868d9]
Mar 17 19:44:07 ucs mysqld: /usr/sbin/mysqld(+0x6a402f)[0x7f4bdcb4902f]
Mar 17 19:44:07 ucs mysqld: /usr/sbin/mysqld(+0x69ab4b)[0x7f4bdcb3fb4b]
Mar 17 19:44:07 ucs mysqld: /usr/sbin/mysqld(+0x5e2a29)[0x7f4bdca87a29]
Mar 17 19:44:07 ucs mysqld: /usr/sbin/mysqld(+0x5d44fc)[0x7f4bdca794fc]
Mar 17 19:44:07 ucs mysqld: /usr/sbin/mysqld(+0x5d8703)[0x7f4bdca7d703]
Mar 17 19:44:07 ucs mysqld: /lib/x86_64-linux-gnu/libpthread.so.0(+0x6b50)[0x7f4bdc06db50]
Mar 17 19:44:07 ucs mysqld: /lib/x86_64-linux-gnu/libc.so.6(clone+0x6d)[0x7f4bda9b070d]
Mar 17 19:44:07 ucs mysqld: The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
Mar 17 19:44:07 ucs mysqld: information that should help you find out what is causing the crash.
Mar 17 19:44:08 ucs mysqld_safe: Number of processes running now: 0
Mar 17 19:44:08 ucs mysqld_safe: mysqld restarted
Mar 17 19:44:08 ucs mysqld: 150317 19:44:08 [Note] Plugin 'FEDERATED' is disabled.
Mar 17 19:44:08 ucs mysqld: 150317 19:44:08 InnoDB: The InnoDB memory heap is disabled
Mar 17 19:44:08 ucs mysqld: 150317 19:44:08 InnoDB: Mutexes and rw_locks use GCC atomic builtins
Mar 17 19:44:08 ucs mysqld: 150317 19:44:08 InnoDB: Compressed tables use zlib 1.2.7
Mar 17 19:44:08 ucs mysqld: 150317 19:44:08 InnoDB: Using Linux native AIO
Mar 17 19:44:08 ucs mysqld: 150317 19:44:08 InnoDB: Initializing buffer pool, size = 128.0M
Mar 17 19:44:08 ucs mysqld: 150317 19:44:08 InnoDB: Completed initialization of buffer pool
Mar 17 19:44:08 ucs mysqld: 150317 19:44:08 InnoDB: highest supported file format is Barracuda.
Mar 17 19:44:08 ucs mysqld: InnoDB: 1 transaction(s) which must be rolled back or cleaned up
Mar 17 19:44:08 ucs mysqld: InnoDB: in total 4 row operations to undo
Mar 17 19:44:08 ucs mysqld: InnoDB: Trx id counter is 95A100
Mar 17 19:44:08 ucs mysqld: InnoDB: Cleaning up trx with id 9557F1
Mar 17 19:44:08 ucs mysqld: 150317 19:44:08  InnoDB: Waiting for the background threads to start

#2

Hallo,

ich würde entweder direkt ein Backup einspielen oder den Anweisungen aus den Meldungen folge leisten:Mar 17 19:44:07 ucs mysqld: InnoDB: If you get repeated assertion failures or crashes, even Mar 17 19:44:07 ucs mysqld: InnoDB: immediately after the mysqld startup, there may be Mar 17 19:44:07 ucs mysqld: InnoDB: corruption in the InnoDB tablespace. Please refer to Mar 17 19:44:07 ucs mysqld: InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html

Wenn das nicht hilft evtl.: Mar 17 19:44:07 ucs mysqld: The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains Mar 17 19:44:07 ucs mysqld: information that should help you find out what is causing the crash.

Mit freundlichen Grüßen
Janis Meybohm