VPS重启后MYSQL启动不起了求助
Usage: /root/lnmp {start|stop|reload|restart|kill|status}=========================================================================
Stoping LNMP...
Stopping nginx daemon: nginx.
Gracefully shutting down php-fpm . done
ERROR! MySQL server PID file could not be found!
Starting LNMP...
Starting nginx daemon: nginx.
Starting php-fpmdone
Starting MySQL.. ERROR! The server quit without updating PID file (/usr/local/mysql/var/default.hostname.pid).
Exit code: 1
# ps aux |grep mysq*
root 42390.00.1 30401168 ? Ss 17:34 0:00 /bin/bash -c cd "/"; ps aux |grep mysq* 2>&1 | head -n 10000; echo
# kill 4239
/bin/bash: line 0: kill: (4239) - No such process
Exit code: 1
# service mysql start
Starting MySQL........ ERROR! The server quit without updating PID file (/usr/local/mysql/var/default.hostname.pid).
Exit code: 1
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 133456 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 0x30000
/usr/local/mysql/bin/mysqld(my_print_stacktrace+0x33)
/usr/local/mysql/bin/mysqld(handle_fatal_signal+0x432)
/lib/libc.so.6(abort+0x17a)
/usr/local/mysql/bin/mysqld
/usr/local/mysql/bin/mysqld
/usr/local/mysql/bin/mysqld
/usr/local/mysql/bin/mysqld
/usr/local/mysql/bin/mysqld
/usr/local/mysql/bin/mysqld
/usr/local/mysql/bin/mysqld
/lib/libpthread.so.0(+0x6a49)
/lib/libc.so.6(clone+0x5e)
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.
160703 17:35:58 mysqld_safe mysqld from pid file /usr/local/mysql/var/default.hostname.pid ended 错误信息。。。
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 = 133456 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 0x30000
/usr/local/mysql/bin/mysqld(my_print_stacktrace+0x33)
/usr/local/mysql/bin/mysqld(handle_fatal_signal+0x432)
/lib/libc.so.6(abort+0x17a)
/usr/local/mysql/bin/mysqld
/usr/local/mysql/bin/mysqld
/usr/local/mysql/bin/mysqld
160703 17:58:02 Event Scheduler: Loaded 0 events
160703 17:58:02 /usr/local/mysql/bin/mysqld: ready for connections.
Version: '5.5.28-log'socket: '/tmp/mysql.sock'port: 3306Source distribution
/usr/local/mysql/bin/mysqld
/usr/local/mysql/bin/mysqld
/usr/local/mysql/bin/mysqld
/usr/local/mysql/bin/mysqld
/lib/libpthread.so.0(+0x6a49)
/lib/libc.so.6(clone+0x5e)
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.
160703 17:58:02 mysqld_safe Number of processes running now: 0
160703 17:58:02 mysqld_safe mysqld restarted
160703 17:58:02 InnoDB: The InnoDB memory heap is disabled
160703 17:58:02 InnoDB: Mutexes and rw_locks use GCC atomic builtins
160703 17:58:02 InnoDB: Compressed tables use zlib 1.2.3
160703 17:58:02 InnoDB: Initializing buffer pool, size = 16.0M
160703 17:58:02 InnoDB: Completed initialization of buffer pool
160703 17:58:02 InnoDB: highest supported file format is Barracuda.
InnoDB: The log sequence number in ibdata files does not match
InnoDB: the log sequence number in the ib_logfiles!
160703 17:58:02InnoDB: 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: Last MySQL binlog file position 0 5602, file name ./mysql-bin.000126
160703 17:58:02InnoDB: Waiting for the background threads to start
160703 17:58:03 InnoDB: 1.1.8 started; log sequence number 4422896040
160703 17:58:03 Recovering after a crash using mysql-bin
160703 17:58:03 Starting crash recovery...
160703 17:58:03 Crash recovery finished.
160703 17:58:03 Server hostname (bind-address): '0.0.0.0'; port: 3306
160703 17:58:03 - '0.0.0.0' resolves to '0.0.0.0';
160703 17:58:03 Server socket created on IP: '0.0.0.0'.
160703 17:58:03InnoDB: Assertion failure in thread 2874518384 in file trx0purge.c line 829
InnoDB: Failing assertion: purge_sys->purge_trx_no <= purge_sys->rseg->last_trx_no
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
InnoDB: If you get repeated assertion failures or crashes, even
InnoDB: immediately after the mysqld startup, there may be
InnoDB: corruption in the InnoDB tablespace. Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
09:58:03 UTC - mysqld got signal 6 ;
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 = 133456 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 0x30000
/usr/local/mysql/bin/mysqld(my_print_stacktrace+0x33)
/usr/local/mysql/bin/mysqld(handle_fatal_signal+0x432)
/lib/libc.so.6(abort+0x17a)
/usr/local/mysql/bin/mysqld
/usr/local/mysql/bin/mysqld
/usr/local/mysql/bin/mysqld
/usr/local/mysql/bin/mysqld
/usr/local/mysql/bin/mysqld
/usr/local/mysql/bin/mysqld
/usr/local/mysql/bin/mysqld
/lib/libpthread.so.0(+0x6a49)
/lib/libc.so.6(clone+0x5e)
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.
160703 17:58:03 mysqld_safe mysqld from pid file /usr/local/mysql/var/default.hostname.pid ended 首先检查硬盘或分区占用情况，不行的话再试试看https://bbs.vpser.net/thread-13040-1-1.html
回复 3# 的帖子
innodb_force_recovery=6加上这个 可以正常启动
修复了数据库 有些提示不能直接修复的
去掉innodb_force_recovery=6后 还是 原来那样
页:
[1]