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

Mariadb 10.1.13 got killed by SIGNAL 11

    XMLWordPrintable

Details

    • Bug
    • Status: Open (View Workflow)
    • Major
    • Resolution: Unresolved
    • 10.1.13, 10.1.16, 10.1
    • 10.1
    • None
    • None
    • Operating System : Red Hat Enterprise Linux Server
      Operating System Version : release 6.8 (Santiago) Kernel 2.6.32-642.1.1.el6.x86_64 (x86_64)

    Description

      Mariadb got killed, here is the logs

      160816 16:10: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 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.13-MariaDB
      key_buffer_size=8589934592
      read_buffer_size=131072
      max_used_connections=203
      max_threads=1026
      thread_count=83
      It is possible that mysqld could use up to
      key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 10642180 K  bytes of memory
      Hope that's ok; if not, decrease some variables in the equation.
       
      Thread pointer: 0x0x7f8f34c95008
      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 = 0x7f8f6dd99d40 thread_stack 0x40000
      

      /usr/sbin/mysqld(my_print_stacktrace+0x2b)[0x7f917e320e0b]
      /usr/sbin/mysqld(handle_fatal_signal+0x475)[0x7f917de81055]
      /lib64/libpthread.so.0(+0xf7e0)[0x7f917d2857e0]
      /usr/sbin/mysqld(_Z18get_datetime_valueP3THDPPP4ItemS3_16enum_field_typesPb+0x41)[0x7f917deb0a01]
      /usr/sbin/mysqld(_ZN14Arg_comparator16compare_temporalE16enum_field_types+0x60)[0x7f917deb0cb0]
      /usr/sbin/mysqld(_ZN12Item_func_ge7val_intEv+0x2a)[0x7f917deace4a]
      /usr/sbin/mysqld(_ZN4Item8val_boolEv+0xac)[0x7f917de918cc]
      /usr/sbin/mysqld(_ZN14Item_func_case9find_itemEP6String+0x174)[0x7f917deb31c4]
      /usr/sbin/mysqld(_ZN14Item_func_case6int_opEv+0x75)[0x7f917deb3595]
      /usr/sbin/mysqld(_ZN27Item_func_hybrid_field_type7val_intEv+0x9c)[0x7f917ded921c]
      /usr/sbin/mysqld(_ZN4Item13save_in_fieldEP5Fieldb+0x15c)[0x7f917de8fabc]
      mysys/stacktrace.c:247(my_print_stacktrace)[0x7f917ddb6292]
      /usr/sbin/mysqld(+0x49c9ee)[0x7f917dd539ee]
      /usr/sbin/mysqld(+0x3a1d0b)[0x7f917dc58d0b]
      /usr/sbin/mysqld(+0x3a33f5)[0x7f917dc5a3f5]
      /usr/sbin/mysqld(_ZN4JOIN14optimize_innerEv+0x5fa)[0x7f917dd5f6ea]
      /usr/sbin/mysqld(_ZN4JOIN8optimizeEv+0x20)[0x7f917dd62060]
      /usr/sbin/mysqld(_Z12mysql_selectP3THDPPP4ItemP10TABLE_LISTjR4ListIS1_ES2_jP8st_orderSB_S2_SB_yP13select_resultP18st_select_lex_unitP13st_select_lex+0x9d)[0x7f917dd621bd]
      /usr/sbin/mysqld(_Z13handle_selectP3THDP3LEXP13select_resultm+0x25d)[0x7f917dd65b5d]
      /usr/sbin/mysqld(+0x4510c2)[0x7f917dd080c2]
      /usr/sbin/mysqld(_Z21mysql_execute_commandP3THD+0x5e40)[0x7f917dd143d0]
      /usr/sbin/mysqld(_Z11mysql_parseP3THDPcjP12Parser_state+0x28d)[0x7f917dd1790d]
      /usr/sbin/mysqld(_Z16dispatch_command19enum_server_commandP3THDPcj+0x243b)[0x7f917dd1a56b]
      

      Server version: 10.1.13-MariaDB
      key_buffer_size=8589934592
      read_buffer_size=131072
      max_used_connections=203
      max_threads=1026
      thread_count=83
      It is possible that mysqld could use up to
      key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 10642180 K  bytes of memory
      Hope that's ok; if not, decrease some variables in the equation.
       
      Thread pointer: 0x0x7f8f34c95008
      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 = 0x7f8f6dd99d40 thread_stack 0x40000
      

      /usr/sbin/mysqld(my_print_stacktrace+0x2b)[0x7f917e320e0b]
      /usr/sbin/mysqld(handle_fatal_signal+0x475)[0x7f917de81055]
      /lib64/libpthread.so.0(+0xf7e0)[0x7f917d2857e0]
      /usr/sbin/mysqld(_Z18get_datetime_valueP3THDPPP4ItemS3_16enum_field_typesPb+0x41)[0x7f917deb0a01]
      /usr/sbin/mysqld(_ZN14Arg_comparator16compare_temporalE16enum_field_types+0x60)[0x7f917deb0cb0]
      /usr/sbin/mysqld(_ZN12Item_func_ge7val_intEv+0x2a)[0x7f917deace4a]
      /usr/sbin/mysqld(_ZN4Item8val_boolEv+0xac)[0x7f917de918cc]
      /usr/sbin/mysqld(_ZN14Item_func_case9find_itemEP6String+0x174)[0x7f917deb31c4]
      /usr/sbin/mysqld(_ZN14Item_func_case6int_opEv+0x75)[0x7f917deb3595]
      /usr/sbin/mysqld(_ZN27Item_func_hybrid_field_type7val_intEv+0x9c)[0x7f917ded921c]
      /usr/sbin/mysqld(_ZN4Item13save_in_fieldEP5Fieldb+0x15c)[0x7f917de8fabc]
      mysys/stacktrace.c:247(my_print_stacktrace)[0x7f917ddb6292]
      /usr/sbin/mysqld(+0x49c9ee)[0x7f917dd539ee]
      /usr/sbin/mysqld(+0x3a1d0b)[0x7f917dc58d0b]
      /usr/sbin/mysqld(+0x3a33f5)[0x7f917dc5a3f5]
      /usr/sbin/mysqld(_ZN4JOIN14optimize_innerEv+0x5fa)[0x7f917dd5f6ea]
      /usr/sbin/mysqld(_ZN4JOIN8optimizeEv+0x20)[0x7f917dd62060]
      /usr/sbin/mysqld(_Z12mysql_selectP3THDPPP4ItemP10TABLE_LISTjR4ListIS1_ES2_jP8st_orderSB_S2_SB_yP13select_resultP18st_select_lex_unitP13st_select_lex+0x9d)[0x7f917dd621bd]
      /usr/sbin/mysqld(_Z13handle_selectP3THDP3LEXP13select_resultm+0x25d)[0x7f917dd65b5d]
      /usr/sbin/mysqld(+0x4510c2)[0x7f917dd080c2]
      /usr/sbin/mysqld(_Z21mysql_execute_commandP3THD+0x5e40)[0x7f917dd143d0]
      /usr/sbin/mysqld(_Z11mysql_parseP3THDPcjP12Parser_state+0x28d)[0x7f917dd1790d]
      /usr/sbin/mysqld(_Z16dispatch_command19enum_server_commandP3THDPcj+0x243b)[0x7f917dd1a56b]
      /usr/sbin/mysqld(_Z10do_commandP3THD+0x16b)[0x7f917dd1ab1b]
      /usr/sbin/mysqld(_Z24do_handle_one_connectionP3THD+0x17f)[0x7f917ddd64af]
      /usr/sbin/mysqld(handle_one_connection+0x47)[0x7f917ddd6607]
      /lib64/libpthread.so.0(+0x7aa1)[0x7f917d27daa1]
      /lib64/libc.so.6(clone+0x6d)[0x7f917b762aad]
      

      Trying to get some variables.
      Some pointers may be invalid and cause the dump to abort.
      Query (0x7f8eec5ff020): is an invalid pointer
      Connection ID (thread ID): 102556786
      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_condition_pushdown=off,index_condition_pushdown=on,derived_merge=on,derived_with_keys=on,firstmatch=on,loosescan=on,materialization=on,in_to_exists=on,semijoin=on,partial_match_rowid_merge=on,partial_match_table_scan=on,subquery_cache=on,mrr=off,mrr_cost_based=off,mrr_sort_keys=off,outer_join_with_cache=on,semijoin_with_cache:
      

      Attachments

        1. alter.sql
          0.2 kB
        2. custom_903.sql
          12 kB
        3. error.log
          4 kB
        4. my.cnf
          4 kB
        5. my.cnf
          6 kB
        6. queries.log
          43 kB

        Issue Links

          Activity

            People

              Unassigned Unassigned
              Jaiswal Ashish
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:

                Git Integration

                  Error rendering 'com.xiplink.jira.git.jira_git_plugin:git-issue-webpanel'. Please contact your Jira administrators.