[ERLEDIGT] nach servercrash mysql startet nicht mehr

Code:
Sep 24 20:31:05 **** mysqld[1633]: 100924 22:31:05  InnoDB: Database was not shut down normally!

Sep 24 20:31:05 **** mysqld[1633]: InnoDB: Starting crash recovery.

Sep 24 20:31:05 **** mysqld[1633]: InnoDB: Reading tablespace information from the .ibd files...

Sep 24 20:31:05 **** mysqld[1633]: InnoDB: Restoring possible half-written data pages from the doublewrite

Sep 24 20:31:05 **** mysqld[1633]: InnoDB: buffer...

Sep 24 20:31:05 **** mysqld[1633]: 100924 22:31:05  InnoDB: Starting log scan based on checkpoint at

Sep 24 20:31:05 **** mysqld[1633]: InnoDB: log sequence number 7 3162206652.

Sep 24 20:31:05 **** mysqld[1633]: InnoDB: Doing recovery: scanned up to log sequence number 7 3162207707

Sep 24 20:31:05 **** mysqld[1633]: InnoDB: 1 transaction(s) which must be rolled back or cleaned up

Sep 24 20:31:05 **** mysqld[1633]: InnoDB: in total 1 row operations to undo

Sep 24 20:31:05 **** mysqld[1633]: InnoDB: Trx id counter is 0 6609920

Sep 24 20:31:05 **** mysqld[1633]: 100924 22:31:05  InnoDB: Starting an apply batch of log records to the database...

Sep 24 20:31:05 **** mysqld[1633]: InnoDB: Progress in percents: 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 mysqld got signal 11;

Sep 24 20:31:05 **** mysqld[1633]: This could be because you hit a bug. It is also possible that this binary

Sep 24 20:31:05 **** mysqld[1633]: or one of the libraries it was linked against is corrupt, improperly built,

Sep 24 20:31:05 **** mysqld[1633]: or misconfigured. This error can also be caused by malfunctioning hardware.

Sep 24 20:31:05 **** mysqld[1633]: We will try our best to scrape up some info that will hopefully help diagnose

Sep 24 20:31:05 **** mysqld[1633]: the problem, but since we have already crashed, something is definitely wrong

Sep 24 20:31:05 **** mysqld[1633]: and this may fail.

Sep 24 20:31:05 **** mysqld[1633]: 

Sep 24 20:31:05 **** mysqld[1633]: key_buffer_size=0

Sep 24 20:31:05 **** mysqld[1633]: read_buffer_size=131072

Sep 24 20:31:05 **** mysqld[1633]: max_used_connections=0

Sep 24 20:31:05 **** mysqld[1633]: max_connections=100

Sep 24 20:31:05 **** mysqld[1633]: threads_connected=0

Sep 24 20:31:05 **** mysqld[1633]: It is possible that mysqld could use up to 

Sep 24 20:31:05 **** mysqld[1633]: key_buffer_size + (read_buffer_size + sort_buffer_size)*max_connections = 217599 K

Sep 24 20:31:05 **** mysqld[1633]: bytes of memory

Sep 24 20:31:05 **** mysqld[1633]: Hope that's ok; if not, decrease some variables in the equation.

Sep 24 20:31:05 **** mysqld[1633]: 

Sep 24 20:31:05 **** mysqld[1633]: thd=(nil)

Sep 24 20:31:05 **** mysqld[1633]: Attempting backtrace. You can use the following information to find out

Sep 24 20:31:05 **** mysqld[1633]: where mysqld died. If you see no messages after this, something went

Sep 24 20:31:05 **** mysqld[1633]: terribly wrong...

Sep 24 20:31:05 **** mysqld[1633]: Cannot determine thread, fp=0xb51ad4ac, backtrace may not be correct.

Sep 24 20:31:05 **** mysqld[1633]: Stack range sanity check OK, backtrace follows:

Sep 24 20:31:05 **** mysqld[1633]: 0x81c0759

Sep 24 20:31:05 **** mysqld[1633]: 0x83cbae2

Sep 24 20:31:05 **** mysqld[1633]: 0x83cc76b

Sep 24 20:31:05 **** mysqld[1633]: 0x83902e5

Sep 24 20:31:05 **** mysqld[1633]: 0x83921f0

Sep 24 20:31:05 **** mysqld[1633]: 0x837f45a

Sep 24 20:31:05 **** mysqld[1633]: 0x83aa80c

Sep 24 20:31:05 **** mysqld[1633]: 0x82f03d8

Sep 24 20:31:05 **** mysqld[1633]: 0xb7fac0bd

Sep 24 20:31:05 **** mysqld[1633]: 0xb7de701e

Sep 24 20:31:05 **** mysqld[1633]: New value of fp=(nil) failed sanity check, terminating stack trace!

Sep 24 20:31:05 **** mysqld[1633]: Please read http://dev.mysql.com/doc/mysql/en/using-stack-trace.html and follow instructions on how to resolve the stack trace. Resolved

Sep 24 20:31:05 **** mysqld[1633]: stack trace is much more helpful in diagnosing the problem, so please do 

Sep 24 20:31:05 **** mysqld[1633]: resolve it

Sep 24 20:31:05 **** mysqld[1633]: The manual page at http://www.mysql.com/doc/en/Crashing.html contains

Sep 24 20:31:05 **** mysqld[1633]: information that should help you find out what is causing the crash.

Sep 24 20:31:05 **** mysqld_safe[1641]: ended

Sep 24 20:31:20 **** /etc/init.d/mysql[1808]: 0 processes alive and '/usr/bin/mysqladmin --defaults-file=/etc/mysql/debian.cnf ping' resulted in

Sep 24 20:31:20 **** /etc/init.d/mysql[1808]: ^G/usr/bin/mysqladmin: connect to server at 'localhost' failed

Sep 24 20:31:20 **** /etc/init.d/mysql[1808]: error: 'Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2)'

Sep 24 20:31:20 **** /etc/init.d/mysql[1808]: Check that mysqld is running and that the socket: '/var/run/mysqld/mysqld.sock' exists!

Sep 24 20:31:20 **** /etc/init.d/mysql[1808]: