hakiu 发表于 2016-1-13 18:52:13

mysql好好的启动不了了

160113 18:44:46 mysqld_safe Starting mysqld daemon with databases from /usr/local/mysql/var
160113 18:44:46 Plugin 'InnoDB' is disabled.
10:44:46 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=1000
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 = 795907 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 0x40000
/usr/local/mysql/bin/mysqld(my_print_stacktrace+0x2e)
/usr/local/mysql/bin/mysqld(handle_fatal_signal+0x41a)
/lib64/libpthread.so.0
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.
160113 18:44:46 mysqld_safe mysqld from pid file /usr/local/mysql/var/user.pid ended

licess 发表于 2016-1-14 09:26:49

首先检查硬盘或分区占用情况,再看https://bbs.vpser.net/thread-13040-1-1.html
页: [1]
查看完整版本: mysql好好的启动不了了