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

mariabackup crashing 10.4.15

    XMLWordPrintable

Details

    • Bug
    • Status: Closed (View Workflow)
    • Critical
    • Resolution: Incomplete
    • 10.4.15
    • N/A
    • Backup
    • CentOS Linux release 8.1.1911 (Core)

    Description

      The mariabackup is crashing constantly everyday.

      2023-05-19 12:10:33 0x7f2aa0fbd700  InnoDB: Assertion failure in file /home/buildbot/buildbot/padding_for_CPACK_RPM_BUILD_SOURCE_DIRS_PREFIX/mariadb-10.4.15/extra/mariabackup/xtrabackup.cc line 660
      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.
      230519 12:10:33 [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.15-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 = 5933 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
      /bin/mariabackup(my_print_stacktrace+0x2e)[0x560ff405327e]
      /bin/mariabackup(handle_fatal_signal+0x54d)[0x560ff3bb5ced]
      sigaction.c:0(__restore_rt)[0x7f2aa5228dd0]
      :0(__GI_raise)[0x7f2aa32e799f]
      :0(__GI_abort)[0x7f2aa32d1cf5]
      /bin/mariabackup(+0x5cf739)[0x560ff382d739]
      /bin/mariabackup(+0x581c3f)[0x560ff37dfc3f]
      /bin/mariabackup(+0xb7b7b8)[0x560ff3dd97b8]
      /bin/mariabackup(+0xb7ecd6)[0x560ff3ddccd6]
      /bin/mariabackup(+0xb7eed4)[0x560ff3ddced4]
      /bin/mariabackup(+0x5fcc17)[0x560ff385ac17]
      /bin/mariabackup(+0x5fd000)[0x560ff385b000]
      pthread_create.c:0(start_thread)[0x7f2aa521e2de]
      :0(__GI___clone)[0x7f2aa33ac4b3]
      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
      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             755424               755424               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       755424               755424               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 %e
       
      /etc/script/daily_db_backup_2021.sh: line 40: 885093 Aborted                 (core dumped)
      

      the /usr/lib/systemd/systemd-coredump file has been attached as dbdump2.tar.gz

      Attachments

        Activity

          People

            Unassigned Unassigned
            shexphobos Xesh
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Git Integration

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