当前位置: 首页 > 知识库问答 >
问题:

错误:MySQL意外关闭-XAMPP

尹承业
2023-03-14
Error: MySQL shutdown unexpectedly.
1:33:01  [mysql]    This may be due to a blocked port, missing dependencies, 
1:33:01  [mysql]    improper privileges, a crash, or a shutdown by another method.
1:33:01  [mysql]    Press the Logs button to view error logs and check
1:33:01  [mysql]    the Windows Event Viewer for more clues
1:33:01  [mysql]    If you need more help, copy and post this
1:33:01  [mysql]    entire log window on the forums
017-10-18 03:52:49 efc 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.
2017-10-18  3:52:49 3836 [Note] InnoDB: innodb_empty_free_list_algorithm has been changed to legacy because of small buffer pool size. In order to use backoff, increase buffer pool at least up to 20MB.
2017-10-18  3:52:49 3836 [Note] InnoDB: Using mutexes to ref count buffer pool pages
2017-10-18  3:52:49 3836 [Note] InnoDB: The InnoDB memory heap is disabled
2017-10-18  3:52:49 3836 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2017-10-18  3:52:49 3836 [Note] InnoDB: _mm_lfence() and _mm_sfence() are used for memory barrier
2017-10-18  3:52:49 3836 [Note] InnoDB: Compressed tables use zlib 1.2.3
2017-10-18  3:52:49 3836 [Note] InnoDB: Using generic crc32 instructions
2017-10-18  3:52:49 3836 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2017-10-18  3:52:49 3836 [Note] InnoDB: Completed initialization of buffer pool
2017-10-18  3:52:49 3836 [Note] InnoDB: Restoring page 0 of tablespace 0
2017-10-18  3:52:49 3836 [Warning] InnoDB: Doublewrite does not have page_no=0 of space: 0
2017-10-18  3:52:49 3836 [ERROR] InnoDB: space header page consists of zero bytes in data file C:\xampp\mysql\data\ibdata1
2017-10-18  3:52:49 3836 [ERROR] InnoDB: Could not open or create the system tablespace. If you tried to add new data files to the system tablespace, and it failed here, you should now edit innodb_data_file_path in my.cnf back to what it was, and remove the new ibdata files InnoDB created in this failed attempt. InnoDB only wrote those files full of zeros, but did not yet use them in any way. But be careful: do not remove old data files which contain your precious data!
2017-10-18  3:52:49 3836 [ERROR] Plugin 'InnoDB' init function returned error.
2017-10-18  3:52:49 3836 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
2017-10-18  3:52:49 3836 [Note] Plugin 'FEEDBACK' is disabled.
2017-10-18  3:52:49 3836 [ERROR] Unknown/unsupported storage engine: InnoDB
2017-10-18  3:52:49 3836 [ERROR] Aborting

共有1个答案

宓跃
2023-03-14

通过Install 5.6.35/PHP 5.6.35-XAMPP解决

使用Windows10、XAMPP7.2.2也有同样的问题。

  1. 备份htdocs项目
  2. 卸载的XAMPP 7.2.x
  3. 安装XAMPP 5.6.x
  4. 将备份项目粘贴到HTDocs
  5. 发现Apache端口号问题,请在httpd.conf中将80更改为8080
  6. 工作正常!
 类似资料:
  • 以下是错误日志的内容: 2018-08-18 11:53:23 4DC INNODB:警告:不推荐使用innodb_additional_mem_pool_size。在以后的版本中,该选项可能会与innodb_use_sys_malloc选项和INNODB的内部内存分配器一起删除。 2018-08-18 11:53:23 1244[注]INNODB:innodb_empty_free_list_a

  • 那只是日志的一部分,完整的有点太大了。 帮忙?

  • 但结果显示相同。有人能帮忙吗? 提前感谢S.K Setia

  • 我试图得到我的网站,我有一些问题时启动我的XAMPP Apache服务器 我在这里尝试了解决方案,但没有成功 我尝试的是: 将默认端口从80和433更改为8080和443 杀死所有HTTP连接与 逆转我所有的更改(因为我一直试图从这里安装一个ssl安全证书) 我没有成功添加安全证书,现在Apache甚至没有启动 我知道这是一个非常常见的问题,我读过很多关于这个问题的答案,但都没有成功。 以下是我对

  • 问题内容: 当我打开XAMPP并单击启动MySQL按钮时,它给我一个错误。我刚刚开始,但是现在不起作用。 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]

  • 我刚刚安装了XAMPP,当我尝试在XAMPP控制面板中启动Apache和MySQL时,现在出现以下错误: 19:27:08[mysql]错误:mysql意外关闭 19:27:08[mysql]这可能是由于端口被阻止、缺少依赖项、 19:27:08[mysql]权限不正确、崩溃或其他方法关闭所致 19:27:08[mysql]按Logs按钮查看错误日志,并查看Windows事件查看器中的更多线索 1