- 积分
- 19
- 威望
-
- 金钱
-
- 注册时间
- 2016-1-13
- 在线时间
- 小时
- 最后登录
- 1970-1-1
|
160113 18:44:46 mysqld_safe Starting mysqld daemon with databases from /usr/local/mysql/var
160113 18:44:46 [Note] 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 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 0x40000
/usr/local/mysql/bin/mysqld(my_print_stacktrace+0x2e)[0x760ece]
/usr/local/mysql/bin/mysqld(handle_fatal_signal+0x41a)[0x654daa]
/lib64/libpthread.so.0[0x3643c0f710]
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 |
|