求助：ERROR! MySQL server PID file could not be found!
160621 16:29:30 mysqld_safe Starting mysqld daemon with databases from /usr/local/mysql/var160621 16:29:31 InnoDB: The InnoDB memory heap is disabled
160621 16:29:31 InnoDB: Mutexes and rw_locks use GCC atomic builtins
160621 16:29:31 InnoDB: Compressed tables use zlib 1.2.3
160621 16:29:31 InnoDB: Initializing buffer pool, size = 16.0M
160621 16:29:31 InnoDB: Completed initialization of buffer pool
160621 16:29:31 InnoDB: highest supported file format is Barracuda.
160621 16:29:31InnoDB: Waiting for the background threads to start
160621 16:29:32 InnoDB: 5.5.37 started; log sequence number 18038217
08:29:32 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 = 134092 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.
160621 16:29:32 mysqld_safe mysqld from pid file /usr/local/mysql/var/ZWCLC6X-9607.pid ended 解决，根目录空间被日志占满了
页:
[1]