如何解决“错误: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面板中打开MySql日志。最后，它说您正在3306端口运行mysqlid的另一个实例我打开我的任务管理器(Ctrl+Shift+Esc)，然后找到mysqlid和结束任务。

2020-08-01 04:32:53

其他回答

也有同样的问题。

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)尝试不同的东西。

2021-07-13 18:21:56

请检查系统时间是否正确。我的时间设定在2040年，修正日期就解决了问题。

2016-12-26 06:11:07

从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时，我在我的C:\xampp\mysql\data\mysql_error.log中得到了同样的错误。

2013-08-05 01:20:32 6780 [ERROR] InnoDB: Attempted to open a previously 
  opened tablespace. Previous tablespace mysql/slave_relay_log_info uses 
  space ID: 3 at filepath: .\mysql\slave_relay_log_info.ibd. Cannot open  
  tablespace test_database/test_table which uses space ID: 3 at filepath:  
  .\test_database\test_table.ibd

你必须仔细阅读错误。这说明test_database阻止mysql启动。

你可以清除这个有问题的数据库，以下步骤可以解决这个问题:

确保mysql和xampp完全关闭。去你的mysql安装目录，我的是:C:\xampp\mysql\data 您应该看到一个文件夹，其名称为您创建的数据库。我的是test_database。在其他地方创建一个名为C:\xampp\mysql\data\mysql\backuptablespace的新文件夹将有问题的数据库表文件夹拖放到备份目录中(不要删除)。重新启动mysql。对我来说，它像预期的那样在1秒内就开始了。

如果它不起作用，把文件放回你开始的地方，你就会回到你开始的地方。

如果你不想删除数据库并且没有备份:

如果你没有表数据的备份，mysql不会启动，因为某些东西损坏了，你将不得不使用消除的过程来猜测和检查你的方式，确切地说，你做了什么损坏了它。遵循以下步骤:

Make a clone of the entire C:\xampp\ and store it somewhere safe so you can get back to where you started. Use a "binary search" approach to try to locate the corrupted item in the mysql database. It could be a file, or a table, or a database, or a user or anything. Delete the entire database and see if that allows mysql to start. If it does, then put back the database and try removing some of the tables. If it doesn't, then try yanking out something else until it does start. Try removing these files from C:\xampp\mysql\data\mysql: db.frm db.MRD db.MYI db.opt user.frm user.MYD user.MYI When you get mysql to start, try putting things back until you find the one thing that you add which prevents it from starting. One bonus for this is you learn how mysql works under the hood.

核选项:

你搞砸了mysql服务器。卸载并重新安装XAMPP可以消除损坏。

2013-08-08 17:25:06

进入任务管理器然后搜索mysqld，右键单击并选择END TASK并刷新XAMPP

2019-09-07 06:05:43

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

推荐文章

最新文章

标签