如何解决“错误: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

其他回答

通过重新安装Xampp修复了它。

如果你不想经历对方提出的所有技术问题。

备份htdocs文件夹，然后卸载Xampp，它会问你是否想保留htdocs文件夹，选择退出。完全卸载, 移除残留物。再次安装，复制你备份的htdocs文件夹。

你就完成了。

2020-10-22 20:47:27

我的Xampp MySQL工作如下:

01.Go to mysql/data/ directory
02. delete the ibdata1 & ib_logfile*(ib_logfile0,ib_logfile1,ib_logfile101) file
03. restart xampp server

2016-12-04 09:45:07

如果你不需要损坏表中的数据，你可以通过丢弃表空间来删除它:

ALTER TABLE sakila.actor DISCARD TABLESPACE;

之后，你可以删除表本身:

DROP TABLE sakila.actor;

如果第一步不起作用，首先替换actor。从具有相同结构的空表中复制Ibd文件。

源

2021-08-17 07:13:46

我也遇到过这个问题，我是这样解决的。 1. 确保xampp不在子目录下。例如，它应该是C:\xampp 2. 在运行应用程序时，您可能需要以管理员身份运行。

希望这能起作用!

2013-08-13 18:31:41

在mysql配置文件(my.ini)的[mysqld]部分下面添加以下一行，然后重新启动apache web服务器和mysql服务。

[mysqld]
innodb_force_recovery = 4

2013-12-16 17:40:41

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

推荐文章

最新文章

标签