当我打开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.

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


当前回答

重要提示:删除此文件可能导致任何现有的MySQL数据不可用。慎用

嘿,我刚做了这个,它起作用了:

退出Xampp服务器 转到C:\xampp\mysql\data目录 删除ibdata1文件 重新启动xampp服务器

应该可以

其他回答

也有同样的问题。

STAEP 1

backup folder xampp/mysql/data (saved it as `xampp/mysql/_old_data`).

STAEP 2

去xampp/mysql/data,删除所有的文件,但没有文件夹!与数据库。

STAEP 3

At this stage your database will not work. You need to go to your backup folder `xampp/mysql/_old_data` and copy over "`ibdata1`" file to `xampp/mysql/data`.

之后,一切工作如预期,包括phpmyadmin和控制台。

STAEP 4

如果这没有帮助的话。可以删除xampp/mysql/data文件夹,并将xampp/mysql/_old_data重命名为xampp/mysql/data。 (ROLLBACK)尝试不同的东西。

进入mysql/data/目录 删除所有随机文件(除了实际的数据库文件夹) 重启Apache和MySQL。

它应该能解决这个问题。

上述解决方案对我来说都没用。然后我做了以下事情:

我删除了C:\xampp\mysql\data\目录下的所有文件,除了这个目录下的文件夹。 它工作得非常好,但我以前的数据库现在不能工作了。 所以,如果你不关心,上面会删除所有你以前的数据库在phpmyadmin。

如果你正在使用MariaDB,你可以试试这个:

进入mysql/data/目录 将aria_log_control重命名为aria_log_control_old 重启“Mysql”

在我的情况下,我同步我的mysql数据和htdocs到dropbox,我只需要删除mysql/data文件夹和子文件夹中的冲突文件。dropbox会告诉你,有冲突的文件可以通过名称来识别。这为我解决了问题。