MySQL 未在 XAMPP 上启动 [英] MySQL not launching on XAMPP

问题描述

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

I can't get MySQL to launch via XAMPP, it was fine the last time I opened it a few months back;

我按照 my.cnf 恢复后更新了错误:

Updated errors after I have followed the my.cnf recovery:

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: .itnami_wordpresswp_usermeta.ibd. Cannot open tablespace mysql/innodb_index_stats which uses space ID: 2 at filepath: .mysqlinnodb_index_stats.ibd
InnoDB: Error: could not open single-table tablespace file .mysqlinnodb_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.

推荐答案

根据错误日志的建议，我觉得你应该试试这个.我打算在评论中写这个，但是你很难读懂，所以我会把它作为一个答案来代替

Base on the suggestions of the error log, I think you should try this. I planned to write this in a comment, but that will hard for you to read, so I'll make it as an answer instead

您无法启动 MySQL，因为 XAMPP 无法打开文件 .mysqlinnodb_index_stats.ibd，如

You can't launch MySQL because XAMPP can't open file .mysqlinnodb_index_stats.ibd as shown in

Error: could not open single-table tablespace file .mysqlinnodb_index_stats.ibd

以下是如何修复它的建议:

And here is suggestions how to fix it:

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

(1) 是关于许可的.转到 .mysqlinnodb_index_stats.ibd 并检查您是否有权读取 innodb_index_stats.ibd

(1) is about permission. Go to .mysqlinnodb_index_stats.ibd and check if you have permission to read 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)你可以尝试删除.mysqlinnodb_index_stats.ibd.我的建议是将 innodb_index_stats.ibd 复制到另一个位置，以防万一发生其他情况

(2) you can try to delete .mysqlinnodb_index_stats.ibd. My suggestion is copy innodb_index_stats.ibd to another location just in case anything else happen

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++来编辑文件.它位于xamppmysql

(3) If you can't delete nnodb_index_stats.ibd, you can try modify my.cnf file and set innodb_force_recovery > 0 (you can use notepad or notepad++ to edit the file. It locate in xamppmysql

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

Try these first to see if it helps you

更新请尝试在 xamppmysqldata 找到文件 ibdata1 并将其删除或重命名，然后重新启动 XAMPP，希望这对您有用

UPDATE Please try to locate file ibdata1 locate at xamppmysqldata and delete it or rename it, then restart XAMPP, hope this gonna work for you

这篇关于MySQL 未在 XAMPP 上启动的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！