Dec 29 16:19:42 database44 mysqld: 211229 16:19:42 [ERROR] mysqld got signal 11 ;

Dec 29 16:19:42 database44 mysqld: This could be because you hit a bug. It is also possible that this binary

Dec 29 16:19:42 database44 mysqld: or one of the libraries it was linked against is corrupt, improperly built,

Dec 29 16:19:42 database44 mysqld: or misconfigured. This error can also be caused by malfunctioning hardware.

Dec 29 16:19:42 database44 mysqld: To report this bug, see https://mariadb.com/kb/en/reporting-bugs

Dec 29 16:19:42 database44 mysqld: We will try our best to scrape up some info that will hopefully help

Dec 29 16:19:42 database44 mysqld: diagnose the problem, but since we have already crashed,

Dec 29 16:19:42 database44 mysqld: something is definitely wrong and this may fail.

Dec 29 16:19:42 database44 mysqld: Server version: 10.4.22-MariaDB-log

Dec 29 16:19:42 database44 mysqld: key_buffer_size=134217728

Dec 29 16:19:42 database44 mysqld: read_buffer_size=131072

Dec 29 16:19:42 database44 mysqld: max_used_connections=95

Dec 29 16:19:42 database44 mysqld: max_threads=2002

Dec 29 16:19:42 database44 mysqld: thread_count=54

Dec 29 16:19:42 database44 mysqld: It is possible that mysqld could use up to

Dec 29 16:19:42 database44 mysqld: key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 4537042 K  bytes of memory

Dec 29 16:19:42 database44 mysqld: Hope that's ok; if not, decrease some variables in the equation.

Dec 29 16:19:42 database44 mysqld: Thread pointer: 0x7f87280008c8

Dec 29 16:19:42 database44 mysqld: Attempting backtrace. You can use the following information to find out

Dec 29 16:19:42 database44 mysqld: where mysqld died. If you see no messages after this, something went

Dec 29 16:19:42 database44 mysqld: terribly wrong...