mysql 无法启动

lijiabin945

前段时间经常自动重启，今天宕掉后就启动不了了。。。大神帮忙看下错误日志，这是什么原因，怎么恢复？

error.log.2 (525.88 KB, 下载次数: 388)

2015-5-8 17:59 上传

点击文件名下载附件

lijiabin945

这是错误日志

150506 22:36:13 [Note] Plugin 'FEDERATED' is disabled.
150506 22:36:18 InnoDB: The InnoDB memory heap is disabled
150506 22:36:18 InnoDB: Mutexes and rw_locks use GCC atomic builtins
150506 22:36:18 InnoDB: Compressed tables use zlib 1.2.3.4
150506 22:36:19 InnoDB: Initializing buffer pool, size = 128.0M
150506 22:36:19 InnoDB: Completed initialization of buffer pool
150506 22:36:20 InnoDB: highest supported file format is Barracuda.
InnoDB: The log sequence number in ibdata files does not match
InnoDB: the log sequence number in the ib_logfiles!
150506 22:36:21  InnoDB: Database was not shut down normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files...
InnoDB: Restoring possible half-written data pages from the doublewrite
InnoDB: buffer...
150506 22:37:46  InnoDB: Waiting for the background threads to start
150506 22:37:47 InnoDB: 5.5.31 started; log sequence number 646967245
150506 22:38:00 [Note] Server hostname (bind-address): '127.0.0.1'; port: 3306
150506 22:38:01 [Note]   - '127.0.0.1' resolves to '127.0.0.1';
150506 22:38:01 [Note] Server socket created on IP: '127.0.0.1'.
150506 22:38:08 [Note] Event Scheduler: Loaded 0 events
150506 22:38:08 [Note] /usr/sbin/mysqld: ready for connections.
Version: '5.5.31-0ubuntu0.12.04.2'  socket: '/var/run/mysqld/mysqld.sock'  port: 3306  (Ubuntu)
150506 22:59:31 [Note] Plugin 'FEDERATED' is disabled.
150506 22:59:34 InnoDB: The InnoDB memory heap is disabled
150506 22:59:34 InnoDB: Mutexes and rw_locks use GCC atomic builtins
150506 22:59:34 InnoDB: Compressed tables use zlib 1.2.3.4
150506 22:59:35 InnoDB: Initializing buffer pool, size = 128.0M
150506 22:59:35 InnoDB: Completed initialization of buffer pool
150506 22:59:36 InnoDB: highest supported file format is Barracuda.
InnoDB: The log sequence number in ibdata files does not match
InnoDB: the log sequence number in the ib_logfiles!
150506 22:59:37  InnoDB: Database was not shut down normally!
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files...
InnoDB: Restoring possible half-written data pages from the doublewrite
InnoDB: buffer...
150506 23:01:02  InnoDB: Waiting for the background threads to start
150506 23:01:03 InnoDB: 5.5.31 started; log sequence number 646967265
150506 23:01:05 [Note] Server hostname (bind-address): '127.0.0.1'; port: 3306
150506 23:01:06 [Note]   - '127.0.0.1' resolves to '127.0.0.1';
150506 23:01:06 [Note] Server socket created on IP: '127.0.0.1'.
150506 23:01:19 [Note] Event Scheduler: Loaded 0 events
150506 23:01:19 [Note] /usr/sbin/mysqld: ready for connections.
Version: '5.5.31-0ubuntu0.12.04.2'  socket: '/var/run/mysqld/mysqld.sock'  port: 3306  (Ubuntu)
150506 23:21:54 [Note] Plugin 'FEDERATED' is disabled.
150506 23:21:59 InnoDB: The InnoDB memory heap is disabled
150506 23:21:59 InnoDB: Mutexes and rw_locks use GCC atomic builtins
150506 23:21:59 InnoDB: Compressed tables use zlib 1.2.3.4
150506 23:22:00 InnoDB: Initializing buffer pool, size = 128.0M
150506 23:22:00 InnoDB: Completed initialization of buffer pool
InnoDB: Database page corruption on disk or a failed
InnoDB: file read of page 5.
InnoDB: You may have to recover from a backup.
150506 23:22:01  InnoDB: Page dump in ascii and hex (16384 bytes):
len 16384; hex

【此处省略N 长16进制代码。。。。】

150506 23:22:02  InnoDB: Page checksum 1166353147, prior-to-4.0.14-form checksum 784031149
InnoDB: stored checksum 1166353147, prior-to-4.0.14-form stored checksum 380661338
InnoDB: Page lsn 0 646967311, low 4 bytes of lsn at page end 646967285
InnoDB: Page number (if stored to page already) 5,
InnoDB: space id (if created with >= MySQL-4.1.1 and stored already) 0
InnoDB: Page may be a transaction system page
InnoDB: Database page corruption on disk or a failed
InnoDB: file read of page 5.
InnoDB: You may have to recover from a backup.
InnoDB: It is also possible that your operating
InnoDB: system has corrupted its own file cache
InnoDB: and rebooting your computer removes the
InnoDB: error.
InnoDB: If the corrupt page is an index page
InnoDB: you can also try to fix the corruption
InnoDB: by dumping, dropping, and reimporting
InnoDB: the corrupt table. You can use CHECK
InnoDB: TABLE to scan your table for corruption.
InnoDB: See also http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
InnoDB: Ending processing because of a corrupt database page.
150506 23:22:02  InnoDB: Assertion failure in thread 140496071862080 in file buf0buf.c line 3629
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
InnoDB: If you get repeated assertion failures or crashes, even
InnoDB: immediately after the mysqld startup, there may be
InnoDB: corruption in the InnoDB tablespace. Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
15:22:02 UTC - mysqld got signal 6 ;
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=16777216
read_buffer_size=131072
max_used_connections=0
max_threads=151
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 = 346682 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 0x30000
/usr/sbin/mysqld(my_print_stacktrace+0x29)[0x7fc7cc9367b9]
/usr/sbin/mysqld(handle_fatal_signal+0x483)[0x7fc7cc7fc8f3]
/lib/x86_64-linux-gnu/libpthread.so.0(+0xfcb0)[0x7fc7cb549cb0]
/lib/x86_64-linux-gnu/libc.so.6(gsignal+0x35)[0x7fc7cabb4425]
/lib/x86_64-linux-gnu/libc.so.6(abort+0x17b)[0x7fc7cabb7b8b]
/usr/sbin/mysqld(+0x645171)[0x7fc7cca26171]
/usr/sbin/mysqld(+0x6509e8)[0x7fc7cca319e8]
/usr/sbin/mysqld(+0x65138c)[0x7fc7cca3238c]
/usr/sbin/mysqld(+0x640c16)[0x7fc7cca21c16]
/usr/sbin/mysqld(+0x6131ac)[0x7fc7cc9f41ac]
/usr/sbin/mysqld(+0x6153cc)[0x7fc7cc9f63cc]
/usr/sbin/mysqld(+0x60118c)[0x7fc7cc9e218c]
/usr/sbin/mysqld(+0x5cae89)[0x7fc7cc9abe89]
/usr/sbin/mysqld(_Z24ha_initialize_handlertonP13st_plugin_int+0x41)[0x7fc7cc7fefc1]
/usr/sbin/mysqld(+0x30afc1)[0x7fc7cc6ebfc1]
/usr/sbin/mysqld(_Z11plugin_initPiPPci+0xa94)[0x7fc7cc6ef5e4]
/usr/sbin/mysqld(+0x284686)[0x7fc7cc665686]
/usr/sbin/mysqld(_Z11mysqld_mainiPPc+0x59b)[0x7fc7cc668e2b]
/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xed)[0x7fc7cab9f76d]
/usr/sbin/mysqld(+0x27e1b5)[0x7fc7cc65f1b5]
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.
150506 23:22:26 [Note] Plugin 'FEDERATED' is disabled.
150506 23:22:26 InnoDB: The InnoDB memory heap is disabled
150506 23:22:26 InnoDB: Mutexes and rw_locks use GCC atomic builtins
150506 23:22:26 InnoDB: Compressed tables use zlib 1.2.3.4
150506 23:22:26 InnoDB: Initializing buffer pool, size = 128.0M
150506 23:22:26 InnoDB: Completed initialization of buffer pool
InnoDB: Database page corruption on disk or a failed
InnoDB: file read of page 5.
InnoDB: You may have to recover from a backup.
150506 23:22:27  InnoDB: Page dump in ascii and hex (16384 bytes):
len 16384; hex

kider

感觉应该是内存分配问题，过大了...