设为首页收藏本站

 找回密码
 注册论坛

QQ登录

只需一步,快速开始

用百度帐号登录

只需两步,快速登录

新浪微博账号登陆

只需一步,快速开始

搜索
查看: 46|回复: 0

linux mysql数据库启动失败日志 mysqld got signal 6 使用innodb_force_recovery = 6恢复模式备份sql导出还原

[复制链接]

签到天数: 2392 天

[LV.Master]伴坛终老

 成长值: 21700
发表于 2018/6/30 18:48 | 显示全部楼层 |阅读模式 |Google Chrome 67.0.3396.99|Windows 10
天涯海角搜一下: 百度 谷歌 360 搜狗 有道 雅虎 必应 即刻
2018-06-30 18:40:36 7f26ae2da720  InnoDB: Assertion failure in thread 139804107712288 in file fut0lst.ic line 83
InnoDB: Failing assertion: addr.page == FIL_NULL || addr.boffset >= FIL_PAGE_DATA
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/ ... nnodb-recovery.html
InnoDB: about forcing recovery.
10:40:36 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=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 = 338700 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+0x35)[0x8e6cb5]
/usr/sbin/mysqld(handle_fatal_signal+0x494)[0x669684]
/lib64/libpthread.so.0(+0xf7e0)[0x7f26adeba7e0]
/lib64/libc.so.6(gsignal+0x35)[0x7f26ac95a495]
/lib64/libc.so.6(abort+0x175)[0x7f26ac95bc75]
/usr/sbin/mysqld[0xaab250]
/usr/sbin/mysqld[0xa067c0]
/usr/sbin/mysqld[0xa1df03]
/usr/sbin/mysqld[0xa1a98f]
/usr/sbin/mysqld[0xa1b868]
/usr/sbin/mysqld[0xa10b62]
/usr/sbin/mysqld[0xa10fc8]
/usr/sbin/mysqld[0x9480c0]
/usr/sbin/mysqld[0x5ace76]
/usr/sbin/mysqld(_Z24plugin_foreach_with_maskP3THDPFcS0_P13st_plugin_intPvEijS3_+0x29c)[0x6f432c]
/usr/sbin/mysqld(_Z10ha_recoverP7st_hash+0x9f)[0x5ac8ef]
/usr/sbin/mysqld[0x59ef7d]
/usr/sbin/mysqld(_Z11mysqld_mainiPPc+0x42d)[0x5a3f1d]
/lib64/libc.so.6(__libc_start_main+0xfd)[0x7f26ac946d1d]
/usr/sbin/mysqld[0x595579]
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.
2018-06-30 18:43:10 24491 [Warning] Buffered warning: option 'table_definition_cache': unsigned value 200 adjusted to 400

先停止数据库
  1. service mysqld stop
复制代码

设置恢复模式
  1. vi /etc/my.cnf
复制代码

[mysqld]下方增加
  1. innodb_force_recovery = 6
复制代码

使用恢复模式启动mysql
  1. service mysqld restart
复制代码

测试密码连接,如果成功按下ctrl+c退出
  1. mysql -uroot -p123456
复制代码

备份全部数据库表,主要修改你自己的密码:
  1. mysqldump -uroot -p123456 --all-databases  > all_mysql_backup.sql
复制代码


备份原有mysql目录并且删除
  1. service mysqld stop
  2. cp -r /var/lib/mysql/ /var/lib/mysql.bak
  3. rm -rf /var/lib/mysql/*
复制代码

关闭恢复模式
  1. vi /etc/my.cnf
复制代码

删除或者注释之前添加的innodb_force_recovery = 6
以正常模式启动mysql
  1. service mysqld restart
复制代码

给数据库root用户设置密码,例如之前的123456
  1. mysqladmin -u root password 123456
复制代码

使用之间备份的sql文件恢复数据:
  1. mysql -uroot -p123456 -e "source /root/all_mysql_backup.sql"
复制代码


然后就修好了,一切恢复正常

欢迎光临IT技术交流论坛:http://bbs.itzmx.com/
回复

使用道具 举报

您需要登录后才可以回帖 登录 | 注册论坛 用百度帐号登录新浪微博账号登陆

本版积分规则

手机版|Archiver|Mail me|网站地图|IT技术交流论坛 ( 闽ICP备13013206号-7 )

GMT+8, 2018/7/22 22:21 , Processed in 0.250129 second(s), 43 queries , Gzip On, Memcache On.

Powered by itzmx!

© 2011-2018 sakura

快速回复 返回顶部 返回列表