mysql error

Problems with the Windows version of XAMPP, questions, comments, and anything related.

mysql error

Postby spid3r » 17. January 2023 11:39

I read similar post but i cant find solution so i post my logs

when i try to start mysql i got this error :

2023-01-17 11:24:18 0 [Note] mysqld.exe: Aria engine: starting recovery
recovered pages: 0%230117 11:24:18 [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.27-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 = 20302 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...
VCRUNTIME140.dll!memcpy()
mysqld.exe!parse_user()
mysqld.exe!parse_user()
mysqld.exe!parse_user()
mysqld.exe!parse_user()
mysqld.exe!parse_user()
mysqld.exe!parse_user()
mysqld.exe!parse_user()
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()
ucrtbase.dll!_crt_at_quick_exit()
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\mysql\data\
Minidump written to C:\xampp\mysql\data\mysqld.dmp

if i do the command mysqld --defaults-file=mysql\bin\my.ini --standalone --

i got this

# mysqld --defaults-file=mysql\bin\my.ini --standalone --console
2023-01-17 11:13:26 0 [Note] Using unique option prefix 'key_buffer' is error-prone and can break in the future. Please use the full name 'key_buffer_size' instead.
2023-01-17 11:13:26 0 [Note] mysqld (mysqld 10.4.27-MariaDB) starting as process 15160 ...
2023-01-17 11:13:26 0 [Note] mysqld: Aria engine: starting recovery
recovered pages: 0%230117 11:13:26 [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.27-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 = 20302 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...
VCRUNTIME140.dll!memcpy()
mysqld.exe!parse_user()
mysqld.exe!parse_user()
mysqld.exe!parse_user()
mysqld.exe!parse_user()
mysqld.exe!parse_user()
mysqld.exe!parse_user()
mysqld.exe!parse_user()
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\mysql\data\
Minidump written to C:\xampp\mysql\data\mysqld.dmp

Suggest? thanks in advance
spid3r
 
Posts: 2
Joined: 17. January 2023 11:21
XAMPP version: 82
Operating System: win 11

Re: mysql error

Postby spid3r » 18. January 2023 11:44

i find a temporary solution : remove aria_control_log file and restart mysql. :D
spid3r
 
Posts: 2
Joined: 17. January 2023 11:21
XAMPP version: 82
Operating System: win 11


Return to XAMPP for Windows

Who is online

Users browsing this forum: No registered users and 161 guests