MySql 意外停止 [英] MySql stops unexpectedly

查看:33
本文介绍了MySql 意外停止的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

MySql 意外停止

这是错误日志的副本:

2019-07-03 13:27:50 0 [ERROR] InnoDB:您的数据库可能已损坏或您可能复制了 InnoDB 表空间但没有复制 InnoDB 日志文件.请参阅https://mariadb.com/kb/en/library/innodb-recovery-模式/有关强制恢复的信息.

2019-07-03 13:27:50 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.

2019-07-03 13:27:50 0 [注意]InnoDB:128 个回滚段中有 128 个处于活动状态.

2019-07-03 13:27:50 0 [Note] InnoDB: 128 out of 128 rollback segments are active.

2019-07-03 13:27:50 0 [ERROR] InnoDB: Page [page id: space=0, page number=305]日志序列号 2834539 在未来!当前系统日志序列号 1604011.

2019-07-03 13:27:50 0 [ERROR] InnoDB: Page [page id: space=0, page number=305] log sequence number 2834539 is in the future! Current system log sequence number 1604011.

2019-07-03 13:27:50 0 [错误] InnoDB:你的数据库可能已损坏,或者您可能已复制 InnoDB 表空间但不是 InnoDB 日志文件.请参阅https://mariadb.com/kb/en/library/innodb-recovery-模式/有关强制恢复的信息.

2019-07-03 13:27:50 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.

2019-07-03 13:27:50 0 [注意] InnoDB:为临时表创建共享表空间

2019-07-03 13:27:50 0 [Note] InnoDB: Creating shared tablespace for temporary tables

2019-07-03 13:27:50 0 [注意] InnoDB:设置文件'C:\xampp\mysql\data\ibtmp1'大小为 12 MB.物理写满文件;请稍等 ...2019-07-03 13:27:50 0 [注意] InnoDB:文件'C:\xampp\mysql\data\ibtmp1'大小现在是 12 MB.

2019-07-03 13:27:50 0 [Note] InnoDB: Setting file 'C:\xampp\mysql\data\ibtmp1' size to 12 MB. Physically writing the file full; Please wait ... 2019-07-03 13:27:50 0 [Note] InnoDB: File 'C:\xampp\mysql\data\ibtmp1' size is now 12 MB.

2019-07-03 13:27:50 0 [注意] InnoDB:等待清除开始

2019-07-03 13:27:50 0 [Note] InnoDB: Waiting for purge to start

2019-07-03 13:27:50 0 [注意] InnoDB:10.3.16 启动;日志序列号 1604002;交易 ID 1432

2019-07-03 13:27:50 0 [Note] InnoDB: 10.3.16 started; log sequence number 1604002; transaction id 1432

2019-07-03 13:27:50 0 [注意] InnoDB:从C:\xampp\mysql\data\ib_buffer_pool

2019-07-03 13:27:50 0 [Note] InnoDB: Loading buffer pool(s) from C:\xampp\mysql\data\ib_buffer_pool

2019-07-03 13:27:50 0 [ERROR] InnoDB: Page [page id: space=0, page number=9] 日志序列号2841120在未来!当前系统日志序列号 1604011.2019-07-03 13:27:50 0 [ERROR] InnoDB:您的数据库可能已损坏或您可能复制了 InnoDB 表空间但没有复制 InnoDB 日志文件.请参阅https://mariadb.com/kb/en/library/innodb-recovery-模式/有关强制恢复的信息.

2019-07-03 13:27:50 0 [ERROR] InnoDB: Page [page id: space=0, page number=9] log sequence number 2841120 is in the future! Current system log sequence number 1604011. 2019-07-03 13:27:50 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.

2019-07-03 13:27:50 0 [ERROR] InnoDB: Page [page id: space=0, page number=243] 日志序列号2082633在未来!当前系统日志序列号 1604011.2019-07-03 13:27:50 0 [ERROR] InnoDB:您的数据库可能已损坏或您可能复制了 InnoDB 表空间但没有复制 InnoDB 日志文件.请参阅https://mariadb.com/kb/en/library/innodb-recovery-模式/有关强制恢复的信息.

2019-07-03 13:27:50 0 [ERROR] InnoDB: Page [page id: space=0, page number=243] log sequence number 2082633 is in the future! Current system log sequence number 1604011. 2019-07-03 13:27:50 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.

2019-07-03 13:27:50 0 [ERROR] InnoDB: Page [page id: space=1, page number=0] 日志序列号1608629在未来!当前系统日志序列号 1604011.2019-07-03 13:27:50 0 [注意] 插件反馈"被禁用.

2019-07-03 13:27:50 0 [ERROR] InnoDB: Page [page id: space=1, page number=0] log sequence number 1608629 is in the future! Current system log sequence number 1604011. 2019-07-03 13:27:50 0 [Note] Plugin 'FEEDBACK' is disabled.

2019-07-03 13:27:50 0 [ERROR] InnoDB:您的数据库可能已损坏,或者您可能已复制 InnoDB 表空间但未复制 InnoDB 日志文件.请参考 https://mariadb.com/kb/en/library/innodb-恢复模式/有关强制恢复的信息.

2019-07-03 13:27:50 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.

2019-07-03 13:27:50 0 [ERROR] InnoDB: Page [page id: space=1, page number=1] 日志序列号1604111在未来!当前系统日志序列号 1604011.2019-07-03 13:27:50 0 [ERROR] InnoDB:您的数据库可能已损坏或您可能复制了 InnoDB 表空间但没有复制 InnoDB 日志文件.请参阅https://mariadb.com/kb/en/library/innodb-recovery-模式/有关强制恢复的信息.

2019-07-03 13:27:50 0 [ERROR] InnoDB: Page [page id: space=1, page number=1] log sequence number 1604111 is in the future! Current system log sequence number 1604011. 2019-07-03 13:27:50 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innodb-recovery-modes/ for information about forcing recovery.

2019-07-03 13:27:50 0 [注意] 在 IP 上创建的服务器套接字:'::'.

2019-07-03 13:27:50 0 [Note] Server socket created on IP: '::'.

2019-07-03 13:27:50 0 [错误] InnoDB:页面 [页面

2019-07-03 13:27:50 0 [ERROR] InnoDB: Page [page

  • 我该怎么做才能让我的数据库重新启动并运行?非常感谢所有帮助!
  • 推荐答案

    我也遇到了这个问题,并搜索了很多,只有一种解决方案对我有用.

    I also faced this issue and searched a lot only one solution worked for me.

    只需将 C:\xampp\mysql\backup 中的所有文件复制到 C:\xampp\mysql\data

    Just copy all files from C:\xampp\mysql\backup to C:\xampp\mysql\data

    确保备份您的数据文件夹以避免任何进一步的问题.

    Make sure to take backup of your data folder to avoid any further problems.

    如果您看到任何与表引擎相关的错误,那么您可以将文件 ibdata1 从备份数据文件夹复制到当前数据文件夹

    If you see any error related to table engine then you can copy file ibdata1 from your backup data folder to current data folder

    这篇关于MySql 意外停止的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆