【问题标题】:Windows 8.1 Wampserver Mysql won't run [closed]Windows 8.1 Wampserver Mysql 不会运行 [关闭]
【发布时间】:2014-12-08 18:07:28
【问题描述】:

我安装了 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.

【问题讨论】:

    标签: mysql wampserver windows-8.1


    【解决方案1】:

    我找到了解决办法

    1. 备份您的 \wamp\bin\mysql\mysql5.6.12\data 文件夹以防万一。

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

    并将这一行添加到 wampmysqld 部分 [wampmysqld](或 [mysqld] 如果你没有 [wampmysqld])

    innodb_force_recovery = 1

    然后保存 my.ini

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

    给它一分钟恢复,然后再次检查mysql错误日志,看看它是否已经恢复了数据库。

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

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

    【讨论】:

    猜你喜欢
    • 1970-01-01
    • 2016-05-30
    • 1970-01-01
    • 1970-01-01
    • 2013-10-31
    • 2014-04-26
    • 1970-01-01
    • 2013-11-06
    • 1970-01-01
    相关资源
    最近更新 更多