Apache运行但MySQL不启动-WAMP

Question

我在WIN7上安装了WAWMP。它工作得很好，但自从我重新启动我的系统，我遇到了一个问题。

问题是MySQL没有启动，但Apache像往常一样运行。当我测试端口80时，它表示Apache正在运行。

我尝试在MySQL的My.ini中更改端口，但MySQL仍然无法启动。

以下是我尝试启动MySQL时的最新日志

2014-06-18 08:15:23 4496 [Note] Plugin 'FEDERATED' is disabled.
2014-06-18 08:15:23 4496 [Note] InnoDB: The InnoDB memory heap is disabled
2014-06-18 08:15:23 4496 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2014-06-18 08:15:23 4496 [Note] InnoDB: Compressed tables use zlib 1.2.3
2014-06-18 08:15:23 4496 [Note] InnoDB: Not using CPU crc32 instructions
2014-06-18 08:15:23 4496 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2014-06-18 08:15:23 4496 [Note] InnoDB: Completed initialization of buffer pool
2014-06-18 08:15:23 4496 [Note] InnoDB: Highest supported file format is Barracuda.
2014-06-18 08:15:24 4496 [Note] InnoDB: The log sequence numbers 1625977 and 1625977 in ibdata files do not match the log sequence number 22262437 in the ib_logfiles!
2014-06-18 08:15:24 4496 [Note] InnoDB: Database was not shutdown normally!
2014-06-18 08:15:24 4496 [Note] InnoDB: Starting crash recovery.
2014-06-18 08:15:24 4496 [Note] InnoDB: Reading tablespace information from the .ibd files...
2014-06-18 08:15:24 4496 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace joomla_web/intern_extensions uses space ID: 104 at filepath: .\joomla_web\intern_extensions.ibd. Cannot open tablespace test/joomla_assets which uses space ID: 104 at filepath: .\test\joomla_assets.ibd
InnoDB: Error: could not open single-table tablespace file .\test\joomla_assets.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.

Answer 1

尝试转到控制面板、管理工具、服务或运行services.msc（快捷方式）尝试启动、停止和重新启动MYSQL服务。