如何解决“错误: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一打开就停止了。

日志上写着:-

10:31:21 [mysql]检测到问题! 10:31:21 [mysql] 3306端口被“无法打开进程”使用! 10:31:21 [mysql]如果没有配置的空闲端口，mysql将不会启动! 10:31:21 [mysql]你需要卸载/禁用/重新配置阻塞应用程序 10:31:21 [mysql]或重新配置mysql和控制面板侦听不同的端口

我停止了端口3306 wamp上正在运行的服务(在我的情况下)，在那之后它工作得很好。在配置设置中更改端口也可以工作。

YW!

2021-10-31 19:04:44

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

2016-12-26 06:11:07

重要提示:不要删除ibdata1文件。你可以毁掉你所有的数据库。

相反，首先尝试使用XAMPP附带的MySQL备份文件夹。所以接下来的步骤:

将mysql/data文件夹重命名为mysql/data_old 复制mysql/backup文件夹，命名为mysql/data 将所有数据库文件夹从mysql/data_old复制到mysql/data(除了mysql, performance_schema和phpmyadmin文件夹) 将mysql/data_old/ibdata1文件拷贝到mysql/data文件夹中从XAMPP控制面板启动MySQL

And,瞧!

编辑(2023年1月7日)

正如一些用户所提到的，这是一种紧急解决方案，而不是永久解决方案。在恢复数据后，强烈建议备份它，并重新安装XAMPP，因为失败与XAMPP的一些文件的故障有关，而不是数据库。

2020-05-17 22:20:02

重要提示:删除此文件可能导致任何现有的MySQL数据不可用。慎用

嘿，我刚做了这个，它起作用了:

退出Xampp服务器转到C:\xampp\mysql\data目录删除ibdata1文件重新启动xampp服务器

应该可以

2013-08-10 13:14:39

Error: MySQL shutdown unexpectedly

This is the best answer 

1)Rename the folder mysql/data to mysql/data_old (you can use any name)
2)Create a new folder mysql/data
3)Copy the content that resides in mysql/backup to the new mysql/data folder
4)Copy all your database folders that are in mysql/data_old to mysql/data (skipping the mysql, performance_schema, and phpmyadmin folders from data_old)
5)Finally copy the ibdata1 file from mysql/data_old and replace it inside mysql/data folder
6)Start MySQL from XAMPP control panel

2021-06-11 04:55:40

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

推荐文章

最新文章

标签