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

mysqld got signal 11 ;

    XMLWordPrintable

Details

    • Bug
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Duplicate
    • 10.11.7
    • 10.4.29
    • Backup
    • None
    • centos 7

    Description

      Server version: 10.11.7-MariaDB source revision: 87e13722a95af5d9378d990caf48cb6874439347
      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 = 6236 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 hay tal fichero
      Printing to addr2line failed
      mariabackup(my_print_stacktrace+0x2e)[0x56042cfa677e]
      mariabackup(handle_fatal_signal+0x2f7)[0x56042ca57267]
      sigaction.c:0(__restore_rt)[0x7fc3b4dff630]
      /lib64/libc.so.6(+0xc0f10)[0x7fc3b42d4f10]
      addr2line: 'mariabackup': No hay tal fichero
      mariabackup(+0x756158)[0x56042c6c7158]
      mariabackup(_Z12backup_startP7ds_ctxtS0_R14CorruptedPages+0x10d)[0x56042c6cb59d]
      mariabackup(+0x73fea7)[0x56042c6b0ea7]
      mariabackup(main+0x17a)[0x56042c65747a]
      /lib64/libc.so.6(__libc_start_main+0xf5)[0x7fc3b4236555]
      addr2line: 'mariabackup': No hay tal fichero
      mariabackup(+0x72f273)[0x56042c6a0273]
      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             127957               127957               processes
      Max open files            1024                 4096                 files
      Max locked memory         65536                65536                bytes
      Max address space         unlimited            unlimited            bytes
      Max file locks            unlimited            unlimited            locks
      Max pending signals       127957               127957               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 3.10.0-1160.88.1.el7.x86_64 (mockbuild@kbuilder.bsys.centos.org) (gcc version 4.8.5 20150623 (Red Hat 4.8.5-44) (GCC) ) #1 SMP Tue Mar 7 15:41:52 UTC 2023
       
      Violación de segmento
      

      Attachments

        Issue Links

          Activity

            People

              danblack Daniel Black
              jlionelmo JOSE MEDINA
              Votes:
              0 Vote for this issue
              Watchers:
              3 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.