mariabackup gives core dump

Linux, Fedora 64, up to date. /data/docs/2022/power 16:27 > mariabackup --backup --user=admini --password=opJaifyefEl7 --target-dir=/run/media/dpawson/sibc/dbbackup [00] 2022-08-24 16:30:10 Connecting to MySQL server host: localhost, user: admini, password: set, port: not set, socket: not set [00] 2022-08-24 16:30:10 Using server version 10.5.16-MariaDB mariabackup based on MariaDB server 10.5.16-MariaDB Linux (x86_64) [00] 2022-08-24 16:30:10 uses posix_fadvise(). [00] 2022-08-24 16:30:10 cd to /var/lib/mysql/ [00] 2022-08-24 16:30:10 open files limit requested 0, set to 1024 [00] 2022-08-24 16:30:10 mariabackup: using the following InnoDB configuration: [00] 2022-08-24 16:30:10 innodb_data_home_dir = [00] 2022-08-24 16:30:10 innodb_data_file_path = ibdata1:12M:autoextend [00] 2022-08-24 16:30:10 innodb_log_group_home_dir = ./ [00] 2022-08-24 16:30:10 InnoDB: Using Linux native AIO 2022-08-24 16:30:10 0 [Note] InnoDB: Number of pools: 1 2022-08-24 16:30:10 0 [Warning] InnoDB: Unable to open "./ib_logfile0" to check native AIO read support. 2022-08-24 16:30:10 0 [Warning] InnoDB: Linux Native AIO disabled. 2022-08-24 16:30:10 0 [ERROR] InnoDB: Operating system error number 13 in a file operation. 2022-08-24 16:30:10 0 [ERROR] InnoDB: The error means mysqld does not have the access rights to the directory. 2022-08-24 16:30:10 0 [ERROR] [FATAL] InnoDB: open(./ib_logfile0) returned Generic error 220824 16:30:10 [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.5.16-MariaDB 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 = 6049 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 Printing to addr2line failed mariabackup(my_print_stacktrace+0x3f)[0x557bfadea87f] mariabackup(handle_fatal_signal+0x489)[0x557bfa9c2999] ??:0(restore_rt)[0x7f06d9f24a70] ??:0(pthread_kill_implementation)[0x7f06d9f74c4c] :0(GI_raise)[0x7f06d9f249c6] :0(GI_abort)[0x7f06d9f0e7f4] addr2line: 'mariabackup': No such file mariabackup(+0x5b7dfa)[0x557bfa549dfa] mariabackup(+0x5c8877)[0x557bfa55a877] mariabackup(+0x62a0db)[0x557bfa5bc0db] mariabackup(main+0x169)[0x557bfa55f509] ??:0(libc_start_call_main)[0x7f06d9f0f550] :0(libc_start_main_alias_2)[0x7f06d9f0f609] addr2line: 'mariabackup': No such file mariabackup(_start+0x25)[0x557bfa598d05] 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