VPS侦探论坛

 找回密码
 注册
查看: 848|回复: 1

MySQL出现不知原因地自动关闭,内存够,提供日志...

[复制链接]
发表于 2023-9-5 10:16:23 | 显示全部楼层 |阅读模式

服务器的内存是管够的,我查看一下mysql日志,发日志内容:
  1. 2023-09-05 00:01:08 30215 [Note] InnoDB: The log sequence numbers 987181250 and 987181250 in ibdata files do not match the log sequence number 987742792 in the ib_logfiles!
  2. 2023-09-05 00:01:08 30215 [Note] InnoDB: Database was not shutdown normally!
  3. 2023-09-05 00:01:08 30215 [Note] InnoDB: Starting crash recovery.
  4. 2023-09-05 00:01:08 30215 [Note] InnoDB: Reading tablespace information from the .ibd files...
  5. 2023-09-05 00:01:08 30215 [Note] InnoDB: Restoring possible half-written data pages
  6. 2023-09-05 00:01:08 30215 [Note] InnoDB: from the doublewrite buffer...
  7. InnoDB: Last MySQL binlog file position 0 270835, file name mysql-bin.000080
  8. 2023-09-05 00:01:09 30215 [Note] InnoDB: 128 rollback segment(s) are active.
  9. 2023-09-05 00:01:09 30215 [Note] InnoDB: Waiting for purge to start
  10. 2023-09-05 00:01:09 30215 [Note] InnoDB: 5.6.51 started; log sequence number 987742792
复制代码
在网上搜索教程,修改my.cnf文件,在my.cnf中的[mysqld]中添加:
innodb_force_recovery = 6
innodb_purge_threads = 1
重启Mysql之后发现文章页面打开不了。首页可以打开。这个方法试了不行。不知道怎么去解决了。求解决方法



美国VPS推荐: 遨游主机LinodeLOCVPS主机云搬瓦工80VPSVultr美国VPS主机中国VPS推荐: 阿里云腾讯云。LNMP付费服务(代装/问题排查)QQ 503228080
发表于 2023-9-5 16:22:32 | 显示全部楼层


innodb_force_recovery的值从1到6挨个试试看看它自己能修复不,innodb_purge_threads参数别加
Linux下Nginx+MySQL+PHP自动安装工具:https://lnmp.org
您需要登录后才可以回帖 登录 | 注册

本版积分规则

小黑屋|手机版|Archiver|VPS侦探 ( 鲁ICP备16040043号-1 )

GMT+8, 2024-4-25 16:00 , Processed in 0.025980 second(s), 16 queries .

Powered by Discuz! X3.4

© 2001-2023 Discuz! Team.

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