3

我无法通过 XAMPP 启动 MySQL,几个月前我上次打开它时还好;

在我遵循 my.cnf 恢复后更新了错误:

2013-10-06 19:29:23 7920 [Note] Plugin 'FEDERATED' is disabled.
2013-10-06 19:29:23 15fc InnoDB: Warning: Using innodb_additional_mem_pool_size is DEPRECATED. This option may be removed in future releases, together with the option innodb_use_sys_malloc and with the InnoDB's internal memory allocator.
2013-10-06 19:29:23 7920 [Note] InnoDB: The InnoDB memory heap is disabled
2013-10-06 19:29:23 7920 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2013-10-06 19:29:23 7920 [Note] InnoDB: Compressed tables use zlib 1.2.3
2013-10-06 19:29:23 7920 [Note] InnoDB: Not using CPU crc32 instructions
2013-10-06 19:29:23 7920 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2013-10-06 19:29:23 7920 [Note] InnoDB: Completed initialization of buffer pool
2013-10-06 19:29:23 7920 [Note] InnoDB: Highest supported file format is Barracuda.
2013-10-06 19:29:23 7920 [Note] InnoDB: The log sequence numbers 0 and 0 in ibdata files do not match the log sequence number 198755718 in the ib_logfiles!
2013-10-06 19:29:23 7920 [Note] InnoDB: Database was not shutdown normally!
2013-10-06 19:29:23 7920 [Note] InnoDB: Starting crash recovery.
2013-10-06 19:29:23 7920 [Note] InnoDB: Reading tablespace information from the .ibd files...
2013-10-06 19:29:23 7920 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace bitnami_wordpress/wp_usermeta uses space ID: 2 at filepath: .\bitnami_wordpress\wp_usermeta.ibd. Cannot open tablespace mysql/innodb_index_stats which uses space ID: 2 at filepath: .\mysql\innodb_index_stats.ibd
InnoDB: Error: could not open single-table tablespace file .\mysql\innodb_index_stats.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.
4

2 回答 2

6

我通过删除~/x-ampp/mysql/data中的所有ib_logfiles解决了同样的问题

于 2015-02-10T09:46:52.493 回答
3

根据错误日志的建议,我认为你应该试试这个。我打算在评论中写这个,但这对你来说很难阅读,所以我会把它作为一个答案

您无法启动 MySQL,因为 XAMPP 无法打开文件.\mysql\innodb_index_stats.ibd,如图所示

Error: could not open single-table tablespace file .\mysql\innodb_index_stats.ibd

以下是如何解决它的建议:

1) If there is a permission problem in the file and mysqld cannot
open the file, you should modify the permissions.

(1)关于许可。转到.\mysql\innodb_index_stats.ibd并检查您是否有阅读权限innodb_index_stats.ibd

2) If the table is not needed, or you can restore it from a backup,
then you can remove the .ibd file, and InnoDB will do a normal
crash recovery and ignore that table.

(2) 可以尝试删除.\mysql\innodb_index_stats.ibd。我的建议是复制innodb_index_stats.ibd到另一个位置以防万一发生其他事情

3) If the file system or the disk is broken, and you cannot remove
the .ibd file, you can set innodb_force_recovery > 0 in my.cnf
and force InnoDB to continue crash recovery here.

(3)如果不能删除nnodb_index_stats.ibd,可以尝试修改my.cnf文件并设置innodb_force_recovery > 0(可以使用notepad或notepad++编辑文件。它位于xampp\mysql\

先试试这些看看对你有没有帮助

更新 请尝试找到文件ibdata1定位xampp\mysql\data并将其删除或重命名,然后重新启动XAMPP,希望这对你有用

于 2013-10-06T18:00:39.530 回答