wdcp mysql 启动报错 InnoDB: Database page corruption on disk or a failed

  1. 2017-10-23 23:32:34
  2. 热度: 575 ℃
  3. 标签:
  4. 作者: 友乐

今天 友乐遇到了这个问题

171023 23:09:01 [Note] Plugin ‘FEDERATED’ is disabled.
171023 23:09:01 InnoDB: The InnoDB memory heap is disabled
171023 23:09:01 InnoDB: Mutexes and rw_locks use GCC atomic builtins
171023 23:09:01 InnoDB: Compressed tables use zlib 1.2.3
171023 23:09:01 InnoDB: Initializing buffer pool, size = 128.0M
171023 23:09:01 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.
171023 23:09:01 InnoDB: Page dump in ascii and hex (16384 bytes):
len 16384; hex
InnoDB: End of page dump
171023 23:09:01 InnoDB: Page checksum 3492583682, prior-to-4.0.14-form checksum 1518151141
InnoDB: stored checksum 3492583682, prior-to-4.0.14-form stored checksum 973933999
InnoDB: Page lsn 0 10766424, low 4 bytes of lsn at page end 10758879
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.
171023 23:09:01 InnoDB: Assertion failure in thread 140615904253728 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.
15:09:01 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.54/bin/mysqld(my_print_stacktrace+0x2e)[0x76451e]
/www/wdlinux/mysql-5.5.54/bin/mysqld(handle_fatal_signal+0x41a)[0x65878a]
/lib64/libpthread.so.0(+0xf7e0)[0x7fe3b0c3e7e0]
/lib64/libc.so.6(gsignal+0x35)[0x7fe3af8d4495]
/lib64/libc.so.6(abort+0x175)[0x7fe3af8d5c75]
/www/wdlinux/mysql-5.5.54/bin/mysqld[0x8397a9]
/www/wdlinux/mysql-5.5.54/bin/mysqld[0x843168]
/www/wdlinux/mysql-5.5.54/bin/mysqld[0x84385f]
/www/wdlinux/mysql-5.5.54/bin/mysqld[0x837f79]
/www/wdlinux/mysql-5.5.54/bin/mysqld[0x80b646]
/www/wdlinux/mysql-5.5.54/bin/mysqld[0x80b6ee]
/www/wdlinux/mysql-5.5.54/bin/mysqld[0x7fa063]
/www/wdlinux/mysql-5.5.54/bin/mysqld[0x7c79f9]
/www/wdlinux/mysql-5.5.54/bin/mysqld(_Z24ha_initialize_handlertonP13st_plugin_int+0x41)[0x65b291]
/www/wdlinux/mysql-5.5.54/bin/mysqld[0x579735]
/www/wdlinux/mysql-5.5.54/bin/mysqld(_Z11plugin_initPiPPci+0x7d8)[0x57ca98]
/www/wdlinux/mysql-5.5.54/bin/mysqld[0x508058]
/www/wdlinux/mysql-5.5.54/bin/mysqld(_Z11mysqld_mainiPPc+0x383)[0x50acc3]
/lib64/libc.so.6(__libc_start_main+0xfd)[0x7fe3af8c0d1d]
/www/wdlinux/mysql-5.5.54/bin/mysqld[0x501e8d]
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.

解决办法:查看/www/wdlinux/mysql/data下面的文件,找到以下3个文件.

-rw-rw—- 1 mysql mysql 18874368 Oct 23 23:17 ibdata1
-rw-rw—- 1 mysql mysql 5242880 Oct 23 23:17 ib_logfile0
-rw-rw—- 1 mysql mysql 5242880 Oct 23 23:17 ib_logfile1

删除,然后重启mysql

 

[root@faith data]# /etc/init.d/mysqld restart
MySQL server PID file could not be found! [FAILED]
Starting MySQL.Logging to ‘/www/wdlinux/mysql-5.5.54/data/faith.err’.
.. [ OK ]

 

完成 ,问题就解决了.

上面解决这个问题,有的数据库表里面的数据将会丢失,innodb的表会找不到数据了,

再认真看下:

171023 23:09:01 [Note] Plugin ‘FEDERATED’ is disabled.
171023 23:09:01 InnoDB: The InnoDB memory heap is disabled

这2句话说的是 FEDERATED的插件不支持了,现在给他开启 插件,方法是修改/etc/my.cnf文件在[mysqld]下面加一行

federated

再加一行 innodb_force_recovery=1

如果innodb_force_recovery=1不好使,你可以试试用2~6,再不行就dump一下然后重建。再重启mysqld 就好使了,数据也找回来了

 [root@faith ~]# /etc/init.d/mysqld restart
Shutting down MySQL… [ Failed]
Starting MySQL.. [ OK ]

转载请注明:友乐网站搬家迁移上云服务 » wdcp mysql 启动报错 InnoDB: Database page corruption on disk or a failed

本文固定链接: https://www.7hubei.com/272.html | 友乐网站搬家迁移上云服务

提示:我们主营主机、域名,并做网站搬家、源码安装、服务器搭建、网站建设等网站相关工作。
QQ号:76963956 微信号:76963956
该文章由 友乐 于2017年10月23日发表在 问题教程 分类下。