【问题标题】:MySQL not launching on XAMPPMySQL 未在 XAMPP 上启动
【发布时间】:2013-10-13 06:11:15
【问题描述】:

我无法通过 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.

【问题讨论】:

  • 已经在您的错误报告中提供了有关如何修复它的建议。您尝试过其中任何一个吗?
  • @DoanCuong 我不会撒谎,我只是一名设计师,所以大部分技术内容对我来说都是中国的,即使有建议我也不知道从哪里开始!跨度>

标签: mysql xampp


【解决方案1】:

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

您无法启动 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++编辑文件,位于xampp\mysql\

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

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

【讨论】:

  • 我遇到的问题是我在我的系统上根本找不到 innodb_index_stats.ibd,我已经尝试搜索该文件但它似乎不存在?
  • 奇怪,它应该在xampp\mysql\data,你检查过那个位置吗?
  • 啊是的,它在那里,我尝试重命名文件并复制备份,但没有任何效果...我在 xampp/mysql 中也找不到 my.cnf?
  • 所以我完成了恢复,但仍然无法启动:我已将新错误添加到主帖
  • @DaveBurns 回答已编辑,看看是否对您有帮助:)
【解决方案2】:

我通过删除 ~/x-ampp/mysql/data

中的所有 ib_logfiles 解决了同样的问题

【讨论】:

    猜你喜欢
    • 2018-12-02
    • 2018-12-21
    • 2019-12-02
    • 2021-03-26
    • 2020-11-01
    • 2016-03-10
    • 2013-12-30
    • 2017-03-26
    • 2016-01-05
    相关资源
    最近更新 更多