phpmyadmin MySQL意外关闭(导入数据库转储后不久MySQL不再启动)

nwo49xxi  于 2022-11-09  发布在  PHP
关注(0)|答案(1)|浏览(222)

我正在使用XAMPP进行本地网站开发。我第二次注意到MySQL在从PHPMyAdmin中的服务器导出数据库而创建的SQL文件中导入(大)数据库后崩溃/损坏了一段时间。与此同时,一切都很好。
当我现在尝试启动MySQL时,错误为:

12:17:23 AM  [mysql]    Attempting to start MySQL app...
12:17:23 AM  [mysql]    Status change detected: running
12:17:25 AM  [mysql]    Status change detected: stopped
12:17:25 AM  [mysql]    Error: MySQL shutdown unexpectedly.
12:17:25 AM  [mysql]    This may be due to a blocked port, missing dependencies, 
12:17:25 AM  [mysql]    improper privileges, a crash, or a shutdown by another method.
12:17:25 AM  [mysql]    Press the Logs button to view error logs and check
12:17:25 AM  [mysql]    the Windows Event Viewer for more clues
12:17:25 AM  [mysql]    If you need more help, copy and post this
12:17:25 AM  [mysql]    entire log window on the forums

检查mysql_error. log并没有显示出什么特别有用的信息:

2022-07-18  0:17:24 0 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2022-07-18  0:17:24 0 [Note] InnoDB: Uses event mutexes
2022-07-18  0:17:24 0 [Note] InnoDB: Compressed tables use zlib 1.2.11
2022-07-18  0:17:24 0 [Note] InnoDB: Number of pools: 1
2022-07-18  0:17:24 0 [Note] InnoDB: Using SSE2 crc32 instructions
2022-07-18  0:17:24 0 [Note] InnoDB: Initializing buffer pool, total size = 16M, instances = 1, chunk size = 16M
2022-07-18  0:17:24 0 [Note] InnoDB: Completed initialization of buffer pool
2022-07-18  0:17:24 0 [Note] InnoDB: 128 out of 128 rollback segments are active.
2022-07-18  0:17:24 0 [Note] InnoDB: Creating shared tablespace for temporary tables
2022-07-18  0:17:24 0 [Note] InnoDB: Setting file 'C:\xampp\mysql\data\ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
2022-07-18  0:17:24 0 [Note] InnoDB: File 'C:\xampp\mysql\data\ibtmp1' size is now 12 MB.
2022-07-18  0:17:24 0 [Note] InnoDB: Waiting for purge to start
2022-07-18  0:17:24 0 [Note] InnoDB: 10.4.24 started; log sequence number 56544792; transaction id 997
2022-07-18  0:17:24 0 [Note] InnoDB: Loading buffer pool(s) from C:\xampp\mysql\data\ib_buffer_pool
2022-07-18  0:17:24 0 [Note] Plugin 'FEEDBACK' is disabled.
2022-07-18  0:17:24 0 [Note] InnoDB: Buffer pool(s) load completed at 220718  0:17:24
2022-07-18  0:17:24 0 [Note] Server socket created on IP: '::'.

然而,检查Windows日志-〉应用程序下的Windows事件查看器似乎显示了启动失败的罪魁祸首:

The description for Event ID 100 from source MariaDB cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.

If the event originated on another computer, the display information had to be saved with the event.

The following information was included with the event: 

mysqld.exe: Error on close of 'C:\xampp\mysql\data\aria_log_control' (Errcode: 9 "Bad file descriptor")

The system cannot find the file specified

要点似乎是关闭aria_log_control文件时的错误。我不太明白这个错误。文件存在并且没有被锁定。删除文件并不能解决问题。还有deleting aria_log.00000001 does not work。MySQL的启动怎么会因为这个原因而失败,MySQL怎么会突然无法启动(突然出现)?我也尝试重新启动Windows,但问题没有得到解决。我确信我的系统上没有恶意软件导致这些问题。在C:\xampp\mysql\data中移动/重命名我的数据库文件夹不起作用,直接移动/重命名C:\xampp\mysql\data也不起作用。我能做些什么来避免这个MySQL启动故障?除了完全重新安装XAMPP之外,我该如何修复它?后者可以恢复MySQL并运行,但这不是一个很好的解决方案,我必须重新创建数据库,导入架构和数据库数据本身只是为了再次发生该问题(很可能)。

rekjcdws

rekjcdws1#

错误是Windows报告在尝试关闭aria_log_control文件时文件未打开(可能已关闭)。
这是一个MariaDB实现错误,但不会导致任何数据损坏。在某些路径中,可能会超过open_files_limit。
删除控制文件并从备份中恢复没有帮助。提高open_file_limit或它所依赖的变量可能会有帮助。如果没有帮助,请暂时忽略此Windows错误消息。
我已经在这个基础上创建了错误报告(MDEV-29117)。作为参考,你的SQL文件中有多少个表。这些是Aria,InnoDB还是混合体?

相关问题