2024-01-18  0:42:02 6415776 [Warning] Aborted connection 6415776 to db: 'unconnected' user: 'gtid' host: '10.76.25.17' (Got an error writing communication packets)
2024-01-18  0:52:56 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/
240118  0:52:56 [ERROR] mysqld got signal 6 ;
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.11.5-MariaDB-log source revision: 7875294b6b74b53dd3aaa723e6cc103d2bb47b2c
key_buffer_size=67108864
read_buffer_size=131072
max_used_connections=648
max_threads=802
thread_count=60
It is possible that mysqld could use up to
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 1831964 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
/usr/sbin/mariadbd(my_print_stacktrace+0x2e)[0x555f8aba612e]
/usr/sbin/mariadbd(handle_fatal_signal+0x485)[0x555f8a69f5b5]
/lib64/libpthread.so.0(+0x12cf0)[0x7f4156b47cf0]
/lib64/libc.so.6(gsignal+0x10f)[0x7f4155ea3acf]
/lib64/libc.so.6(abort+0x127)[0x7f4155e76ea5]
/usr/sbin/mariadbd(+0x690f45)[0x555f8a2f4f45]
/usr/sbin/mariadbd(+0x688c88)[0x555f8a2ecc88]
/usr/sbin/mariadbd(_ZN5tpool19thread_pool_generic13timer_generic7executeEPv+0x38)[0x555f8ab3a698]
/usr/sbin/mariadbd(_ZN5tpool4task7executeEv+0x2b)[0x555f8ab3b3bb]
/usr/sbin/mariadbd(_ZN5tpool19thread_pool_generic11worker_mainEPNS_11worker_dataE+0x4f)[0x555f8ab38eff]
/lib64/libstdc++.so.6(+0xc2b13)[0x7f415665eb13]
/lib64/libpthread.so.0(+0x81ca)[0x7f4156b3d1ca]
/lib64/libc.so.6(clone+0x43)[0x7f4155e8ee73]
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...
Working directory at /var/lib/mysql
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             2013326              2013326              processes
Max open files            32768                32768                files
Max locked memory         65536                65536                bytes
Max address space         unlimited            unlimited            bytes
Max file locks            unlimited            unlimited            locks
Max pending signals       2013326              2013326              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: |/usr/lib/systemd/systemd-coredump %P %u %g %s %t %c %h %e

Kernel version: Linux version 4.18.0-477.15.1.el8_8.x86_64 (mockbuild@x86-64-02.build.eng.rdu2.redhat.com) (gcc version 8.5.0 20210514 (Red Hat 8.5.0-18) (GCC)) #1 SMP Fri Jun 2 08:27:19 EDT 2023