[00] 2020-09-03 07:41:07 DDL tracking : rename 3608442 "./beta/z_392.ibd","./beta/#sql-ib3608457.ibd" 2020-09-03 07:41:07 0x7f18a3c9f700 InnoDB: Assertion failure in file /home/buildbot/buildbot/padding_for_CPACK_RPM_BUILD_SOURCE_DIRS_PREFIX/mariadb-10.4.13/extra/mariabackup/xtrabackup.cc line 664 InnoDB: Failing assertion: opt_no_lock InnoDB: We intentionally generate a memory trap. InnoDB: Submit a detailed bug report to https://jira.mariadb.org/ InnoDB: If you get repeated assertion failures or crashes, even InnoDB: immediately after the mysqld startup, there may be InnoDB: corruption in the InnoDB tablespace. Please refer to InnoDB: https://mariadb.com/kb/en/library/innodb-recovery-modes/ InnoDB: about forcing recovery. [00] 2020-09-03 07:41:07 ...done [00] 2020-09-03 07:41:07 Copying ./beta/z_241.ibd to /mnt/backup/dbbackup_daily/20200903/beta/z_241.new 200903 7:41:07 [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.4.13-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 = 5932 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... [00] 2020-09-03 07:41:07 ...done [00] 2020-09-03 07:41:07 Copying ./beta/z_242.ibd to /mnt/backup/dbbackup_daily/20200903/beta/z_242.new stack_bottom = 0x0 thread_stack 0x49000 /bin/mariabackup(my_print_stacktrace+0x2e)[0x55b3b9a4e18e] /bin/mariabackup(handle_fatal_signal+0x54d)[0x55b3b95b0b6d] sigaction.c:0(__restore_rt)[0x7f18a7f03dd0] :0(__GI_raise)[0x7f18a5fc999f] :0(__GI_abort)[0x7f18a5fb3cf5] /bin/mariabackup(+0x5c523d)[0x55b3b922d23d] /bin/mariabackup(+0x577f0f)[0x55b3b91dff0f] /bin/mariabackup(+0xb6ba71)[0x55b3b97d3a71] /bin/mariabackup(+0xb6ef86)[0x55b3b97d6f86] /bin/mariabackup(+0xb6f187)[0x55b3b97d7187] /bin/mariabackup(+0x5f1f47)[0x55b3b9259f47] /bin/mariabackup(+0x5f2340)[0x55b3b925a340] pthread_create.c:0(start_thread)[0x7f18a7ef92de] :0(__GI___clone)[0x7f18a608e4b3] The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html 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 376958 376958 processes Max open files 16384 16384 files Max locked memory 16777216 16777216 bytes Max address space unlimited unlimited bytes Max file locks unlimited unlimited locks Max pending signals 376958 376958 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 ... /etc/script/daily_db_backup_new.sh: line 26: 433785 Aborted (core dumped) /bin/mariabackup --defaults-file=/etc/mariabackup.cnf --backup --target-dir=/mnt/backup/dbbackup_daily/"$BACKUP_DAY"/