自 2023 年 10 月 20 日起，我的 xampp 安装 (8.2.4) 中的 mysql 实例不再启动。它尝试了几秒钟，但崩溃并显示无意义的文本（您将在下面找到它，德语）。大约两周前到现在，我没有对我的系统进行任何更改。操作系统、新软件、编程……都没有什么可能导致此问题。在这段时间内我几乎只玩了一些游戏并使用了我的浏览器。
当然，我想查看错误日志，并且这样做我想使用 xampp-Control-Panel 中的按钮的简单方法，但这不起作用。一条消息提示说找不到日志文件。最重要的是，还有更多带有奇怪路径的消息。这个问题（通过 xampp 按钮打开 mysql-error-log）是我自己解决的，方法是删除 xampp 建议的安装路径中的空格。太疯狂了，我的安装以这种方式工作了几年（带空格），突然间它引起了问题。没关系。
现在访问 mysql-error-log（您将在下面找到它），我看到几个条目指出 ibd 文件丢失。我从旧备份中恢复了这些文件，但绝对没有更改这些文件或相关数据库上的任何内容。同样，奇怪的是，当它之前工作时（没有恢复这些文件），这突然成为一个问题。也许 Windows-Defender 产生了影响？我查了一下——不，没有。而且我没有使用任何其他防病毒软件。
如果没有这些 ibd-missing-errors，当前的 mysql-error-log 和问题之前的旧日志看起来几乎相同。比较这些将导致一个事实，即它在“在 IP: '::' 上创建的服务器套接字。”行之后崩溃。在旧的工作日志中，此行之后 mysqld.exe 将成功启动。目前情况已不再如此，我不知道为什么。
你们有什么想法吗？你能帮我吗？
我尝试过的：
由于 xampp-Control-Panel 中的文本建议我使用管理权限并删除安装路径中的空格（当我想打开错误日志时），我正是这么做的。
这以前不是必需的，它解决的唯一两件事是 a) 通过控制面板访问错误日志和 b) 控制面板中不再有关于此主题的提示。
我从 2023 年 6 月 13 日的备份中恢复
mysql-error-log 中的相关错误就消失了。
有多个“zen_civ5”表，其中 ibd 文件也丢失。这些是非常旧的表，我在一两年前删除（DROP）。同样，系统坚持在这些桌子上，这很奇怪。好吧，为了解决问题，我从一个非常旧的备份（2019）导入了这些表，这有助于删除日志中的相关错误。
此时日志对我没有任何帮助，因为最后一行是“在 IP: '::' 上创建的服务器套接字。”。 所以我大胆地寻找端口 3306。也许另一个程序决定使用它？我用了'netstat -aon |在控制台中查找“3306”没有任何结果。所以该端口可以免费使用。 （3306 是正确的，因为它在控制面板中可见，并且位于 mysql 的 my.ini 中。）
我还尝试将端口更改为3307并删除xampp / mysql / data中的ibdata1，ib_logfile0，ib_logfile1，ib_logfile101，就像互联网上许多其他问题中所建议的那样（将其从mysql更改为my.ini，从php更改为php.ini） 。也没有帮助。
我还下载了两个新的 xampp 安装（普通和便携式）并快速设置（更正路径）。两者都可以完美地运行apache，但是两者在mysql上都有同样的问题。所以几乎可以肯定这与我的安装无关。它必须与我的系统有关。或者你觉得怎么样？
=== 来自 xampp-Control-Panel 的资源 #1 文本 ===
19:11:31 [main] Dein Benutzerprofil besitzt keine Administratorenrechte! Das reicht aus für die meisten
19:11:31 [main] Anwendungsfunktionen, aber wann immer du etwas mit Windows-Diensten tun möchtest,
19:11:31 [main] wird eine Sicherheitsabfrage erscheinen oder etwas wird garnicht erst funktionieren!
19:11:31 [main] Also denke daran diese Anwendung mit Administratorrechten zu starten!
19:11:31 [main] ACHTUNG: Der XAMPP Installationspfad enthält Leerzeichen. Dies könnte die Funktionalität von Programmen/Scripten beeinflussen
17:21:10 [mysql] Autostart aktiv: Starte...
17:21:10 [mysql] Versuche MySQL zu starten...
17:21:11 [mysql] Statusänderung erkannt: gestartet
17:21:15 [mysql] Statusänderung erkannt: gestoppt
17:21:15 [mysql] Fehler: MySQL wurde unerwartet beendet
17:21:15 [mysql] Ursache könnte ein geblockter Port, fehlende Abhängigkeiten,
17:21:15 [mysql] fehlende Berechtigungen, ein Absturz oder ein Abbruch einer anderen Methode sein.
17:21:15 [mysql] Drücke den Logs Button um error logs zu sehen und prüfe
17:21:15 [mysql] im Windows Event Viewer für weitere Hinweise
17:21:15 [mysql] Wenn du weitere Hilfe benötigst, kopiere den kompletten Inhalt des Log Fensters
17:21:15 [mysql] und füge ihn als Ergänzung in einem neuen Forum Eintrag hinzu.
===资源#2 mysql_error-问题发生时的日志===
2023-10-26 21:45:53 0 [Note] Starting MariaDB 10.4.28-MariaDB source revision c8f2e9a5c0ac5905f28b050b7df5a9ffd914b7e7 as process 16744
2023-10-26 21:45:53 0 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2023-10-26 21:45:53 0 [Note] InnoDB: Uses event mutexes
2023-10-26 21:45:53 0 [Note] InnoDB: Compressed tables use zlib 1.2.12
2023-10-26 21:45:53 0 [Note] InnoDB: Number of pools: 1
2023-10-26 21:45:53 0 [Note] InnoDB: Using SSE2 crc32 instructions
2023-10-26 21:45:53 0 [Note] InnoDB: Initializing buffer pool, total size = 16M, instances = 1, chunk size = 16M
2023-10-26 21:45:53 0 [Note] InnoDB: Completed initialization of buffer pool
2023-10-26 21:45:53 0 [ERROR] InnoDB: Operating system error number 2 in a file operation.
2023-10-26 21:45:53 0 [Note] InnoDB: Some operating system error numbers are described at https://mariadb.com/kb/en/library/operating-system-error-codes/
2023-10-26 21:45:53 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\mysql\slave_master_info.ibd' OS error: 71
2023-10-26 21:45:53 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2023-10-26 21:45:53 0 [Note] InnoDB: Some operating system error numbers are described at https://mariadb.com/kb/en/library/operating-system-error-codes/
2023-10-26 21:45:53 0 [ERROR] InnoDB: Could not find a valid tablespace file for ``mysql`.`slave_master_info``. Please refer to https://mariadb.com/kb/en/innodb-data-dictionary-troubleshooting/ for how to resolve the issue.
2023-10-26 21:45:53 0 [Warning] InnoDB: Ignoring tablespace for `mysql`.`slave_master_info` because it could not be opened.
2023-10-26 21:45:53 0 [ERROR] InnoDB: Operating system error number 2 in a file operation.
2023-10-26 21:45:53 0 [Note] InnoDB: Some operating system error numbers are described at https://mariadb.com/kb/en/library/operating-system-error-codes/
2023-10-26 21:45:53 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\mysql\slave_relay_log_info.ibd' OS error: 71
2023-10-26 21:45:53 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2023-10-26 21:45:53 0 [Note] InnoDB: Some operating system error numbers are described at https://mariadb.com/kb/en/library/operating-system-error-codes/
2023-10-26 21:45:53 0 [ERROR] InnoDB: Could not find a valid tablespace file for ``mysql`.`slave_relay_log_info``. Please refer to https://mariadb.com/kb/en/innodb-data-dictionary-troubleshooting/ for how to resolve the issue.
2023-10-26 21:45:53 0 [Warning] InnoDB: Ignoring tablespace for `mysql`.`slave_relay_log_info` because it could not be opened.
2023-10-26 21:45:53 0 [ERROR] InnoDB: Operating system error number 2 in a file operation.
2023-10-26 21:45:53 0 [Note] InnoDB: Some operating system error numbers are described at https://mariadb.com/kb/en/library/operating-system-error-codes/
2023-10-26 21:45:53 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\mysql\slave_worker_info.ibd' OS error: 71
2023-10-26 21:45:53 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2023-10-26 21:45:53 0 [Note] InnoDB: Some operating system error numbers are described at https://mariadb.com/kb/en/library/operating-system-error-codes/
2023-10-26 21:45:53 0 [ERROR] InnoDB: Could not find a valid tablespace file for ``mysql`.`slave_worker_info``. Please refer to https://mariadb.com/kb/en/innodb-data-dictionary-troubleshooting/ for how to resolve the issue.
2023-10-26 21:45:53 0 [Warning] InnoDB: Ignoring tablespace for `mysql`.`slave_worker_info` because it could not be opened.
2023-10-26 21:45:53 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2023-10-26 21:45:53 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2023-10-26 21:45:53 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2023-10-26 21:45:53 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\zen_civ5\log_admin.ibd' OS error: 203
2023-10-26 21:45:53 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2023-10-26 21:45:53 0 [Note] InnoDB: Some operating system error numbers are described at https://mariadb.com/kb/en/library/operating-system-error-codes/
2023-10-26 21:45:53 0 [ERROR] InnoDB: Could not find a valid tablespace file for ``zen_civ5`.`log_admin``. Please refer to https://mariadb.com/kb/en/innodb-data-dictionary-troubleshooting/ for how to resolve the issue.
2023-10-26 21:45:53 0 [Warning] InnoDB: Ignoring tablespace for `zen_civ5`.`log_admin` because it could not be opened.
2023-10-26 21:45:53 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2023-10-26 21:45:53 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2023-10-26 21:45:53 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2023-10-26 21:45:53 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\zen_civ5\log_dev.ibd' OS error: 203
2023-10-26 21:45:53 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2023-10-26 21:45:53 0 [Note] InnoDB: Some operating system error numbers are described at https://mariadb.com/kb/en/library/operating-system-error-codes/
2023-10-26 21:45:53 0 [ERROR] InnoDB: Could not find a valid tablespace file for ``zen_civ5`.`log_dev``. Please refer to https://mariadb.com/kb/en/innodb-data-dictionary-troubleshooting/ for how to resolve the issue.
2023-10-26 21:45:53 0 [Warning] InnoDB: Ignoring tablespace for `zen_civ5`.`log_dev` because it could not be opened.
2023-10-26 21:45:53 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2023-10-26 21:45:53 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2023-10-26 21:45:53 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2023-10-26 21:45:53 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\zen_civ5\log_user.ibd' OS error: 203
2023-10-26 21:45:53 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2023-10-26 21:45:53 0 [Note] InnoDB: Some operating system error numbers are described at https://mariadb.com/kb/en/library/operating-system-error-codes/
2023-10-26 21:45:53 0 [ERROR] InnoDB: Could not find a valid tablespace file for ``zen_civ5`.`log_user``. Please refer to https://mariadb.com/kb/en/innodb-data-dictionary-troubleshooting/ for how to resolve the issue.
2023-10-26 21:45:53 0 [Warning] InnoDB: Ignoring tablespace for `zen_civ5`.`log_user` because it could not be opened.
2023-10-26 21:45:53 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2023-10-26 21:45:53 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2023-10-26 21:45:53 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2023-10-26 21:45:53 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\zen_civ5\mls_areas.ibd' OS error: 203
2023-10-26 21:45:53 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2023-10-26 21:45:53 0 [Note] InnoDB: Some operating system error numbers are described at https://mariadb.com/kb/en/library/operating-system-error-codes/
2023-10-26 21:45:53 0 [ERROR] InnoDB: Could not find a valid tablespace file for ``zen_civ5`.`mls_areas``. Please refer to https://mariadb.com/kb/en/innodb-data-dictionary-troubleshooting/ for how to resolve the issue.
2023-10-26 21:45:53 0 [Warning] InnoDB: Ignoring tablespace for `zen_civ5`.`mls_areas` because it could not be opened.
2023-10-26 21:45:53 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2023-10-26 21:45:53 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2023-10-26 21:45:53 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2023-10-26 21:45:53 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\zen_civ5\mls_content.ibd' OS error: 203
2023-10-26 21:45:53 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2023-10-26 21:45:53 0 [Note] InnoDB: Some operating system error numbers are described at https://mariadb.com/kb/en/library/operating-system-error-codes/
2023-10-26 21:45:53 0 [ERROR] InnoDB: Could not find a valid tablespace file for ``zen_civ5`.`mls_content``. Please refer to https://mariadb.com/kb/en/innodb-data-dictionary-troubleshooting/ for how to resolve the issue.
2023-10-26 21:45:53 0 [Warning] InnoDB: Ignoring tablespace for `zen_civ5`.`mls_content` because it could not be opened.
2023-10-26 21:45:53 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2023-10-26 21:45:53 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2023-10-26 21:45:53 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2023-10-26 21:45:53 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\zen_civ5\mls_types.ibd' OS error: 203
2023-10-26 21:45:53 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2023-10-26 21:45:53 0 [Note] InnoDB: Some operating system error numbers are described at https://mariadb.com/kb/en/library/operating-system-error-codes/
2023-10-26 21:45:53 0 [ERROR] InnoDB: Could not find a valid tablespace file for ``zen_civ5`.`mls_types``. Please refer to https://mariadb.com/kb/en/innodb-data-dictionary-troubleshooting/ for how to resolve the issue.
2023-10-26 21:45:53 0 [Warning] InnoDB: Ignoring tablespace for `zen_civ5`.`mls_types` because it could not be opened.
2023-10-26 21:45:53 0 [ERROR] InnoDB: Operating system error number 3 in a file operation.
2023-10-26 21:45:53 0 [ERROR] InnoDB: The error means the system cannot find the path specified.
2023-10-26 21:45:53 0 [ERROR] InnoDB: If you are installing InnoDB, remember that you must create directories yourself, InnoDB does not create them.
2023-10-26 21:45:53 0 [ERROR] InnoDB: Cannot open datafile for read-only: '.\zen_civ5\project_settings.ibd' OS error: 203
2023-10-26 21:45:53 0 [ERROR] InnoDB: Operating system error number 203 in a file operation.
2023-10-26 21:45:53 0 [Note] InnoDB: Some operating system error numbers are described at https://mariadb.com/kb/en/library/operating-system-error-codes/
2023-10-26 21:45:53 0 [ERROR] InnoDB: Could not find a valid tablespace file for ``zen_civ5`.`project_settings``. Please refer to https://mariadb.com/kb/en/innodb-data-dictionary-troubleshooting/ for how to resolve the issue.
2023-10-26 21:45:53 0 [Warning] InnoDB: Ignoring tablespace for `zen_civ5`.`project_settings` because it could not be opened.
2023-10-26 21:45:53 0 [Note] InnoDB: 128 out of 128 rollback segments are active.
2023-10-26 21:45:53 0 [Note] InnoDB: Creating shared tablespace for temporary tables
2023-10-26 21:45:53 0 [Note] InnoDB: Setting file 'C:\Software\_Proggen\xampp-8.2.4\mysql\data\ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
2023-10-26 21:45:53 0 [Note] InnoDB: File 'C:\Software\_Proggen\xampp-8.2.4\mysql\data\ibtmp1' size is now 12 MB.
2023-10-26 21:45:53 0 [Note] InnoDB: Waiting for purge to start
2023-10-26 21:45:53 0 [Note] InnoDB: 10.4.28 started; log sequence number 266632383; transaction id 65753929
2023-10-26 21:45:53 0 [Note] Plugin 'FEEDBACK' is disabled.
2023-10-26 21:45:53 0 [Note] InnoDB: Loading buffer pool(s) from C:\Software\_Proggen\xampp-8.2.4\mysql\data\ib_buffer_pool
2023-10-26 21:45:53 0 [Note] InnoDB: Buffer pool(s) load completed at 231026 21:45:53
2023-10-26 21:45:53 0 [Note] Server socket created on IP: '::'.
=== 资源 #3 当前 mysql_error-我的措施后的日志 ===
2023-10-27 18:42:58 0 [Note] Starting MariaDB 10.4.28-MariaDB source revision c8f2e9a5c0ac5905f28b050b7df5a9ffd914b7e7 as process 16164
2023-10-27 18:42:58 0 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2023-10-27 18:42:58 0 [Note] InnoDB: Uses event mutexes
2023-10-27 18:42:58 0 [Note] InnoDB: Compressed tables use zlib 1.2.12
2023-10-27 18:42:58 0 [Note] InnoDB: Number of pools: 1
2023-10-27 18:42:58 0 [Note] InnoDB: Using SSE2 crc32 instructions
2023-10-27 18:42:58 0 [Note] InnoDB: Initializing buffer pool, total size = 16M, instances = 1, chunk size = 16M
2023-10-27 18:42:58 0 [Note] InnoDB: Completed initialization of buffer pool
2023-10-27 18:42:58 0 [Note] InnoDB: 128 out of 128 rollback segments are active.
2023-10-27 18:42:58 0 [Note] InnoDB: Creating shared tablespace for temporary tables
2023-10-27 18:42:58 0 [Note] InnoDB: Setting file 'C:\Software\_Proggen\xampp-8.2.4\mysql\data\ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
2023-10-27 18:42:58 0 [Note] InnoDB: File 'C:\Software\_Proggen\xampp-8.2.4\mysql\data\ibtmp1' size is now 12 MB.
2023-10-27 18:42:58 0 [Note] InnoDB: Waiting for purge to start
2023-10-27 18:42:58 0 [Note] InnoDB: 10.4.28 started; log sequence number 266632410; transaction id 65753929
2023-10-27 18:42:58 0 [Note] InnoDB: Loading buffer pool(s) from C:\Software\_Proggen\xampp-8.2.4\mysql\data\ib_buffer_pool
2023-10-27 18:42:58 0 [Note] Plugin 'FEEDBACK' is disabled.
2023-10-27 18:42:58 0 [Note] InnoDB: Buffer pool(s) load completed at 231027 18:42:58
2023-10-27 18:42:58 0 [Note] Server socket created on IP: '::'.
===资源#4正常mysql_error-问题发生前的日志===
自 2023 年 10 月 20 日以来，此功能完美运行
2023-03-18 19:48:19 19a4 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.
2023-03-18 19:48:19 6564 [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.
2023-03-18 19:48:19 6564 [Note] InnoDB: Using mutexes to ref count buffer pool pages
2023-03-18 19:48:19 6564 [Note] InnoDB: The InnoDB memory heap is disabled
2023-03-18 19:48:19 6564 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2023-03-18 19:48:19 6564 [Note] InnoDB: _mm_lfence() and _mm_sfence() are used for memory barrier
2023-03-18 19:48:19 6564 [Note] InnoDB: Compressed tables use zlib 1.2.3
2023-03-18 19:48:19 6564 [Note] InnoDB: Using generic crc32 instructions
2023-03-18 19:48:19 6564 [Note] InnoDB: Initializing buffer pool, size = 16.0M
2023-03-18 19:48:19 6564 [Note] InnoDB: Completed initialization of buffer pool
2023-03-18 19:48:19 6564 [Note] InnoDB: Highest supported file format is Barracuda.
2023-03-18 19:48:19 6564 [Note] InnoDB: 128 rollback segment(s) are active.
2023-03-18 19:48:19 6564 [Note] InnoDB: Waiting for purge to start
2023-03-18 19:48:19 6564 [Note] InnoDB: Percona XtraDB (http://www.percona.com) 5.6.36-82.2 started; log sequence number 200477146
2023-03-18 19:48:19 7788 [Note] InnoDB: Dumping buffer pool(s) not yet started
2023-03-18 19:48:19 6564 [Note] Plugin 'FEEDBACK' is disabled.
2023-03-18 19:48:19 6564 [Note] Server socket created on IP: '::'.
2023-03-18 19:48:19 6564 [Note] C:\software\xampp7.0.24\mysql\bin\mysqld.exe: ready for connections.
Version: '10.1.28-MariaDB' socket: '' port: 3306 mariadb.org binary distribution
2023-04-13 4:21:27 7904 [Note] C:\software\xampp7.0.24\mysql\bin\mysqld.exe: Normal shutdown
您无法从您拥有的 MariaDB 物理备份中获取 InnoDB 表 (ibd+frm) 文件并将其恢复到原始状态。与其他备份人员有着深厚的联系。
备份只能完全恢复或根本不恢复。
切勿删除 ib_logfile*，您将丢失数据。
对于仍然存在的已删除文件，手动
drop table zen_civ5.log_user因为
mysql.slave*mariadb-upgrade.exe