[MDEV-14277] binlog_encryption.rpl_parallel failed in buildbot, timeout, assertion `count > 0' failed Created: 2017-11-03  Updated: 2020-09-08  Resolved: 2020-09-08

Status: Closed
Project: MariaDB Server
Component/s: Tests
Affects Version/s: 10.1
Fix Version/s: N/A

Type: Bug Priority: Major
Reporter: Alice Sherepa Assignee: Unassigned
Resolution: Duplicate Votes: 0
Labels: None

Issue Links:
Duplicate
duplicates MDEV-10653 SHOW SLAVE STATUS Can Deadlock an Err... Closed
Relates
relates to MDEV-12979 rpl.rpl_parallel_mdev6589 fails in bu... Closed

 Description   

http://buildbot.askmonty.org/buildbot/builders/kvm-fulltest2/builds/10242/steps/test_3/logs/stdio

binlog_encryption.rpl_parallel 'innodb_plugin,stmt' w1 [ fail ]  timeout after 900 seconds
 
        Test ended at 2017-11-02 23:23:26
 
 
 
Test case timeout after 900 seconds
 
 
 
== /mnt/buildbot/build/mariadb-10.1.29/mysql-test/var/1/log/rpl_parallel.log == 
64	64
 
65	65
 
66	66
 
67	67
 
68	68
 
69	69
 
70	70
 
SET debug_sync='RESET';
 
SET debug_sync='now SIGNAL d0_cont';
 
SET debug_sync='now WAIT_FOR t1_waiting';
 
SET debug_sync='now SIGNAL d3_cont';
 
SET debug_sync='now WAIT_FOR t2_waiting';
 
SET debug_sync='now SIGNAL d1_cont';
 
SET debug_sync='now WAIT_FOR t3_waiting';
 
SET debug_sync='now SIGNAL d2_cont';
 
SET debug_sync='now WAIT_FOR t4_waiting';
 
KILL THD_ID;
 
SET debug_sync='now WAIT_FOR t3_killed';
 
SET debug_sync='now SIGNAL t1_cont';
 
include/wait_for_slave_sql_error.inc [errno=1317,1927,1964]
 
 
 
 == /mnt/buildbot/build/mariadb-10.1.29/mysql-test/var/1/tmp/analyze-timeout-mysqld.2.err ==
 
mysqltest: Could not open connection 'default' after 500 attempts: 2002 Can't connect to local MySQL server through socket '/mnt/buildbot/build/mariadb-10.1.29/mysql-test/var/tmp/1/mysqld.2.sock' (111 "Connection refused")
 
 
 
 == /mnt/buildbot/build/mariadb-10.1.29/mysql-test/var/1/tmp/analyze-timeout-mysqld.1.err ==
 
mysqltest: Could not open connection 'default' after 500 attempts: 2002 Can't connect to local MySQL server through socket '/mnt/buildbot/build/mariadb-10.1.29/mysql-test/var/tmp/1/mysqld.1.sock' (111 "Connection refused")



 Comments   
Comment by Alice Sherepa [ 2017-11-17 ]

http://buildbot.askmonty.org/buildbot/builders/kvm-fulltest2/builds/10438/steps/mtr_nm/logs/stdio, Assertion `count > 0' failed.

binlog_encryption.rpl_parallel 'row,xtradb' w1 [ fail ]
 
        Test ended at 2017-11-16 17:54:36
 
 
 
CURRENT_TEST: binlog_encryption.rpl_parallel
 
mysqltest: In included file "./include/wait_for_slave_param.inc": 
included from ./include/wait_for_slave_sql_error.inc at line 41:
 
included from ./extra/rpl_tests/rpl_parallel.inc at line 1476:
 
included from /mnt/buildbot/build/mariadb-10.1.30/mysql-test/suite/binlog_encryption/rpl_parallel.test at line 2:
 
At line 119: query 'let $_show_slave_status_value= query_get_value("SHOW SLAVE STATUS", $slave_param, 1)' failed: 2013: Lost connection to MySQL server during query
 
 
 
The result from queries just before the failure was:
 
< snip >
 
INSERT INTO t2 VALUES (32);
 
SET sql_log_bin= 1;
 
INSERT INTO t2 VALUES (32);
 
FLUSH LOGS;
 
INSERT INTO t2 VALUES (33);
 
INSERT INTO t2 VALUES (34);
 
SELECT * FROM t2 WHERE a >= 30 ORDER BY a;
 
a
 
31
 
32
 
33
 
34
 
include/save_master_gtid.inc
 
include/wait_for_slave_sql_error.inc [errno=1062]
 
include/stop_slave_io.inc
 
SET GLOBAL slave_parallel_threads=10;
 
START SLAVE;
 
include/wait_for_slave_sql_error.inc [errno=1062]
 
START SLAVE SQL_THREAD;
 
include/wait_for_slave_sql_error.inc [errno=1062]
 
 
 
More results from queries before failure can be found in /mnt/buildbot/build/mariadb-10.1.30/mysql-test/var/1/log/rpl_parallel.log
 
 
 
 
 
Server [mysqld.2 - pid: 9429, winpid: 9429, exit: 256] failed during test run
 
Server log from this test:
 
----------SERVER LOG START-----------
 
2017-11-16 17:54:27 3071969600 [Note] /mnt/buildbot/build/mariadb-10.1.30/sql/mysqld (mysqld 10.1.30-MariaDB-debug) starting as process 9430 ...
 
2017-11-16 17:54:27 3071969600 [Warning] Could not increase number of max_open_files to more than 1024 (request: 4162)
 
2017-11-16 17:54:27 3071969600 [Note] Plugin 'SEQUENCE' is disabled.
 
2017-11-16 17:54:27 3071969600 [Note] Plugin 'partition' is disabled.
 
innodb_open_files should not be greater than the open_files_limit.
 
2017-11-16 17:54:27 3071969600 [Note] InnoDB: innodb_empty_free_list_algorithm has been changed to legacy because of small buffer pool size. In order to use backoff, increase buffer pool at least up to 20MB.
 
 
 
2017-11-16 17:54:27 3071969600 [Note] InnoDB: Using mutexes to ref count buffer pool pages
 
2017-11-16 17:54:27 3071969600 [Note] InnoDB:  InnoDB: !!!!!!!! UNIV_DEBUG switched on !!!!!!!!!
 
2017-11-16 17:54:27 3071969600 [Note] InnoDB:  InnoDB: !!!!!!!! UNIV_SYNC_DEBUG switched on !!!!!!!!!
 
2017-11-16 17:54:27 3071969600 [Note] InnoDB: The InnoDB memory heap is disabled
 
2017-11-16 17:54:27 3071969600 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
 
2017-11-16 17:54:27 3071969600 [Note] InnoDB: GCC builtin __sync_synchronize() is used for memory barrier
 
2017-11-16 17:54:27 3071969600 [Note] InnoDB: Compressed tables use zlib 1.2.3.4
 
2017-11-16 17:54:27 3071969600 [Note] InnoDB: Using Linux native AIO
 
2017-11-16 17:54:27 3071969600 [Note] InnoDB: Using generic crc32 instructions
 
2017-11-16 17:54:27 3071969600 [Note] InnoDB: Initializing buffer pool, size = 8.0M
 
2017-11-16 17:54:27 3071969600 [Note] InnoDB: Completed initialization of buffer pool
 
2017-11-16 17:54:27 3071969600 [Note] InnoDB: Highest supported file format is Barracuda.
 
2017-11-16 17:54:29 3071969600 [Note] InnoDB: 128 rollback segment(s) are active.
 
2017-11-16 17:54:29 3071969600 [Note] InnoDB: Waiting for purge to start
 
2017-11-16 17:54:29 3071969600 [Note] InnoDB:  Percona XtraDB (http://www.percona.com) 5.6.36-82.2 started; log sequence number 1629415
 
2017-11-16 17:54:29 2825902912 [Note] InnoDB: Dumping buffer pool(s) not yet started
 
2017-11-16 17:54:29 3071969600 [Note] Plugin 'INNODB_SYS_DATAFILES' is disabled.
 
2017-11-16 17:54:29 3071969600 [Note] Plugin 'INNODB_SYS_TABLESTATS' is disabled.
 
2017-11-16 17:54:29 3071969600 [Note] Plugin 'INNODB_SYS_INDEXES' is disabled.
 
2017-11-16 17:54:29 3071969600 [Note] Plugin 'XTRADB_RSEG' is disabled.
 
2017-11-16 17:54:29 3071969600 [Note] Plugin 'CHANGED_PAGE_BITMAPS' is disabled.
 
2017-11-16 17:54:29 3071969600 [Note] Plugin 'INNODB_FT_BEING_DELETED' is disabled.
 
2017-11-16 17:54:29 3071969600 [Note] Plugin 'INNODB_LOCK_WAITS' is disabled.
 
2017-11-16 17:54:29 3071969600 [Note] Plugin 'INNODB_TABLESPACES_ENCRYPTION' is disabled.
 
2017-11-16 17:54:29 3071969600 [Note] Plugin 'XTRADB_INTERNAL_HASH_TABLES' is disabled.
 
2017-11-16 17:54:29 3071969600 [Note] Plugin 'INNODB_SYS_FIELDS' is disabled.
 
2017-11-16 17:54:29 3071969600 [Note] Plugin 'INNODB_CMPMEM_RESET' is disabled.
 
2017-11-16 17:54:29 3071969600 [Note] Plugin 'FEEDBACK' is disabled.
 
2017-11-16 17:54:29 3071969600 [Note] Plugin 'INNODB_CMP' is disabled.
 
2017-11-16 17:54:29 3071969600 [Note] Plugin 'INNODB_FT_INDEX_TABLE' is disabled.
 
2017-11-16 17:54:29 3071969600 [Note] Plugin 'INNODB_SYS_TABLESPACES' is disabled.
 
2017-11-16 17:54:29 3071969600 [Note] Plugin 'INNODB_MUTEXES' is disabled.
 
2017-11-16 17:54:29 3071969600 [Note] Plugin 'INNODB_CMP_RESET' is disabled.
 
2017-11-16 17:54:29 3071969600 [Note] Plugin 'INNODB_FT_INDEX_CACHE' is disabled.
 
2017-11-16 17:54:29 3071969600 [Note] Plugin 'INNODB_FT_DEFAULT_STOPWORD' is disabled.
 
2017-11-16 17:54:29 3071969600 [Note] Plugin 'INNODB_SYS_COLUMNS' is disabled.
 
2017-11-16 17:54:29 3071969600 [Note] Plugin 'INNODB_FT_CONFIG' is disabled.
 
2017-11-16 17:54:29 3071969600 [Note] Plugin 'INNODB_CMP_PER_INDEX_RESET' is disabled.
 
2017-11-16 17:54:29 3071969600 [Note] Plugin 'XTRADB_READ_VIEW' is disabled.
 
2017-11-16 17:54:29 3071969600 [Note] Plugin 'INNODB_SYS_SEMAPHORE_WAITS' is disabled.
 
2017-11-16 17:54:29 3071969600 [Note] Plugin 'INNODB_CHANGED_PAGES' is disabled.
 
2017-11-16 17:54:29 3071969600 [Note] Plugin 'INNODB_FT_DELETED' is disabled.
 
2017-11-16 17:54:29 3071969600 [Note] Plugin 'INNODB_TABLESPACES_SCRUBBING' is disabled.
 
2017-11-16 17:54:29 3071969600 [Warning] /mnt/buildbot/build/mariadb-10.1.30/sql/mysqld: unknown option '--loose-pam-debug'
 
2017-11-16 17:54:29 3071969600 [Note] Server socket created on IP: '127.0.0.1'.
 
2017-11-16 17:54:29 3071969600 [Note] /mnt/buildbot/build/mariadb-10.1.30/sql/mysqld: ready for connections.
 
Version: '10.1.30-MariaDB-debug'  socket: '/mnt/buildbot/build/mariadb-10.1.30/mysql-test/var/tmp/1/mysqld.2.sock'  port: 16001  Source distribution
 
2017-11-16 17:54:29 2865753920 [Note] 'CHANGE MASTER TO executed'. Previous state master_host='', master_port='3306', master_log_file='', master_log_pos='4'. New state master_host='127.0.0.1', master_port='16000', master_log_file='master-bin.000001', master_log_pos='4'.
 
2017-11-16 17:54:29 2865147712 [Note] Slave I/O thread: connected to master 'root@127.0.0.1:16000',replication started in log 'master-bin.000001' at position 4
 
2017-11-16 17:54:29 2846871360 [Note] Slave SQL thread initialized, starting replication in log 'master-bin.000001' at position 4, relay log './slave-relay-bin.000001' position: 4
 
2017-11-16 17:54:29 2846871360 [Note] Error reading relay log event: slave SQL thread was killed
 
2017-11-16 17:54:29 2846871360 [Note] Slave SQL thread exiting, replication stopped in log 'master-bin.000001' at position 350
 
2017-11-16 17:54:29 2865147712 [Note] Slave I/O thread exiting, read up to log 'master-bin.000001', position 350
 
2017-11-16 17:54:29 2865753920 [Note] 'CHANGE MASTER TO executed'. Previous state master_host='127.0.0.1', master_port='16000', master_log_file='master-bin.000001', master_log_pos='350'. New state master_host='127.0.0.1', master_port='16000', master_log_file='master-bin.000001', master_log_pos='350'.
 
2017-11-16 17:54:29 2865753920 [Note] Previous Using_Gtid=No. New Using_Gtid=Slave_Pos
 
2017-11-16 17:54:29 2865147712 [Note] Slave I/O thread: connected to master 'root@127.0.0.1:16000',replication starts at GTID position ''
 
2017-11-16 17:54:29 2846871360 [Note] Slave SQL thread initialized, starting replication in log 'master-bin.000001' at position 350, relay log './slave-relay-bin.000001' position: 4; GTID position ''
 
2017-11-16 17:54:29 2846871360 [Note] Error reading relay log event: slave SQL thread was killed
 
2017-11-16 17:54:29 2846871360 [Note] Slave SQL thread exiting, replication stopped in log 'master-bin.000001' at position 350; GTID position ''
 
2017-11-16 17:54:29 2865147712 [Note] Slave I/O thread exiting, read up to log 'master-bin.000001', position 350; GTID position 
2017-11-16 17:54:29 2846871360 [Note] Slave I/O thread: connected to master 'root@127.0.0.1:16000',replication starts at GTID position ''
 
2017-11-16 17:54:29 2807295808 [Note] Slave SQL thread initialized, starting replication in log 'master-bin.000001' at position 350, relay log './slave-relay-bin.000001' position: 4; GTID position ''
 
2017-11-16 17:54:29 2807295808 [Note] Error reading relay log event: slave SQL thread was killed
 
2017-11-16 17:54:29 2807295808 [Note] Slave SQL thread exiting, replication stopped in log 'master-bin.000001' at position 1936; GTID position '0-1-9,1-1-1'
 
2017-11-16 17:54:29 2846871360 [Note] Slave I/O thread exiting, read up to log 'master-bin.000001', position 1936; GTID position 1-1-1,0-1-9
 
2017-11-16 17:54:29 2806386496 [Note] Slave I/O thread: connected to master 'root@127.0.0.1:16000',replication starts at GTID position '1-1-1,0-1-9'
 
2017-11-16 17:54:29 2807295808 [Note] Slave SQL thread initialized, starting replication in log 'master-bin.000001' at position 1936, relay log './slave-relay-bin.000001' position: 4; GTID position '0-1-9,1-1-1'
 
2017-11-16 17:54:30 2807295808 [Note] Error reading relay log event: slave SQL thread was killed
 
2017-11-16 17:54:30 2807295808 [Note] Slave SQL thread exiting, replication stopped in log 'master-bin.000001' at position 2495; GTID position '0-1-9,1-1-2,2-1-1'
 
2017-11-16 17:54:30 2806386496 [Note] Slave I/O thread exiting, read up to log 'master-bin.000001', position 2495; GTID position 1-1-2,2-1-1,0-1-9
 
2017-11-16 17:54:30 2807295808 [Note] Slave I/O thread: connected to master 'root@127.0.0.1:16000',replication starts at GTID position '1-1-2,0-1-9,2-1-1'
 
2017-11-16 17:54:30 2807902016 [Note] Slave SQL thread initialized, starting replication in log 'master-bin.000001' at position 2495, relay log './slave-relay-bin.000001' position: 4; GTID position '0-1-9,1-1-2,2-1-1'
 
2017-11-16 17:54:30 2807902016 [Note] Error reading relay log event: slave SQL thread was killed
 
2017-11-16 17:54:30 2807902016 [Note] Slave SQL thread exiting, replication stopped in log 'master-bin.000002' at position 1481; GTID position '0-1-14,1-1-2,2-1-1'
 
2017-11-16 17:54:30 2807295808 [Note] Slave I/O thread exiting, read up to log 'master-bin.000002', position 1481; GTID position 1-1-2,0-1-14,2-1-1
 
2017-11-16 17:54:30 2807902016 [Note] Slave I/O thread: connected to master 'root@127.0.0.1:16000',replication starts at GTID position '1-1-2,0-1-14,2-1-1'
 
2017-11-16 17:54:30 2806992704 [Note] Slave SQL thread initialized, starting replication in log 'master-bin.000002' at position 1481, relay log './slave-relay-bin.000001' position: 4; GTID position '0-1-14,1-1-2,2-1-1'
 
2017-11-16 17:54:30 2806992704 [Note] Error reading relay log event: slave SQL thread was killed
 
2017-11-16 17:54:30 2806992704 [Note] Slave SQL thread exiting, replication stopped in log 'master-bin.000002' at position 1906; GTID position '0-1-15,1-1-2,2-1-1'
 
2017-11-16 17:54:30 2807902016 [Note] Slave I/O thread exiting, read up to log 'master-bin.000002', position 2220; GTID position 1-1-2,0-1-17,2-1-1
 
2017-11-16 17:54:30 2806992704 [Note] Slave I/O thread: connected to master 'root@127.0.0.1:16000',replication starts at GTID position '1-1-2,0-1-15,2-1-1'
 
2017-11-16 17:54:30 2808205120 [Note] Slave SQL thread initialized, starting replication in log 'master-bin.000002' at position 1906, relay log './slave-relay-bin.000001' position: 4; GTID position '0-1-15,1-1-2,2-1-1'
 
2017-11-16 17:54:30 2808205120 [Note] Error reading relay log event: slave SQL thread was killed
 
2017-11-16 17:54:30 2808205120 [Note] Slave SQL thread exiting, replication stopped in log 'master-bin.000002' at position 2220; GTID position '0-1-17,1-1-2,2-1-1'
 
2017-11-16 17:54:30 2806992704 [Note] Slave I/O thread exiting, read up to log 'master-bin.000002', position 2220; GTID position 1-1-2,0-1-17,2-1-1
 
2017-11-16 17:54:30 2808205120 [Note] Slave I/O thread: connected to master 'root@127.0.0.1:16000',replication starts at GTID position '1-1-2,0-1-17,2-1-1'
 
2017-11-16 17:54:30 2807598912 [Note] Slave SQL thread initialized, starting replication in log 'master-bin.000002' at position 2220, relay log './slave-relay-bin.000001' position: 4; GTID position '0-1-17,1-1-2,2-1-1'
 
2017-11-16 17:54:31 2808811328 [ERROR] Slave SQL: Connection was killed, Gtid 0-1-19, Internal MariaDB error code: 1927
 
2017-11-16 17:54:31 2808811328 [Warning] Slave: Connection was killed Error_code: 1927
 
2017-11-16 17:54:31 2808811328 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'master-bin.000002' position 2220; GTID position '0-1-17,1-1-2,2-1-1'
 
2017-11-16 17:54:31 2807598912 [Note] Error reading relay log event: slave SQL thread was killed
 
2017-11-16 17:54:31 2846871360 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964
 
2017-11-16 17:54:31 2846871360 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964
 
2017-11-16 17:54:31 2846871360 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'master-bin.000002' position 2220; GTID position '0-1-17,1-1-2,2-1-1'
 
2017-11-16 17:54:31 2807598912 [Note] Slave SQL thread exiting, replication stopped in log 'master-bin.000002' at position 2503; GTID position '0-1-18,1-1-2,2-1-1'
 
2017-11-16 17:54:31 2808205120 [Note] Slave I/O thread exiting, read up to log 'master-bin.000002', position 3106; GTID position 1-1-2,0-1-20,2-1-1
 
2017-11-16 17:54:31 2808205120 [Note] Slave I/O thread: connected to master 'root@127.0.0.1:16000',replication starts at GTID position '1-1-2,0-1-18,2-1-1'
 
2017-11-16 17:54:31 2807598912 [Note] Slave SQL thread initialized, starting replication in log 'master-bin.000002' at position 2503, relay log './slave-relay-bin.000001' position: 4; GTID position '0-1-18,1-1-2,2-1-1'
 
2017-11-16 17:54:31 2807598912 [Note] Error reading relay log event: slave SQL thread was killed
 
2017-11-16 17:54:31 2807598912 [Note] Slave SQL thread exiting, replication stopped in log 'master-bin.000002' at position 3251; GTID position '0-1-21,1-1-2,2-1-1'
 
2017-11-16 17:54:31 2808205120 [Note] Slave I/O thread exiting, read up to log 'master-bin.000002', position 3251; GTID position 1-1-2,0-1-21,2-1-1
 
2017-11-16 17:54:31 2809114432 [Note] Slave I/O thread: connected to master 'root@127.0.0.1:16000',replication starts at GTID position '1-1-2,0-1-21,2-1-1'
 
2017-11-16 17:54:31 2807598912 [Note] Slave SQL thread initialized, starting replication in log 'master-bin.000002' at position 3251, relay log './slave-relay-bin.000001' position: 4; GTID position '0-1-21,1-1-2,2-1-1'
 
2017-11-16 17:54:31 2806386496 [ERROR] Slave SQL: Connection was killed, Gtid 0-1-23, Internal MariaDB error code: 1927
 
2017-11-16 17:54:31 2806386496 [Warning] Slave: Connection was killed Error_code: 1927
 
2017-11-16 17:54:31 2806386496 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'master-bin.000002' position 3251; GTID position '0-1-21,1-1-2,2-1-1'
 
2017-11-16 17:54:31 2807598912 [Note] Error reading relay log event: slave SQL thread was killed
 
2017-11-16 17:54:31 2865147712 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964
 
2017-11-16 17:54:31 2865147712 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964
 
2017-11-16 17:54:31 2865147712 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'master-bin.000002' position 3251; GTID position '0-1-21,1-1-2,2-1-1'
 
2017-11-16 17:54:31 2807598912 [Note] Slave SQL thread exiting, replication stopped in log 'master-bin.000002' at position 3534; GTID position '0-1-22,1-1-2,2-1-1'
 
2017-11-16 17:54:31 2806386496 [Note] Slave SQL thread initialized, starting replication in log 'master-bin.000002' at position 3534, relay log './slave-relay-bin.000001' position: 4; GTID position '0-1-22,1-1-2,2-1-1'
 
2017-11-16 17:54:31 2806386496 [Note] Error reading relay log event: slave SQL thread was killed
 
2017-11-16 17:54:31 2806386496 [Note] Slave SQL thread exiting, replication stopped in log 'master-bin.000002' at position 4282; GTID position '0-1-25,1-1-2,2-1-1'
 
2017-11-16 17:54:31 2809114432 [Note] Slave I/O thread exiting, read up to log 'master-bin.000002', position 4282; GTID position 1-1-2,0-1-25,2-1-1
 
2017-11-16 17:54:31 2846871360 [Note] Slave I/O thread: connected to master 'root@127.0.0.1:16000',replication starts at GTID position '1-1-2,0-1-25,2-1-1'
 
2017-11-16 17:54:31 2807598912 [Note] Slave SQL thread initialized, starting replication in log 'master-bin.000002' at position 4282, relay log './slave-relay-bin.000001' position: 4; GTID position '0-1-25,1-1-2,2-1-1'
 
2017-11-16 17:54:31 2807598912 [Note] Error reading relay log event: slave SQL thread was killed
 
2017-11-16 17:54:31 2807598912 [Note] Slave SQL thread exiting, replication stopped in log 'master-bin.000002' at position 4282; GTID position '0-1-25,1-1-2,2-1-1'
 
2017-11-16 17:54:31 2846871360 [Note] Slave I/O thread exiting, read up to log 'master-bin.000002', position 4282; GTID position 1-1-2,0-1-25,2-1-1
 
2017-11-16 17:54:31 2865753920 [Note] 'CHANGE MASTER TO executed'. Previous state master_host='127.0.0.1', master_port='16000', master_log_file='master-bin.000002', master_log_pos='4282'. New state master_host='127.0.0.1', master_port='16000', master_log_file='master-bin.000002', master_log_pos='4282'.
 
2017-11-16 17:54:31 2865753920 [Note] Previous Using_Gtid=Slave_Pos. New Using_Gtid=No
 
2017-11-16 17:54:31 2806992704 [Note] Slave SQL thread initialized, starting replication in log 'master-bin.000002' at position 4282, relay log './slave-relay-bin.000001' position: 4
 
2017-11-16 17:54:31 2807598912 [Note] Slave I/O thread: connected to master 'root@127.0.0.1:16000',replication started in log 'master-bin.000002' at position 4282
 
2017-11-16 17:54:32 2806689600 [ERROR] Slave SQL: Connection was killed, Gtid 0-1-27, Internal MariaDB error code: 1927
 
2017-11-16 17:54:32 2806689600 [Warning] Slave: Connection was killed Error_code: 1927
 
2017-11-16 17:54:32 2806689600 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'master-bin.000002' position 4282
 
2017-11-16 17:54:32 2807295808 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964
 
2017-11-16 17:54:32 2807295808 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964
 
2017-11-16 17:54:32 2807295808 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'master-bin.000002' position 4282
 
2017-11-16 17:54:32 2806992704 [Note] Error reading relay log event: slave SQL thread was killed
 
2017-11-16 17:54:32 2806992704 [Note] Slave SQL thread exiting, replication stopped in log 'master-bin.000002' at position 4565
 
2017-11-16 17:54:32 2806992704 [Note] Slave SQL thread initialized, starting replication in log 'master-bin.000002' at position 4565, relay log './slave-relay-bin.000002' position: 821
 
2017-11-16 17:54:32 2806992704 [Note] Error reading relay log event: slave SQL thread was killed
 
2017-11-16 17:54:32 2806992704 [Note] Slave SQL thread exiting, replication stopped in log 'master-bin.000002' at position 5313
 
2017-11-16 17:54:32 2807598912 [Note] Slave I/O thread exiting, read up to log 'master-bin.000002', position 5313
 
2017-11-16 17:54:32 2865753920 [Note] 'CHANGE MASTER TO executed'. Previous state master_host='127.0.0.1', master_port='16000', master_log_file='master-bin.000002', master_log_pos='5313'. New state master_host='127.0.0.1', master_port='16000', master_log_file='master-bin.000002', master_log_pos='5313'.
 
2017-11-16 17:54:32 2865753920 [Note] Previous Using_Gtid=No. New Using_Gtid=Slave_Pos
 
2017-11-16 17:54:32 2808508224 [Note] Slave I/O thread: connected to master 'root@127.0.0.1:16000',replication starts at GTID position '1-1-2,0-1-29,2-1-1'
 
2017-11-16 17:54:32 2806992704 [Note] Slave SQL thread initialized, starting replication in log 'master-bin.000002' at position 5313, relay log './slave-relay-bin.000001' position: 4; GTID position '0-1-29,1-1-2,2-1-1'
 
2017-11-16 17:54:32 2806992704 [Note] Error reading relay log event: slave SQL thread was killed
 
2017-11-16 17:54:32 2806992704 [Note] Slave SQL thread exiting, replication stopped in log 'master-bin.000002' at position 5313; GTID position '0-1-29,1-1-2,2-1-1'
 
2017-11-16 17:54:32 2808508224 [Note] Slave I/O thread exiting, read up to log 'master-bin.000002', position 5313; GTID position 1-1-2,0-1-29,2-1-1
 
2017-11-16 17:54:32 2808508224 [Note] Slave I/O thread: connected to master 'root@127.0.0.1:16000',replication starts at GTID position '1-1-2,0-1-29,2-1-1'
 
2017-11-16 17:54:32 2806992704 [Note] Slave SQL thread initialized, starting replication in log 'master-bin.000002' at position 5313, relay log './slave-relay-bin.000001' position: 4; GTID position '0-1-29,1-1-2,2-1-1'
 
2017-11-16 17:54:32 2807598912 [ERROR] Slave SQL: Connection was killed, Gtid 0-1-33, Internal MariaDB error code: 1927
 
2017-11-16 17:54:32 2807598912 [Warning] Slave: Connection was killed Error_code: 1927
 
2017-11-16 17:54:32 2807598912 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'master-bin.000002' position 6965; GTID position '0-1-30,1-1-3,2-1-2,3-1-1'
 
2017-11-16 17:54:32 2806992704 [Note] Error reading relay log event: slave SQL thread was killed
 
2017-11-16 17:54:32 2806992704 [Note] Slave SQL thread exiting, replication stopped in log 'master-bin.000002' at position 7208; GTID position '0-1-31,1-1-3,2-1-2,3-1-1'
 
2017-11-16 17:54:32 2808508224 [Note] Slave I/O thread exiting, read up to log 'master-bin.000002', position 7727; GTID position 1-1-3,0-1-34,3-1-1,2-1-2
 
2017-11-16 17:54:32 2808508224 [Note] Slave I/O thread: connected to master 'root@127.0.0.1:16000',replication starts at GTID position '1-1-3,0-1-31,3-1-1,2-1-2'
 
2017-11-16 17:54:32 2806992704 [Note] Slave SQL thread initialized, starting replication in log 'master-bin.000002' at position 7208, relay log './slave-relay-bin.000001' position: 4; GTID position '0-1-31,1-1-3,2-1-2,3-1-1'
 
2017-11-16 17:54:32 2806992704 [Note] Error reading relay log event: slave SQL thread was killed
 
2017-11-16 17:54:32 2806992704 [Note] Slave SQL thread exiting, replication stopped in log 'master-bin.000002' at position 7885; GTID position '0-1-35,1-1-3,2-1-2,3-1-1'
 
2017-11-16 17:54:32 2808508224 [Note] Slave I/O thread exiting, read up to log 'master-bin.000002', position 7885; GTID position 1-1-3,0-1-35,3-1-1,2-1-2
 
2017-11-16 17:54:32 2808811328 [Note] Slave SQL thread initialized, starting replication in log 'master-bin.000002' at position 7885, relay log './slave-relay-bin.000001' position: 4; GTID position '0-1-35,1-1-3,2-1-2,3-1-1'
 
2017-11-16 17:54:32 2806992704 [Note] Slave I/O thread: connected to master 'root@127.0.0.1:16000',replication starts at GTID position '1-1-3,0-1-35,3-1-1,2-1-2'
 
2017-11-16 17:54:33 2808811328 [ERROR] Slave SQL: Connection was killed, Internal MariaDB error code: 1927
 
2017-11-16 17:54:33 2808811328 [Warning] Slave: Connection was killed Error_code: 1927
 
2017-11-16 17:54:33 2808811328 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'master-bin.000002' position 7885; GTID position '0-1-35,1-1-3,2-1-2,3-1-1'
 
2017-11-16 17:54:33 2808811328 [Note] Slave SQL thread exiting, replication stopped in log 'master-bin.000002' at position 8112; GTID position '0-1-36,1-1-3,2-1-2,3-1-1'
 
2017-11-16 17:54:33 2806992704 [Note] Slave I/O thread exiting, read up to log 'master-bin.000002', position 18278; GTID position 1-1-3,0-1-37,3-1-1,2-1-2
 
2017-11-16 17:54:33 2806992704 [Note] Slave I/O thread: connected to master 'root@127.0.0.1:16000',replication starts at GTID position '1-1-3,0-1-36,3-1-1,2-1-2'
 
2017-11-16 17:54:33 2808205120 [Note] Slave SQL thread initialized, starting replication in log 'master-bin.000002' at position 8112, relay log './slave-relay-bin.000001' position: 4; GTID position '0-1-36,1-1-3,2-1-2,3-1-1'
 
2017-11-16 17:54:33 2808205120 [Note] Error reading relay log event: slave SQL thread was killed
 
2017-11-16 17:54:33 2808205120 [Note] Slave SQL thread exiting, replication stopped in log 'master-bin.000002' at position 18434; GTID position '0-1-38,1-1-3,2-1-2,3-1-1'
 
2017-11-16 17:54:33 2806992704 [Note] Slave I/O thread exiting, read up to log 'master-bin.000002', position 18434; GTID position 1-1-3,0-1-38,3-1-1,2-1-2
 
2017-11-16 17:54:33 2808205120 [Note] Slave I/O thread: connected to master 'root@127.0.0.1:16000',replication starts at GTID position '1-1-3,0-1-38,3-1-1,2-1-2'
 
2017-11-16 17:54:33 2807902016 [Note] Slave SQL thread initialized, starting replication in log 'master-bin.000002' at position 18434, relay log './slave-relay-bin.000001' position: 4; GTID position '0-1-38,1-1-3,2-1-2,3-1-1'
 
2017-11-16 17:54:33 2807902016 [Note] Error reading relay log event: slave SQL thread was killed
 
2017-11-16 17:54:33 2807902016 [Note] Slave SQL thread exiting, replication stopped in log 'master-bin.000002' at position 18434; GTID position '0-1-38,1-1-3,2-1-2,3-1-1'
 
2017-11-16 17:54:33 2808205120 [Note] Slave I/O thread exiting, read up to log 'master-bin.000002', position 18434; GTID position 1-1-3,0-1-38,3-1-1,2-1-2
 
2017-11-16 17:54:33 2807902016 [Note] Slave I/O thread: connected to master 'root@127.0.0.1:16000',replication starts at GTID position '1-1-3,0-1-38,3-1-1,2-1-2'
 
2017-11-16 17:54:33 2808205120 [Note] Slave SQL thread initialized, starting replication in log 'master-bin.000002' at position 18434, relay log './slave-relay-bin.000001' position: 4; GTID position '0-1-38,1-1-3,2-1-2,3-1-1'
 
2017-11-16 17:54:33 2808205120 [Note] Error reading relay log event: slave SQL thread was killed
 
2017-11-16 17:54:33 2808205120 [Note] Slave SQL thread exiting, replication stopped in log 'master-bin.000002' at position 19304; GTID position '0-1-44,1-1-3,2-1-2,3-1-1'
 
2017-11-16 17:54:33 2807902016 [Note] Slave I/O thread exiting, read up to log 'master-bin.000002', position 19304; GTID position 1-1-3,0-1-44,3-1-1,2-1-2
 
2017-11-16 17:54:33 2808508224 [Note] Slave I/O thread: connected to master 'root@127.0.0.1:16000',replication starts at GTID position '1-1-3,0-1-44,3-1-1,2-1-2'
 
2017-11-16 17:54:33 2808205120 [Note] Slave SQL thread initialized, starting replication in log 'master-bin.000002' at position 19304, relay log './slave-relay-bin.000001' position: 4; GTID position '0-1-44,1-1-3,2-1-2,3-1-1'
 
2017-11-16 17:54:33 2808205120 [Note] Error reading relay log event: slave SQL thread was killed
 
2017-11-16 17:54:33 2808205120 [Note] Slave SQL thread exiting, replication stopped in log 'master-bin.000002' at position 19594; GTID position '0-1-46,1-1-3,2-1-2,3-1-1'
 
2017-11-16 17:54:33 2808508224 [Note] Slave I/O thread exiting, read up to log 'master-bin.000002', position 19594; GTID position 1-1-3,0-1-46,3-1-1,2-1-2
 
2017-11-16 17:54:33 2808205120 [Note] Slave I/O thread: connected to master 'root@127.0.0.1:16000',replication starts at GTID position '1-1-3,0-1-46,3-1-1,2-1-2'
 
2017-11-16 17:54:33 2807902016 [Note] Slave SQL thread initialized, starting replication in log 'master-bin.000002' at position 19594, relay log './slave-relay-bin.000001' position: 4; GTID position '0-1-46,1-1-3,2-1-2,3-1-1'
 
2017-11-16 17:54:33 2809114432 [ERROR] Slave SQL: Could not execute Write_rows_v1 event on table test.t3; Duplicate entry '111' for key 'PRIMARY', Error_code: 1062; handler error HA_ERR_FOUND_DUPP_KEY; the event's master log master-bin.000002, end_log_pos 19859, Gtid 0-1-48, Internal MariaDB error code: 1062
 
2017-11-16 17:54:33 2809114432 [Warning] Slave: Duplicate entry '111' for key 'PRIMARY' Error_code: 1062
 
2017-11-16 17:54:33 2809114432 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'master-bin.000002' position 19739; GTID position '0-1-47,1-1-3,2-1-2,3-1-1'
 
2017-11-16 17:54:33 2807902016 [Note] Error reading relay log event: slave SQL thread was killed
 
2017-11-16 17:54:33 2807902016 [Note] Slave SQL thread exiting, replication stopped in log 'master-bin.000002' at position 19739; GTID position '0-1-47,1-1-3,2-1-2,3-1-1'
 
2017-11-16 17:54:33 2806992704 [Note] Slave SQL thread initialized, starting replication in log 'master-bin.000002' at position 19739, relay log './slave-relay-bin.000001' position: 4; GTID position '0-1-47,1-1-3,2-1-2,3-1-1'
 
2017-11-16 17:54:33 2806992704 [Note] Error reading relay log event: slave SQL thread was killed
 
2017-11-16 17:54:33 2806992704 [Note] Slave SQL thread exiting, replication stopped in log 'master-bin.000002' at position 20033; GTID position '0-1-49,1-1-3,2-1-2,3-1-1'
 
2017-11-16 17:54:33 2808205120 [Note] Slave I/O thread exiting, read up to log 'master-bin.000002', position 20033; GTID position 1-1-3,0-1-49,3-1-1,2-1-2
 
2017-11-16 17:54:33 2808508224 [Note] Slave I/O thread: connected to master 'root@127.0.0.1:16000',replication starts at GTID position '1-1-3,0-1-49,3-1-1,2-1-2'
 
2017-11-16 17:54:33 2806992704 [Note] Slave SQL thread initialized, starting replication in log 'master-bin.000002' at position 20033, relay log './slave-relay-bin.000001' position: 4; GTID position '0-1-49,1-1-3,2-1-2,3-1-1'
 
2017-11-16 17:54:33 2806992704 [Note] Error reading relay log event: slave SQL thread was killed
 
2017-11-16 17:54:33 2806992704 [Note] Slave SQL thread exiting, replication stopped in log 'master-bin.000002' at position 20682; GTID position '0-1-53,1-1-3,2-1-2,3-1-1'
 
2017-11-16 17:54:33 2808508224 [Note] Slave I/O thread exiting, read up to log 'master-bin.000002', position 20682; GTID position 1-1-3,0-1-53,3-1-1,2-1-2
 
2017-11-16 17:54:33 2806992704 [Note] Slave I/O thread: connected to master 'root@127.0.0.1:16000',replication starts at GTID position '1-1-3,0-1-53,3-1-1,2-1-2'
 
2017-11-16 17:54:33 2808811328 [Note] Slave SQL thread initialized, starting replication in log 'master-bin.000002' at position 20682, relay log './slave-relay-bin.000001' position: 4; GTID position '0-1-53,1-1-3,2-1-2,3-1-1'
 
2017-11-16 17:54:34 2808811328 [Note] Error reading relay log event: slave SQL thread was killed
 
2017-11-16 17:54:34 2808811328 [Note] Slave SQL thread exiting, replication stopped in log 'master-bin.000002' at position 21315; GTID position '0-1-57,1-1-3,2-1-2,3-1-1'
 
2017-11-16 17:54:34 2806992704 [Note] Slave I/O thread exiting, read up to log 'master-bin.000002', position 21315; GTID position 1-1-3,0-1-57,3-1-1,2-1-2
 
2017-11-16 17:54:34 2806689600 [Note] Slave I/O thread: connected to master 'root@127.0.0.1:16000',replication starts at GTID position '1-1-3,0-1-57,3-1-1,2-1-2'
 
2017-11-16 17:54:34 2808811328 [Note] Slave SQL thread initialized, starting replication in log 'master-bin.000002' at position 21315, relay log './slave-relay-bin.000001' position: 4; GTID position '0-1-57,1-1-3,2-1-2,3-1-1'
 
2017-11-16 17:54:34 2808811328 [Note] Error reading relay log event: slave SQL thread was killed
 
2017-11-16 17:54:34 2808811328 [Note] Slave SQL thread exiting, replication stopped in log 'master-bin.000002' at position 22019; GTID position '0-1-61,1-1-3,2-1-2,3-1-1'
 
2017-11-16 17:54:34 2806689600 [Note] Slave I/O thread exiting, read up to log 'master-bin.000002', position 22019; GTID position 1-1-3,0-1-61,3-1-1,2-1-2
 
2017-11-16 17:54:34 2808811328 [Note] Slave I/O thread: connected to master 'root@127.0.0.1:16000',replication starts at GTID position '1-1-3,0-1-61,3-1-1,2-1-2'
 
2017-11-16 17:54:34 2808205120 [Note] Slave SQL thread initialized, starting replication in log 'master-bin.000002' at position 22019, relay log './slave-relay-bin.000001' position: 4; GTID position '0-1-61,1-1-3,2-1-2,3-1-1'
 
2017-11-16 17:54:34 2807902016 [ERROR] Slave SQL: Query partially completed on the master (error on master: 1317) and was aborted. There is a chance that your master is inconsistent at this point. If you are sure that your master is ok, run this query manually on the slave and then restart the slave with SET GLOBAL SQL_SLAVE_SKIP_COUNTER=1; START SLAVE; . Query: 'INSERT INTO t6 VALUES (1), (2), (3)', Gtid 0-1-68, Internal MariaDB error code: 1317
 
2017-11-16 17:54:34 2807902016 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'master-bin.000003' position 794; GTID position '0-1-67,1-1-3,2-1-2,3-1-1'
 
2017-11-16 17:54:34 2808205120 [Note] Error reading relay log event: slave SQL thread was killed
 
2017-11-16 17:54:34 2808205120 [Note] Slave SQL thread exiting, replication stopped in log 'master-bin.000003' at position 794; GTID position '0-1-67,1-1-3,2-1-2,3-1-1'
 
2017-11-16 17:54:34 2808811328 [Note] Slave I/O thread exiting, read up to log 'master-bin.000003', position 999; GTID position 1-1-3,0-1-68,3-1-1,2-1-2
 
2017-11-16 17:54:34 2808205120 [Note] Slave SQL thread initialized, starting replication in log 'master-bin.000003' at position 794, relay log './slave-relay-bin.000001' position: 4; GTID position '0-1-68,1-1-3,2-1-2,3-1-1'
 
2017-11-16 17:54:34 2808811328 [Note] Slave I/O thread: connected to master 'root@127.0.0.1:16000',replication starts at GTID position '1-1-3,0-1-68,3-1-1,2-1-2'
 
2017-11-16 17:54:34 2808205120 [Note] Error reading relay log event: slave SQL thread was killed
 
2017-11-16 17:54:34 2808205120 [Note] Slave SQL thread exiting, replication stopped in log 'master-bin.000003' at position 1321; GTID position '0-1-70,1-1-3,2-1-2,3-1-1'
 
2017-11-16 17:54:34 2808811328 [Note] Slave I/O thread exiting, read up to log 'master-bin.000003', position 1321; GTID position 1-1-3,0-1-70,3-1-1,2-1-2
 
2017-11-16 17:54:34 2808205120 [Note] Slave SQL thread initialized, starting replication in log 'master-bin.000003' at position 1321, relay log './slave-relay-bin.000001' position: 4; GTID position '0-1-70,1-1-3,2-1-2,3-1-1'
 
2017-11-16 17:54:34 2808811328 [Note] Slave I/O thread: connected to master 'root@127.0.0.1:16000',replication starts at GTID position '1-1-3,0-1-70,3-1-1,2-1-2'
 
2017-11-16 17:54:34 2808205120 [ERROR] Slave SQL: Could not execute Write_rows_v1 event on table test.t2; Duplicate entry '32' for key 'PRIMARY', Error_code: 1062; handler error HA_ERR_FOUND_DUPP_KEY; the event's master log master-bin.000003, end_log_pos 1434, Gtid 0-1-71, Internal MariaDB error code: 1062
 
2017-11-16 17:54:34 2808205120 [Warning] Slave: Duplicate entry '32' for key 'PRIMARY' Error_code: 1062
 
2017-11-16 17:54:34 2808205120 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'master-bin.000003' position 1321; GTID position '0-1-70,1-1-3,2-1-2,3-1-1'
 
2017-11-16 17:54:34 2808205120 [Note] Slave SQL thread exiting, replication stopped in log 'master-bin.000003' at position 1321; GTID position '0-1-70,1-1-3,2-1-2,3-1-1'
 
2017-11-16 17:54:34 2808811328 [ERROR] Error reading packet from server: Lost connection to MySQL server during query (server_errno=2013)
 
2017-11-16 17:54:34 2808811328 [Note] Slave I/O thread exiting, read up to log 'master-bin.000004', position 732; GTID position 1-1-3,0-1-73,3-1-1,2-1-2
 
2017-11-16 17:54:34 2808811328 [Note] Slave I/O thread: connected to master 'root@127.0.0.1:16000',replication starts at GTID position '1-1-3,0-1-70,3-1-1,2-1-2'
 
2017-11-16 17:54:34 2808205120 [Note] Slave SQL thread initialized, starting replication in log 'master-bin.000003' at position 1321, relay log './slave-relay-bin.000001' position: 4; GTID position '0-1-70,1-1-3,2-1-2,3-1-1'
 
2017-11-16 17:54:34 2806386496 [ERROR] Slave SQL: Could not execute Write_rows_v1 event on table test.t2; Duplicate entry '32' for key 'PRIMARY', Error_code: 1062; handler error HA_ERR_FOUND_DUPP_KEY; the event's master log master-bin.000003, end_log_pos 1434, Gtid 0-1-71, Internal MariaDB error code: 1062
 
2017-11-16 17:54:34 2806386496 [Warning] Slave: Duplicate entry '32' for key 'PRIMARY' Error_code: 1062
 
2017-11-16 17:54:34 2806386496 [ERROR] Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with "SLAVE START". We stopped at log 'master-bin.000003' position 1321; GTID position '0-1-70,1-1-3,2-1-2,3-1-1'
 
2017-11-16 17:54:34 2808205120 [Note] Slave SQL thread exiting, replication stopped in log 'master-bin.000003' at position 1321; GTID position '0-1-70,1-1-3,2-1-2,3-1-1'
 
2017-11-16 17:54:34 2846871360 [Note] Slave SQL thread initialized, starting replication in log 'master-bin.000003' at position 1321, relay log './slave-relay-bin.000002' position: 4; GTID position '0-1-70,1-1-3,2-1-2,3-1-1'
 
mysqld: /home/buildbot/buildbot/build/mariadb-10.1.30/sql/rpl_parallel.cc:1930: rpl_parallel_thread* rpl_parallel_thread_pool::get_thread(rpl_parallel_thread**, rpl_parallel_entry*): Assertion `count > 0' failed.
 
171116 17:54:34 [ERROR] mysqld got signal 6 ;
 
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.30-MariaDB-debug
 
key_buffer_size=1048576
 
read_buffer_size=131072
 
max_used_connections=7
 
max_threads=153
 
thread_count=6
 
It is possible that mysqld could use up to 
key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 61851 K  bytes of memory
 
Hope that's ok; if not, decrease some variables in the equation.
 
 
 
Thread pointer: 0xa99b6f40
 
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 = 0xa9afbe74 thread_stack 0x48400
 
/mnt/buildbot/build/mariadb-10.1.30/sql/mysqld(my_print_stacktrace+0x32)[0x8b3a109]
 
/mnt/buildbot/build/mariadb-10.1.30/sql/mysqld(handle_fatal_signal+0x3b0)[0x84e1168]
 
[0xb76fc400]
 
[0xb76fc424]
 
/lib/i386-linux-gnu/libc.so.6(gsignal+0x4f)[0xb71d81ef]
 
/lib/i386-linux-gnu/libc.so.6(abort+0x175)[0xb71db835]
 
/lib/i386-linux-gnu/libc.so.6(+0x27095)[0xb71d1095]
 
/lib/i386-linux-gnu/libc.so.6(+0x27147)[0xb71d1147]
 
/mnt/buildbot/build/mariadb-10.1.30/sql/mysqld(_ZN24rpl_parallel_thread_pool10get_threadEPP19rpl_parallel_threadP18rpl_parallel_entry+0x49)[0x844a2af]
 
/mnt/buildbot/build/mariadb-10.1.30/sql/mysqld(_ZN18rpl_parallel_entry13choose_threadEP14rpl_group_infoPbP17PSI_stage_info_v1b+0x322)[0x844a7d0]
 
/mnt/buildbot/build/mariadb-10.1.30/sql/mysqld(_ZN12rpl_parallel8do_eventEP14rpl_group_infoP9Log_eventy+0x5f6)[0x844ba0e]
 
/mnt/buildbot/build/mariadb-10.1.30/sql/mysqld[0x8211ca2]
 
/mnt/buildbot/build/mariadb-10.1.30/sql/mysqld(handle_slave_sql+0xf81)[0x8215414]
 
/mnt/buildbot/build/mariadb-10.1.30/sql/mysqld[0x86b3f9c]
 
/lib/i386-linux-gnu/libpthread.so.0(+0x6d4c)[0xb7484d4c]
 
/lib/i386-linux-gnu/libc.so.6(clone+0x5e)[0xb7294ace]
 
 
 
Trying to get some variables.
 
Some pointers may be invalid and cause the dump to abort.
 
Query (0x0): 
Connection ID (thread ID): 321
 
Status: NOT_KILLED
 
----------SERVER LOG END-------------

Comment by Alice Sherepa [ 2017-11-30 ]

rpl.rpl_parallel failed in buildbot, rpl_parallel.cc:1930: rpl_parallel_thread* rpl_parallel_thread_pool::get_thread: Assertion `count > 0' failed, 10.1 - http://buildbot.askmonty.org/buildbot/builders/kvm-fulltest2/builds/10589/steps/mtr_ps/logs/stdio

Generated at Thu Feb 08 08:12:18 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.