【发布时间】：2016-12-28 16:55:54
【问题描述】：
我在我的 32 位 Windows 7 上安装了 WAMP。它工作了几天，但之后开始出现问题。
我怀疑问题出在 MySQL 上，因为我已经测试了我的 80 端口并且它工作正常。我无法启动 wampmysqld 服务。它抛出错误“1067-进程意外终止”。
在 WAMP 向导中，MySQL 服务为绿色，这表明 MySQL 服务尚未启动。 MySQL 日志显示为
2016-08-22 13:27:56 6020 [Note] Plugin 'FEDERATED' is disabled.
2016-08-22 13:27:56 6020 [Note] InnoDB: Using atomics to ref count buffer pool pages
2016-08-22 13:27:56 6020 [Note] InnoDB: The InnoDB memory heap is disabled
2016-08-22 13:27:56 6020 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2016-08-22 13:27:56 6020 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2016-08-22 13:27:56 6020 [Note] InnoDB: Completed initialization of buffer pool
2016-08-22 13:27:56 6020 [Note] InnoDB: Highest supported file format is Barracuda.
2016-08-22 13:27:56 6020 [Note] InnoDB: The log sequence numbers 80291311 and 80291311 in ibdata files do not match the log sequence number 86947014 in the ib_logfiles!
2016-08-22 13:27:56 6020 [Note] InnoDB: Database was not shutdown normally!
2016-08-22 13:27:56 6020 [Note] InnoDB: Starting crash recovery.
2016-08-22 13:27:56 6020 [Note] InnoDB: Reading tablespace information from the .ibd files...
2016-08-22 13:27:56 6020 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace dbzenroc/roc_changeaddress uses space ID: 435 at filepath: .\dbzenroc\roc_changeaddress.ibd. Cannot open tablespace joomla/dtfp2_updates which uses space ID: 435 at filepath: .\joomla\dtfp2_updates.ibd
InnoDB: Error: could not open single-table tablespace file .\joomla\dtfp2_updates.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.
我们将不胜感激立即提供帮助。谢谢。
【问题讨论】：
-
错误日志显示问题所在并为您提供三种可能的恢复方法 - 您是否检查了问题文件并尝试了可能的恢复程序？