56,678
社区成员
发帖
与我相关
我的任务
分享【mysql启动错误】请大神帮忙看下错误日志，分析下原因，指点一下解决方法，谢谢~
系统版本 centos 7 64位，mysql启动报错，最开始装了之后是能正常启动的，后来卸载了再重装，就无法启动了。
日志如下：
180430 10:09:59 mysqld_safe Logging to '/var/log/mysqld.log'.
180430 10:09:59 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
2018-04-30 10:10:00 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
2018-04-30 10:10:00 0 [Note] /usr/sbin/mysqld (mysqld 5.6.40) starting as process 10818 ...
2018-04-30 10:10:00 10818 [Warning] Buffered warning: Changed limits: max_open_files: 1024 (requested 5000)
2018-04-30 10:10:00 10818 [Warning] Buffered warning: Changed limits: table_open_cache: 431 (requested 2000)
2018-04-30 10:10:00 10818 [Note] Plugin 'FEDERATED' is disabled.
/usr/sbin/mysqld: Unknown storage engine 'InnoDB'
2018-04-30 10:10:00 10818 [ERROR] Can't open the mysql.plugin table. Please run mysql_upgrade to create it.
2018-04-30 10:10:00 10818 [Note] InnoDB: Using atomics to ref count buffer pool pages
2018-04-30 10:10:00 10818 [Note] InnoDB: The InnoDB memory heap is disabled
2018-04-30 10:10:00 10818 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2018-04-30 10:10:00 10818 [Note] InnoDB: Memory barrier is not used
2018-04-30 10:10:00 10818 [Note] InnoDB: Compressed tables use zlib 1.2.3
2018-04-30 10:10:00 10818 [Note] InnoDB: Using Linux native AIO
2018-04-30 10:10:00 10818 [Note] InnoDB: Using CPU crc32 instructions
2018-04-30 10:10:00 10818 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2018-04-30 10:10:00 10818 [Note] InnoDB: Completed initialization of buffer pool
2018-04-30 10:10:00 10818 [Note] InnoDB: Highest supported file format is Barracuda.
2018-04-30 10:10:00 10818 [Note] InnoDB: The log sequence numbers 2589937 and 2589937 in ibdata files do not match the log sequence number 2590220 in the ib_logfiles!
2018-04-30 10:10:00 10818 [Note] InnoDB: Database was not shutdown normally!
2018-04-30 10:10:00 10818 [Note] InnoDB: Starting crash recovery.
2018-04-30 10:10:00 10818 [Note] InnoDB: Reading tablespace information from the .ibd files...
2018-04-30 10:10:00 10818 [Note] InnoDB: Restoring possible half-written data pages
2018-04-30 10:10:00 10818 [Note] InnoDB: from the doublewrite buffer...
InnoDB: wrong number of columns in SYS_INDEXES record
InnoDB: wrong number of columns in SYS_INDEXES record
InnoDB: wrong number of columns in SYS_INDEXES record
InnoDB: wrong number of columns in SYS_INDEXES record
InnoDB: wrong number of columns in SYS_INDEXES record
02:10:00 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=8388608
read_buffer_size=131072
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 = 68108 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/sbin/mysqld(my_print_stacktrace+0x3b)[0x8e9ceb]
/usr/sbin/mysqld(handle_fatal_signal+0x491)[0x675ca1]
/lib64/libpthread.so.0(+0xf5e0)[0x7f5c9aa765e0]
/usr/sbin/mysqld[0xa6f8d8]
/usr/sbin/mysqld[0xa71819]
/usr/sbin/mysqld[0x9dda11]
/usr/sbin/mysqld[0x91b298]
/usr/sbin/mysqld(_Z24ha_initialize_handlertonP13st_plugin_int+0x48)[0x5b6028]
/usr/sbin/mysqld[0x6fe4e0]
/usr/sbin/mysqld(_Z11plugin_initPiPPci+0x940)[0x704cb0]
/usr/sbin/mysqld(_Z11mysqld_mainiPPc+0x8ad)[0x5af9ed]
/lib64/libc.so.6(__libc_start_main+0xf5)[0x7f5c9965cc05]
/usr/sbin/mysqld[0x5a24bd]
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.
180430 10:10:00 mysqld_safe mysqld from pid file /var/run/mysqld/mysqld.pid ended
180430 10:12:33 mysqld_safe Logging to '/var/log/mysqld.log'.
180430 10:12:33 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
2018-04-30 10:12:33 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
2018-04-30 10:12:33 0 [Note] /usr/sbin/mysqld (mysqld 5.6.40) starting as process 12289 ...
2018-04-30 10:12:33 12289 [Warning] Buffered warning: Changed limits: max_open_files: 1024 (requested 5000)
2018-04-30 10:12:33 12289 [Warning] Buffered warning: Changed limits: table_open_cache: 431 (requested 2000)
2018-04-30 10:12:33 12289 [Note] Plugin 'FEDERATED' is disabled.
/usr/sbin/mysqld: Unknown storage engine 'InnoDB'
2018-04-30 10:12:33 12289 [ERROR] Can't open the mysql.plugin table. Please run mysql_upgrade to create it.
2018-04-30 10:12:33 12289 [Note] InnoDB: Using atomics to ref count buffer pool pages
2018-04-30 10:12:33 12289 [Note] InnoDB: The InnoDB memory heap is disabled
2018-04-30 10:12:33 12289 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2018-04-30 10:12:33 12289 [Note] InnoDB: Memory barrier is not used
2018-04-30 10:12:33 12289 [Note] InnoDB: Compressed tables use zlib 1.2.3
2018-04-30 10:12:33 12289 [Note] InnoDB: Using Linux native AIO
2018-04-30 10:12:33 12289 [Note] InnoDB: Using CPU crc32 instructions
2018-04-30 10:12:33 12289 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2018-04-30 10:12:33 12289 [Note] InnoDB: Completed initialization of buffer pool
2018-04-30 10:12:33 12289 [Note] InnoDB: Highest supported file format is Barracuda.
2018-04-30 10:12:33 12289 [Note] InnoDB: The log sequence numbers 2589937 and 2589937 in ibdata files do not match the log sequence number 2590220 in the ib_logfiles!
2018-04-30 10:12:33 12289 [Note] InnoDB: Database was not shutdown normally!
2018-04-30 10:12:33 12289 [Note] InnoDB: Starting crash recovery.
2018-04-30 10:12:33 12289 [Note] InnoDB: Reading tablespace information from the .ibd files...
2018-04-30 10:12:33 12289 [Note] InnoDB: Restoring possible half-written data pages
2018-04-30 10:12:33 12289 [Note] InnoDB: from the doublewrite buffer...
InnoDB: wrong number of columns in SYS_INDEXES record
InnoDB: wrong number of columns in SYS_INDEXES record
InnoDB: wrong number of columns in SYS_INDEXES record
InnoDB: wrong number of columns in SYS_INDEXES record
InnoDB: wrong number of columns in SYS_INDEXES record
02:12:33 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=8388608
read_buffer_size=131072
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 = 68108 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/sbin/mysqld(my_print_stacktrace+0x3b)[0x8e9ceb]
/usr/sbin/mysqld(handle_fatal_signal+0x491)[0x675ca1]
/lib64/libpthread.so.0(+0xf5e0)[0x7fd2754855e0]
/usr/sbin/mysqld[0xa6f8d8]
/usr/sbin/mysqld[0xa71819]
/usr/sbin/mysqld[0x9dda11]
/usr/sbin/mysqld[0x91b298]
/usr/sbin/mysqld(_Z24ha_initialize_handlertonP13st_plugin_int+0x48)[0x5b6028]
/usr/sbin/mysqld[0x6fe4e0]
/usr/sbin/mysqld(_Z11plugin_initPiPPci+0x940)[0x704cb0]
/usr/sbin/mysqld(_Z11mysqld_mainiPPc+0x8ad)[0x5af9ed]
/lib64/libc.so.6(__libc_start_main+0xf5)[0x7fd27406bc05]
/usr/sbin/mysqld[0x5a24bd]
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.
180430 10:12:33 mysqld_safe mysqld from pid file /var/run/mysqld/mysqld.pid ended
日志如下：
180430 10:09:59 mysqld_safe Logging to '/var/log/mysqld.log'.
180430 10:09:59 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
2018-04-30 10:10:00 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
2018-04-30 10:10:00 0 [Note] /usr/sbin/mysqld (mysqld 5.6.40) starting as process 10818 ...
2018-04-30 10:10:00 10818 [Warning] Buffered warning: Changed limits: max_open_files: 1024 (requested 5000)
2018-04-30 10:10:00 10818 [Warning] Buffered warning: Changed limits: table_open_cache: 431 (requested 2000)
2018-04-30 10:10:00 10818 [Note] Plugin 'FEDERATED' is disabled.
/usr/sbin/mysqld: Unknown storage engine 'InnoDB'
2018-04-30 10:10:00 10818 [ERROR] Can't open the mysql.plugin table. Please run mysql_upgrade to create it.
2018-04-30 10:10:00 10818 [Note] InnoDB: Using atomics to ref count buffer pool pages
2018-04-30 10:10:00 10818 [Note] InnoDB: The InnoDB memory heap is disabled
2018-04-30 10:10:00 10818 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2018-04-30 10:10:00 10818 [Note] InnoDB: Memory barrier is not used
2018-04-30 10:10:00 10818 [Note] InnoDB: Compressed tables use zlib 1.2.3
2018-04-30 10:10:00 10818 [Note] InnoDB: Using Linux native AIO
2018-04-30 10:10:00 10818 [Note] InnoDB: Using CPU crc32 instructions
2018-04-30 10:10:00 10818 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2018-04-30 10:10:00 10818 [Note] InnoDB: Completed initialization of buffer pool
2018-04-30 10:10:00 10818 [Note] InnoDB: Highest supported file format is Barracuda.
2018-04-30 10:10:00 10818 [Note] InnoDB: The log sequence numbers 2589937 and 2589937 in ibdata files do not match the log sequence number 2590220 in the ib_logfiles!
2018-04-30 10:10:00 10818 [Note] InnoDB: Database was not shutdown normally!
2018-04-30 10:10:00 10818 [Note] InnoDB: Starting crash recovery.
2018-04-30 10:10:00 10818 [Note] InnoDB: Reading tablespace information from the .ibd files...
2018-04-30 10:10:00 10818 [Note] InnoDB: Restoring possible half-written data pages
2018-04-30 10:10:00 10818 [Note] InnoDB: from the doublewrite buffer...
InnoDB: wrong number of columns in SYS_INDEXES record
InnoDB: wrong number of columns in SYS_INDEXES record
InnoDB: wrong number of columns in SYS_INDEXES record
InnoDB: wrong number of columns in SYS_INDEXES record
InnoDB: wrong number of columns in SYS_INDEXES record
02:10:00 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=8388608
read_buffer_size=131072
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 = 68108 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/sbin/mysqld(my_print_stacktrace+0x3b)[0x8e9ceb]
/usr/sbin/mysqld(handle_fatal_signal+0x491)[0x675ca1]
/lib64/libpthread.so.0(+0xf5e0)[0x7f5c9aa765e0]
/usr/sbin/mysqld[0xa6f8d8]
/usr/sbin/mysqld[0xa71819]
/usr/sbin/mysqld[0x9dda11]
/usr/sbin/mysqld[0x91b298]
/usr/sbin/mysqld(_Z24ha_initialize_handlertonP13st_plugin_int+0x48)[0x5b6028]
/usr/sbin/mysqld[0x6fe4e0]
/usr/sbin/mysqld(_Z11plugin_initPiPPci+0x940)[0x704cb0]
/usr/sbin/mysqld(_Z11mysqld_mainiPPc+0x8ad)[0x5af9ed]
/lib64/libc.so.6(__libc_start_main+0xf5)[0x7f5c9965cc05]
/usr/sbin/mysqld[0x5a24bd]
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.
180430 10:10:00 mysqld_safe mysqld from pid file /var/run/mysqld/mysqld.pid ended
180430 10:12:33 mysqld_safe Logging to '/var/log/mysqld.log'.
180430 10:12:33 mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
2018-04-30 10:12:33 0 [Warning] TIMESTAMP with implicit DEFAULT value is deprecated. Please use --explicit_defaults_for_timestamp server option (see documentation for more details).
2018-04-30 10:12:33 0 [Note] /usr/sbin/mysqld (mysqld 5.6.40) starting as process 12289 ...
2018-04-30 10:12:33 12289 [Warning] Buffered warning: Changed limits: max_open_files: 1024 (requested 5000)
2018-04-30 10:12:33 12289 [Warning] Buffered warning: Changed limits: table_open_cache: 431 (requested 2000)
2018-04-30 10:12:33 12289 [Note] Plugin 'FEDERATED' is disabled.
/usr/sbin/mysqld: Unknown storage engine 'InnoDB'
2018-04-30 10:12:33 12289 [ERROR] Can't open the mysql.plugin table. Please run mysql_upgrade to create it.
2018-04-30 10:12:33 12289 [Note] InnoDB: Using atomics to ref count buffer pool pages
2018-04-30 10:12:33 12289 [Note] InnoDB: The InnoDB memory heap is disabled
2018-04-30 10:12:33 12289 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
2018-04-30 10:12:33 12289 [Note] InnoDB: Memory barrier is not used
2018-04-30 10:12:33 12289 [Note] InnoDB: Compressed tables use zlib 1.2.3
2018-04-30 10:12:33 12289 [Note] InnoDB: Using Linux native AIO
2018-04-30 10:12:33 12289 [Note] InnoDB: Using CPU crc32 instructions
2018-04-30 10:12:33 12289 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2018-04-30 10:12:33 12289 [Note] InnoDB: Completed initialization of buffer pool
2018-04-30 10:12:33 12289 [Note] InnoDB: Highest supported file format is Barracuda.
2018-04-30 10:12:33 12289 [Note] InnoDB: The log sequence numbers 2589937 and 2589937 in ibdata files do not match the log sequence number 2590220 in the ib_logfiles!
2018-04-30 10:12:33 12289 [Note] InnoDB: Database was not shutdown normally!
2018-04-30 10:12:33 12289 [Note] InnoDB: Starting crash recovery.
2018-04-30 10:12:33 12289 [Note] InnoDB: Reading tablespace information from the .ibd files...
2018-04-30 10:12:33 12289 [Note] InnoDB: Restoring possible half-written data pages
2018-04-30 10:12:33 12289 [Note] InnoDB: from the doublewrite buffer...
InnoDB: wrong number of columns in SYS_INDEXES record
InnoDB: wrong number of columns in SYS_INDEXES record
InnoDB: wrong number of columns in SYS_INDEXES record
InnoDB: wrong number of columns in SYS_INDEXES record
InnoDB: wrong number of columns in SYS_INDEXES record
02:12:33 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=8388608
read_buffer_size=131072
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 = 68108 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/sbin/mysqld(my_print_stacktrace+0x3b)[0x8e9ceb]
/usr/sbin/mysqld(handle_fatal_signal+0x491)[0x675ca1]
/lib64/libpthread.so.0(+0xf5e0)[0x7fd2754855e0]
/usr/sbin/mysqld[0xa6f8d8]
/usr/sbin/mysqld[0xa71819]
/usr/sbin/mysqld[0x9dda11]
/usr/sbin/mysqld[0x91b298]
/usr/sbin/mysqld(_Z24ha_initialize_handlertonP13st_plugin_int+0x48)[0x5b6028]
/usr/sbin/mysqld[0x6fe4e0]
/usr/sbin/mysqld(_Z11plugin_initPiPPci+0x940)[0x704cb0]
/usr/sbin/mysqld(_Z11mysqld_mainiPPc+0x8ad)[0x5af9ed]
/lib64/libc.so.6(__libc_start_main+0xf5)[0x7fd27406bc05]
/usr/sbin/mysqld[0x5a24bd]
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.
180430 10:12:33 mysqld_safe mysqld from pid file /var/run/mysqld/mysqld.pid ended
...全文
请发表友善的回复…
发表回复
