【新手小白求救】mysql 启动MySQL server PID file could not be found!
centos 64位key_buffer_size=1677160318 20:32:35 mysqld_safe mysqld from pid file /usr/local/mysql/var/VM_10_67_centos.pid ended160318 20:47:14 mysqld_safe Starting mysqld daemon with databases from /usr/local/mysql/var160318 20:47:14 InnoDB: The InnoDB memory heap is disabled160318 20:47:14 InnoDB: Mutexes and rw_locks use GCC atomic builtins160318 20:47:14 InnoDB: Compressed tables use zlib 1.2.7160318 20:47:14 InnoDB: Initializing buffer pool, size = 16.0M160318 20:47:14 InnoDB: Completed initialization of buffer pool160318 20:47:14 InnoDB: highest supported file format is Barracuda.InnoDB: Log scan progressed past the checkpoint lsn 208366134160318 20:47:14InnoDB: 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 doublewriteInnoDB: buffer...InnoDB: Doing recovery: scanned up to log sequence number 208366144InnoDB: Last MySQL binlog file position 0 2699, file name ./mysql-bin.000008160318 20:47:14InnoDB: Waiting for the background threads to start160318 20:47:15 InnoDB: 5.5.42 started; log sequence number 20836614412:47:15 UTC - mysqld got signal 11 ;This could be because you hit a bug. It is also possible that this binaryor 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 helpdiagnose the problem, but since we have already crashed, something is definitely wrong and this may fail.key_buffer_size=16777216read_buffer_size=262144max_used_connections=0max_threads=1000thread_count=0connection_count=0It is possible that mysqld could use up to key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 795907 Kbytes of memoryHope that's ok; if not, decrease some variables in the equation.Thread pointer: 0x0Attempting backtrace. You can use the following information to find outwhere mysqld died. If you see no messages after this, something wentterribly wrong...stack_bottom = 0 thread_stack 0x40000/usr/local/mysql/bin/mysqld(my_print_stacktrace+0x20)/usr/local/mysql/bin/mysqld(handle_fatal_signal+0x359)/usr/lib64/libpthread.so.0(+0xf130)The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html containsinformation that should help you find out what is causing the crash.160318 20:47:15 mysqld_safe mysqld from pid file /usr/local/mysql/var/VM_10_67_centos.pid ended 日志文件说明
军哥怎么办呐？？？？？？？？？？？？？？？？？？？？？？？？？？？？？？？？？？？？
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+0x20)
/usr/local/mysql/bin/mysqld(handle_fatal_signal+0x359)
/usr/lib64/libpthread.so.0(+0xf130)
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.
160318 20:31:55 mysqld_safe mysqld from pid file /usr/local/mysql/var/VM_10_67_centos.pid ended
160318 20:32:33 mysqld_safe Starting mysqld daemon with databases from /usr/local/mysql/var
160318 20:32:33 InnoDB: The InnoDB memory heap is disabled
160318 20:32:33 InnoDB: Mutexes and rw_locks use GCC atomic builtins
160318 20:32:33 InnoDB: Compressed tables use zlib 1.2.7
160318 20:32:34 InnoDB: Initializing buffer pool, size = 16.0M
160318 20:32:34 InnoDB: Completed initialization of buffer pool
160318 20:32:34 InnoDB: highest supported file format is Barracuda.
InnoDB: Log scan progressed past the checkpoint lsn 208366134
160318 20:32:34InnoDB: 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...
InnoDB: Doing recovery: scanned up to log sequence number 208366144
InnoDB: Last MySQL binlog file position 0 2699, file name ./mysql-bin.000008
160318 20:32:34InnoDB: Waiting for the background threads to start
160318 20:32:35 InnoDB: 5.5.42 started; log sequence number 208366144
12:32:35 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=1677160318 20:32:35 mysqld_safe mysqld from pid file /usr/local/mysql/var/VM_10_67_centos.pid ended
160318 20:47:14 mysqld_safe Starting mysqld daemon with databases from /usr/local/mysql/var
160318 20:47:14 InnoDB: The InnoDB memory heap is disabled
160318 20:47:14 InnoDB: Mutexes and rw_locks use GCC atomic builtins
160318 20:47:14 InnoDB: Compressed tables use zlib 1.2.7
160318 20:47:14 InnoDB: Initializing buffer pool, size = 16.0M
160318 20:47:14 InnoDB: Completed initialization of buffer pool
160318 20:47:14 InnoDB: highest supported file format is Barracuda.
InnoDB: Log scan progressed past the checkpoint lsn 208366134
160318 20:47:14InnoDB: 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...
InnoDB: Doing recovery: scanned up to log sequence number 208366144
InnoDB: Last MySQL binlog file position 0 2699, file name ./mysql-bin.000008
160318 20:47:14InnoDB: Waiting for the background threads to start
160318 20:47:15 InnoDB: 5.5.42 started; log sequence number 208366144
12:47:15 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+0x20)
/usr/local/mysql/bin/mysqld(handle_fatal_signal+0x359)
/usr/lib64/libpthread.so.0(+0xf130)
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.
160318 20:47:15 mysqld_safe mysqld from pid file /usr/local/mysql/var/VM_10_67_centos.pid ended 首先检查硬盘或分区占用情况，再看https://bbs.vpser.net/thread-13040-1-1.html
http://bbs.vpser.net/thread-13040-1-1.html
军哥还是不行啊，怎么办好急啊，拜托军哥了。回复 3# 的帖子
军哥还是不行啊，怎么办好急啊，拜托军哥了。 目前别没其他什么好办法 和你一个问题，解决没有呀
页:
[1]