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

signal 11 in cleanup phase

    XMLWordPrintable

Details

    • Bug
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Incomplete
    • None
    • N/A
    • Server
    • None
    • Red Hat
      MariaDB Enterprise 10.2.14 build 18904

    Description

      2 crashes, same stacktrace

      Same statement runs fine with build 18409

       
      Server version: 10.2.14-MariaDB-log
      key_buffer_size=67108864
      read_buffer_size=131072
      max_used_connections=466
      max_threads=1002
      thread_count=388
      It is possible that mysqld could use up to 
      key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 2267691 K  bytes of memory
      Hope that's ok; if not, decrease some variables in the equation.
       
      Thread pointer: 0x7fbae08f0158
      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 = 0x7fbad169bd80 thread_stack 0x40000
      /usr/sbin/mysqld(my_print_stacktrace+0x38)[0x5580daa757eb]
      /usr/sbin/mysqld(handle_fatal_signal+0x3d7)[0x5580da4a5b98]
      /lib64/libpthread.so.0(+0xf5e0)[0x7fbe6891a5e0]
      /usr/sbin/mysqld(_ZN12Item_func_in7cleanupEv+0x3a)[0x5580da5e67a8]
      /usr/sbin/mysqld(_ZN4Item11delete_selfEv+0x23)[0x5580da1f0367]
      /usr/sbin/mysqld(_ZN11Query_arena10free_itemsEv+0x2e)[0x5580da1e8d76]
      /usr/sbin/mysqld(_ZN3THD19cleanup_after_queryEv+0x111)[0x5580da1e4599]
      /usr/sbin/mysqld(_ZN18Prepared_statement12cleanup_stmtEv+0x5b)[0x5580da252659]
      /usr/sbin/mysqld(_ZN18Prepared_statement7executeEP6Stringb+0x55f)[0x5580da254b57]
      /usr/sbin/mysqld(_ZN18Prepared_statement12execute_loopEP6StringbPhS2_+0x13b)[0x5580da25307d]
      /usr/sbin/mysqld(+0x644056)[0x5580da251056]
      /usr/sbin/mysqld(_Z19mysqld_stmt_executeP3THDPcj+0x78)[0x5580da250e08]
      /usr/sbin/mysqld(_Z16dispatch_command19enum_server_commandP3THDPcjbb+0xb58)[0x5580da22b7e2]
      /usr/sbin/mysqld(_Z10do_commandP3THD+0x54c)[0x5580da22a7b1]
      /usr/sbin/mysqld(_Z24do_handle_one_connectionP7CONNECT+0x1bd)[0x5580da3534d4]
      /usr/sbin/mysqld(handle_one_connection+0x30)[0x5580da353234]
      /lib64/libpthread.so.0(+0x7e25)[0x7fbe68912e25]
      /lib64/libc.so.6(clone+0x6d)[0x7fbe66f6534d]
       
      Trying to get some variables.
      Some pointers may be invalid and cause the dump to abort.
      Query (0x7fbae08f98c0): select dependency0_.childObjectId as childObj1_127_, dependency0_.childObjectType as childObj2_127_, dependency0_.locationid as location3_127_, dependency0_.parentObjectId as parentOb4_127_, dependency0_.parentObjectType as parentOb5_127_, dependency0_.functionName as function6_127_, dependency0_.IsActivated as IsActiva7_127_, dependency0_.IntradayStatus as Intraday8_127_, dependency0_.paramOrder as paramOrd9_127_, dependency0_.priority as priorit10_127_ from v_ratedependencymap dependency0_ where (dependency0_.childObjectId in ('163475' , '163476' , '163477' , '163478')) and dependency0_.childObjectType='RAW' and dependency0_.locationid=101
      Connection ID (thread ID): 13702
      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=on,mrr_cost_based=on,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=on,table_elimination=on,extended_keys=on,exists_to_in=on,orderby_uses_equalities=on,condition_pushdown_for_derived=on,split_grouping_derived=on
       
      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.
      

      180315 11:00:30 [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.2.14-MariaDB-log
      key_buffer_size=67108864
      read_buffer_size=131072
      max_used_connections=38
      max_threads=1002
      thread_count=44
      It is possible that mysqld could use up to 
      key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 2267691 K  bytes of memory
      Hope that's ok; if not, decrease some variables in the equation.
       
      Thread pointer: 0x7f8c70016b68
      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 = 0x7f8d00cd7d80 thread_stack 0x40000
      /usr/sbin/mysqld(my_print_stacktrace+0x38)[0x5644c56017eb]
      /usr/sbin/mysqld(handle_fatal_signal+0x3d7)[0x5644c5031b98]
      sigaction.c:0(__restore_rt)[0x7f9006c2f5e0]
      sql/item_cmpfunc.h:2355(Item_func_in::cleanup())[0x5644c51727a8]
      sql/item.h:1848(Item::delete_self())[0x5644c4d7c367]
      sql/sql_class.cc:3690(Query_arena::free_items())[0x5644c4d74d76]
      sql/sql_class.cc:2228(THD::cleanup_after_query())[0x5644c4d70599]
      sql/sql_prepare.cc:3810(Prepared_statement::cleanup_stmt())[0x5644c4dde659]
      sql/sql_prepare.cc:4776(Prepared_statement::execute(String*, bool))[0x5644c4de0b57]
      sql/sql_prepare.cc:4172(Prepared_statement::execute_loop(String*, bool, unsigned char*, unsigned char*))[0x5644c4ddf07d]
      sql/sql_prepare.cc:3170(mysql_stmt_execute_common)[0x5644c4ddd056]
      sql/sql_prepare.cc:3069(mysqld_stmt_execute(THD*, char*, unsigned int))[0x5644c4ddce08]
      sql/sql_parse.cc:1778(dispatch_command(enum_server_command, THD*, char*, unsigned int, bool, bool))[0x5644c4db77e2]
      sql/sql_parse.cc:1383(do_command(THD*))[0x5644c4db67b1]
      sql/sql_connect.cc:1335(do_handle_one_connection(CONNECT*))[0x5644c4edf4d4]
      sql/sql_connect.cc:1242(handle_one_connection)[0x5644c4edf234]
      pthread_create.c:0(start_thread)[0x7f9006c27e25]
      /lib64/libc.so.6(clone+0x6d)[0x7f900527a34d]
       
      Trying to get some variables.
      Some pointers may be invalid and cause the dump to abort.
      Query (0x7f8c70025ea0): select dependency0_.childObjectId as childObj1_127_, dependency0_.childObjectType as childObj2_127_, dependency0_.locationid as location3_127_, dependency0_.parentObjectId as parentOb4_127_, dependency0_.parentObjectType as parentOb5_127_, dependency0_.functionName as function6_127_, dependency0_.IsActivated as IsActiva7_127_, dependency0_.IntradayStatus as Intraday8_127_, dependency0_.paramOrder as paramOrd9_127_, dependency0_.priority as priorit10_127_ from v_ratedependencymap dependency0_ where (dependency0_.childObjectId in ('163479' , '163480' , '163481' , '163482' , '163483' , '163484' , '163485')) and dependency0_.childObjectType='RAW' and dependency0_.locationid=101
      Connection ID (thread ID): 22
      Status: NOT_KILLED
      

      Attachments

        Issue Links

          Activity

            People

              elenst Elena Stepanova
              Richard Richard Stracke
              Votes:
              1 Vote for this issue
              Watchers:
              6 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.