完美解决mysql启动后随即关闭的问题（ibdata1文件损坏导致）_小皮面板的mysql启动了又关闭

185 浏览量更新于2023-05-04 评论 1 收藏 54KB PDF 举报

身份认证购VIP最低享 7 折!

领优惠券(最高得80元）

资源详情

资源评论

资源推荐

完美解决完美解决mysql启动后随即关闭的问题（启动后随即关闭的问题（ibdata1文件损坏导文件损坏导

致）致）

机房一台服务器上的mysql运行一段时间了，突然出现了一个很奇怪的现象：重启后无法恢复了！准确情况是：启动mysql后

随即就又关闭了。

查看查看mysql错误日志如下：错误日志如下：

160920 22:41:41 mysqld_safe Starting mysqld daemon with databases from /home/MysqlData/

2016-09-20 22:41:41 0 [Note] /Data/app/mysql5.6.25/bin/mysqld (mysqld 5.6.25-log) starting as process 32372 …

2016-09-20 22:41:42 32372 [Note] Plugin ‘FEDERATED’ is disabled.

2016-09-20 22:41:42 32372 [Warning] option ‘innodb-write-io-threads’: unsigned value 1000 adjusted to 64

2016-09-20 22:41:42 32372 [Warning] option ‘innodb-read-io-threads’: unsigned value 1000 adjusted to 64

2016-09-20 22:41:42 32372 [Note] InnoDB: Using atomics to ref count buffer pool pages

2016-09-20 22:41:42 32372 [Note] InnoDB: The InnoDB memory heap is disabled

2016-09-20 22:41:42 32372 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins

2016-09-20 22:41:42 32372 [Note] InnoDB: Memory barrier is not used

2016-09-20 22:41:42 32372 [Note] InnoDB: Compressed tables use zlib 1.2.3

2016-09-20 22:41:42 32372 [Note] InnoDB: Using CPU crc32 instructions

2016-09-20 22:41:42 32372 [Note] InnoDB: Initializing buffer pool, size = 1.0G

2016-09-20 22:41:42 32372 [Note] InnoDB: Completed initialization of buffer pool

2016-09-20 22:41:42 32372 [Note] InnoDB: Highest supported file format is Barracuda.

2016-09-20 22:41:42 32372 [Note] InnoDB: Log scan progressed past the checkpoint lsn 20293587957

2016-09-20 22:41:42 32372 [Note] InnoDB: Database was not shutdown normally!

2016-09-20 22:41:42 32372 [Note] InnoDB: Starting crash recovery.

2016-09-20 22:41:42 32372 [Note] InnoDB: Reading tablespace information from the .ibd files…

2016-09-20 22:41:42 32372 [Note] InnoDB: Restoring possible half-written data pages

2016-09-20 22:41:42 32372 [Note] InnoDB: from the doublewrite buffer…

InnoDB: Doing recovery: scanned up to log sequence number 20293596130

2016-09-20 22:41:42 32372 [Note] InnoDB: Starting an apply batch of log records to the database…

InnoDB: Progress in percent: 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78

79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99

InnoDB: Apply batch completed

InnoDB: Last MySQL binlog file position 0 136254, file name mysql-bin.000013

2016-09-20 22:41:43 32372 [Note] InnoDB: 128 rollback segment(s) are active.

2016-09-20 22:41:43 32372 [Note] InnoDB: Waiting for purge to start

2016-09-20 22:41:43 7f77a9edd700 InnoDB: Assertion failure in thread 140151928772352 in file trx0purge.cc line 699

InnoDB: Failing assertion: purge_sys->iter.trx_no <= purge_sys->rseg->last_trx_no

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.6/en/forcing-innodb-recovery.html

InnoDB: about forcing recovery.

02:41:43 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.

分析日志后发现，数据库无法重启的原因是因为ibdata1文件损坏，重启后无法正常恢复。

解决办法：解决办法：

需要跳过恢复步骤需要跳过恢复步骤，修改my.cnf文件，在my.cnf中的[mysqld]中添加：

innodb_force_recovery = 6

innodb_purge_threads = 1

解释：解释：

innodb_force_recovery可以设置为1-6,大的数字包含前面所有数字的影响。

具体数字对应的含义：具体数字对应的含义：

本内容试读结束，登录后可阅读更多

下载后可阅读完整内容，剩余1页未读，立即下载

weixin_38582909

粉丝: 5
资源: 975

会员权益专享

完美解决mysql启动后随即关闭的问题（ibdata1文件损坏导致）

评论0

会员权益专享

最新资源

完美解决mysql启动后随即关闭的问题（ibdata1文件损坏导致）

评论0

解决MySQL配置问题，启动闪退等问题

MySQL无法启动的解决办法

mysql 误删除ibdata1之后的恢复方法

ibdata1 过大导致mysql 无法启动

在不能关闭mysql服务情况下，解决ibdata1文件太大的问题

mysql 无法启动 ibdata1 过大

mysql5.5 ibdata1

ibdata1损坏如何恢复

windows环境下，如何在不关闭mysql服务情况下，解决ibdata1文件太大的问题

ibdata1文件太大

mysql5.5 清理 ibdata1

MySQL安装后无法启动

[ERROR] [FATAL] InnoDB: Table flags are 0 in the data dictionary but the flags in file ./ibdata1 are 0x4800!

ibdata1 io error

mysql启动pid文件丢失

mysql ibdata1清理

mysql error 11_mysql Unable to lock ./ibdata1, error: 11

xampp无法启动mysql也没报错_解决电脑死机导致的xampp无法启动mysql

2023-07-14T07:46:41.194078Z 1 [ERROR] [MY-012574] [InnoDB] Unable to lock ./ibdata1 error: 11

mysql 非正常关机_非正常关机时，innodb故障导致mysql无法启动的解决方法

会员权益专享

最新资源