MySQL
mysql 数据库无法启动INNODB 怎么办求高手解决
墨衍会员 · AI 创作全网分发 墨衍智能分发 通过墨衍一键同步至各平台 可同步平台 CSDN微信公众号微博知乎掘金百家号博客园抖音小红书 你的文章也可以这样分发 墨衍会员 ¥399起/年，写一次发全网
我也要 关注 + 加入社区131016 15:33:18 mysqld_safe Starting mysqld daemon with databases from /alidata/server/mysql/var
131016 15:33:18 InnoDB: Initializing buffer pool, size = 800.0M
131016 15:33:18 InnoDB: Completed initialization of buffer pool
InnoDB: The log sequence number in ibdata files does not match
InnoDB: the log sequence number in the ib_logfiles!
131016 15:33:18 InnoDB: 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...
131016 15:33:18 InnoDB: Error: page 7 log sequence number 110 2657205495
InnoDB: is in the future! Current system log sequence number 0 3114505740.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-innodb-recovery.html
InnoDB: for more information.
131016 15:33:18 InnoDB: Error: page 1 log sequence number 93 3574294358
InnoDB: is in the future! Current system log sequence number 0 3114505740.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-innodb-recovery.html
InnoDB: for more information.
131016 15:33:18 InnoDB: Error: page 3 log sequence number 93 3574294358
InnoDB: is in the future! Current system log sequence number 0 3114505740.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-innodb-recovery.html
InnoDB: for more information.
131016 15:33:18 InnoDB: Error: page 2 log sequence number 110 2705000881
InnoDB: is in the future! Current system log sequence number 0 3114505740.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-innodb-recovery.html
InnoDB: for more information.
131016 15:33:18 InnoDB: Error: page 4 log sequence number 110 2721370334
InnoDB: is in the future! Current system log sequence number 0 3114505740.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-innodb-recovery.html
InnoDB: for more information.
131016 15:33:18 InnoDB: Error: page 11 log sequence number 110 1269294416
InnoDB: is in the future! Current system log sequence number 0 3114505740.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-innodb-recovery.html
InnoDB: for more information.
131016 15:33:18 InnoDB: Error: page 62 log sequence number 4 1403116640
InnoDB: is in the future! Current system log sequence number 0 3114505740.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-innodb-recovery.html
InnoDB: for more information.
131016 15:33:18 InnoDB: Error: page 5 log sequence number 110 2791303633
InnoDB: is in the future! Current system log sequence number 0 3114505740.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-innodb-recovery.html
InnoDB: for more information.
131016 15:33:18 InnoDB: Error: page 6 log sequence number 110 2791553052
InnoDB: is in the future! Current system log sequence number 0 3114505740.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-innodb-recovery.html
InnoDB: for more information.
131016 15:33:18 InnoDB: Error: page 769 log sequence number 110 2892239346
InnoDB: is in the future! Current system log sequence number 0 3114505740.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-innodb-recovery.html
InnoDB: for more information.
InnoDB: Error: trying to access page number 77451818 in space 0,
InnoDB: space name /alidata/server/mysql/var/ibdata1,
InnoDB: which is outside the tablespace bounds.
InnoDB: Byte offset 0, len 16384, i/o type 10.
InnoDB: If you get this error at mysqld startup, please check that
InnoDB: your my.cnf matches the ibdata files that you have in the
InnoDB: MySQL server.
131016 15:33:18 InnoDB: Assertion failure in thread 139702648760096 in file fil/fil0fil.c line 4135
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.1/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
07:33:18 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=268435456
read_buffer_size=33554432
max_used_connections=0
max_threads=1024
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 = 67381600 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
/alidata/server/mysql/libexec/mysqld(my_print_stacktrace+0x29) [0x883349]
/alidata/server/mysql/libexec/mysqld(handle_fatal_signal+0x41a) [0x6db72a]
/lib64/libpthread.so.0(+0xf500) [0x7f0f0e7ed500]
/lib64/libc.so.6(gsignal+0x35) [0x7f0f0d6778a5]
/lib64/libc.so.6(abort+0x175) [0x7f0f0d679085]
/alidata/server/mysql/libexec/mysqld(fil_io+0x34e) [0x7a33fe]
/alidata/server/mysql/libexec/mysqld() [0x78be10]
/alidata/server/mysql/libexec/mysqld(buf_read_page+0x21d) [0x78c7ed]
/alidata/server/mysql/libexec/mysqld(buf_page_get_gen+0x363) [0x7863d3]
/alidata/server/mysql/libexec/mysqld(trx_undo_lists_init+0x41b) [0x8164cb]
/alidata/server/mysql/libexec/mysqld() [0x80ce81]
/alidata/server/mysql/libexec/mysqld(trx_rseg_list_and_array_init+0xa3) [0x80d0a3]
/alidata/server/mysql/libexec/mysqld(trx_sys_init_at_db_start+0x140) [0x80de20]
/alidata/server/mysql/libexec/mysqld(innobase_start_or_create_for_mysql+0xfef) [0x7ff0df]
/alidata/server/mysql/libexec/mysqld() [0x76ad6a]
/alidata/server/mysql/libexec/mysqld(ha_initialize_handlerton(st_plugin_int*)+0x31) [0x6cc8d1]
/alidata/server/mysql/libexec/mysqld() [0x753dfd]
/alidata/server/mysql/libexec/mysqld(plugin_init(int*, char**, int)+0x720) [0x755c50]
/alidata/server/mysql/libexec/mysqld() [0x5e5d4f]
/alidata/server/mysql/libexec/mysqld(main+0x1c6) [0x5e9df6]
/lib64/libc.so.6(__libc_start_main+0xfd) [0x7f0f0d663cdd]
/alidata/server/mysql/libexec/mysqld() [0x522479]
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.
131016 15:33:18 mysqld_safe mysqld from pid file /alidata/server/mysql/var/AY131011212338503c43Z.pid ended
这是错误日志 高手帮帮忙啊
131016 15:33:18 InnoDB: Initializing buffer pool, size = 800.0M
131016 15:33:18 InnoDB: Completed initialization of buffer pool
InnoDB: The log sequence number in ibdata files does not match
InnoDB: the log sequence number in the ib_logfiles!
131016 15:33:18 InnoDB: 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...
131016 15:33:18 InnoDB: Error: page 7 log sequence number 110 2657205495
InnoDB: is in the future! Current system log sequence number 0 3114505740.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-innodb-recovery.html
InnoDB: for more information.
131016 15:33:18 InnoDB: Error: page 1 log sequence number 93 3574294358
InnoDB: is in the future! Current system log sequence number 0 3114505740.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-innodb-recovery.html
InnoDB: for more information.
131016 15:33:18 InnoDB: Error: page 3 log sequence number 93 3574294358
InnoDB: is in the future! Current system log sequence number 0 3114505740.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-innodb-recovery.html
InnoDB: for more information.
131016 15:33:18 InnoDB: Error: page 2 log sequence number 110 2705000881
InnoDB: is in the future! Current system log sequence number 0 3114505740.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-innodb-recovery.html
InnoDB: for more information.
131016 15:33:18 InnoDB: Error: page 4 log sequence number 110 2721370334
InnoDB: is in the future! Current system log sequence number 0 3114505740.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-innodb-recovery.html
InnoDB: for more information.
131016 15:33:18 InnoDB: Error: page 11 log sequence number 110 1269294416
InnoDB: is in the future! Current system log sequence number 0 3114505740.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-innodb-recovery.html
InnoDB: for more information.
131016 15:33:18 InnoDB: Error: page 62 log sequence number 4 1403116640
InnoDB: is in the future! Current system log sequence number 0 3114505740.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-innodb-recovery.html
InnoDB: for more information.
131016 15:33:18 InnoDB: Error: page 5 log sequence number 110 2791303633
InnoDB: is in the future! Current system log sequence number 0 3114505740.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-innodb-recovery.html
InnoDB: for more information.
131016 15:33:18 InnoDB: Error: page 6 log sequence number 110 2791553052
InnoDB: is in the future! Current system log sequence number 0 3114505740.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-innodb-recovery.html
InnoDB: for more information.
131016 15:33:18 InnoDB: Error: page 769 log sequence number 110 2892239346
InnoDB: is in the future! Current system log sequence number 0 3114505740.
InnoDB: Your database may be corrupt or you may have copied the InnoDB
InnoDB: tablespace but not the InnoDB log files. See
InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-innodb-recovery.html
InnoDB: for more information.
InnoDB: Error: trying to access page number 77451818 in space 0,
InnoDB: space name /alidata/server/mysql/var/ibdata1,
InnoDB: which is outside the tablespace bounds.
InnoDB: Byte offset 0, len 16384, i/o type 10.
InnoDB: If you get this error at mysqld startup, please check that
InnoDB: your my.cnf matches the ibdata files that you have in the
InnoDB: MySQL server.
131016 15:33:18 InnoDB: Assertion failure in thread 139702648760096 in file fil/fil0fil.c line 4135
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.1/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
07:33:18 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=268435456
read_buffer_size=33554432
max_used_connections=0
max_threads=1024
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 = 67381600 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
/alidata/server/mysql/libexec/mysqld(my_print_stacktrace+0x29) [0x883349]
/alidata/server/mysql/libexec/mysqld(handle_fatal_signal+0x41a) [0x6db72a]
/lib64/libpthread.so.0(+0xf500) [0x7f0f0e7ed500]
/lib64/libc.so.6(gsignal+0x35) [0x7f0f0d6778a5]
/lib64/libc.so.6(abort+0x175) [0x7f0f0d679085]
/alidata/server/mysql/libexec/mysqld(fil_io+0x34e) [0x7a33fe]
/alidata/server/mysql/libexec/mysqld() [0x78be10]
/alidata/server/mysql/libexec/mysqld(buf_read_page+0x21d) [0x78c7ed]
/alidata/server/mysql/libexec/mysqld(buf_page_get_gen+0x363) [0x7863d3]
/alidata/server/mysql/libexec/mysqld(trx_undo_lists_init+0x41b) [0x8164cb]
/alidata/server/mysql/libexec/mysqld() [0x80ce81]
/alidata/server/mysql/libexec/mysqld(trx_rseg_list_and_array_init+0xa3) [0x80d0a3]
/alidata/server/mysql/libexec/mysqld(trx_sys_init_at_db_start+0x140) [0x80de20]
/alidata/server/mysql/libexec/mysqld(innobase_start_or_create_for_mysql+0xfef) [0x7ff0df]
/alidata/server/mysql/libexec/mysqld() [0x76ad6a]
/alidata/server/mysql/libexec/mysqld(ha_initialize_handlerton(st_plugin_int*)+0x31) [0x6cc8d1]
/alidata/server/mysql/libexec/mysqld() [0x753dfd]
/alidata/server/mysql/libexec/mysqld(plugin_init(int*, char**, int)+0x720) [0x755c50]
/alidata/server/mysql/libexec/mysqld() [0x5e5d4f]
/alidata/server/mysql/libexec/mysqld(main+0x1c6) [0x5e9df6]
/lib64/libc.so.6(__libc_start_main+0xfd) [0x7f0f0d663cdd]
/alidata/server/mysql/libexec/mysqld() [0x522479]
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.
131016 15:33:18 mysqld_safe mysqld from pid file /alidata/server/mysql/var/AY131011212338503c43Z.pid ended
这是错误日志 高手帮帮忙啊
...全文
相关推荐
MySQL数据库innodb启动失败无法重启的解决方法
问题介绍 电脑在使用过程中死机，重启后发现mysql没有启动成功，查看错误日志发现是innodb出现问题导致mysql启动失败。 错误日志 $ mysql.server start Starting MySQL . ERROR! The server quit without updating PID file (/usr/local/var/mysql/fdipzonedeMacBook-Air.local.pid). 22:08:37 mysqld_safe Starting mysqld daemon with databases from /usr/local/var/mysql
MySQL无法启动的解决办法
主要介绍了MySQL无法启动的解决办法的相关资料,希望通过本文大家能解决数据库不能启动的问题，需要的朋友可以参考下
windows无法启动MySQL服务报错1067的解决方法
主要为大家详细介绍了windows无法启动MySQL服务报错1067的3种解决方法，具有一定的参考价值，感兴趣的小伙伴们可以参考一下
使用innodb_force_recovery解决MySQL崩溃无法重启问题
主要介绍了使用innodb_force_recovery解决MySQL崩溃无法重启问题,这只一个成功案例,并不是万能的解决方法,需要酌情考虑,需要的朋友可以参考下
MySQL启动报错问题InnoDB:Unable to lock/ibdata1 error
主要介绍了MySQL启动报错问题InnoDB:Unable to lock/ibdata1 error,文中通过示例代码介绍的非常详细，对大家的学习或者工作具有一定的参考学习价值,需要的朋友可以参考下
