ERROR! MySQL server PID file could not be found!

yisou

171209 15:48:58 mysqld_safe Starting mysqld daemon with databases from /usr/local/mysql/var
2017-12-09 15:48:58 0 [Note] /usr/local/mysql/bin/mysqld (mysqld 5.6.29-log) starting as process 9892 ...
2017-12-09 15:48:58 9892 [Note] Plugin 'FEDERATED' is disabled.
2017-12-09 15:48:58 9892 [Note] InnoDB: Using atomics to ref count buffer pool pages
2017-12-09 15:48:58 9892 [Note] InnoDB: The InnoDB memory heap is disabled
2017-12-09 15:48:58 9892 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2017-12-09 15:48:58 9892 [Note] InnoDB: Memory barrier is not used
2017-12-09 15:48:58 9892 [Note] InnoDB: Compressed tables use zlib 1.2.3
2017-12-09 15:48:58 9892 [Note] InnoDB: Using CPU crc32 instructions
2017-12-09 15:48:58 9892 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2017-12-09 15:48:58 9892 [Note] InnoDB: Completed initialization of buffer pool
2017-12-09 15:48:58 9892 [Note] InnoDB: Highest supported file format is Barracuda.
2017-12-09 15:48:58 9892 [Note] InnoDB: The log sequence numbers 1626024 and 1626024 in ibdata files do not match the log sequence number 1639374 in the ib_logfiles!
2017-12-09 15:48:58 9892 [Note] InnoDB: Database was not shutdown normally!
2017-12-09 15:48:58 9892 [Note] InnoDB: Starting crash recovery.
2017-12-09 15:48:58 9892 [Note] InnoDB: Reading tablespace information from the .ibd files...
2017-12-09 15:48:58 9892 [Note] InnoDB: Restoring possible half-written data pages
2017-12-09 15:48:58 9892 [Note] InnoDB: from the doublewrite buffer...
InnoDB: Last MySQL binlog file position 0 6526515, file name mysql-bin.000006
2017-12-09 15:48:58 9892 [Note] InnoDB: 128 rollback segment(s) are active.
2017-12-09 15:48:58 9892 [Note] InnoDB: Waiting for purge to start
2017-12-09 15:48:58 9892 [Note] InnoDB: 5.6.29 started; log sequence number 1639374
07:48:58 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=33554432
read_buffer_size=786432
max_used_connections=0
max_threads=500
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 = 807154 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+0x35)[0x8ec255]
/usr/local/mysql/bin/mysqld(handle_fatal_signal+0x41b)[0x6543fb]
/lib64/libpthread.so.0(+0xf7e0)[0x7fc9cdb637e0]
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.
171209 15:48:58 mysqld_safe mysqld from pid file /usr/local/mysql/var/ZWCLC6-AMP-12859.pid ended

licess

硬盘或分区可能满了