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

[ERROR] mysqld got signal 11

    XMLWordPrintable

Details

    • Bug
    • Status: Closed (View Workflow)
    • Critical
    • Resolution: Incomplete
    • 10.0.36
    • N/A
    • Server
    • CentOS6.8 x64

    Description

      200103 17:32:05 [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/<wbr />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.0.36-MariaDB
      key_buffer_size=134217728
      read_buffer_size=131072
      max_used_connections=252
      max_threads=602
      thread_count=100
      It is possible that mysqld could use up to
      key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 1452959 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 0x48000
      /usr/sbin/mysqld(my_print_<wbr />stacktrace+0x2b)[0xb8435b]
      /usr/sbin/mysqld(handle_fatal_<wbr />signal+0x3b6)[0x73d656]
      sigaction.c:0(__restore_rt)[<wbr />0x7f529f44d7e0]
      /usr/sbin/mysqld[0x8f4b29]
      /usr/sbin/mysqld[0x8f534e]
      /usr/sbin/mysqld[0x8f9afc]
      /usr/sbin/mysqld[0x8fb372]
      pthread_create.c:0(start_<wbr />thread)[0x7f529f445aa1]
      /lib64/libc.so.6(clone+0x6d)[<wbr />0x7f529db5eaad]
      The manual page at http://dev.mysql.com/doc/<wbr />mysql/en/crashing.html contains
      information that should help you find out what is causing the crash.
      200103 17:32:11 mysqld_safe Number of processes running now: 0
      200103 17:32:11 mysqld_safe mysqld restarted
      200103 17:32:12 [Note] /usr/sbin/mysqld (mysqld 10.0.36-MariaDB) starting as process 20284 ...
      200103 17:32:13 [Note] mysqld: Aria engine: starting recovery
      recovered pages: 0% 10% 20% 30% 40% 50% 60% 70% 80% 90% 100% (0.3 seconds); tables to flush: 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0 (0.5 seconds);
      200103 17:32:14 [Note] mysqld: Aria engine: recovery done
      200103 17:32:14 [Note] InnoDB: innodb_empty_free_list_<wbr />algorithm has been changed to legacy because of small buffer pool size. In order to use backoff, increase buffer pool at least up to 20MB.

      200103 17:32:14 [Note] InnoDB: Using mutexes to ref count buffer pool pages
      200103 17:32:14 [Note] InnoDB: The InnoDB memory heap is disabled
      200103 17:32:14 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
      200103 17:32:14 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
      200103 17:32:14 [Note] InnoDB: Compressed tables use zlib 1.2.3
      200103 17:32:14 [Note] InnoDB: Using Linux native AIO
      200103 17:32:14 [Note] InnoDB: Using CPU crc32 instructions
      200103 17:32:14 [Note] InnoDB: Initializing buffer pool, size = 128.0M
      200103 17:32:14 [Note] InnoDB: Completed initialization of buffer pool
      200103 17:32:15 [Note] InnoDB: Highest supported file format is Barracuda.
      200103 17:32:15 [Note] InnoDB: The log sequence numbers 1623899 and 1623899 in ibdata files do not match the log sequence number 1623909 in the ib_logfiles!
      200103 17:32:48 [Note] InnoDB: Restoring possible half-written data pages from the doublewrite buffer...
      200103 17:32:48 [Note] InnoDB: Read redo log up to LSN=1624064
      200103 17:32:48 [Note] InnoDB: 128 rollback segment(s) are active.
      200103 17:32:48 [Note] InnoDB: Waiting for purge to start
      200103 17:32:48 [Note] InnoDB: Percona XtraDB (http://www.percona.com) 5.6.39-83.1 started; log sequence number 1623909
      200103 17:32:48 [Note] Plugin 'FEEDBACK' is disabled.
      200103 17:32:49 [Warning] Failed to setup SSL
      200103 17:32:49 [Warning] SSL error: SSL_CTX_set_default_verify_<wbr />paths failed
      200103 17:32:49 [Warning] SSL error: error:0200100D:system library:fopen:Permission denied
      200103 17:32:49 [Warning] SSL error: error:2006D002:BIO routines:BIO_new_file:system lib
      200103 17:32:49 [Warning] SSL error: error:0B084002:x509 certificate routines:X509_load_cert_crl_<wbr />file:system lib
      200103 17:32:49 [Note] Server socket created on IP: '::'.
      200103 17:32:49 [Warning] 'user' entry 'root@log01' ignored in --skip-name-resolve mode.
      200103 17:32:49 [Warning] 'user' entry '@log01' ignored in --skip-name-resolve mode.
      200103 17:32:49 [Warning] 'user' entry 'safe@Log01' ignored in --skip-name-resolve mode.
      200103 17:32:49 [Warning] 'proxies_priv' entry '@% root@log01' ignored in --skip-name-resolve mode.
      200103 17:32:50 [Note] /usr/sbin/mysqld: ready for connections.

      Attachments

        Activity

          People

            Unassigned Unassigned
            HYUNG KANG
            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.