XAMPP MySQL意外关闭(没有阻塞端口)
XAMPP MySQL意外关闭(没有阻塞端口)
提问于 2022-01-16 10:46:09
从上一次成功到现在我没有做什么特别的事情来破坏它。但现在它给了我这样的信息：
11:37:07 [mysql] Error: MySQL shutdown unexpectedly.
11:37:07 [mysql] This may be due to a blocked port, missing dependencies,
11:37:07 [mysql] improper privileges, a crash, or a shutdown by another method.
11:37:07 [mysql] Press the Logs button to view error logs and check
11:37:07 [mysql] the Windows Event Viewer for more clues
11:37:07 [mysql] If you need more help, copy and post this
11:37:07 [mysql] entire log window on the forums我以前也吃过这个。通常，它出现在MySQL端口(3306)被阻塞时。我只是停止使用它。有一次我的InnoDB被破坏了或者类似的东西，但我也设法修复了它。但是现在我的日志文件绝对没有显示出任何有帮助的东西。它与早期的日志完全匹配。
InnoDB: using atomic writes.
2022-01-16 11:27:36 0 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2022-01-16 11:27:36 0 [Note] InnoDB: Uses event mutexes
2022-01-16 11:27:36 0 [Note] InnoDB: Compressed tables use zlib 1.2.11
2022-01-16 11:27:36 0 [Note] InnoDB: Number of pools: 1
2022-01-16 11:27:36 0 [Note] InnoDB: Using SSE2 crc32 instructions
2022-01-16 11:27:36 0 [Note] InnoDB: Initializing buffer pool, total size = 16M, instances = 1, chunk size = 16M
2022-01-16 11:27:36 0 [Note] InnoDB: Completed initialization of buffer pool
2022-01-16 11:27:36 0 [Note] InnoDB: 128 out of 128 rollback segments are active.
2022-01-16 11:27:36 0 [Note] InnoDB: Creating shared tablespace for temporary tables
2022-01-16 11:27:36 0 [Note] InnoDB: Setting file 'C:\xampp\mysql\data_minecraft\ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
2022-01-16 11:27:36 0 [Note] InnoDB: File 'C:\xampp\mysql\data_minecraft\ibtmp1' size is now 12 MB.
2022-01-16 11:27:36 0 [Note] InnoDB: Waiting for purge to start
2022-01-16 11:27:36 0 [Note] InnoDB: 10.4.17 started; log sequence number 17593598; transaction id 64665
2022-01-16 11:27:36 0 [Note] InnoDB: Loading buffer pool(s) from C:\xampp\mysql\data_minecraft\ib_buffer_pool
2022-01-16 11:27:36 0 [Note] Plugin 'FEEDBACK' is disabled.
2022-01-16 11:27:36 0 [Note] Server socket created on IP: '::'.我重新启动了我的PC几次，并启动了MySQL，将innodb_force_recovery设置为从0到3的每个值，这也没有什么好运气。你们知道我还能做些什么吗？
回答 1
Stack Overflow用户
发布于 2022-01-16 18:27:02
我找到了解决办法。在"mysql/data“文件夹中(您可能想要备份它)，我删除了名称中包含”中继-bin“、”中继-日志“或”主“的每个文件。我无法解释为什么这会起作用。我只是觉得MySQL在试图读取这些文件和创建新的文件时被困住了，但是这对我来说是有效的。
页面原文内容由Stack Overflow提供。腾讯云小微IT领域专用引擎提供翻译支持
原文链接：
https://stackoverflow.com/questions/70729327
复制相关文章
相似问题
腾讯云开发者
