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

Mariabackup --prepare crashed [ERROR] mysqld got signal 11 ;

    XMLWordPrintable

Details

    • Bug
    • Status: Closed (View Workflow)
    • Critical
    • Resolution: Cannot Reproduce
    • 10.4.14, 10.5
    • N/A
    • mariabackup
    • Debian Buster

    Description

      We have a big database to backup when we perform Full Backup and Full Backup Prepare it was successful then we perform First Incremental Backup based on the Full Backup and it was successful and then we perform First Incremental Backup Prepare to full and it was successful then we perform the Second Incremental Backup based from the First Incremental Backup and it was successful by the time we Prepare the Second Incremental Backup we encounter this issue. We encounter this issues for almost a month by now we already upgraded our Mariadb Versions up to the Latest my previous issue with the previous Mariadb Versions has not been resolved.. I attached some files it might help on solving this issue...
      Hope you can help us about this issue..

      200819 17:23:35 [ERROR] mysqld got signal 11 ;
      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.14-MariaDB-1:10.4.14+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 = 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
      mariabackup(my_print_stacktrace+0x2e)[0x563bb2c0034e]
      mariabackup(handle_fatal_signal+0x54d)[0x563bb275ddfd]
      /lib/x86_64-linux-gnu/libpthread.so.0(+0x12730)[0x7f4048899730]
      mariabackup(+0x5b4cf7)[0x563bb23c0cf7]
      mariabackup(+0xb97f1d)[0x563bb29a3f1d]
      mariabackup(+0xb986cc)[0x563bb29a46cc]
      mariabackup(+0xb7c96f)[0x563bb298896f]
      mariabackup(+0xb7d3bd)[0x563bb29893bd]
      mariabackup(+0x5b04ea)[0x563bb23bc4ea]
      mariabackup(+0x59349e)[0x563bb239f49e]
      mariabackup(+0xad0c8c)[0x563bb28dcc8c]
      mariabackup(+0xc11a10)[0x563bb2a1da10]
      /lib/x86_64-linux-gnu/libpthread.so.0(+0x7fa3)[0x7f404888efa3]
      /lib/x86_64-linux-gnu/libc.so.6(clone+0x3f)[0x7f4047da34cf]
      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 /BackupDirectory

      Resource Limits:

      Attachments

        Issue Links

          Activity

            People

              vlad.lesin Vladislav Lesin
              touchmebaby Wilson Echavez
              Votes:
              1 Vote for this issue
              Watchers:
              10 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.