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

[mariabackup] Failed with mysqld got signal 11

    XMLWordPrintable

Details

    • Bug
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Duplicate
    • 10.4.28, 10.4.33
    • 10.4.34
    • Backup
    • None
    • prod

    Description

      While doing the mariabackup on Mariadb 10.4.28, we get the below error message and due to this, we are not able to take the backup on any database. I tried to update mariabackup to 10.4.33 but the problem remains.
      Can you pls look into this and help me with resolution.

      [00] 2024-03-19 01:03:26 Connecting to MySQL server host: localhost, user: bkpuser, password: set, port: not set, socket: not set
      [00] 2024-03-19 01:03:26 Using server version 10.4.28-MariaDB-log
      mariabackup based on MariaDB server 10.4.33-MariaDB Linux (x86_64)
      [00] 2024-03-19 01:03:26 uses posix_fadvise().
      [00] 2024-03-19 01:03:26 cd to /var/lib/mysql/
      [00] 2024-03-19 01:03:26 open files limit requested 0, set to 1024
      
      

      [00] 2024-03-19 01:03:50 Skipping db: ./performance_schema
      [00] 2024-03-19 01:03:50 Finished backing up non-InnoDB tables and files
      240319  1:03:50 [ERROR] mysqld got signal 11 ;
      Sorry, we probably made a mistake, and this is a bug.
       
      Your assistance in bug reporting will enable us to fix this for the next release.
      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.33-MariaDB source revision: 46e3a7658b774942e9320a1acb234373bb44e874
      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 = 5955 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
      Printing to addr2line failed
      mariabackup(my_print_stacktrace+0x2e)[0x559149b883ee]
      [00] 2024-03-19 01:03:50 >> log scanned up to (7569959590615)
      mariabackup(handle_fatal_signal+0x53d)[0x55914969c42d]
      /lib64/libpthread.so.0(+0x12cf0)[0x7ff3e129bcf0]
      /lib64/libc.so.6(opendir+0x4)[0x7ff3e069e2f4]
      addr2line: 'mariabackup': No such file
      mariabackup(+0x63bba8)[0x559149361ba8]
      mariabackup(_Z12backup_startP7ds_ctxtS0_R14CorruptedPages+0x10d)[0x55914936543d]
      mariabackup(+0x626f24)[0x55914934cf24]
      mariabackup(main+0x18e)[0x559149322b5e]
      /lib64/libc.so.6(__libc_start_main+0xe5)[0x7ff3e05e2d85]
      addr2line: 'mariabackup': No such file
      mariabackup(_start+0x2e)[0x55914933e19e]
      The manual page at https://mariadb.com/kb/en/how-to-produce-a-full-stack-trace-for-mariadbd/ 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             401575               401575               processes 
      Max open files            1024                 262144               files     
      Max locked memory         65536                65536                bytes     
      Max address space         unlimited            unlimited            bytes     
      Max file locks            unlimited            unlimited            locks     
      Max pending signals       401575               401575               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
       
      Kernel version: Linux version 4.18.0-425.13.1.el8_7.x86_64 (mockbuild@dal1-prod-builder001.bld.equ.rockylinux.org) (gcc version 8.5.0 20210514 (Red Hat 8.5.0-16) (GCC)) #1 SMP Tue Feb 21 19:25:54 UTC 2023
       
      Segmentation fault (core dumped)
      
      

      Attachments

        Issue Links

          Activity

            People

              Unassigned Unassigned
              geascnbr Kirill
              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.