Windows 8.1 Wampserver Mysql将无法运行

 沛公-若溪 发布于 2023-02-09 14:46

我安装了Windows 8.1然后我重新安装wampserver,一切正常..直到我得到橙色,由于我的MySQL服务器没有运行....

Wampserver 2.4

MySQL 5.6.12

PHP 5.4.12

Apache 2.4.4

这是日志文件

2013-12-18 10:00:00 904 [Note] Plugin 'FEDERATED' is disabled.
2013-12-18 10:00:00 904 [Note] InnoDB: The InnoDB memory heap is disabled
2013-12-18 10:00:00 904 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2013-12-18 10:00:00 904 [Note] InnoDB: Compressed tables use zlib 1.2.3
2013-12-18 10:00:00 904 [Note] InnoDB: Not using CPU crc32 instructions
2013-12-18 10:00:00 904 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2013-12-18 10:00:00 904 [Note] InnoDB: Completed initialization of buffer pool
2013-12-18 10:00:00 904 [Note] InnoDB: Highest supported file format is Barracuda.
2013-12-18 10:00:00 904 [Note] InnoDB: The log sequence numbers 2283844 and 2283844 in ibdata files do not match the log sequence number 2484632 in the ib_logfiles!
2013-12-18 10:00:00 904 [Note] InnoDB: Database was not shutdown normally!
2013-12-18 10:00:00 904 [Note] InnoDB: Starting crash recovery.
2013-12-18 10:00:00 904 [Note] InnoDB: Reading tablespace information from the .ibd files...
2013-12-18 10:00:00 904 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace airbnb/amenities uses space ID: 6 at filepath: .\airbnb\amenities.ibd. Cannot open tablespace webotrip/amenities which uses space ID: 6 at filepath: .\webotrip\amenities.ibd
InnoDB: Error: could not open single-table tablespace file .\webotrip\amenities.ibd
InnoDB: We do not continue the crash recovery, because the table may become
InnoDB: corrupt if we cannot apply the log records in the InnoDB log to it.
InnoDB: To fix the problem and start mysqld:
InnoDB: 1) If there is a permission problem in the file and mysqld cannot
InnoDB: open the file, you should modify the permissions.
InnoDB: 2) If the table is not needed, or you can restore it from a backup,
InnoDB: then you can remove the .ibd file, and InnoDB will do a normal
InnoDB: crash recovery and ignore that table.
InnoDB: 3) If the file system or the disk is broken, and you cannot remove
InnoDB: the .ibd file, you can set innodb_force_recovery > 0 in my.cnf
InnoDB: and force InnoDB to continue crash recovery here.

Abdou Tahiri.. 14

我找到了解决方案

    备份您的\ wamp\bin\mysql\mysql5.6.12\data文件夹JUST IN CASE.

    左键单击wampmanager图标 - > MySQL - > my.ini(编辑mysql配置文件)

并将此行添加到wampmysqld部分[wampmysqld](如果没有[wampmysqld],则添加[mysqld])

innodb_force_recovery = 1

然后保存my.ini

    左键单击wampmanager图标 - > MySQL - >服务 - >重启服务

花一点时间进行恢复,然后再次检查mysql错误日志,看看它是否恢复了数据库.

    左键单击wampmanager图标 - > MySQL - > my.ini(编辑mysql配置文件)

现在删除您之前添加的innodb_force_recovery = 1参数.

1 个回答
  • 我找到了解决方案

      备份您的\ wamp\bin\mysql\mysql5.6.12\data文件夹JUST IN CASE.

      左键单击wampmanager图标 - > MySQL - > my.ini(编辑mysql配置文件)

    并将此行添加到wampmysqld部分[wampmysqld](如果没有[wampmysqld],则添加[mysqld])

    innodb_force_recovery = 1

    然后保存my.ini

      左键单击wampmanager图标 - > MySQL - >服务 - >重启服务

    花一点时间进行恢复,然后再次检查mysql错误日志,看看它是否恢复了数据库.

      左键单击wampmanager图标 - > MySQL - > my.ini(编辑mysql配置文件)

    现在删除您之前添加的innodb_force_recovery = 1参数.

    2023-02-09 14:51 回答
撰写答案
今天,你开发时遇到什么问题呢?
立即提问
热门标签
PHP1.CN | 中国最专业的PHP中文社区 | PNG素材下载 | DevBox开发工具箱 | json解析格式化 |PHP资讯 | PHP教程 | 数据库技术 | 服务器技术 | 前端开发技术 | PHP框架 | 开发工具 | 在线工具
Copyright © 1998 - 2020 PHP1.CN. All Rights Reserved 京公网安备 11010802041100号 | 京ICP备19059560号-4 | PHP1.CN 第一PHP社区 版权所有