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

10.1.18-MariaDB-1~jessie - mysqld got signal 11

    XMLWordPrintable

Details

    • Bug
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Fixed
    • 10.1.18, 10.1, 10.2
    • 10.1.32
    • GIS, Server
    • None
    • Debian GNU/Linux 8.2 (jessie)
      32GB Ram - CPU 16 Core - SSD 1TB
    • 10.2.10

    Description

      170505 16:17:38 [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.1.18-MariaDB-1~jessie
      key_buffer_size=8589934592
      read_buffer_size=2097152
      max_used_connections=1419
      max_threads=5002
      thread_count=1023
      It is possible that mysqld could use up to 
      key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 28979515 K  bytes of memory
      Hope that's ok; if not, decrease some variables in the equation.
       
      Thread pointer: 0x0x7f636b4ec008
      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 = 0x7f6299eef1f8 thread_stack 0x48400
      *** buffer overflow detected ***: /usr/sbin/mysqld terminated
      

      Attachments

        1. mariadb.err
          239 kB
        2. mariadb.err.0
          216 kB

        Activity

          People

            holyfoot Alexey Botchkov
            infodgit dgit
            Votes:
            0 Vote for this issue
            Watchers:
            4 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.