Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Incomplete
-
10.6.12
-
None
-
Microsoft Windows Server 2016 Standard
Description
The MariaDB server has been crashed with the following error after server is up for around 6 days.
2023-07-20 16:54:05 0 [Note] InnoDB: Buffer pool(s) load completed at 230720 16:54:05
2023-07-26 19:11:13 0 [ERROR] [FATAL] InnoDB: innodb_fatal_semaphore_wait_threshold was exceeded for dict_sys.latch. Please refer to https://mariadb.com/kb/en/how-to-produce-a-full-stack-trace-for-mysqld/
230726 19:11:13 [ERROR] mysqld got exception 0x80000003 ;
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.6.12-MariaDB-log source revision: 4c79e15cc3716f69c044d4287ad2160da8101cdc
key_buffer_size=33554432
read_buffer_size=8388608
max_used_connections=94
max_threads=65537
thread_count=94
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 1073794283 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...
server.dll!my_parameter_handler()
ucrtbase.dll!raise()
ucrtbase.dll!abort()
server.dll!json_valid()
server.dll!json_valid()
server.dll!json_valid()
ntdll.dll!RtlGetAce()
ntdll.dll!RtlReleaseSRWLockExclusive()
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:\Program Files\Trellix\IPS Manager\MariaDB\data\
Minidump written to C:\Program Files\Trellix\IPS Manager\MariaDB\data\mariadbd.dmp
Eagerly waiting a reply for the reason for this crash.
Also noticed that a similar issue https://jira.mariadb.org/browse/MDEV-29660 has been created. Whether the above crash is related to this one?
Attachments
Issue Links
- duplicates
-
MDEV-29835 Partial server freeze
- Closed