Problem MySQL Datenbank nach RAID Crash

[Yazu]

Hallo zusammen,

nachdem ich die Konfiguration des RAIDs wieder hergestellt habe und der Server wieder hochfährt habe ich nun ein Problem mit der Datenbank.

Beim starten des Dienstes erhalte ich lediglich die Fehlermeldung "failed!". Im Syslog steht anschließend folgendes:

Jan 27 10:05:15 otrssrv01 mysqld_safe: Starting mysqld daemon with databases from /var/lib/mysql

Jan 27 10:05:15 otrssrv01 mysqld: 140127 10:05:15 [Warning] Using unique option prefix key_buffer instead of key_buffer_size is deprecated and will be removed in a future release. Please use the full name instead.

Jan 27 10:05:15 otrssrv01 mysqld: 140127 10:05:15 [Warning] Using unique option prefix myisam-recover instead of myisam-recover-options is deprecated and will be removed in a future release. Please use the full name instead.

Jan 27 10:05:15 otrssrv01 mysqld: 140127 10:05:15 [Note] Plugin 'FEDERATED' is disabled.

Jan 27 10:05:15 otrssrv01 mysqld: 140127 10:05:15 InnoDB: The InnoDB memory heap is disabled

Jan 27 10:05:15 otrssrv01 mysqld: 140127 10:05:15 InnoDB: Mutexes and rw_locks use GCC atomic builtins

Jan 27 10:05:15 otrssrv01 mysqld: 140127 10:05:15 InnoDB: Compressed tables use zlib 1.2.7

Jan 27 10:05:15 otrssrv01 mysqld: 140127 10:05:15 InnoDB: Using Linux native AIO

Jan 27 10:05:15 otrssrv01 mysqld: 140127 10:05:15 InnoDB: Initializing buffer pool, size = 128.0M

Jan 27 10:05:15 otrssrv01 mysqld: 140127 10:05:15 InnoDB: Completed initialization of buffer pool

Jan 27 10:05:15 otrssrv01 mysqld: 140127 10:05:15 InnoDB: highest supported file format is Barracuda.

Jan 27 10:05:15 otrssrv01 mysqld: InnoDB: Log scan progressed past the checkpoint lsn 52783069665

Jan 27 10:05:15 otrssrv01 mysqld: 140127 10:05:15  InnoDB: Database was not shut down normally!

Jan 27 10:05:15 otrssrv01 mysqld: InnoDB: Starting crash recovery.

Jan 27 10:05:15 otrssrv01 mysqld: InnoDB: Reading tablespace information from the .ibd files...

Jan 27 10:05:15 otrssrv01 mysqld: InnoDB: Restoring possible half-written data pages from the doublewrite

Jan 27 10:05:15 otrssrv01 mysqld: InnoDB: buffer...

Jan 27 10:05:15 otrssrv01 mysqld: InnoDB: Doing recovery: scanned up to log sequence number 52783447797

Jan 27 10:05:15 otrssrv01 mysqld: 140127 10:05:15  InnoDB: Starting an apply batch of log records to the database...

Jan 27 10:05:15 otrssrv01 mysqld: InnoDB: Progress in percents: 0 1 2 3 4 5 6 7 8 9 10 09:05:15 UTC - mysqld got signal 11 ;

Jan 27 10:05:15 otrssrv01 mysqld: This could be because you hit a bug. It is also possible that this binary

Jan 27 10:05:15 otrssrv01 mysqld: or one of the libraries it was linked against is corrupt, improperly built,

Jan 27 10:05:15 otrssrv01 mysqld: or misconfigured. This error can also be caused by malfunctioning hardware.

Jan 27 10:05:15 otrssrv01 mysqld: We will try our best to scrape up some info that will hopefully help

Jan 27 10:05:15 otrssrv01 mysqld: diagnose the problem, but since we have already crashed,

Jan 27 10:05:15 otrssrv01 mysqld: something is definitely wrong and this may fail.

Jan 27 10:05:15 otrssrv01 mysqld:

Jan 27 10:05:15 otrssrv01 mysqld: key_buffer_size=16777216

Jan 27 10:05:15 otrssrv01 mysqld: read_buffer_size=131072

Jan 27 10:05:15 otrssrv01 mysqld: max_used_connections=0

Jan 27 10:05:15 otrssrv01 mysqld: max_threads=151

Jan 27 10:05:15 otrssrv01 mysqld: thread_count=0

Jan 27 10:05:15 otrssrv01 mysqld: connection_count=0

Jan 27 10:05:15 otrssrv01 mysqld: It is possible that mysqld could use up to

Jan 27 10:05:15 otrssrv01 mysqld: key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 346700 K  bytes of memory

Jan 27 10:05:15 otrssrv01 mysqld: Hope that's ok; if not, decrease some variables in the equation.

Jan 27 10:05:15 otrssrv01 mysqld:

Jan 27 10:05:15 otrssrv01 mysqld: Thread pointer: 0x0

Jan 27 10:05:15 otrssrv01 mysqld: Attempting backtrace. You can use the following information to find out

Jan 27 10:05:15 otrssrv01 mysqld: where mysqld died. If you see no messages after this, something went

Jan 27 10:05:15 otrssrv01 mysqld: terribly wrong...

Jan 27 10:05:15 otrssrv01 mysqld: stack_bottom = 0 thread_stack 0x30000

Jan 27 10:05:15 otrssrv01 mysqld: 11 12 13 /usr/sbin/mysqld(my_print_stacktrace+0x29)[0x7f8e1b89be59]

Jan 27 10:05:15 otrssrv01 mysqld: 14 /usr/sbin/mysqld(handle_fatal_signal+0x3d8)[0x7f8e1b783808]

Jan 27 10:05:15 otrssrv01 mysqld: /lib/x86_64-linux-gnu/libpthread.so.0(+0xf030)[0x7f8e1af32030]

Jan 27 10:05:15 otrssrv01 mysqld: 15 /usr/sbin/mysqld(+0x637b65)[0x7f8e1b998b65]

Jan 27 10:05:15 otrssrv01 mysqld: 16 /usr/sbin/mysqld(+0x638e87)[0x7f8e1b999e87]

Jan 27 10:05:15 otrssrv01 mysqld: 17 /usr/sbin/mysqld(+0x626400)[0x7f8e1b987400]

Jan 27 10:05:15 otrssrv01 mysqld: 18 19 /usr/sbin/mysqld(+0x627d02)[0x7f8e1b988d02]

Jan 27 10:05:15 otrssrv01 mysqld: 20 /usr/sbin/mysqld(+0x5c9553)[0x7f8e1b92a553]

Jan 27 10:05:15 otrssrv01 mysqld: 21 22 /usr/sbin/mysqld(+0x5f63b9)[0x7f8e1b9573b9]

Jan 27 10:05:15 otrssrv01 mysqld: 23 24 /usr/sbin/mysqld(+0x586368)[0x7f8e1b8e7368]

Jan 27 10:05:15 otrssrv01 mysqld: /lib/x86_64-linux-gnu/libpthread.so.0(+0x6b50)[0x7f8e1af29b50]

Jan 27 10:05:15 otrssrv01 mysqld: 25 /lib/x86_64-linux-gnu/libc.so.6(clone+0x6d)[0x7f8e1986da7d]

Jan 27 10:05:15 otrssrv01 mysqld: The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains

Jan 27 10:05:15 otrssrv01 mysqld: information that should help you find out what is causing the crash.

Jan 27 10:05:15 otrssrv01 mysqld_safe: mysqld from pid file /var/run/mysqld/mysqld.pid ended

Jan 27 10:05:29 otrssrv01 /etc/init.d/mysql[20462]: 0 processes alive and '/usr/bin/mysqladmin --defaults-file=/etc/mysql/debian.cnf ping' resulted in

Jan 27 10:05:29 otrssrv01 /etc/init.d/mysql[20462]: #007/usr/bin/mysqladmin: connect to server at 'localhost' failed

Jan 27 10:05:29 otrssrv01 /etc/init.d/mysql[20462]: error: 'Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2)'

Jan 27 10:05:29 otrssrv01 /etc/init.d/mysql[20462]: Check that mysqld is running and that the socket: '/var/run/mysqld/mysqld.sock' exists!

Jan 27 10:05:29 otrssrv01 /etc/init.d/mysql[20462]:

Wichtig wäre nur das der Dienst wieder startet, damit ich das Backup einspielen kann. Eine Neuinstallation hat leider nichts gebracht.

[carstenj]

Hi,

kann man so wohl nix zu sagen, mach mal das was da steht und arbeite diese Seite durch:

MySQL :: MySQL 5.6 Reference Manual :: C.5.4.2 What to Do If MySQL Keeps Crashing