如何解决“错误:MySQL关机意外”?

当我打开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控制面板打开外壳

mysqld --console --skip-grant-tables --skip-external-locking

然后再次打开另一个shell并运行

mysqlcheck -r --databases mysql --use-frm

现在关闭两个shell并重新启动xampp。

2022-09-16 05:59:46

其他回答

我已经通过结束任务管理器上mysqlid的任务解决了这个问题。

2019-12-17 06:56:32

我也有同样的问题。我的xampp控制面板将启动apache而不是mysql。问题出在iblogfile中。当你正在运行xampp/mysql时，你的电脑重新启动，而没有正确关闭innodb引擎。进入xampp/mysql并删除

ib_logfile0

and

ib_logfile1

现在重新启动mysql，它应该工作。

2022-08-20 23:52:51

你得到这个错误，因为你的sql端口3306正在忙(其他应用程序正在使用它)

停止3306进程(通过关闭该应用程序结束进程) 但是如何找到它?? 下载Microsoft的TCP查看器打开应用程序并搜索SQL 您将看到SQL正在运行并使用3306端口这就是为什么xampp的mysql无法运行的原因。

只需结束myql进程，就可以开始了启动xampp的mysql，完成

2022-07-21 17:50:17

0.cntr+alt+delet
1.end task mysqld
2.Restart mysql.

2020-03-24 18:26:43

从C:\xampp\mysql创建一个备份你的mysql文件夹。然后转到C:\xampp\mysql\backup复制所有文件并粘贴到C:\xampp\mysql\data中。

然后从你的旧备份文件夹中找到ibdata1文件，你可以在C:\xampp\mysql\data中找到它。复制此文件并粘贴到C:\xampp\mysql\data中。

现在重新启动xampp，它应该工作了。

2020-05-29 06:43:11

如何解决“错误:MySQL关机意外”?

推荐文章

最新文章

标签