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

mysqld got signal 11

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed (View Workflow)
    • Priority: Critical
    • Resolution: Fixed
    • Affects Version/s: 10.1.5
    • Fix Version/s: 10.1.6
    • Component/s: OTHER
    • Labels:
      None
    • Environment:

      Description

      MariaDB is running as as slave, currently with very little activity.
      At the time of the crash there was a script running doing a "check table" on all tables in all databases. There was no other client connected at this time.
      The server failure cannot be repeted. Running th script a second and third time was fine.
      Server crashed with message:

      150618  1:50:07 [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 http://kb.askmonty.org/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.5-MariaDB-log
      key_buffer_size=67108864
      read_buffer_size=131072
      max_used_connections=5
      max_threads=502
      thread_count=1
      It is possible that mysqld could use up to
      key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 1168091 K  bytes of memory
      Hope that's ok; if not, decrease some variables in the equation.
       
      Thread pointer: 0x0x7fef8fefb008
      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 = 0x7fef90491e58 thread_stack 0x48000
      mysys/stacktrace.c:247(my_print_stacktrace)[0x7fef931dcbf9]
      sql/signal_handler.cc:153(handle_fatal_signal)[0x7fef92def98d]
      /lib/x86_64-linux-gnu/libpthread.so.0(+0xf8d0)[0x7fef924498d0]
      sql/sql_plist.h:181(I_P_List_iterator)[0x7fef92da6360]
      mysys/lf_hash.c:125(lfind)[0x7fef931e3a5c]
      include/my_atomic.h:281(my_atomic_storeptr)[0x7fef931e4459]
      sql/table_cache.cc:1084(tdc_iterate(THD*, char (*)(void*, void*), void*, bool))[0x7fef92da7fb3]
      sql/table_cache.cc:267(tc_add_table(THD*, TABLE*))[0x7fef92da833a]
      sql/sql_base.cc:2572(open_table(THD*, TABLE_LIST*, Open_table_context*))[0x7fef92c42f0d]
      sql/sql_base.cc:4019(open_and_process_table)[0x7fef92c46557]
      sql/sql_base.cc:5184(open_and_lock_tables(THD*, DDL_options_st const&, TABLE_LIST*, bool, unsigned int, Prelocking_strategy*))[0x7fef92c46c1d]
      sql/sql_admin.cc:446(mysql_admin_table)[0x7fef92d576d6]
      sql/sql_admin.cc:1210(Sql_cmd_check_table::execute(THD*))[0x7fef92d59046]
      sql/sql_parse.cc:5573(mysql_execute_command(THD*))[0x7fef92c839fc]
      sql/sql_parse.cc:7173(mysql_parse(THD*, char*, unsigned int, Parser_state*))[0x7fef92c8a334]
      sql/sql_parse.cc:1470(dispatch_command(enum_server_command, THD*, char*, unsigned int))[0x7fef92c8cb80]
      sql/sql_parse.cc:1095(do_command(THD*))[0x7fef92c8d29b]
      sql/sql_connect.cc:1347(do_handle_one_connection(THD*))[0x7fef92d4c80c]
      sql/sql_connect.cc:1260(handle_one_connection)[0x7fef92d4c9e7]
      /lib/x86_64-linux-gnu/libpthread.so.0(+0x80a4)[0x7fef924420a4]
      /lib/x86_64-linux-gnu/libc.so.6(clone+0x6d)[0x7fef9085c04d]
       
      Trying to get some variables.
      Some pointers may be invalid and cause the dump to abort.
      Query (0x7fef5eb49020): is an invalid pointer
      Connection ID (thread ID): 17307
      Status: NOT_KILLED
       
      Optimizer switch: index_merge=on,index_merge_union=on,index_merge_sort_union=on,index_merge_intersection=on,index_merge_sort_intersection=off,engine_conditio
       
      The manual page at http://dev.mysql.com/doc/mysql/en/crashing.html contains
      information that should help you find out what is causing the crash.
      150618 01:50:07 mysqld_safe Number of processes running now: 0
      150618 01:50:07 mysqld_safe mysqld restarted
      2015-06-18  1:50:07 139723066570624 [Note] /usr/local/mysql/bin/mysqld (mysqld 10.1.5-MariaDB-log) starting as process 16564 ...

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              svoj Sergey Vojtovich
              Reporter:
              Cyberagent technik Cyberagent technik
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: