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

Mariabackup - Preparing incremental backup crash with mysqld got signal 6

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Major
    • Resolution: Incomplete
    • Affects Version/s: 10.4.10
    • Fix Version/s: N/A
    • Component/s: Backup
    • Environment:
      Debian 10 = OS

      Description

      InnoDB: Failing assertion: free + TRX_UNDO_LOG_XA_HDR_SIZE < srv_page_size - 100
      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.
      200213 10:23:21 [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.10-MariaDB-1:10.4.10+maria~buster
      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 = 5917 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
      mariabackup(my_print_stacktrace+0x2e)[0x563c2ed0971e]
      mariabackup(handle_fatal_signal+0x54d)[0x563c2e864aad]
      /lib/x86_64-linux-gnu/libpthread.so.0(+0x12730)[0x7f708c43b730]
      /lib/x86_64-linux-gnu/libc.so.6(gsignal+0x10b)[0x7f708b8837bb]
      /lib/x86_64-linux-gnu/libc.so.6(abort+0x121)[0x7f708b86e535]
      mariabackup(+0x5b2371)[0x563c2e4e1371]
      mariabackup(+0x5b1f98)[0x563c2e4e0f98]
      mariabackup(+0xc21ef0)[0x563c2eb50ef0]
      mariabackup(+0xb5c9b5)[0x563c2ea8b9b5]
      mariabackup(+0xb5d59b)[0x563c2ea8c59b]
      mariabackup(+0x595449)[0x563c2e4c4449]
      mariabackup(+0x578a62)[0x563c2e4a7a62]
      mariabackup(+0xab70dc)[0x563c2e9e60dc]
      mariabackup(+0xbf3c20)[0x563c2eb22c20]
      /lib/x86_64-linux-gnu/libpthread.so.0(+0x7fa3)[0x7f708c430fa3]
      /lib/x86_64-linux-gnu/libc.so.6(clone+0x3f)[0x7f708b9454cf]
      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 /path/to/backup
      Resource Limits:
      Fatal signal 11 while backtracing
      Segmentation fault

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              Unassigned
              Reporter:
              Wilson Wilson
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: