当我打开XAMPP并单击启动MySQL按钮时,它给了我一个错误。 我刚才启动了它,但现在它不工作了。

12:19:12 PM [mysql] Attempting to start MySQL app... 12:19:12 PM [mysql] Status change detected: running 12:19:13 PM [mysql] Status change detected: stopped 12:19:13 PM [mysql] Error: MySQL shutdown unexpectedly. 12:19:13 PM [mysql] This may be due to a blocked port, missing dependencies, 12:19:13 PM [mysql] improper privileges, a crash, or a shutdown by another method 12:19:13 PM [mysql] Press the Logs button to view error logs and check 12:19:13 PM [mysql] the Windows Event Viewer for more clues 12:19:13 PM [mysql] If you need more help, copy and post this 12:19:13 PM [mysql] entire log window on the forums

以下是错误日志的内容:

2013-08-02 12:19:12 4536 [Note] Plugin 'FEDERATED' is disabled. 2013-08-02 12:19:12 f64 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-08-02 12:19:12 4536 [Note] InnoDB: The InnoDB memory heap is disabled 2013-08-02 12:19:12 4536 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions 2013-08-02 12:19:12 4536 [Note] InnoDB: Compressed tables use zlib 1.2.3 2013-08-02 12:19:12 4536 [Note] InnoDB: Not using CPU crc32 instructions 2013-08-02 12:19:12 4536 [Note] InnoDB: Initializing buffer pool, size = 16.0M 2013-08-02 12:19:12 4536 [Note] InnoDB: Completed initialization of buffer pool 2013-08-02 12:19:12 4536 [Note] InnoDB: Highest supported file format is Barracuda. 2013-08-02 12:19:12 4536 [Note] InnoDB: The log sequence numbers 0 and 0 in ibdata files do not match the log sequence number 1616798 in the ib_logfiles! 2013-08-02 12:19:12 4536 [Note] InnoDB: Database was not shutdown normally! 2013-08-02 12:19:12 4536 [Note] InnoDB: Starting crash recovery. 2013-08-02 12:19:12 4536 [Note] InnoDB: Reading tablespace information from the .ibd files...

最重要的错误信息在这里:

2013-08-02 12:19:12 4536 [ERROR] InnoDB: 试图打开先前打开的表空间。 以前的表空间mysql/innodb_table_stats在filepath: .\mysql\innodb_table_stats.ibd使用的是空间ID: 1。 在文件路径:.\xat\payments.ibd下无法打开空间ID: 1的表空间xat/payments

日志的其余部分:

InnoDB: Error: could not open single-table tablespace file .\xat\payments.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.

这些错误的原因是什么?我该如何纠正它们?


当前回答

我也有这个问题,当我得到这个错误,去xampp->mysql->数据 然后删除所有其他没有文件夹的文件,不要删除文件夹, 然后运行xampp,启动mysql

其他回答

如果以上任何一种方法都不起作用,制作Xampp目录的备份并重新安装Xampp。这当然有用!

复制xampp/mysql/backup/中的所有文件,然后粘贴到/xampp/mysql/data/中 重新启动mysql。

当您不是以管理员身份运行XAMPP时,关闭MySQL经常会导致损坏,这意味着您必须修复或删除表。为了避免这种情况,您需要以管理员身份运行XAMPP,或者使用适当的命令提示符方法关闭MySQL。

您可以按照Kratos的建议删除ibdata1,但这可能会导致数据库损坏,因为数据库的其他部分仍然在/mysql/data/文件夹中。在我的例子中,这些残留数据阻止了我成功安装WordPress。

一个更干净的方法是恢复整个/mysql/data/文件夹。Windows有内置的文件夹版本控制-右键单击/mysql/data/并选择恢复以前的版本。然后可以删除文件夹的当前内容,并将其替换为旧版本的内容。

附录:为了确保您不会忘记以管理员身份运行XAMPP,您可以右键单击XAMPP快捷方式,转到属性,然后是高级,最后以管理员身份运行。

如果上面提到的答案不工作,您可以尝试删除数据中的所有文件,除了文件夹

转到: C:\xampp\mysql\data

后: Goto: C: \ xampp \ mysql \ bin

然后用记事本my.ini打开 它看起来是这样的。

然后删除或注释3306端口,并将其更改为8111,然后使用管理员运行xamp,其工作正常。

Apache - >配置- >打开httpd . conf。搜索监听或80,更新监听端口到8081保存并重新启动服务器。 哦,如果你有Skype,关掉它。