[#MDEV-31471] mysqld got signal 11 while Maria backup

While doing the mariabackup on Mariadb 10.4.24, we get an below error message and due to this we are not able to take the backup. Can you pls look into this and update me on same.

[00] 2023-06-12 07:10:29 Finished backing up non-InnoDB tables and files

230612  7:10:29 [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.4.30-MariaDB source revision: 928012a27ae2d1549f1b3e6975b9d22652bbea3a

key_buffer_size=0

read_buffer_size=131072

max_used_connections=0

max_threads=1

thread_count=0

It is possible that mysqld could use up to

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

addr2line: 'mariabackup': No such file

mariabackup(my_print_stacktrace+0x2e)[0x55f8c476c57e]

mariabackup(handle_fatal_signal+0x317)[0x55f8c4226657]

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

/lib64/libc.so.6(+0xc0f10)[0x7fc93ee4df10]

addr2line: 'mariabackup': No such file

mariabackup(+0x6428c8)[0x55f8c3eeb8c8]

mariabackup(_Z12backup_startP7ds_ctxtS0_R14CorruptedPages+0x10d)[0x55f8c3eefb1d]

mariabackup(+0x62d9a9)[0x55f8c3ed69a9]

mariabackup(main+0x18c)[0x55f8c3e9146c]

/lib64/libc.so.6(__libc_start_main+0xf5)[0x7fc93edaf555]

addr2line: 'mariabackup': No such file

mariabackup(+0x61dfc4)[0x55f8c3ec6fc4]

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 /data/mariadb

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        0                    unlimited            bytes

Max resident set          unlimited            unlimited            bytes

Max processes             63096                63096                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       63096                63096                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/libexec/abrt-hook-ccpp %s %c %p %u %g %t e %P %I %h

[MDEV-31471] mysqld got signal 11 while Maria backup Created: 2023-06-13 Updated: 2023-10-09 Resolved: 2023-07-28
Status:	Closed
Project:	MariaDB Server
Component/s:	None
Affects Version/s:	10.4.30
Fix Version/s:	N/A

[MDEV-31471] mysqld got signal 11 while Maria backup Created: 2023-06-13 Updated: 2023-10-09 Resolved: 2023-07-28