errro mysql shutdown_XAMPP Error: MySQL shutdown unexpectedly.

最新推荐文章于 2021-12-03 17:50:38 发布

桀弟弟

最新推荐文章于 2021-12-03 17:50:38 发布

阅读量1.1k

点赞数

文章标签： errro mysql shutdown

本文链接：https://blog.csdn.net/weixin_36082346/article/details/113287334

版权

祝大家新年快乐，有任何问题可与我联系：

XAMPP出现异常时就会有以下提示：

09:27:52 [mysql ] Error: MySQL shutdown unexpectedly.

09:27:52 [mysql ] This may be due to a blocked port, missing dependencies,

09:27:52 [mysql ] improper privileges, a crash, or a shutdown by another method.

09:27:52 [mysql ] Press the Logs button to view error logs and check

09:27:52 [mysql ] the Windows Event Viewer for more clues

09:27:52 [mysql ] If you need more help, copy and post this

09:27:52 [mysql ] entire log window on the forums

其实单看以上这些错误信息根本就不能解决问题，百度上的方法也是千奇百怪，根本就没用。于是我从错误日志中找到以下错误信息：

InnoDB: Error: could not open single-table tablespace file .\mysql\innodb_index_stats.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.

2015-12-30 09:27:51 5988 [Note] Plugin ‘FEDERATED’ is disabled.

2015-12-30 09:27:51 688 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.

2015-12-30 09:27:51 5988 [Note] InnoDB: The InnoDB memory heap is disabled

2015-12-30 09:27:51 5988 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions

2015-12-30 09:27:51 5988 [Note] InnoDB: Compressed tables use zlib 1.2.3

2015-12-30 09:27:51 5988 [Note] InnoDB: Not using CPU crc32 instructions

2015-12-30 09:27:51 5988 [Note] InnoDB: Initializing buffer pool, size = 16.0M

2015-12-30 09:27:51 5988 [Note] InnoDB: Completed initialization of buffer pool

2015-12-30 09:27:51 5988 [Note] InnoDB: Highest supported file format is Barracuda.

2015-12-30 09:27:51 5988 [Note] InnoDB: The log sequence numbers 619803155 and 619803155 in ibdata files do not match the log sequence number 620046439 in the ib_logfiles!

2015-12-30 09:27:51 5988 [Note] InnoDB: Database was not shutdown normally!

2015-12-30 09:27:51 5988 [Note] InnoDB: Starting crash recovery.

2015-12-30 09:27:51 5988 [Note] InnoDB: Reading tablespace information from the .ibd files…

2015-12-30 09:27:51 5988 [ERROR] InnoDB: Attempted to open a previously opened tablespace. Previous tablespace deps/dep_codelist uses space ID: 2 at filepath: .\deps\dep_codelist.ibd. Cannot open tablespace mysql/innodb_index_stats which uses space ID: 2 at filepath: .\mysql\innodb_index_stats.ibd