mySQL startet nicht mehr

[Stephan]

Hallo zusammen,

ich habe Ordersprinter eingerichtet und es lief bereits ohne Probleme.
Nun musste ich beim erneuten Starten im XAMPP v3.3.0 (Windows 10) feststellen, dass ich meine mySQL nicht mehr zum laufen bekomme.

Nach dem Start der mySQL über XAMPP bekomme ich folgende Fehlermeldung:

22:59:39 [Apache] Versuche Apache zu starten...
22:59:39 [Apache] Statusänderung erkannt: gestartet
22:59:40 [mysql] Versuche MySQL zu starten...
22:59:40 [mysql] Statusänderung erkannt: gestartet
22:59:42 [mysql] Statusänderung erkannt: gestoppt
22:59:42 [mysql] Fehler: MySQL wurde unerwartet beendet
22:59:42 [mysql] Ursache könnte ein geblockter Port, fehlende Abhängigkeiten,
22:59:42 [mysql] fehlende Berechtigungen, ein Absturz oder ein Abbruch einer anderen Methode sein.
22:59:42 [mysql] Drücke den Logs Button um error logs zu sehen und prüfe
22:59:42 [mysql] im Windows Event Viewer für weitere Hinweise
22:59:42 [mysql] Wenn du weitere Hilfe benötigst, kopiere den kompletten Inhalt des Log Fensters
22:59:42 [mysql] und füge ihn als Ergänzung in einem neuen Forum Eintrag hinzu.


In der Apache error.log-Datei habe ich folgende Einträge:

[Mon Jan 22 22:59:40.170058 2024] [ssl:warn] [pid 7384:tid 412] AH01909: www.example.com:443:0 server certificate does NOT include an ID which matches the server name
[Mon Jan 22 22:59:40.214139 2024] [core:warn] [pid 7384:tid 412] AH00098: pid file C:/xampp/apache/logs/httpd.pid overwritten -- Unclean shutdown of previous Apache run?
[Mon Jan 22 22:59:40.217369 2024] [ssl:warn] [pid 7384:tid 412] AH01909: www.example.com:443:0 server certificate does NOT include an ID which matches the server name
[Mon Jan 22 22:59:40.275171 2024] [mpm_winnt:notice] [pid 7384:tid 412] AH00455: Apache/2.4.56 (Win64) OpenSSL/1.1.1t PHP/8.2.4 configured -- resuming normal operations
[Mon Jan 22 22:59:40.275171 2024] [mpm_winnt:notice] [pid 7384:tid 412] AH00456: Apache Lounge VS16 Server built: Mar 7 2023 13:21:03
[Mon Jan 22 22:59:40.275171 2024] [core:notice] [pid 7384:tid 412] AH00094: Command line: 'c:\\xampp\\apache\\bin\\httpd.exe -d C:/xampp/apache'
[Mon Jan 22 22:59:40.280445 2024] [mpm_winnt:notice] [pid 7384:tid 412] AH00418: Parent: Created child process 3008
[Mon Jan 22 22:59:40.828730 2024] [ssl:warn] [pid 3008:tid 416] AH01909: www.example.com:443:0 server certificate does NOT include an ID which matches the server name
[Mon Jan 22 22:59:40.875125 2024] [ssl:warn] [pid 3008:tid 416] AH01909: www.example.com:443:0 server certificate does NOT include an ID which matches the server name
[Mon Jan 22 22:59:40.923242 2024] [mpm_winnt:notice] [pid 3008:tid 416] AH00354: Child: Starting 150 worker threads.

In der mySQL_error.log-Datei habe ich folgende Einträge:

2024-01-22 22:59:35 0 [Note] Starting MariaDB 10.4.28-MariaDB source revision c8f2e9a5c0ac5905f28b050b7df5a9ffd914b7e7 as process 7892
2024-01-22 22:59:35 0 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2024-01-22 22:59:35 0 [Note] InnoDB: Uses event mutexes
2024-01-22 22:59:35 0 [Note] InnoDB: Compressed tables use zlib 1.2.12
2024-01-22 22:59:35 0 [Note] InnoDB: Number of pools: 1
2024-01-22 22:59:35 0 [Note] InnoDB: Using SSE2 crc32 instructions
2024-01-22 22:59:35 0 [Note] InnoDB: Initializing buffer pool, total size = 128M, instances = 1, chunk size = 128M
2024-01-22 22:59:35 0 [Note] InnoDB: Completed initialization of buffer pool
2024-01-22 22:59:35 0 [Note] InnoDB: 128 out of 128 rollback segments are active.
2024-01-22 22:59:35 0 [Note] InnoDB: Creating shared tablespace for temporary tables
2024-01-22 22:59:35 0 [Note] InnoDB: Setting file '\xampp\mysql\data\ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
2024-01-22 22:59:35 0 [Note] InnoDB: File '\xampp\mysql\data\ibtmp1' size is now 12 MB.
2024-01-22 22:59:35 0 [Note] InnoDB: Waiting for purge to start
2024-01-22 22:59:35 1 [ERROR] InnoDB: Page [page id: space=2, page number=0] log sequence number 45018970 is in the future! Current system log sequence number 300459.
2024-01-22 22:59:35 1 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innod ... ery-modes/ for information about forcing recovery.
2024-01-22 22:59:35 1 [ERROR] InnoDB: Page [page id: space=2, page number=3] log sequence number 45018970 is in the future! Current system log sequence number 300459.
2024-01-22 22:59:35 1 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innod ... ery-modes/ for information about forcing recovery.
2024-01-22 22:59:35 1 [ERROR] InnoDB: Page [page id: space=2, page number=5] log sequence number 1912805 is in the future! Current system log sequence number 300459.
2024-01-22 22:59:35 1 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innod ... ery-modes/ for information about forcing recovery.
2024-01-22 22:59:35 1 [ERROR] InnoDB: Page [page id: space=1, page number=3] log sequence number 45125078 is in the future! Current system log sequence number 300459.
2024-01-22 22:59:35 1 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innod ... ery-modes/ for information about forcing recovery.
2024-01-22 22:59:35 1 [ERROR] InnoDB: Page [page id: space=2, page number=8] log sequence number 43834562 is in the future! Current system log sequence number 300459.
2024-01-22 22:59:35 1 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innod ... ery-modes/ for information about forcing recovery.
2024-01-22 22:59:35 3 [ERROR] InnoDB: Page [page id: space=2, page number=4] log sequence number 45019160 is in the future! Current system log sequence number 300459.
2024-01-22 22:59:35 3 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innod ... ery-modes/ for information about forcing recovery.
2024-01-22 22:59:35 0 [Note] InnoDB: 10.4.28 started; log sequence number 300450; transaction id 170
2024-01-22 22:59:35 0 [Note] InnoDB: Loading buffer pool(s) from C:\xampp\mysql\data\ib_buffer_pool
2024-01-22 22:59:35 0 [Note] Plugin 'FEEDBACK' is disabled.
2024-01-22 22:59:35 0 [ERROR] InnoDB: Page [page id: space=2, page number=2] log sequence number 45018941 is in the future! Current system log sequence number 300459.
2024-01-22 22:59:35 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innod ... ery-modes/ for information about forcing recovery.
2024-01-22 22:59:35 0 [Note] Server socket created on IP: '::'.
2024-01-22 22:59:40 0 [Note] Starting MariaDB 10.4.28-MariaDB source revision c8f2e9a5c0ac5905f28b050b7df5a9ffd914b7e7 as process 7672
2024-01-22 22:59:40 0 [Note] InnoDB: Mutexes and rw_locks use Windows interlocked functions
2024-01-22 22:59:40 0 [Note] InnoDB: Uses event mutexes
2024-01-22 22:59:40 0 [Note] InnoDB: Compressed tables use zlib 1.2.12
2024-01-22 22:59:40 0 [Note] InnoDB: Number of pools: 1
2024-01-22 22:59:40 0 [Note] InnoDB: Using SSE2 crc32 instructions
2024-01-22 22:59:40 0 [Note] InnoDB: Initializing buffer pool, total size = 128M, instances = 1, chunk size = 128M
2024-01-22 22:59:40 0 [Note] InnoDB: Completed initialization of buffer pool
2024-01-22 22:59:40 0 [Note] InnoDB: 128 out of 128 rollback segments are active.
2024-01-22 22:59:40 0 [Note] InnoDB: Creating shared tablespace for temporary tables
2024-01-22 22:59:40 0 [Note] InnoDB: Setting file '\xampp\mysql\data\ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
2024-01-22 22:59:40 0 [Note] InnoDB: File '\xampp\mysql\data\ibtmp1' size is now 12 MB.
2024-01-22 22:59:40 0 [Note] InnoDB: Waiting for purge to start
2024-01-22 22:59:40 2 [ERROR] InnoDB: Page [page id: space=2, page number=0] log sequence number 45018970 is in the future! Current system log sequence number 300468.
2024-01-22 22:59:40 2 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innod ... ery-modes/ for information about forcing recovery.
2024-01-22 22:59:40 2 [ERROR] InnoDB: Page [page id: space=2, page number=3] log sequence number 45018970 is in the future! Current system log sequence number 300468.
2024-01-22 22:59:40 2 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innod ... ery-modes/ for information about forcing recovery.
2024-01-22 22:59:40 1 [ERROR] InnoDB: Page [page id: space=2, page number=5] log sequence number 1912805 is in the future! Current system log sequence number 300468.
2024-01-22 22:59:40 1 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innod ... ery-modes/ for information about forcing recovery.
2024-01-22 22:59:40 1 [ERROR] InnoDB: Page [page id: space=1, page number=3] log sequence number 45125078 is in the future! Current system log sequence number 300468.
2024-01-22 22:59:40 1 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innod ... ery-modes/ for information about forcing recovery.
2024-01-22 22:59:40 1 [ERROR] InnoDB: Page [page id: space=2, page number=8] log sequence number 43834562 is in the future! Current system log sequence number 300468.
2024-01-22 22:59:40 1 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innod ... ery-modes/ for information about forcing recovery.
2024-01-22 22:59:40 1 [ERROR] InnoDB: Page [page id: space=2, page number=4] log sequence number 45019160 is in the future! Current system log sequence number 300468.
2024-01-22 22:59:40 1 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innod ... ery-modes/ for information about forcing recovery.
2024-01-22 22:59:40 0 [Note] InnoDB: 10.4.28 started; log sequence number 300459; transaction id 170
2024-01-22 22:59:40 0 [Note] InnoDB: Loading buffer pool(s) from C:\xampp\mysql\data\ib_buffer_pool
2024-01-22 22:59:40 0 [Note] Plugin 'FEEDBACK' is disabled.
2024-01-22 22:59:40 0 [ERROR] InnoDB: Page [page id: space=2, page number=2] log sequence number 45018941 is in the future! Current system log sequence number 300468.
2024-01-22 22:59:40 0 [ERROR] InnoDB: Your database may be corrupt or you may have copied the InnoDB tablespace but not the InnoDB log files. Please refer to https://mariadb.com/kb/en/library/innod ... ery-modes/ for information about forcing recovery.
2024-01-22 22:59:40 0 [Note] Server socket created on IP: '::'.

Ich kann aus den Error logfiles leider keine Rückschlüsse ziehen, was ich unternehmen muss um meine SQL wieder zum Laufen zu bekommen.
Ich wäre euch sehr dankbar, wenn ihr mich bei der Fehlersuche/Fehlerbehebung unterstützen könntet!

Vielen Dank schon mal im Voraus.

Viele Grüße

Stephan

[pichel]

Hallo Stephan,

hattest du die Machine mal hart ausgeschaltet, d.h. sie herunterzufahren?

Ich würde sagen, xampp einfach deinstallieren und neu installieren. Die php-Settinga machen und das letzte nächtliche Backup einspielen.

Gruß,

Stefan

[Stephan]

Hallo Stefan,

vielen Dank für die schnelle Hilfe.
Es könnte durchaus sein, dass das Laptop, ohne zuvor zu Beenden, heruntergefahren wurde.

Ich habe xampp deinstalliert, eine neue Datenbank erstellt und das Backup im Ordersprinter importiert.
Jetzt läuft alles wieder...

Viele Grüße

[pichel]

Hallo Stephan,

das freut mich. Ja, dieses Vorgehen ist auf jeden Fall viel schneller und auch zuverlässiger als eine kaputte Datenbank zu reparieren.

Gruß,

Stefan