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

Mariabackup crash with InnoDB: Assertion failure in file /.../extra/mariabackup/xtrabackup.cc line 875

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Stalled (View Workflow)
    • Priority: Critical
    • Resolution: Unresolved
    • Affects Version/s: 10.2.32, 10.3.24, 10.4.14, 10.5.5
    • Fix Version/s: 10.2, 10.3, 10.4, 10.5
    • Component/s: Backup, Galera
    • Labels:
      None
    • Environment:
      RHEL 7.3

      Description

      [00] 2020-09-04 08:01:16 Executing FLUSH NO_WRITE_TO_BINLOG ENGINE LOGS...
      [00] 2020-09-04 08:01:16 The latest check point (for incremental): '5888524992656'
      mariabackup: Stopping log copying thread.[00] 2020-09-04 08:01:16 DDL tracking : rename 456015 "./reporting/mv_pl_opportunities.ibd","./reporting/#sql-ib456988.ibd"
      2020-09-04 08:01:16 0x7f062f7b0700  InnoDB: Assertion failure in file /home/jenkins/workspace/MariaDBE-Custom-RPM/label/rhel-7/padding_for_CPACK_RPM_BUILD_SOURCE_DIRS_PREFIX_ON_ES_BACKUP_DEBUGSOURCE/extra/mariabackup/xtrabackup.cc line 875
      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.
      200904  8:01:16 [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.2.32-7-MariaDB-enterprise
      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 = 5432 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)[0x55e7a193412e]
      mariabackup(handle_fatal_signal+0x30d)[0x55e7a143504d]
      sigaction.c:0(__restore_rt)[0x7f0635549630]
      :0(__GI_raise)[0x7f063381b377]
      :0(__GI_abort)[0x7f063381ca68]
      addr2line: 'mariabackup': No such file
      mariabackup(+0x458ba4)[0x55e7a1131ba4]
      mariabackup(+0x47a1f2)[0x55e7a11531f2]
      mariabackup(+0xa2ac88)[0x55e7a1703c88]
      mariabackup(+0xa2f5cf)[0x55e7a17085cf]
      mariabackup(+0xa2f98c)[0x55e7a170898c]
      mariabackup(+0x478725)[0x55e7a1151725]
      mariabackup(+0x4789fe)[0x55e7a11519fe]
      pthread_create.c:0(start_thread)[0x7f0635541ea5]
      /lib64/libc.so.6(clone+0x6d)[0x7f06338e38cd]
      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        0                    unlimited            bytes     
      Max resident set          unlimited            unlimited            bytes     
      Max processes             63450                63450                processes 
      Max open files            262144               262144               files     
      Max locked memory         65536                65536                bytes     
      Max address space         unlimited            unlimited            bytes     
      Max file locks            unlimited            unlimited            locks     
      Max pending signals       63450                63450                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: core
      

        Attachments

        1. backup.log
          71 kB
        2. populate.sh
          0.5 kB

          Issue Links

            Activity

              People

              Assignee:
              serg Sergei Golubchik
              Reporter:
              Coker Todd Coker
              Votes:
              5 Vote for this issue
              Watchers:
              8 Start watching this issue

                Dates

                Created:
                Updated: