疯狂痴呆 发表于 2014-12-30 22:53:14

MYSQL启动不了,日志,可以帮看下吗

lnmpa

141230 22:50:02 mysqld_safe Starting mysqld daemon with databases from /usr/local/mysql/var
141230 22:50:02 '--skip-locking' is deprecated and will be removed in a future release. Please use '--skip-external-locking' instead.
141230 22:50:02InnoDB: Initializing buffer pool, size = 8.0M
141230 22:50:02InnoDB: Completed initialization of buffer pool
InnoDB: The log sequence number in ibdata files does not match
InnoDB: the log sequence number in the ib_logfiles!
141230 22:50:02InnoDB: 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...
141230 22:50:02InnoDB: Started; log sequence number 0 44243
14:50:02 UTC - 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.
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=262144
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 = 133331 Kbytes 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



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.
141230 22:50:02 mysqld_safe mysqld from pid file /usr/local/mysql/var/debian.pid ended

licess 发表于 2014-12-31 09:57:36

首先检查硬盘或分区占用情况,再看https://bbs.vpser.net/thread-13040-1-1.html
页: [1]
查看完整版本: MYSQL启动不了,日志,可以帮看下吗