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

rpl.rpl_insert_ignore failed in buildbot, Lost connection to MySQL server during query

    XMLWordPrintable

Details

    • Bug
    • Status: Closed (View Workflow)
    • Major
    • Resolution: Won't Fix
    • 10.1
    • N/A
    • Replication, Tests
    • None

    Description

      http://buildbot.askmonty.org/buildbot/builders/kvm-deb-stretch-ppc64le/builds/1103/steps/mtr/logs/stdio

      rpl.rpl_insert_ignore 'innodb_plugin,row' w4 [ fail ]
              Test ended at 2017-09-27 12:17:19
       
      CURRENT_TEST: rpl.rpl_insert_ignore
      mysqltest: In included file "./include/wait_for_slave_param.inc": 
      included from ./include/wait_for_slave_sql_to_stop.inc at line 36:
      included from ./include/wait_for_slave_to_stop.inc at line 34:
      included from ./include/stop_slave.inc at line 84:
      included from ./include/rpl_for_each_slave.inc at line 33:
      included from ./include/rpl_stop_slaves.inc at line 31:
      included from ./include/rpl_end.inc at line 81:
      included from /usr/share/mysql/mysql-test/suite/rpl/t/rpl_insert_ignore.test at line 16:
      At line 75: query 'let $_slave_check_configured= query_get_value("SHOW SLAVE STATUS", Slave_IO_Running, 1)' failed: 2013: Lost connection to MySQL server during query
       
      The result from queries just before the failure was:
      < snip >
      include/assert.inc [Count of elements in t1 should be 6.]
      include/diff_tables.inc [master:test.t1 , slave:test.t1]
      INSERT IGNORE INTO t1 SELECT NULL, t2.b FROM t2 ORDER BY t2.a;
      include/assert.inc [Count of elements in t1 should be 6.]
      include/assert.inc [In SBR or MIXED modes, the event in the binlog should be the same that was executed. In RBR mode, binlog position should stay unchanged.]
      DROP TABLE t1;
      DROP TABLE t2;
      CREATE TABLE t1 (
      a INT UNSIGNED NOT NULL PRIMARY KEY
      ) ENGINE=myisam;
      CREATE TABLE t2 (
      a INT UNSIGNED
      ) ENGINE=myisam;
      INSERT INTO t1 VALUES (1);
      INSERT INTO t2 VALUES (1);
      INSERT INTO t1 SELECT t2.a FROM t2 ORDER BY t2.a ON DUPLICATE KEY UPDATE t1.a= t1.a;
      include/assert.inc [Sum of elements in t1 should be 1.]
      include/assert.inc [In SBR or MIXED modes, the event in the binlog should be the same that was executed. In RBR mode, binlog position should stay unchanged.]
      drop table t1, t2;
      include/rpl_end.inc
       
      More results from queries before failure can be found in /dev/shm/var/4/log/rpl_insert_ignore.log
       
       
      Server [mysqld.2 - pid: 13703, winpid: 13703, exit: 256] failed during test run
      Server log from this test:
      ----------SERVER LOG START-----------
      2017-09-27 12:17:19 70366544884672 [Note] 'CHANGE MASTER TO executed'. Previous state master_host='127.0.0.1', master_port='16060', master_log_file='', master_log_pos='4'. New state master_host='127.0.0.1', master_port='16060', master_log_file='master-bin.000001', master_log_pos='4'.
      2017-09-27 12:17:19 70366546064320 [Note] Slave SQL thread initialized, starting replication in log 'master-bin.000001' at position 4, relay log './slave-relay-bin.000001' position: 4
      2017-09-27 12:17:19 70366630933440 [Note] Slave I/O thread: connected to master 'root@127.0.0.1:16060',replication started in log 'master-bin.000001' at position 4
      2017-09-27 12:17:19 70366546064320 [Note] Error reading relay log event: slave SQL thread was killed
      2017-09-27 12:17:19 70366546064320 [Note] Slave SQL thread exiting, replication stopped in log 'master-bin.000001' at position 7273
      170927 12:17:19 [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.1.28-MariaDB-1~stretch
      key_buffer_size=1048576
      read_buffer_size=131072
      2017-09-27 12:17:19 70366630933440 [Note] Slave I/O thread exiting, read up to log 'master-bin.000001', position 7273
      max_used_connections=4
      max_threads=153
      thread_count=4
      It is possible that mysqld could use up to 
      key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 62911 K  bytes of memory
      Hope that's ok; if not, decrease some variables in the equation.
       
      Thread pointer: 0x3fff83950008
      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 = 0x3fff7cfb5fe8 thread_stack 0x48400
      /usr/sbin/mysqld(my_print_stacktrace+0x68)[0x271f0a68]
      /usr/sbin/mysqld(handle_fatal_signal+0x430)[0x26bfb310]
      linux-vdso64.so.1(__kernel_sigtramp_rt64+0x0)[0x3fff8a6a04d8]
      /usr/sbin/mysqld(_ZN14rpl_group_info19unmark_start_commitEv+0x34)[0x26af62c4]
      [0x3fff7cfb5750]
      /usr/sbin/mysqld(_Z17ha_rollback_transP3THDb+0x364)[0x26bffd94]
      /usr/sbin/mysqld(_Z14trans_rollbackP3THD+0x78)[0x26b16eb8]
      /usr/sbin/mysqld(_ZN3THD7cleanupEv+0x148)[0x269c8278]
      /usr/sbin/mysqld(_ZN3THDD1Ev+0x7c8)[0x269c8e28]
      /usr/sbin/mysqld(_ZN3THDD0Ev+0x28)[0x269c8fc8]
      /usr/sbin/mysqld(handle_slave_sql+0x1da8)[0x2696cc58]
      /usr/sbin/mysqld(+0x9658b4)[0x26f258b4]
      /lib/powerpc64le-linux-gnu/libpthread.so.0(+0x80dc)[0x3fff8a6580dc]
      /lib/powerpc64le-linux-gnu/libc.so.6(clone+0x98)[0x3fff89d41568]
       
      Trying to get some variables.
      Some pointers may be invalid and cause the dump to abort.
      Query (0x0): 
      Connection ID (thread ID): 16
      Status: KILL_CONNECTION
       
      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,orderby_uses_equalities=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.
      Writing a core file
      ----------SERVER LOG END-------------
       
       
       - saving '/dev/shm/var/4/log/rpl.rpl_insert_ignore-innodb_plugin,row/' to '/dev/shm/var/log/rpl.rpl_insert_ignore-innodb_plugin,row/'
       
      Retrying test rpl.rpl_insert_ignore, attempt(2/3)...
       
      worker[4] > Restart  - not started
      worker[4] > Restart  - not started
      ***Warnings generated in error logs during shutdown after running tests: rpl.rpl_insert_ignore rpl.rpl_insert_id_pk
       
      170927 12:17:19 [ERROR] mysqld got signal 11 ;
      Attempting backtrace. You can use the following information to find out
      

      Attachments

        Activity

          People

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