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

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

当前回答

There are a number of things I've tried. This is the 2nd time this has happened to me. On my first time, I've to reinstall my xampp. And on the third day, mysql crashed again. I've tried everything I found on the internet. Like, innodb_flush_method=normal in my.ini file and deleting ibdata1, ib_logfile1, ib_logfile0 files, and others but none of these works. So later I tried to run xampp with admin privilege and install apache and mysql as a service as it was instructed on xampp control panel itself. After starting mysql, I read error-log again and from there I came to know that one of my databases is responsible for this. That database file won't let mysql start. So I deleted everything in the data folder and then in cmd I navigated to C:/xampp/mysql/bin path and ran these commands:

mysqld——初始化

mysql_install_db

mysql又开始运行了。但是我的数据库和数据丢失了。

2020-07-19 11:26:10

其他回答

这是更精确的答案，对我来说很管用!!!!！一个更干净的方法是恢复整个/mysql/data/文件夹。Windows有内置的文件夹版本控制-右键单击/mysql/data/并选择恢复以前的版本。然后可以删除文件夹的当前内容，并将其替换为旧版本的内容。正如Ryan Williams所提到的。

2019-07-25 14:59:50

如果这里列出的解决方案都不适合你和我一样，那么

进入任务管理器。进入“服务”选项卡。查找名为“MySQL80”的服务。右键单击它并选择“stop”。回到XAMPP控制面板，启动MySQL服务。

这对我很管用。

2020-10-09 04:54:32

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

转到： C：\xampp\mysql\data

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

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

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

2020-01-28 02:36:09

也有同样的问题。

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

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

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

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

你就完成了。

2020-10-22 20:47:27

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

推荐文章

最新文章

标签