数据库奔溃
191021 9:54:32 [Note] Plugin 'FEDERATED' is disabled.
191021 9:54:32 InnoDB: The InnoDB memory heap is disabled
191021 9:54:32 InnoDB: Mutexes and rw_locks use GCC atomic builtins
191021 9:54:32 InnoDB: Compressed tables use zlib 1.2.11
191021 9:54:32 InnoDB: Initializing buffer pool, size = 128.0M
191021 9:54:32 InnoDB: Completed initialization of buffer pool
InnoDB: Database page corruption on disk or a failed
InnoDB: file read of page 5.
InnoDB: You may have to recover from a backup.
191021 9:54:33 InnoDB: Page dump in ascii and hex (16384 bytes):
InnoDB: End of page dump
191021 9:54:33 InnoDB: Page checksum 931012578, prior-to-4.0.14-form checksum 3279382822
InnoDB: stored checksum 931012578, prior-to-4.0.14-form stored checksum 3721273398
InnoDB: Page lsn 0 1418356529, low 4 bytes of lsn at page end 1418352050
InnoDB: Page number (if stored to page already) 5,
InnoDB: space id (if created with >= MySQL-4.1.1 and stored already) 0
InnoDB: Page may be a transaction system page
InnoDB: Database page corruption on disk or a failed
InnoDB: file read of page 5.
InnoDB: You may have to recover from a backup.
InnoDB: It is also possible that your operating
InnoDB: system has corrupted its own file cache
InnoDB: and rebooting your computer removes the
InnoDB: error.
InnoDB: If the corrupt page is an index page
InnoDB: you can also try to fix the corruption
InnoDB: by dumping, dropping, and reimporting
InnoDB: the corrupt table. You can use CHECK
InnoDB: TABLE to scan your table for corruption.
InnoDB: See also http://dev.mysql.com/doc/refman/5.5/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
InnoDB: Ending processing because of a corrupt database page.
191021 9:54:33 InnoDB: Assertion failure in thread 140516137690944 in file buf0buf.c line 3623
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.
01:54:33 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=12582912
read_buffer_size=1048576
max_used_connections=0
max_threads=300
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 = 630147 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
/www/wdlinux/mysql-5.5.62/bin/mysqld(my_print_stacktrace+0x20)[0x7667e0]
/www/wdlinux/mysql-5.5.62/bin/mysqld(handle_fatal_signal+0x359)[0x65d5a9]
/lib64/libpthread.so.0(+0xf5d0)[0x7fcc7636f5d0]
/lib64/libc.so.6(gsignal+0x37)[0x7fcc7536f207]
/lib64/libc.so.6(abort+0x148)[0x7fcc753708f8]
/www/wdlinux/mysql-5.5.62/bin/mysqld[0x7e0646]
/www/wdlinux/mysql-5.5.62/bin/mysqld[0x7ea970]
/www/wdlinux/mysql-5.5.62/bin/mysqld[0x7eb243]
/www/wdlinux/mysql-5.5.62/bin/mysqld[0x7dc5e9]
/www/wdlinux/mysql-5.5.62/bin/mysqld[0x7b22d6]
/www/wdlinux/mysql-5.5.62/bin/mysqld[0x7b40ce]
/www/wdlinux/mysql-5.5.62/bin/mysqld[0x7a1a22]
/www/wdlinux/mysql-5.5.62/bin/mysqld[0x772ca4]
/www/wdlinux/mysql-5.5.62/bin/mysqld(_Z24ha_initialize_handlertonP13st_plugin_int+0x41)[0x65f461]
/www/wdlinux/mysql-5.5.62/bin/mysqld[0x58aed6]
/www/wdlinux/mysql-5.5.62/bin/mysqld(_Z11plugin_initPiPPci+0x860)[0x58ebf0]
/www/wdlinux/mysql-5.5.62/bin/mysqld[0x517c54]
/www/wdlinux/mysql-5.5.62/bin/mysqld(_Z11mysqld_mainiPPc+0x38b)[0x51c57b]
/lib64/libc.so.6(__libc_start_main+0xf5)[0x7fcc7535b3d5]
/www/wdlinux/mysql-5.5.62/bin/mysqld[0x513ac5]
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.
数据库奔溃
lnmp restart
出现Starting MySQL..................................
然后就启动不起来。
要kill -9 掉后台的mysql进程才行，执行lnmp stop也没有杀死mysql
日志有大量这个错误
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock /usr/local/mysql/var/ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock /usr/local/mysql/var/ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock /usr/local/mysql/var/ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
InnoDB: Unable to lock /usr/local/mysql/var/ibdata1, error: 11
InnoDB: Check that you do not already have another mysqld process
InnoDB: using the same InnoDB data or log files.
我看了下数据库，没有用到InnoDB，有办法禁用InnoDB或卸载他吗？
是不是禁用了InnoDB应该就正常了，现在用的是正式版最新的
检查方法：
检查一下是否有其他mysql进程在运行，是否有其他程序占用了3306端口
有mysql进程需要先kill掉
kill -9 pidof mysqld
然后 mv ibdata1 ibdata1.backup
再尝试启动