自2023年10月20日起，我的xampp安装中的mysql示例（8.2.4）不再启动。它尝试了几秒钟，但崩溃了，并显示了一个没有意义的文本（你会发现它下面，德国）.我没有做任何改变我的系统几乎2周前，到这个日期和现在.没有与操作系统，没有新的软件，没有编程，.没有什么可能导致这个问题.在这段时间内，我几乎只玩了一些游戏，并使用我的浏览器.
当然，我想看到的错误日志，这样做，我想使用简单的方法与按钮在xampp控制面板，这并没有工作。一条消息提示说，它找不到日志文件。在这之上，有更多的消息与奇怪的切割路径。这个问题（通过xampp按钮打开mysql-error-log）是我自己解决的，通过删除安装路径中的空格，这是xampp建议的。这是疯狂的，我的安装是为yaears这样工作（与空格），突然它造成的问题。没关系。
现在访问mysql-error-log（你会在下面找到它）我看到几个条目指出，ibd文件丢失.我恢复theese从旧备份，但definetely没有改变任何关于theese文件或相关数据库.再次，这是奇怪的，这是突然一个问题，当它以前工作（没有恢复theese文件）.也许Windows-Defender有影响？我检查-不，它没有.我没有使用任何其他防病毒软件.
如果没有这些ibd-missing-errors，当前的mysql-error-log和问题之前的旧的mysql-error-log看起来几乎是一样的。比较这些会导致这样的事实，它在“Server socket created on IP：'：：'."行之后崩溃。在这行之后的旧工作日志中，mysqld.exe将成功启动。目前情况不再是这样，我不知道为什么。
你们有什么主意吗？能帮帮我吗？
我试过：
由于xampp-Control-Panel中的文本建议我使用Admin-Rights并删除installation-path中的空格（当我想打开错误日志时），我确实这样做了。

• xampp-在没有空格的路径中重复安装
• xampp-使用管理员安装-已启动权限

这在以前是不必要的，它解决的唯一两件事是：a）通过控制面板访问错误日志，b）控制面板中不再提示此主题。
我从备份恢复13.06.2023

• slave_master_info.ibd & .frm
• slave_relay_log_info.ibd & .frm
• slave_worker_info.ibd & .frm

这样，mysql-error-log中的相关错误就消失了。
有多个“zen_civ5”-表，其中ibd文件也丢失. These是非常旧的表，我删除（DROP）超过1-2年前.再次，这是奇怪的，系统坚持在theese表.好吧，为了解决这个问题，我从一个非常旧的备份导入theese表（2019），这有助于删除日志中的相关错误.
在这一点上，日志没有帮助我任何进一步，因为最后一行是“服务器套接字创建在IP：'：：'."。所以我采取了一个蓝色的镜头，并寻找端口3306。也许另一个程序决定使用它？我用'netstat -aon|在控制台中找到“3306”'，没有任何结果。所以端口是免费使用的。（3306是正确的，因为它在控制面板中可见，并且在mysql的my.ini中。）
我也试着把端口号改为3307，并删除xampp/mysql/data中的ibdata 1，ib_logfile0，ib_logfile1，ib_logfile101，就像在网上的许多其他问题中建议的那样（在my.ini中把它从mysql中修改，在php.ini中把它从php中修改）。
我还下载了两个新的xampp-Installations（普通的和便携式的），并快速设置（纠正路径）。两者都可以正常运行Apache，但都有同样的mysql问题。所以几乎可以肯定的是，这与我的安装无关。它必须与我的系统有关。或者你怎么想？
=来自xampp控制面板的请求#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-Log when the problem occurred =

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-Log后我的措施=

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-Log之前的问题发生=
自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

型