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

rpl.rpl_parallel_multilevel failed in buildbot, server crashed

    XMLWordPrintable

Details

    • Bug
    • Status: Open (View Workflow)
    • Major
    • Resolution: Unresolved
    • 10.4
    • 10.4
    • Replication, Tests
    • None

    Description

      http://buildbot.askmonty.org/buildbot/builders/mac-1012-bintar/builds/5564

      10.4 c5c515130cac1ae05b21a7836da91a4a

      rpl.rpl_parallel_multilevel 'innodb,stmt' [ fail ]
              Test ended at 2019-07-01 05:38:40
       
      CURRENT_TEST: rpl.rpl_parallel_multilevel
       
       
      Could not execute 'check-testcase' before testcase 'rpl.rpl_parallel_multilevel' (res: 1):
      mysqltest: Logging to '/Users/buildbot/maria-slave/mac-1012-bintar/build/mysql-test/var/tmp/check-mysqld_1.log'.
      mysqltest: Results saved in '/Users/buildbot/maria-slave/mac-1012-bintar/build/mysql-test/var/tmp/check-mysqld_1.result'.
      mysqltest: Connecting to server localhost:16000 (socket /Users/buildbot/maria-slave/mac-1012-bintar/build/mysql-test/var/tmp/mysqld.1.sock) as 'root', connection 'default', attempt 0 ...
      mysqltest: ... Connected.
      mysqltest: Start processing test commands from './include/check-testcase.test' ...
      mysqltest: At line 91: query 'select count(*) from mysql.proc' failed: 2013: Lost connection to MySQL server during query
      not ok
      mysqltest failed but provided no output
      The result from queries just before the failure was:
      < snip >
      

      190701  5:38:40 [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.4.7-MariaDB-log
      key_buffer_size=1048576
      read_buffer_size=131072
      max_used_connections=1
      max_threads=153
      thread_count=8
      It is possible that mysqld could use up to 
      key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 63508 K  bytes of memory
      Hope that's ok; if not, decrease some variables in the equation.
       
      Thread pointer: 0x7f8f0b884208
      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 = 0x700003667e60 thread_stack 0x49000
      0   mysqld                              0x000000010dd7bf2c my_print_stacktrace + 60
      0   mysqld                              0x000000010d45e0c4 handle_fatal_signal + 740
      addr2line: /usr/lib/system/libsystem_platform.dylib: file format not recognized
      0   libsystem_platform.dylib            0x00007fff6f20af5a _sigtramp + 26
      0   ???                                 0x00007f8f0b89d0c0 0x0 + 140252350632128
      0   mysqld                              0x000000010d7d63d1 _ZN11MDL_context27release_transactional_locksEv + 161
      0   mysqld                              0x000000010d6b4181 _Z21mysql_execute_commandP3THD + 32785
      0   mysqld                              0x000000010d6a8a37 _Z11mysql_parseP3THDPcjP12Parser_statebb + 791
      0   mysqld                              0x000000010d6a5c6f _Z16dispatch_command19enum_server_commandP3THDPcjbb + 2383
      0   mysqld                              0x000000010d6a8ed7 _Z10do_commandP3THD + 711
      0   mysqld                              0x000000010d7cad2c _Z24do_handle_one_connectionP7CONNECT + 844
      0   mysqld                              0x000000010d7ca9c8 handle_one_connection + 56
      0   mysqld                              0x000000010dc5169b pfs_spawn_thread + 299
      addr2line: /usr/lib/system/libsystem_pthread.dylib: file format not recognized
      0   libsystem_pthread.dylib             0x00007fff6f214661 _pthread_body + 340
      0   libsystem_pthread.dylib             0x00007fff6f21450d _pthread_body + 0
      0   libsystem_pthread.dylib             0x00007fff6f213bf9 thread_start + 13
       
      Trying to get some variables.
      Some pointers may be invalid and cause the dump to abort.
      Query (0x7f8f0b89d020): is an invalid pointer
      Connection ID (thread ID): 9
      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=on,table_elimination=on,extended_keys=on,exists_to_in=on,orderby_uses_equalities=on,condition_pushdown_for_derived=on,split_materialized=on,condition_pushdown_for_subquery=on,rowid_filter=on,condition_pushdown_from_having=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.
       
      We think the query pointer is invalid, but we will try to print it anyway. 
      Query: select count(*) from mysql.proc
      

      Attachments

        Activity

          People

            sanja Oleksandr Byelkin
            elenst Elena Stepanova
            Votes:
            0 Vote for this issue
            Watchers:
            2 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.