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

LP:1038786 - mysqld got signal 11 Hit a bug ?

    Details

    • Type: Bug
    • Status: Closed
    • Resolution: Duplicate
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: None
    • Labels:

      Description

      Dear,

      This is the many time my server crashes with the same problem, 120819 12:04:11 [ERROR] mysqld got signal 11 ;
      This could be because you hit a bug etc.

      CentOs 6.2 64Bits.
      mariadb-5.5.25
      Intel(R) Xeon(R) CPU E31240 @ 3.30GHz
      16Go Ram
      2 x SSD 128Go SanDisk
      1300req/sec average for 3500 DB.

      Last crash :

      120819 12:04:11 [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: 5.5.25-MariaDB-log
      key_buffer_size=2122317824
      read_buffer_size=131072
      max_used_connections=425
      max_threads=3002
      thread_count=30
      It is possible that mysqld could use up to
      key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 395976802 K bytes of memory
      Hope that's ok; if not, decrease some variables in the equation.

      Thread pointer: 0x0x3b85cc0
      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 = 0x7f01c4784d98 thread_stack 0x40000
      ??:0(my_print_stacktrace)[0xa6d3de]
      ??:0(handle_fatal_signal)[0x6c584b]
      :0()[0x7f0274d334a0]
      ??:0(ha_maria::ft_init_ext(unsigned int, unsigned int, String*))[0x986eb0]
      ??:0(Item_func_match::init_search(bool))[0x7215f3]
      ??:0(Item_func_match::init_search(bool))[0x721535]
      ??:0(init_ftfuncs(THD*, st_select_lex*, bool))[0x53c3f8]
      ??:0(JOIN::optimize())[0x5cb95e]
      ??:0(mysql_select(THD*, Item**, TABLE_LIST, unsigned int, List<Item>&, Item*, unsigned int, st_order*, st_order*, Item*, st_order*, unsigned long long, select_result*, st_select_lex_unit*, st_select_lex*))[0x5d3fc2]
      ??:0(handle_select(THD*, LEX*, select_result*, unsigned long))[0x5d4bbd]
      ??:0(execute_sqlcom_select(THD*, TABLE_LIST*))[0x581fbc]
      ??:0(mysql_execute_command(THD*))[0x588ff0]
      ??:0(mysql_parse(THD*, char*, unsigned int, Parser_state*))[0x58b389]
      ??:0(dispatch_command(enum_server_command, THD*, char*, unsigned int))[0x58c688]
      ??:0(do_handle_one_connection(THD*))[0x640b63]
      ??:0(handle_one_connection)[0x640cac]
      :0()[0x7f0274d2b7f1]
      :0()[0x7f02736a1ccd]

      Trying to get some variables.
      Some pointers may be invalid and cause the dump to abort.
      Query (0x7f00aa191cd8): is an invalid pointer
      Connection ID (thread ID): 434408348
      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=on,join_cache_incremental=on,join_cache_hashed=on,join_cache_bka=on,optimize_join_buffer_size=off,table_elimination=on,extended_keys=off

      Old crash :

      120714 23:37:45 [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: 5.5.25-MariaDB-log
      key_buffer_size=2122317824
      read_buffer_size=131072
      max_used_connections=133
      max_threads=3002
      thread_count=21
      It is possible that mysqld could use up to
      key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 395976802 K bytes of memory
      Hope that's ok; if not, decrease some variables in the equation.

      Thread pointer: 0x0x43d21b0
      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 = 0x7f7034508d98 thread_stack 0x40000
      ??:0(my_print_stacktrace)[0xa6d3de]
      ??:0(handle_fatal_signal)[0x6c584b]
      :0()[0x7f70d87ba4a0]
      ??:0(ha_maria::ft_init_ext(unsigned int, unsigned int, String*))[0x986eb0]
      ??:0(Item_func_match::init_search(bool))[0x7215f3]
      ??:0(Item_func_match::init_search(bool))[0x721535]
      ??:0(init_ftfuncs(THD*, st_select_lex*, bool))[0x53c3f8]
      ??:0(JOIN::optimize())[0x5cb95e]
      ??:0(mysql_select(THD*, Item**, TABLE_LIST, unsigned int, List<Item>&, Item*, unsigned int, st_order*, st_order*, Item*, st_order*, unsigned long long, select_result*, st_select_lex_unit*, st_select_lex*))[0x5d3fc2]
      ??:0(handle_select(THD*, LEX*, select_result*, unsigned long))[0x5d4bbd]
      ??:0(execute_sqlcom_select(THD*, TABLE_LIST*))[0x581fbc]
      ??:0(mysql_execute_command(THD*))[0x588ff0]
      ??:0(mysql_parse(THD*, char*, unsigned int, Parser_state*))[0x58b389]
      ??:0(dispatch_command(enum_server_command, THD*, char*, unsigned int))[0x58c688]
      ??:0(do_handle_one_connection(THD*))[0x640b63]
      ??:0(handle_one_connection)[0x640cac]
      :0()[0x7f70d87b27f1]
      :0()[0x7f70d7128ccd]

      Trying to get some variables.
      Some pointers may be invalid and cause the dump to abort.
      Query (0x7f6f0d121fb8): is an invalid pointer
      Connection ID (thread ID): 60462379
      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_key$

      Old Crash :

      120716 23:54:48 [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: 5.5.25-MariaDB-log
      key_buffer_size=2122317824
      read_buffer_size=131072
      max_used_connections=101
      max_threads=3002
      thread_count=23
      It is possible that mysqld could use up to
      key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 395976802 K bytes of memory
      Hope that's ok; if not, decrease some variables in the equation.

      Thread pointer: 0x0x379e670
      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 = 0x7f0f6c4cad98 thread_stack 0x40000
      ??:0(my_print_stacktrace)[0xa6d3de]
      ??:0(handle_fatal_signal)[0x6c584b]
      :0()[0x7f103059b4a0]
      ??:0(ha_maria::ft_init_ext(unsigned int, unsigned int, String*))[0x986eb0]
      ??:0(Item_func_match::init_search(bool))[0x7215f3]
      ??:0(Item_func_match::init_search(bool))[0x721535]
      ??:0(init_ftfuncs(THD*, st_select_lex*, bool))[0x53c3f8]
      ??:0(JOIN::optimize())[0x5cb95e]
      ??:0(mysql_select(THD*, Item**, TABLE_LIST, unsigned int, List<Item>&, Item*, unsigned int, st_order*, st_order*, Item*, st_order*, unsigned long long, select_result*, st_select_lex_unit*, st_select_lex*))[0x5d3fc2]
      ??:0(handle_select(THD*, LEX*, select_result*, unsigned long))[0x5d4bbd]
      ??:0(execute_sqlcom_select(THD*, TABLE_LIST*))[0x581fbc]
      ??:0(mysql_execute_command(THD*))[0x588ff0]
      ??:0(mysql_parse(THD*, char*, unsigned int, Parser_state*))[0x58b389]
      ??:0(dispatch_command(enum_server_command, THD*, char*, unsigned int))[0x58c688]
      ??:0(do_handle_one_connection(THD*))[0x640b63]
      ??:0(handle_one_connection)[0x640cac]
      :0()[0x7f10305937f1]
      :0()[0x7f102ef09ccd]

      Trying to get some variables.
      Some pointers may be invalid and cause the dump to abort.
      Query (0x7f0e5994e648): is an invalid pointer
      Connection ID (thread ID): 16992022
      Status: NOT_KILLED

        Gliffy Diagrams

          Attachments

            Activity

            Hide
            elenst Elena Stepanova added a comment -

            Re: mysqld got signal 11 Hit a bug ?
            Hi,

            Do you happen to have any idea what was executed on the server at the time it crashed? Maybe you have a process list monitor, or server general log (a.k.a. SQL log)? Whatever you could provide in regard to the offending query might help to find the reason of the error.

            Is it a high-load production server? If not, and since you have been getting the crash repeatedly, maybe you could enable general log for a while and send it to us after the server crashes again?

            Thank you.

            Show
            elenst Elena Stepanova added a comment - Re: mysqld got signal 11 Hit a bug ? Hi, Do you happen to have any idea what was executed on the server at the time it crashed? Maybe you have a process list monitor, or server general log (a.k.a. SQL log)? Whatever you could provide in regard to the offending query might help to find the reason of the error. Is it a high-load production server? If not, and since you have been getting the crash repeatedly, maybe you could enable general log for a while and send it to us after the server crashes again? Thank you.
            Hide
            gurvan Gurvan added a comment -

            Re: mysqld got signal 11 Hit a bug ?
            Hi,

            I have no idea of what was executed at this time.
            This is a shared MySQL server with 6000 websites.
            Other logs do not indicate any problem.

            The server is not high-load, if need cacti :
            http://cacti.free-h.org/graph_view.php?action=tree&tree_id=1&leaf_id=1638

            This error seems very specific with a request .

            Gurvan.

            Show
            gurvan Gurvan added a comment - Re: mysqld got signal 11 Hit a bug ? Hi, I have no idea of what was executed at this time. This is a shared MySQL server with 6000 websites. Other logs do not indicate any problem. The server is not high-load, if need cacti : http://cacti.free-h.org/graph_view.php?action=tree&tree_id=1&leaf_id=1638 This error seems very specific with a request . Gurvan.
            Hide
            ratzpo Rasmus Johansson added a comment -

            Launchpad bug id: 1038786

            Show
            ratzpo Rasmus Johansson added a comment - Launchpad bug id: 1038786
            Hide
            elenst Elena Stepanova added a comment -

            Now we have a test case for this crash, MDEV-4316.
            While this bug report was submitted earlier, it didn't have enough information to reproduce it (the crashing query and data structures), while the newer one does, which is why this one is marked a duplicate and vice versa.

            Show
            elenst Elena Stepanova added a comment - Now we have a test case for this crash, MDEV-4316 . While this bug report was submitted earlier, it didn't have enough information to reproduce it (the crashing query and data structures), while the newer one does, which is why this one is marked a duplicate and vice versa.

              People

              • Assignee:
                Unassigned
                Reporter:
                gurvan Gurvan
              • Votes:
                0 Vote for this issue
                Watchers:
                1 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: