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

mysqld got signal 11

    XMLWordPrintable

Details

    Description

      Hello,
      we had an issue with mariadb 5.5.35 and couldn't reproduce the problem.
      OS - Centos 6.

      140211 12:43:57 [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.35-MariaDB-log
      key_buffer_size=268435456
      read_buffer_size=131072
      max_used_connections=727
      max_threads=742
      thread_count=585
      It is possible that mysqld could use up to 
      key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 24684221 K  bytes of memory
      Hope that's ok; if not, decrease some variables in the equation.
       
      Thread pointer: 0x0x7fbd83a4d7e0
      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 = 0x7fa027b6ed58 thread_stack 0x48000
      (my_addr_resolve failure: fork)
      /usr/libexec/mysqld(my_print_stacktrace+0x2e) [0x7fbcd586cc5e]
      /usr/libexec/mysqld(handle_fatal_signal+0x4ac) [0x7fbcd54b551c]
      /lib64/libpthread.so.0(+0x3578c0f500) [0x7fbcd4be1500]
      /usr/libexec/mysqld(+0x7660e0) [0x7fbcd57770e0]
      /usr/libexec/mysqld(+0x76684c) [0x7fbcd577784c]
      /usr/libexec/mysqld(+0x7533be) [0x7fbcd57643be]
      /usr/libexec/mysqld(+0x74f5d7) [0x7fbcd57605d7]
      /usr/libexec/mysqld(+0x751ecf) [0x7fbcd5762ecf]
      /usr/libexec/mysqld(+0x744c99) [0x7fbcd5755c99]
      /usr/libexec/mysqld(+0x6f94f7) [0x7fbcd570a4f7]
      /usr/libexec/mysqld(+0x6c9984) [0x7fbcd56da984]
      /usr/libexec/mysqld(handler::read_range_next()+0x7a) [0x7fbcd54b6dba]
      /usr/libexec/mysqld(handler::multi_range_read_next(void**)+0xb2) [0x7fbcd5460182]
      /usr/libexec/mysqld(Mrr_simple_index_reader::get_next(void**)+0x20) [0x7fbcd5460240]
      /usr/libexec/mysqld(DsMrr_impl::dsmrr_next(void**)+0x2f) [0x7fbcd54604ff]
      /usr/libexec/mysqld(QUICK_RANGE_SELECT::get_next()+0x52) [0x7fbcd558a7b2]
      /usr/libexec/mysqld(QUICK_ROR_INTERSECT_SELECT::get_next()+0x23e) [0x7fbcd558bffe]
      /usr/libexec/mysqld(+0x597b68) [0x7fbcd55a8b68]
      /usr/libexec/mysqld(sub_select(JOIN*, st_join_table*, bool)+0x1ee) [0x7fbcd53aa75e]
      /usr/libexec/mysqld(+0x39ca05) [0x7fbcd53ada05]
      /usr/libexec/mysqld(JOIN::exec()+0x739) [0x7fbcd53c7639]
      /usr/libexec/mysqld(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*)+0x128) [0x7fbcd53c96b8]
      /usr/libexec/mysqld(handle_select(THD*, LEX*, select_result*, unsigned long)+0x2b3) [0x7fbcd53ca2d3]
      /usr/libexec/mysqld(+0x36535f) [0x7fbcd537635f]
      /usr/libexec/mysqld(mysql_execute_command(THD*)+0x30b5) [0x7fbcd537d435]
      /usr/libexec/mysqld(mysql_parse(THD*, char*, unsigned int, Parser_state*)+0x142) [0x7fbcd53805e2]
      /usr/libexec/mysqld(dispatch_command(enum_server_command, THD*, char*, unsigned int)+0x175b) [0x7fbcd5381ddb]
      /usr/libexec/mysqld(do_handle_one_connection(THD*)+0xff) [0x7fbcd543599f]
      /usr/libexec/mysqld(handle_one_connection+0x51) [0x7fbcd5435ae1]
      /usr/libexec/mysqld(+0x829ed8) [0x7fbcd583aed8]
      /lib64/libpthread.so.0(+0x3578c07851) [0x7fbcd4bd9851]
      /lib64/libc.so.6(clone+0x6d) [0x7fbcd34f994d]
       
      Trying to get some variables.
      Some pointers may be invalid and cause the dump to abort.
      Query (0x7fa174dab928): is an invalid pointer
      Connection ID (thread ID): 49263308
      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
       
      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.
      140211 12:43:58 mysqld_safe Number of processes running now: 0
      140211 12:43:58 mysqld_safe mysqld restarted

      Attachments

        Issue Links

          Activity

            People

              jplindst Jan Lindström (Inactive)
              chernomor Sergey Chernomorets (Inactive)
              Votes:
              1 Vote for this issue
              Watchers:
              5 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.