Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Incomplete
    • Affects Version/s: 10.0.13
    • Fix Version/s: N/A
    • Labels:
    • Environment:
      CentOS release 6.5 (X86_64)

      Description

      I got this bug over 50 times.
      I don't know the cause, and I don't get this error now.
      I installed Microsoft ODBC Driver 11 for SQL Server with unixODBC2.3.0.

      140827 16:26:33 [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.0.13-MariaDB
      key_buffer_size=16384
      read_buffer_size=262144
      max_used_connections=1
      max_threads=153
      thread_count=1
      It is possible that mysqld could use up to 
      key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 52121 K  bytes of memory
      Hope that's ok; if not, decrease some variables in the equation.
      
      Thread pointer: 0x0x7f9a343f3008
      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 = 0x7f9a3ccc1d10 thread_stack 0x3c000
      /usr/sbin/mysqld(my_print_stacktrace+0x2b)[0xb7054b]
      /usr/sbin/mysqld(handle_fatal_signal+0x398)[0x727588]
      /lib64/libpthread.so.0[0x362140f710]
      /usr/lib64/mysql/plugin/ha_connect.so(_ZN10ha_connect8rnd_nextEPh+0x12f)[0x7f9a34d3725f]
      /usr/sbin/mysqld(_ZN7handler11ha_rnd_nextEPh+0x16c)[0x72bb5c]
      /usr/sbin/mysqld(_Z13rr_sequentialP11READ_RECORD+0x1a)[0x81392a]
      /usr/sbin/mysqld(_Z10sub_selectP4JOINP13st_join_tableb+0x161)[0x5f66d1]
      /usr/sbin/mysqld[0x60d80d]
      /usr/sbin/mysqld(_ZN4JOIN10exec_innerEv+0xa3d)[0x62067d]
      /usr/sbin/mysqld(_ZN4JOIN4execEv+0x11)[0x6224f1]
      /usr/sbin/mysqld(_Z12mysql_selectP3THDPPP4ItemP10TABLE_LISTjR4ListIS1_ES2_jP8st_orderSB_S2_SB_yP13select_resultP18st_select_lex_unitP13st_select_lex+0x1dd)[0x61f0bd]
      /usr/sbin/mysqld(_Z13handle_selectP3THDP3LEXP13select_resultm+0x28d)[0x62284d]
      /usr/sbin/mysqld[0x5ca456]
      /usr/sbin/mysqld(_Z21mysql_execute_commandP3THD+0x4c4f)[0x5d51af]
      /usr/sbin/mysqld[0x5d6cc2]
      /usr/sbin/mysqld(_Z16dispatch_command19enum_server_commandP3THDPcj+0x1b20)[0x5d8e80]
      /usr/sbin/mysqld(_Z24do_handle_one_connectionP3THD+0x453)[0x696993]
      /usr/sbin/mysqld(handle_one_connection+0x42)[0x696a62]
      /lib64/libpthread.so.0[0x36214079d1]
      /lib64/libc.so.6(clone+0x6d)[0x36210e8b5d]
      
      Trying to get some variables.
      Some pointers may be invalid and cause the dump to abort.
      Query (0x7f9a22871020): is an invalid pointer
      Connection ID (thread ID): 2
      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=on,exists_to_in=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.
      

        Gliffy Diagrams

          Attachments

            Activity

            Hide
            elenst Elena Stepanova added a comment - - edited

            Hi,

            Were you using the Connect engine extensively? Have you stopped using it, or upgraded the server, or what else could have changed before you stopped observed the bug?

            Show
            elenst Elena Stepanova added a comment - - edited Hi, Were you using the Connect engine extensively? Have you stopped using it, or upgraded the server, or what else could have changed before you stopped observed the bug?
            Hide
            elenst Elena Stepanova added a comment -

            Closing as incomplete for now, please comment to re-open if you have additional information.

            Show
            elenst Elena Stepanova added a comment - Closing as incomplete for now, please comment to re-open if you have additional information.

              People

              • Assignee:
                Unassigned
                Reporter:
                takuya Takuya Aoki
              • Votes:
                0 Vote for this issue
                Watchers:
                4 Start watching this issue

                Dates

                • Due:
                  Created:
                  Updated:
                  Resolved: