sudden signal 11 after shutdown

2023-05-11 14:00:57 0 [Note] /usr/sbin/mariadbd (initiated by: unknown): Normal shutdown

2023-05-11 14:00:57 1 [Note] Stopping ack receiver thread

2023-05-11 14:01:17 0 [Warning] /usr/sbin/mariadbd: Thread 118516 (user : 'xxxx') did not exit

2023-05-11 14:01:17 0 [Warning] /usr/sbin/mariadbd: Thread 118487 (user : 'xxxx') did not exit

230511 14:17:40 [ERROR] mysqld got signal 11 ;

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.9-5-MariaDB-enterprise-log

key_buffer_size=67108864

read_buffer_size=131072

max_used_connections=76

max_threads=3002

thread_count=2

It is possible that mysqld could use up to 

key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 6676289 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 0x40000

/usr/sbin/mariadbd(my_print_stacktrace+0x2e)[0x5625f1296cce]

/usr/sbin/mariadbd(handle_fatal_signal+0x485)[0x5625f0d31705]

sigaction.c:0(__restore_rt)[0x7ff52e896630]

:0(__select_nocancel)[0x7ff52dda0a33]

/usr/sbin/mariadbd(my_sleep+0x3f)[0x5625f12949ef]

/usr/sbin/mariadbd(_Z11mysqld_mainiPPc+0x187a)[0x5625f0a2a61a]

??:0(__libc_start_main)[0x7ff52dccd555]

/usr/sbin/mariadbd(+0x6f0f43)[0x5625f0a1df43]

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 /mariadb/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             1031060              1031060              processes 

Max open files            278528               278528               files     

Max locked memory         65536                65536                bytes     

Max address space         unlimited            unlimited            bytes     

Max file locks            unlimited            unlimited            locks     

Max pending signals       1031060              1031060              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-1160.80.1.el7.x86_64 (mockbuild@x86-vm-41.build.eng.bos.redhat.com) (gcc version 4.8.5 20150623 (Red Hat 4.8.5-44) (GCC) ) #1 SMP Sat Oct 8 18:13:21 UTC 2022

2023-05-11 14:19:13 0 [Note] InnoDB: Compressed tables use zlib 1.2.7