Uploaded image for project: 'MariaDB Server'
  1. MariaDB Server
  2. MDEV-38945

Frequent Incremental MariaDB-backup failure - Segmentation fault

    XMLWordPrintable

Details

    • Bug
    • Status: Needs Feedback (View Workflow)
    • Major
    • Resolution: Unresolved
    • 10.11.15
    • 10.11
    • Backup
    • Oracle Linux Server 9.7

    Description

      Hi Support,

      Good day, We experience a frequent backup failure on one of our databases . In line with this we would like to request for your expertise on encountered error below.

      Occurs during incremental backup:

      [00] 2026-03-03 04:36:45 Compressing and streaming ./centreon/host.ibd
      [00] 2026-03-03 04:36:45         ...done
      [00] 2026-03-03 04:36:45 Start copying aria log file tail: /local/mysql//aria_log.00000001
      [00] 2026-03-03 04:36:45 Stop copying aria log file tail: /local/mysql//aria_log.00000001, copied 0 bytes
      260303  4:36:45 [ERROR] /bin/mariabackup got signal 11 ;
      Sorry, we probably made a mistake, and this is a bug.
       
      Your assistance in bug reporting will enable us to fix this for the next release.
      To report this bug, see https://mariadb.com/kb/en/reporting-bugs about how to report
      a bug on https://jira.mariadb.org/.
       
      Please include the information from the server start above, to the end of the
      information below.
       
      Server version: 10.11.15-MariaDB source revision: cb0d6dd835023a7162ace471cd047161f205dd58
       
      The information page at https://mariadb.com/kb/en/how-to-produce-a-full-stack-trace-for-mariadbd/
      contains instructions to obtain a better version of the backtrace below.
      Following these instructions will help MariaDB developers provide a fix quicker.
       
      Attempting backtrace. Include this in the bug report.
      (note: Retrieving this information may fail)
       
      Thread pointer: 0x0
      stack_bottom = 0x0 thread_stack 0x49000
      /bin/mariabackup(my_print_stacktrace+0x2e)[0x55ac26a89c8e]
      /bin/mariabackup(handle_fatal_signal+0x305)[0x55ac26590f55]
      /lib64/libc.so.6(+0x3fc30)[0x7fd23c03fc30]
      Writing a core file...
      Working directory at /local/mysql
      Resource Limits (excludes unlimited resources):
      Limit                     Soft Limit           Hard Limit           Units
      Max stack size            8388608              unlimited            bytes
      Max processes             94144                94144                processes
      Max open files            32000                32000                files
      Max locked memory         8388608              8388608              bytes
      Max pending signals       94144                94144                signals
      Max msgqueue size         819200               819200               bytes
      Max nice priority         0                    0
      Max realtime priority     0                    0
      Core pattern: |/usr/lib/systemd/systemd-coredump %P %u %g %s %t %c %h %d %F
       
      Kernel version: Linux version 5.14.0-611.13.1.el9_7.x86_64 (mockbuild@host-100-100-224-76) (gcc (GCC) 11.5.0 20240719 (Red Hat             11.5.0-11.0.1), GNU ld version 2.35.2-67.0.1.el9) #1 SMP PREEMPT_DYNAMIC Tue Dec 9 01:44:24 PST 2025
       
      mysql_backup_xtra.sh: line 32: 3474451 Segmentation fault      (core dumped) /bin/mariabackup --backup --user=*****--password=******--port=3306 --innodb-log-buffer-size=2G --parallel=4 --stream=xbstream --compress --tar            get-dir $backup_loc/$ext/$bhour --incremental-basedir=$backup_loc/full/00 > $backup_loc/$ext/$bhour/$host"_"`date +%F"_"%H%M`$            ext.xbstream
      
      

      Attachments

        Activity

          People

            Unassigned Unassigned
            bulanm bulan
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:

              Git Integration

                Error rendering 'com.xiplink.jira.git.jira_git_plugin:git-issue-webpanel'. Please contact your Jira administrators.