Fehler: MySQL wurde unerwartet beendet

Irgendwelche Probleme mit XAMPP für Windows? Dann ist hier genau der richtige Ort um nachzufragen.

Fehler: MySQL wurde unerwartet beendet

Postby Jori » 10. March 2021 17:35

Guten Abend.
Ich weiß das es schon den einen oder anderen Beitrag darüber gibt, jedoch finde ich keine Lösung für mein Problem das mein MySQL Server nicht mehr starten möchte.
Geändert habe ich nichts und von heut auf morgen lässt der Server sich nicht mehr starten. Die Ports hab ich auch schon versucht zu ändern, ohne Erfolg. Bin von der XAMPP Version 7.4.12 auf 7.4.15 um gestiegen, der Fehler kommt immer wieder.
Hier im Detail:

Fehleranzeige in der Console:
Code: Select all
17:22:13  [mysql]    Fehler: MySQL wurde unerwartet beendet
17:22:13  [mysql]    Ursache könnte ein geblockter Port, fehlende Abhängigkeiten,
17:22:13  [mysql]    fehlende Berechtigungen, ein Absturz oder ein Abbruch einer anderen Methode sein.
17:22:13  [mysql]    Drücke den Logs Button um error logs zu sehen und prüfe
17:22:13  [mysql]    im Windows Event Viewer für weitere Hinweise
17:22:13  [mysql]    Wenn du weitere Hilfe benötigst, kopiere den kompletten Inhalt des Log Fensters
17:22:13  [mysql]    und füge ihn als Ergänzung in einem neuen Forum Eintrag hinzu.


Fehlerausgabe in der mysql_error.log Datei:

Code: Select all
2021-03-10 17:19:00 0 [ERROR] mysqld.exe: File 'C:\xampp_7_4_15\mysql\data\aria_log.00000001' not found (Errcode: 2 "No such file or directory")
2021-03-10 17:19:00 0 [ERROR] mysqld.exe: Aria engine: log initialization failed
210310 17:19:00 [ERROR] mysqld got exception 0xc0000005 ;
This could be because you hit a bug. It is also possible that this binary
or one of the libraries it was linked against is corrupt, improperly built,
or misconfigured. This error can also be caused by malfunctioning hardware.

To report this bug, see https://mariadb.com/kb/en/reporting-bugs

We will try our best to scrape up some info that will hopefully help
diagnose the problem, but since we have already crashed,
something is definitely wrong and this may fail.

Server version: 10.4.17-MariaDB
key_buffer_size=16777216
read_buffer_size=262144
max_used_connections=0
max_threads=65537
thread_count=0
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 20290 K  bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x0
Attempting backtrace. You can use the following information to find out
where mysqld died. If you see no messages after this, something went
terribly wrong...
mysqld.exe!strmov()
mysqld.exe!strmov()
mysqld.exe!strmov()
mysqld.exe!strmov()
mysqld.exe!?ha_initialize_handlerton@@YAHPEAUst_plugin_int@@@Z()
mysqld.exe!?plugin_init@@YAHPEAHPEAPEADH@Z()
mysqld.exe!?plugin_init@@YAHPEAHPEAPEADH@Z()
mysqld.exe!?init_net_server_extension@@YAXPEAVTHD@@@Z()
mysqld.exe!?win_main@@YAHHPEAPEAD@Z()
mysqld.exe!?mysql_service@@YAXPEAX@Z()
mysqld.exe!?mysqld_main@@YAHHPEAPEAD@Z()
mysqld.exe!strxnmov()
KERNEL32.DLL!BaseThreadInitThunk()
ntdll.dll!RtlUserThreadStart()
The manual page at https://mariadb.com/kb/en/how-to-produce-a-full-stack-trace-for-mysqld/ contains
information that should help you find out what is causing the crash.
Writing a core file at C:\xampp_7_4_15\mysql\data\
Minidump written to C:\xampp_7_4_15\mysql\data\mysqld.dmp
2021-03-10 17:21:40 0 [ERROR] mysqld.exe: File 'C:\xampp_7_4_15\mysql\data\aria_log.00000001' not found (Errcode: 2 "No such file or directory")
2021-03-10 17:21:40 0 [ERROR] mysqld.exe: Aria engine: log initialization failed
210310 17:21:40 [ERROR] mysqld got exception 0xc0000005 ;
This could be because you hit a bug. It is also possible that this binary
or one of the libraries it was linked against is corrupt, improperly built,
or misconfigured. This error can also be caused by malfunctioning hardware.

To report this bug, see https://mariadb.com/kb/en/reporting-bugs

We will try our best to scrape up some info that will hopefully help
diagnose the problem, but since we have already crashed,
something is definitely wrong and this may fail.

Server version: 10.4.17-MariaDB
key_buffer_size=16777216
read_buffer_size=262144
max_used_connections=0
max_threads=65537
thread_count=0
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 20290 K  bytes of memory
Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x0
Attempting backtrace. You can use the following information to find out
where mysqld died. If you see no messages after this, something went
terribly wrong...
mysqld.exe!strmov()
mysqld.exe!strmov()
mysqld.exe!strmov()
mysqld.exe!strmov()
mysqld.exe!?ha_initialize_handlerton@@YAHPEAUst_plugin_int@@@Z()
mysqld.exe!?plugin_init@@YAHPEAHPEAPEADH@Z()
mysqld.exe!?plugin_init@@YAHPEAHPEAPEADH@Z()
mysqld.exe!?init_net_server_extension@@YAXPEAVTHD@@@Z()
mysqld.exe!?win_main@@YAHHPEAPEAD@Z()
mysqld.exe!?mysql_service@@YAXPEAX@Z()
mysqld.exe!?mysqld_main@@YAHHPEAPEAD@Z()
mysqld.exe!strxnmov()
KERNEL32.DLL!BaseThreadInitThunk()
ntdll.dll!RtlUserThreadStart()
The manual page at https://mariadb.com/kb/en/how-to-produce-a-full-stack-trace-for-mysqld/ contains
information that should help you find out what is causing the crash.
Writing a core file at C:\xampp_7_4_15\mysql\data\
Minidump written to C:\xampp_7_4_15\mysql\data\mysqld.dmp


Ich hoffe um Hilfe.
LG Jori
Jori
 
Posts: 1
Joined: 10. March 2021 17:23
XAMPP version: c3.2.4
Operating System: Win 10 64 Bit

Return to XAMPP für Windows

Who is online

Users browsing this forum: No registered users and 30 guests