XAMPP-MySQL意外关闭 [英] XAMPP - MySQL shutdown unexpectedly

问题描述

当我打开XAMPP并单击启动MySQL"按钮时，它给我一个错误. 我刚刚开始，但是现在不起作用.

When I open XAMPP and click start MySQL button and it gives me an error. I had started it just before, but now it isn't working.

12:19:12 PM [mysql]尝试启动MySQL应用程序...
12:19:12 PM [mysql]检测到状态更改:正在运行
12:19:13 PM [mysql]检测到状态更改:已停止
12:19:13 PM [mysql]错误:MySQL意外关闭.
12:19:13 PM [mysql]这可能是由于端口阻塞，缺少依赖项，
12:19:13 PM [mysql]权限不当，崩溃或通过其他方法关闭
12:19:13 PM [mysql]按下日志按钮以查看错误日志并检查
12:19:13 PM [mysql] Windows事件查看器以获取更多线索
12:19:13 PM [mysql]如果您需要更多帮助，请复制并发布此内容
12:19:13 PM [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

以下是错误日志的内容:

Here is the contents of the error log:

2013-08-02 12:19:12 4536 [注意]插件"FEDERATED"已禁用.
2013-08-02 12:19:12 f64 InnoDB:警告:不建议使用innodb_additional_mem_pool_size.在将来的发行版中，此选项可能与选项innodb_use_sys_malloc和InnoDB的内部内存分配器一起删除.
2013-08-02 12:19:12 4536 [Note] InnoDB:InnoDB内存堆已禁用
2013-08-02 12:19:12 4536 [Note] InnoDB:互斥锁和rw_locks使用Windows互锁函数
2013-08-02 12:19:12 4536 [Note] InnoDB:压缩表使用zlib 1.2.3
2013-08-02 12:19:12 4536 [Note] InnoDB:未使用CPU crc32指令
2013-08-02 12:19:12 4536 [注意] InnoDB:正在初始化缓冲池，大小= 16.0M
2013-08-02 12:19:12 4536 [Note] InnoDB:完成缓冲池的初始化
2013-08-02 12:19:12 4536 [Note] InnoDB:支持的最高文件格式是梭子鱼.
2013-08-02 12:19:12 4536 [Note] InnoDB:ibdata文件中的日志序列号0和0与ib_logfiles中的日志序列号1616798不匹配！
2013-08-02 12:19:12 4536 [注意] InnoDB:数据库未正常关闭！
2013-08-02 12:19:12 4536 [Note] InnoDB:开始崩溃恢复.
2013-08-02 12:19:12 4536 [注意] InnoDB:正在从.ibd文件中读取表空间信息...

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...

最重要的错误消息在这里:

The most important error message is here:

2013-08-02 12:19:12 4536 [错误] InnoDB:
尝试打开以前打开的表空间.
上一个表空间 mysql/innodb_table_stats 在文件路径:.\ mysql \ innodb_table_stats.ibd 中使用空间ID:1.
无法打开文件空间为.\ xat \ payments.ibd

2013-08-02 12:19:12 4536 [ERROR] InnoDB:
Attempted to open a previously opened tablespace.
Previous tablespace mysql/innodb_table_stats uses space ID: 1 at filepath: .\mysql\innodb_table_stats.ibd.
Cannot open tablespace xat/payments which uses space ID: 1 at filepath: .\xat\payments.ibd

其余日志:

InnoDB:错误:无法打开单表表空间文件.\ xat \ payments.ibd
InnoDB:我们不会继续进行崩溃恢复，因为该表可能会变成
InnoDB:如果无法将InnoDB日志中的日志记录应用于该数据库，则会损坏.
InnoDB:要解决此问题并启动mysqld:
InnoDB:1)如果文件中存在权限问题，并且mysqld无法
InnoDB:打开文件，应该修改权限.
InnoDB:2)如果不需要该表，或者您可以从备份中还原它，
InnoDB:然后您可以删除.ibd文件，然后InnoDB将执行正常操作
InnoDB:崩溃恢复，并忽略该表.
InnoDB:3)如果文件系统或磁盘损坏，并且无法删除
InnoDB:.ibd文件，您可以在my.cnf
中将innodb_force_recovery> 0设置为 InnoDB:并强制InnoDB在此处继续崩溃恢复.

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.

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

What is the cause of these errors and how can I rectify them?

推荐答案

嘿，我做到了，它奏效了:

Hey I just did this and it worked:

1. 退出 Xampp服务器
2. 转到您的C:\xampp\mysql\data目录
3. 删除 ibdata1文件
4. 重启 xampp服务器

1. exit Xampp server
2. go to your C:\xampp\mysql\data directory
3. delete the ibdata1 file
4. restart xampp server

它应该工作

这篇关于XAMPP-MySQL意外关闭的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！