Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Duplicate
-
10.11.10
-
redhat enterprise linux 7.9
-
Can result in hang or crash
Description
Signal 6 occurred in MariaDB 10.11.10.
A coredump has been created and uploads the content as well.
It happened on the Slave server, and after signal 6 occurred, I restarted mariadbd in mysqld-safe, and now it's synchronizing normally.
2025-06-14 8:23:24 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/
|
250614 8:23:24 [ERROR] mysqld got signal 6 ;
|
Sorry, we probably made a mistake, and this is a bug.
|
|
|
Your assistance in bug reporting will enable us to fix this for the next release.
|
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.11.10-MariaDB-log source revision: 3d0fb150289716ca75cd64d62823cf715ee47646
|
key_buffer_size=8388608
|
read_buffer_size=2097152
|
max_used_connections=1699
|
max_threads=4002
|
thread_count=617
|
It is possible that mysqld could use up to
|
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 16507410 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...
|
stack_bottom = 0x0 thread_stack 0x49000
|
Can't start addr2line
|
/engn001/mysql/bin/mariadbd(my_print_stacktrace+0x2e)[0x55b10ebe01be]
|
/engn001/mysql/bin/mariadbd(handle_fatal_signal+0x307)[0x55b10e61dbc7]
|
/lib64/libpthread.so.0(+0xf630)[0x7ff351057630]
|
/lib64/libc.so.6(gsignal+0x37)[0x7ff35028d377]
|
/lib64/libc.so.6(abort+0x148)[0x7ff35028ea68]
|
2025-06-14 8:23:25 0 [Note] /engn001/mysql/bin/mariadbd (initiated by: unknown): Normal shutdown
|
/engn001/mysql/bin/mariadbd(+0xf0d150)[0x55b10ea6d150]
|
2025-06-14 8:23:25 0 [Note] Event Scheduler: Killing the scheduler thread, thread id 3
|
2025-06-14 8:23:25 0 [Note] Event Scheduler: Waiting for the scheduler thread to reply
|
2025-06-14 8:23:25 0 [Note] Event Scheduler: Stopped
|
/engn001/mysql/bin/mariadbd(+0xec083b)[0x55b10ea2083b]
|
/engn001/mysql/bin/mariadbd(_ZN5tpool19thread_pool_generic13timer_generic7executeEPv+0x40)[0x55b10eb6bc20]
|
/engn001/mysql/bin/mariadbd(_ZN5tpool4task7executeEv+0x2b)[0x55b10eb6cc1b]
|
/engn001/mysql/bin/mariadbd(_ZN5tpool19thread_pool_generic11worker_mainEPNS_11worker_dataE+0x69)[0x55b10eb69f99]
|
/lib64/libstdc++.so.6(+0xb5070)[0x7ff350bf2070]
|
/lib64/libpthread.so.0(+0x7ea5)[0x7ff35104fea5]
|
/lib64/libc.so.6(clone+0x6d)[0x7ff3503558cd]
|
The manual page at https://mariadb.com/kb/en/how-to-produce-a-full-stack-trace-for-mariadbd/ contains
|
information that should help you find out what is causing the crash.
|
Writing a core file...
|
Working directory at /data001/DATA
|
Resource Limits:
|
Limit Soft Limit Hard Limit Units
|
Max cpu time unlimited unlimited seconds
|
Max file size unlimited unlimited bytes
|
Max data size unlimited unlimited bytes
|
Max stack size 8388608 unlimited bytes
|
Max core file size unlimited unlimited bytes
|
Max resident set unlimited unlimited bytes
|
Max processes 65535 65535 processes
|
Max open files 65535 65535 files
|
Max locked memory 65536 65536 bytes
|
Max address space unlimited unlimited bytes
|
Max file locks unlimited unlimited locks
|
Max pending signals 514890 514890 signals
|
Max msgqueue size 819200 819200 bytes
|
Max nice priority 0 0
|
Max realtime priority 0 0
|
Max realtime timeout unlimited unlimited us
|
Core pattern: core
|
|
|
Kernel version: Linux version 3.10.0-1062.el7.x86_64 (mockbuild@x86-040.build.eng.bos.redhat.com) (gcc version 4.8.5 20150623 (Red Hat 4.8.5-39) (GCC) ) #1 SMP Thu Jul 18 20:25:13 UTC 2019
|
Attachments
Issue Links
- duplicates
-
MDEV-35424 False alarm/crash: innodb_fatal_semaphore_wait_threshold was exceeded for dict_sys.latch
-
- Needs Feedback
-