当我尝试启动WAMP时，它会加载，但保持橙色。
通过左键单击WAMP，然后转到MySQL-＆gt; Service，我可以看到Start / Resume为绿色，表示它没有启动MySQL。 （Apache似乎已经开始）
MySQL v 5.6.17
我查了下面的错误日志，但没有找到任何有用的东西。
[Thu Feb 25 15:02:04.507685 2016] [mpm_winnt:notice] [pid 7344:tid 708] AH00455: Apache/2.4.9 (Win32) PHP/5.5.12 configured -- resuming normal operations
[Thu Feb 25 15:02:04.508184 2016] [mpm_winnt:notice] [pid 7344:tid 708] AH00456: Apache Lounge VC11 Server built: Mar 16 2014 12:13:13
[Thu Feb 25 15:02:04.508184 2016] [core:notice] [pid 7344:tid 708] AH00094: Command line: 'd:\\wamp\\bin\\apache\\apache2.4.9\\bin\\httpd.exe -d D:/wamp/bin/apache/apache2.4.9'
[Thu Feb 25 15:02:04.515686 2016] [mpm_winnt:notice] [pid 7344:tid 708] AH00418: Parent: Created child process 12348
[Thu Feb 25 15:02:05.487426 2016] [mpm_winnt:notice] [pid 12348:tid 588] AH00354: Child: Starting 64 worker threads.
MySQL错误日志：
2016-03-02 13:05:25 52448 [Note] Plugin 'FEDERATED' is disabled.
2016-03-02 13:05:25 52448 [Note] InnoDB: Using atomics to ref count buffer pool pages
2016-03-02 13:05:25 52448 [Note] InnoDB: The InnoDB memory heap is disabled
2016-03-02 13:05:25 52448 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2016-03-02 13:05:25 52448 [Note] InnoDB: Compressed tables use zlib 1.2.3
2016-03-02 13:05:25 52448 [Note] InnoDB: Not using CPU crc32 instructions
2016-03-02 13:05:25 52448 [Note] InnoDB: Initializing buffer pool, size = 128.0M
2016-03-02 13:05:25 52448 [Note] InnoDB: Completed initialization of buffer pool
2016-03-02 13:05:25 52448 [Note] InnoDB: Highest supported file format is Barracuda.
2016-03-02 13:05:25 52448 [Note] InnoDB: The log sequence numbers 1598839555 and 1598839555 in ibdata files do not match the log sequence number 1598839565 in the ib_logfiles!
2016-03-02 13:05:25 52448 [Note] InnoDB: Database was not shutdown normally!
2016-03-02 13:05:25 52448 [Note] InnoDB: Starting crash recovery.
2016-03-02 13:05:25 52448 [Note] InnoDB: Reading tablespace information from the .ibd files...
2016-03-02 13:05:25 52448 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace mysite1/cache uses space ID: 10 at filepath: .\mysite1\cache.ibd. Cannot open tablespace mysite2/my_table which uses space ID: 10 at filepath: .\mysite2\my_table.ibd
InnoDB: Error: could not open single-table tablespace file .\mysite2\my_table.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.