Details

      Description

      Hello,

      Below is a crash report from MariaDB 10.3.8, the report isn't much and does not give much direction. Anything I can do to help provide better next steps

      181219  8:29:19 [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.3.8-MariaDB-log
      key_buffer_size=134217728
      read_buffer_size=131072
      max_used_connections=73
      max_threads=2002
      thread_count=47
      It is possible that mysqld could use up to
      key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 4532133 K  bytes of memory
      Hope that's ok; if not, decrease some variables in the equation.
       
      Thread pointer: 0x7ed3780008c8
      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 = 0x7ed514473d30 thread_stack 0x49000
      /usr/sbin/mysqld(my_print_stacktrace+0x2e)[0x56497058cece]
      /usr/sbin/mysqld(handle_fatal_signal+0x357)[0x564970029577]
      

        Attachments

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              djuntgen Dave Juntgen
            • Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: