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

Got an InnoDB: Assertion failure in file /home/buildbot/buildbot/build/mariadb-10.3.36/extra/mariabackup/xtrabackup.cc line 6045 when try to launch mariabackup --backup




      Hi, when I try to run the mariabackup --backup command I got the error in my terminal:

      command is sudo mariabackup --backup --target-dir = /123cluster/mariadb/backups/ --user = root --password = password

      And terminal output is:

      2022-10-24 10:09:05 0x7f882655c7c0 InnoDB: Assertion failure in file /home/buildbot/buildbot/build/mariadb-10.3.36/extra/mariabackup/xtrabackup.cc line 6045
      InnoDB: Failing assertion: appended
      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.
      221024 10:09:05 [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.3.36-MariaDB-1:10.3.36+maria~ubu1804
      It is possible that mysqld could use up to
      key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 5604 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
      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 /123cluster/mariadb/ubuntu_master
      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 256207 256207 processes
      Max open files 1024 1048576 files
      Max locked memory 16777216 16777216 bytes
      Max address space unlimited unlimited bytes
      Max file locks unlimited unlimited locks
      Max pending signals 256207 256207 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

      Kernel version: Linux version 5.3.18-3-pve (build@pve) (gcc version 8.3.0 (Debian 8.3.0-6)) #1 SMP PVE 5.3.18-3 (Tue, 17 Mar 2020 16:33:19 +0100)


      How can I fix this error? Thanks for your help.




            bar Alexander Barkov
            KonstantinSH Konstantin SH
            0 Vote for this issue
            2 Start watching this issue



              Git Integration

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