binlog_encryption.rpl_parallel failed in buildbot

binlog_encryption.rpl_parallel 'innodb,mix' w2 [ fail ]

        Test ended at 2017-08-24 15:09:56

CURRENT_TEST: binlog_encryption.rpl_parallel

mysqltest: In included file "./extra/rpl_tests/rpl_parallel.inc": 

included from /mnt/buildbot/build/mariadb-10.3.1/mysql-test/suite/binlog_encryption/rpl_parallel.test at line 2:

At line 1567: failed in 'select master_pos_wait('master-bin.000004', 1716, 300, '')': 2013: Lost connection to MySQL server during query

The result from queries just before the failure was:

< snip >

include/start_slave.inc

SET debug_sync= 'now WAIT_FOR waiting';

SELECT * FROM t4 ORDER BY a;

a	b

1	NULL

3	NULL

4	4

5	NULL

6	NULL

SET debug_sync= 'now SIGNAL cont';

include/stop_slave.inc

SET GLOBAL debug_dbug=@old_dbug;

SET GLOBAL binlog_format= @old_format;

SET GLOBAL slave_parallel_threads=0;

SET GLOBAL slave_parallel_threads=10;

include/start_slave.inc

*** MDEV-7237: Parallel replication: incorrect relaylog position after stop/start the slave ***

connection server_1;

INSERT INTO t2 VALUES (40);

connection server_2;

More results from queries before failure can be found in /mnt/buildbot/build/mariadb-10.3.1/mysql-test/var/2/log/rpl_parallel.log

Server [mysqld.2 - pid: 3404, winpid: 3404, exit: 256] failed during test run

Server log from this test:

----------SERVER LOG START-----------

2017-08-24 15:09:47 0 [Note] /mnt/buildbot/build/mariadb-10.3.1/sql/mysqld (mysqld 10.3.1-MariaDB-debug-log) starting as process 3405 ...

2017-08-24 15:09:47 0 [Warning] Could not increase number of max_open_files to more than 1024 (request: 4162)

2017-08-24 15:09:47 0 [Note] Plugin 'partition' is disabled.

2017-08-24 15:09:47 0 [Note] InnoDB: !!!!!!!! UNIV_DEBUG switched on !!!!!!!!!

2017-08-24 15:09:47 0 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins

2017-08-24 15:09:47 0 [Note] InnoDB: Uses event mutexes

2017-08-24 15:09:47 0 [Note] InnoDB: Compressed tables use zlib 1.2.3.4

2017-08-24 15:09:47 0 [Note] InnoDB: Using Linux native AIO

2017-08-24 15:09:47 0 [Note] InnoDB: Number of pools: 1

2017-08-24 15:09:47 0 [Note] InnoDB: Using generic crc32 instructions

2017-08-24 15:09:47 0 [Note] InnoDB: Initializing buffer pool, total size = 8M, instances = 1, chunk size = 8M

2017-08-24 15:09:47 0 [Note] InnoDB: Completed initialization of buffer pool

2017-08-24 15:09:47 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().

2017-08-24 15:09:47 0 [Note] InnoDB: 128 out of 128 rollback segments are active.

2017-08-24 15:09:47 0 [Note] InnoDB: Creating shared tablespace for temporary tables

2017-08-24 15:09:47 0 [Note] InnoDB: Setting file './ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...

2017-08-24 15:09:47 0 [Note] InnoDB: File './ibtmp1' size is now 12 MB.

2017-08-24 15:09:48 0 [Note] InnoDB: Waiting for purge to start

2017-08-24 15:09:48 0 [Note] InnoDB: 5.7.19 started; log sequence number 1632811

2017-08-24 15:09:48 0 [Note] InnoDB: Loading buffer pool(s) from /run/shm/var_auto_vtrH/2/mysqld.2/data/ib_buffer_pool

2017-08-24 15:09:48 0 [Note] InnoDB: Buffer pool(s) load completed at 170824 15:09:48

2017-08-24 15:09:48 0 [Note] Plugin 'SEQUENCE' is disabled.

2017-08-24 15:09:48 0 [Note] Plugin 'INNODB_SYS_DATAFILES' is disabled.

2017-08-24 15:09:48 0 [Note] Plugin 'INNODB_SYS_TABLESTATS' is disabled.

2017-08-24 15:09:48 0 [Note] Plugin 'INNODB_TABLESPACES_SCRUBBING' is disabled.

2017-08-24 15:09:48 0 [Note] Plugin 'INNODB_CMP' is disabled.

2017-08-24 15:09:48 0 [Note] Plugin 'INNODB_FT_DELETED' is disabled.

2017-08-24 15:09:48 0 [Note] Plugin 'INNODB_CMP_RESET' is disabled.

2017-08-24 15:09:48 0 [Note] Plugin 'INNODB_LOCK_WAITS' is disabled.

2017-08-24 15:09:48 0 [Note] Plugin 'INNODB_TABLESPACES_ENCRYPTION' is disabled.

2017-08-24 15:09:48 0 [Note] Plugin 'INNODB_CMPMEM_RESET' is disabled.

2017-08-24 15:09:48 0 [Note] Plugin 'FEEDBACK' is disabled.

2017-08-24 15:09:48 0 [Note] Plugin 'INNODB_FT_INDEX_TABLE' is disabled.

2017-08-24 15:09:48 0 [Note] Plugin 'INNODB_CMP_PER_INDEX_RESET' is disabled.

2017-08-24 15:09:48 0 [Note] Plugin 'user_variables' is disabled.

2017-08-24 15:09:48 0 [Note] Plugin 'INNODB_FT_INDEX_CACHE' is disabled.

2017-08-24 15:09:48 0 [Note] Plugin 'INNODB_FT_BEING_DELETED' is disabled.

2017-08-24 15:09:48 0 [Note] Plugin 'INNODB_FT_DEFAULT_STOPWORD' is disabled.

2017-08-24 15:09:48 0 [Note] Plugin 'INNODB_FT_CONFIG' is disabled.

2017-08-24 15:09:48 0 [Note] Plugin 'INNODB_SYS_TABLESPACES' is disabled.

2017-08-24 15:09:48 0 [Note] Plugin 'INNODB_MUTEXES' is disabled.

2017-08-24 15:09:48 0 [Note] Plugin 'INNODB_SYS_SEMAPHORE_WAITS' is disabled.

2017-08-24 15:09:48 0 [Warning] /mnt/buildbot/build/mariadb-10.3.1/sql/mysqld: unknown option '--loose-pam-debug'

2017-08-24 15:09:48 0 [Note] Server socket created on IP: '127.0.0.1'.

2017-08-24 15:09:48 0 [Note] Reading of all Master_info entries succeded

2017-08-24 15:09:48 0 [Note] Added new Master_info '' to hash table

2017-08-24 15:09:48 0 [Note] /mnt/buildbot/build/mariadb-10.3.1/sql/mysqld: ready for connections.

Version: '10.3.1-MariaDB-debug-log'  socket: '/mnt/buildbot/build/mariadb-10.3.1/mysql-test/var/tmp/2/mysqld.2.sock'  port: 16061  Source distribution

2017-08-24 15:09:49 10 [Note] Deleted Master_info file '/mnt/buildbot/build/mariadb-10.3.1/mysql-test/var/2/mysqld.2/data/master.info'.

2017-08-24 15:09:49 10 [Note] Deleted Master_info file '/mnt/buildbot/build/mariadb-10.3.1/mysql-test/var/2/mysqld.2/data/relay-log.info'.

2017-08-24 15:09:49 10 [Note] Master connection name: ''  Master_info_file: 'master.info'  Relay_info_file: 'relay-log.info'

2017-08-24 15:09:49 10 [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='16060', master_log_file='master-bin.000001', master_log_pos='4'.

2017-08-24 15:09:49 12 [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-08-24 15:09:49 13 [Note] Slave SQL thread initialized, starting replication in log 'master-bin.000001' at position 4, relay log './slave-relay-bin.000001' position: 4

2017-08-24 15:09:49 13 [Note] Error reading relay log event: slave SQL thread was killed

2017-08-24 15:09:49 13 [Note] Slave SQL thread exiting, replication stopped in log 'master-bin.000001' at position 369

2017-08-24 15:09:49 12 [Note] Slave I/O thread exiting, read up to log 'master-bin.000001', position 369

2017-08-24 15:09:49 10 [Note] Master connection name: ''  Master_info_file: 'master.info'  Relay_info_file: 'relay-log.info'

2017-08-24 15:09:49 10 [Note] 'CHANGE MASTER TO executed'. Previous state master_host='127.0.0.1', master_port='16060', master_log_file='master-bin.000001', master_log_pos='369'. New state master_host='127.0.0.1', master_port='16060', master_log_file='master-bin.000001', master_log_pos='369'.

2017-08-24 15:09:49 10 [Note] Previous Using_Gtid=No. New Using_Gtid=Slave_Pos

2017-08-24 15:09:49 16 [Note] Slave I/O thread: connected to master 'root@127.0.0.1:16060',replication starts at GTID position ''

2017-08-24 15:09:49 17 [Note] Slave SQL thread initialized, starting replication in log 'master-bin.000001' at position 369, relay log './slave-relay-bin.000001' position: 4; GTID position ''

2017-08-24 15:09:49 17 [Note] Error reading relay log event: slave SQL thread was killed

2017-08-24 15:09:49 17 [Note] Slave SQL thread exiting, replication stopped in log 'master-bin.000001' at position 369; GTID position ''

2017-08-24 15:09:49 16 [Note] Slave I/O thread exiting, read up to log 'master-bin.000001', position 369; GTID position 

2017-08-24 15:09:49 28 [Note] Slave I/O thread: connected to master 'root@127.0.0.1:16060',replication starts at GTID position ''

2017-08-24 15:09:49 29 [Note] Slave SQL thread initialized, starting replication in log 'master-bin.000001' at position 369, relay log './slave-relay-bin.000001' position: 4; GTID position ''

2017-08-24 15:09:49 29 [Note] Error reading relay log event: slave SQL thread was killed

2017-08-24 15:09:49 29 [Note] Slave SQL thread exiting, replication stopped in log 'master-bin.000001' at position 2171; GTID position '0-1-9,1-1-1'

2017-08-24 15:09:49 28 [Note] Slave I/O thread exiting, read up to log 'master-bin.000001', position 2171; GTID position 1-1-1,0-1-9

2017-08-24 15:09:49 41 [Note] Slave I/O thread: connected to master 'root@127.0.0.1:16060',replication starts at GTID position '1-1-1,0-1-9'

2017-08-24 15:09:49 42 [Note] Slave SQL thread initialized, starting replication in log 'master-bin.000001' at position 2171, relay log './slave-relay-bin.000001' position: 4; GTID position '0-1-9,1-1-1'

2017-08-24 15:09:49 42 [Note] Error reading relay log event: slave SQL thread was killed

2017-08-24 15:09:49 42 [Note] Slave SQL thread exiting, replication stopped in log 'master-bin.000001' at position 2754; GTID position '0-1-9,1-1-2,2-1-1'

2017-08-24 15:09:49 41 [Note] Slave I/O thread exiting, read up to log 'master-bin.000001', position 2754; GTID position 1-1-2,2-1-1,0-1-9

2017-08-24 15:09:50 54 [Note] Slave I/O thread: connected to master 'root@127.0.0.1:16060',replication starts at GTID position '1-1-2,0-1-9,2-1-1'

2017-08-24 15:09:50 55 [Note] Slave SQL thread initialized, starting replication in log 'master-bin.000001' at position 2754, relay log './slave-relay-bin.000001' position: 4; GTID position '0-1-9,1-1-2,2-1-1'

2017-08-24 15:09:50 55 [Note] Error reading relay log event: slave SQL thread was killed

2017-08-24 15:09:50 55 [Note] Slave SQL thread exiting, replication stopped in log 'master-bin.000002' at position 1560; GTID position '0-1-14,1-1-2,2-1-1'

2017-08-24 15:09:50 54 [Note] Slave I/O thread exiting, read up to log 'master-bin.000002', position 1560; GTID position 1-1-2,0-1-14,2-1-1

2017-08-24 15:09:50 68 [Note] Slave I/O thread: connected to master 'root@127.0.0.1:16060',replication starts at GTID position '1-1-2,0-1-14,2-1-1'

2017-08-24 15:09:50 69 [Note] Slave SQL thread initialized, starting replication in log 'master-bin.000002' at position 1560, relay log './slave-relay-bin.000001' position: 4; GTID position '0-1-14,1-1-2,2-1-1'

2017-08-24 15:09:50 69 [Note] Error reading relay log event: slave SQL thread was killed

2017-08-24 15:09:50 69 [Note] Slave SQL thread exiting, replication stopped in log 'master-bin.000002' at position 2009; GTID position '0-1-15,1-1-2,2-1-1'

2017-08-24 15:09:50 68 [Note] Slave I/O thread exiting, read up to log 'master-bin.000002', position 2347; GTID position 1-1-2,0-1-17,2-1-1

2017-08-24 15:09:50 80 [Note] Slave I/O thread: connected to master 'root@127.0.0.1:16060',replication starts at GTID position '1-1-2,0-1-15,2-1-1'

2017-08-24 15:09:50 81 [Note] Slave SQL thread initialized, starting replication in log 'master-bin.000002' at position 2009, relay log './slave-relay-bin.000001' position: 4; GTID position '0-1-15,1-1-2,2-1-1'

2017-08-24 15:09:50 81 [Note] Error reading relay log event: slave SQL thread was killed

2017-08-24 15:09:50 81 [Note] Slave SQL thread exiting, replication stopped in log 'master-bin.000002' at position 2347; GTID position '0-1-17,1-1-2,2-1-1'

2017-08-24 15:09:50 80 [Note] Slave I/O thread exiting, read up to log 'master-bin.000002', position 2347; GTID position 1-1-2,0-1-17,2-1-1

2017-08-24 15:09:50 92 [Note] Slave I/O thread: connected to master 'root@127.0.0.1:16060',replication starts at GTID position '1-1-2,0-1-17,2-1-1'

2017-08-24 15:09:50 93 [Note] Slave SQL thread initialized, starting replication in log 'master-bin.000002' at position 2347, relay log './slave-relay-bin.000001' position: 4; GTID position '0-1-17,1-1-2,2-1-1'

2017-08-24 15:09:50 102 [ERROR] Slave SQL: Connection was killed, Gtid 0-1-19, Internal MariaDB error code: 1927

2017-08-24 15:09:50 102 [Warning] Slave: Connection was killed Error_code: 1927

2017-08-24 15:09:50 102 [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 2347; GTID position '0-1-17,1-1-2,2-1-1'

2017-08-24 15:09:50 93 [Note] Error reading relay log event: slave SQL thread was killed

2017-08-24 15:09:50 98 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964

2017-08-24 15:09:50 98 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964

2017-08-24 15:09:50 98 [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 2642; GTID position '0-1-18,1-1-2,2-1-1'

2017-08-24 15:09:50 93 [Note] Slave SQL thread exiting, replication stopped in log 'master-bin.000002' at position 2642; GTID position '0-1-18,1-1-2,2-1-1'

2017-08-24 15:09:51 92 [Note] Slave I/O thread exiting, read up to log 'master-bin.000002', position 3273; GTID position 1-1-2,0-1-20,2-1-1

2017-08-24 15:09:51 104 [Note] Slave I/O thread: connected to master 'root@127.0.0.1:16060',replication starts at GTID position '1-1-2,0-1-18,2-1-1'

2017-08-24 15:09:51 105 [Note] Slave SQL thread initialized, starting replication in log 'master-bin.000002' at position 2642, relay log './slave-relay-bin.000001' position: 4; GTID position '0-1-18,1-1-2,2-1-1'

2017-08-24 15:09:51 105 [Note] Error reading relay log event: slave SQL thread was killed

2017-08-24 15:09:51 105 [Note] Slave SQL thread exiting, replication stopped in log 'master-bin.000002' at position 3441; GTID position '0-1-21,1-1-2,2-1-1'

2017-08-24 15:09:51 104 [Note] Slave I/O thread exiting, read up to log 'master-bin.000002', position 3441; GTID position 1-1-2,0-1-21,2-1-1

2017-08-24 15:09:51 116 [Note] Slave I/O thread: connected to master 'root@127.0.0.1:16060',replication starts at GTID position '1-1-2,0-1-21,2-1-1'

2017-08-24 15:09:51 117 [Note] Slave SQL thread initialized, starting replication in log 'master-bin.000002' at position 3441, relay log './slave-relay-bin.000001' position: 4; GTID position '0-1-21,1-1-2,2-1-1'

2017-08-24 15:09:51 118 [ERROR] Slave SQL: Connection was killed, Gtid 0-1-23, Internal MariaDB error code: 1927

2017-08-24 15:09:51 118 [Warning] Slave: Connection was killed Error_code: 1927

2017-08-24 15:09:51 118 [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 3441; GTID position '0-1-21,1-1-2,2-1-1'

2017-08-24 15:09:51 117 [Note] Error reading relay log event: slave SQL thread was killed

2017-08-24 15:09:51 125 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964

2017-08-24 15:09:51 125 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964

2017-08-24 15:09:51 125 [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 3441; GTID position '0-1-21,1-1-2,2-1-1'

2017-08-24 15:09:51 117 [Note] Slave SQL thread exiting, replication stopped in log 'master-bin.000002' at position 3736; GTID position '0-1-22,1-1-2,2-1-1'

2017-08-24 15:09:51 128 [Note] Slave SQL thread initialized, starting replication in log 'master-bin.000002' at position 3736, relay log './slave-relay-bin.000001' position: 4; GTID position '0-1-22,1-1-2,2-1-1'

2017-08-24 15:09:51 128 [Note] Error reading relay log event: slave SQL thread was killed

2017-08-24 15:09:51 128 [Note] Slave SQL thread exiting, replication stopped in log 'master-bin.000002' at position 4535; GTID position '0-1-25,1-1-2,2-1-1'

2017-08-24 15:09:51 116 [Note] Slave I/O thread exiting, read up to log 'master-bin.000002', position 4535; GTID position 1-1-2,0-1-25,2-1-1

2017-08-24 15:09:51 139 [Note] Slave I/O thread: connected to master 'root@127.0.0.1:16060',replication starts at GTID position '1-1-2,0-1-25,2-1-1'

2017-08-24 15:09:51 140 [Note] Slave SQL thread initialized, starting replication in log 'master-bin.000002' at position 4535, relay log './slave-relay-bin.000001' position: 4; GTID position '0-1-25,1-1-2,2-1-1'

2017-08-24 15:09:51 140 [Note] Error reading relay log event: slave SQL thread was killed

2017-08-24 15:09:51 140 [Note] Slave SQL thread exiting, replication stopped in log 'master-bin.000002' at position 4535; GTID position '0-1-25,1-1-2,2-1-1'

2017-08-24 15:09:51 139 [Note] Slave I/O thread exiting, read up to log 'master-bin.000002', position 4535; GTID position 1-1-2,0-1-25,2-1-1

2017-08-24 15:09:51 10 [Note] Master connection name: ''  Master_info_file: 'master.info'  Relay_info_file: 'relay-log.info'

2017-08-24 15:09:51 10 [Note] 'CHANGE MASTER TO executed'. Previous state master_host='127.0.0.1', master_port='16060', master_log_file='master-bin.000002', master_log_pos='4535'. New state master_host='127.0.0.1', master_port='16060', master_log_file='master-bin.000002', master_log_pos='4535'.

2017-08-24 15:09:51 10 [Note] Previous Using_Gtid=Slave_Pos. New Using_Gtid=No

2017-08-24 15:09:51 151 [Note] Slave I/O thread: connected to master 'root@127.0.0.1:16060',replication started in log 'master-bin.000002' at position 4535

2017-08-24 15:09:51 152 [Note] Slave SQL thread initialized, starting replication in log 'master-bin.000002' at position 4535, relay log './slave-relay-bin.000001' position: 4

2017-08-24 15:09:51 157 [ERROR] Slave SQL: Connection was killed, Gtid 0-1-27, Internal MariaDB error code: 1927

2017-08-24 15:09:51 157 [Warning] Slave: Connection was killed Error_code: 1927

2017-08-24 15:09:51 157 [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 4535

2017-08-24 15:09:51 152 [Note] Error reading relay log event: slave SQL thread was killed

2017-08-24 15:09:51 158 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964

2017-08-24 15:09:51 158 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964

2017-08-24 15:09:51 158 [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 4535

2017-08-24 15:09:51 152 [Note] Slave SQL thread exiting, replication stopped in log 'master-bin.000002' at position 4830

2017-08-24 15:09:51 163 [Note] Slave SQL thread initialized, starting replication in log 'master-bin.000002' at position 4830, relay log './slave-relay-bin.000002' position: 851

2017-08-24 15:09:51 163 [Note] Error reading relay log event: slave SQL thread was killed

2017-08-24 15:09:51 163 [Note] Slave SQL thread exiting, replication stopped in log 'master-bin.000002' at position 5629

2017-08-24 15:09:51 151 [Note] Slave I/O thread exiting, read up to log 'master-bin.000002', position 5629

2017-08-24 15:09:51 10 [Note] Master connection name: ''  Master_info_file: 'master.info'  Relay_info_file: 'relay-log.info'

2017-08-24 15:09:51 10 [Note] 'CHANGE MASTER TO executed'. Previous state master_host='127.0.0.1', master_port='16060', master_log_file='master-bin.000002', master_log_pos='5629'. New state master_host='127.0.0.1', master_port='16060', master_log_file='master-bin.000002', master_log_pos='5629'.

2017-08-24 15:09:51 10 [Note] Previous Using_Gtid=No. New Using_Gtid=Slave_Pos

2017-08-24 15:09:51 174 [Note] Slave I/O thread: connected to master 'root@127.0.0.1:16060',replication starts at GTID position '1-1-2,0-1-29,2-1-1'

2017-08-24 15:09:51 175 [Note] Slave SQL thread initialized, starting replication in log 'master-bin.000002' at position 5629, relay log './slave-relay-bin.000001' position: 4; GTID position '0-1-29,1-1-2,2-1-1'

2017-08-24 15:09:51 175 [Note] Error reading relay log event: slave SQL thread was killed

2017-08-24 15:09:51 175 [Note] Slave SQL thread exiting, replication stopped in log 'master-bin.000002' at position 5629; GTID position '0-1-29,1-1-2,2-1-1'

2017-08-24 15:09:51 174 [Note] Slave I/O thread exiting, read up to log 'master-bin.000002', position 5629; GTID position 1-1-2,0-1-29,2-1-1

2017-08-24 15:09:51 186 [Note] Slave I/O thread: connected to master 'root@127.0.0.1:16060',replication starts at GTID position '1-1-2,0-1-29,2-1-1'

2017-08-24 15:09:51 187 [Note] Slave SQL thread initialized, starting replication in log 'master-bin.000002' at position 5629, relay log './slave-relay-bin.000001' position: 4; GTID position '0-1-29,1-1-2,2-1-1'

2017-08-24 15:09:52 188 [ERROR] Slave SQL: Connection was killed, Gtid 0-1-33, Internal MariaDB error code: 1927

2017-08-24 15:09:52 188 [Warning] Slave: Connection was killed Error_code: 1927

2017-08-24 15:09:52 188 [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 7341; GTID position '0-1-30,1-1-3,2-1-2,3-1-1'

2017-08-24 15:09:52 187 [Note] Error reading relay log event: slave SQL thread was killed

2017-08-24 15:09:52 191 [ERROR] Slave (additional info): Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964

2017-08-24 15:09:52 191 [Warning] Slave: Commit failed due to failure of an earlier commit on which this one depends Error_code: 1964

2017-08-24 15:09:52 191 [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 7596; GTID position '0-1-31,1-1-3,2-1-2,3-1-1'

2017-08-24 15:09:52 187 [Note] Slave SQL thread exiting, replication stopped in log 'master-bin.000002' at position 7596; GTID position '0-1-31,1-1-3,2-1-2,3-1-1'

2017-08-24 15:09:52 186 [Note] Slave I/O thread exiting, read up to log 'master-bin.000002', position 8151; GTID position 1-1-3,0-1-34,3-1-1,2-1-2

2017-08-24 15:09:52 192 [Note] Slave I/O thread: connected to master 'root@127.0.0.1:16060',replication starts at GTID position '1-1-3,0-1-31,3-1-1,2-1-2'

2017-08-24 15:09:52 193 [Note] Slave SQL thread initialized, starting replication in log 'master-bin.000002' at position 7596, relay log './slave-relay-bin.000001' position: 4; GTID position '0-1-31,1-1-3,2-1-2,3-1-1'

2017-08-24 15:09:52 193 [Note] Error reading relay log event: slave SQL thread was killed

2017-08-24 15:09:52 193 [Note] Slave SQL thread exiting, replication stopped in log 'master-bin.000002' at position 8321; GTID position '0-1-35,1-1-3,2-1-2,3-1-1'

2017-08-24 15:09:52 192 [Note] Slave I/O thread exiting, read up to log 'master-bin.000002', position 8321; GTID position 1-1-3,0-1-35,3-1-1,2-1-2

2017-08-24 15:09:52 204 [Note] Slave I/O thread: connected to master 'root@127.0.0.1:16060',replication starts at GTID position '1-1-3,0-1-35,3-1-1,2-1-2'

2017-08-24 15:09:52 205 [Note] Slave SQL thread initialized, starting replication in log 'master-bin.000002' at position 8321, relay log './slave-relay-bin.000001' position: 4; GTID position '0-1-35,1-1-3,2-1-2,3-1-1'

2017-08-24 15:09:52 205 [ERROR] Slave SQL: Connection was killed, Internal MariaDB error code: 1927

2017-08-24 15:09:52 205 [Warning] Slave: Connection was killed Error_code: 1927

2017-08-24 15:09:52 205 [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 8321; GTID position '0-1-35,1-1-3,2-1-2,3-1-1'

2017-08-24 15:09:52 205 [Note] Slave SQL thread exiting, replication stopped in log 'master-bin.000002' at position 8560; GTID position '0-1-36,1-1-3,2-1-2,3-1-1'

2017-08-24 15:09:52 204 [Note] Slave I/O thread exiting, read up to log 'master-bin.000002', position 18738; GTID position 1-1-3,0-1-37,3-1-1,2-1-2

2017-08-24 15:09:52 216 [Note] Slave I/O thread: connected to master 'root@127.0.0.1:16060',replication starts at GTID position '1-1-3,0-1-36,3-1-1,2-1-2'

2017-08-24 15:09:52 217 [Note] Slave SQL thread initialized, starting replication in log 'master-bin.000002' at position 8560, relay log './slave-relay-bin.000001' position: 4; GTID position '0-1-36,1-1-3,2-1-2,3-1-1'

2017-08-24 15:09:52 217 [Note] Error reading relay log event: slave SQL thread was killed

2017-08-24 15:09:52 217 [Note] Slave SQL thread exiting, replication stopped in log 'master-bin.000002' at position 18906; GTID position '0-1-38,1-1-3,2-1-2,3-1-1'

2017-08-24 15:09:52 216 [Note] Slave I/O thread exiting, read up to log 'master-bin.000002', position 18906; GTID position 1-1-3,0-1-38,3-1-1,2-1-2

2017-08-24 15:09:52 228 [Note] Slave I/O thread: connected to master 'root@127.0.0.1:16060',replication starts at GTID position '1-1-3,0-1-38,3-1-1,2-1-2'

2017-08-24 15:09:52 229 [Note] Slave SQL thread initialized, starting replication in log 'master-bin.000002' at position 18906, relay log './slave-relay-bin.000001' position: 4; GTID position '0-1-38,1-1-3,2-1-2,3-1-1'

2017-08-24 15:09:52 229 [Note] Error reading relay log event: slave SQL thread was killed

2017-08-24 15:09:52 229 [Note] Slave SQL thread exiting, replication stopped in log 'master-bin.000002' at position 18906; GTID position '0-1-38,1-1-3,2-1-2,3-1-1'

2017-08-24 15:09:52 228 [Note] Slave I/O thread exiting, read up to log 'master-bin.000002', position 18906; GTID position 1-1-3,0-1-38,3-1-1,2-1-2

2017-08-24 15:09:52 240 [Note] Slave I/O thread: connected to master 'root@127.0.0.1:16060',replication starts at GTID position '1-1-3,0-1-38,3-1-1,2-1-2'

2017-08-24 15:09:52 241 [Note] Slave SQL thread initialized, starting replication in log 'master-bin.000002' at position 18906, relay log './slave-relay-bin.000001' position: 4; GTID position '0-1-38,1-1-3,2-1-2,3-1-1'

2017-08-24 15:09:52 241 [Note] Error reading relay log event: slave SQL thread was killed

2017-08-24 15:09:52 241 [Note] Slave SQL thread exiting, replication stopped in log 'master-bin.000002' at position 20190; GTID position '0-1-44,1-1-3,2-1-2,3-1-1'

2017-08-24 15:09:52 240 [Note] Slave I/O thread exiting, read up to log 'master-bin.000002', position 20190; GTID position 1-1-3,0-1-44,3-1-1,2-1-2

2017-08-24 15:09:52 244 [Note] Slave I/O thread: connected to master 'root@127.0.0.1:16060',replication starts at GTID position '1-1-3,0-1-44,3-1-1,2-1-2'

2017-08-24 15:09:52 245 [Note] Slave SQL thread initialized, starting replication in log 'master-bin.000002' at position 20190, relay log './slave-relay-bin.000001' position: 4; GTID position '0-1-44,1-1-3,2-1-2,3-1-1'

2017-08-24 15:09:52 245 [Note] Error reading relay log event: slave SQL thread was killed

2017-08-24 15:09:52 245 [Note] Slave SQL thread exiting, replication stopped in log 'master-bin.000002' at position 20618; GTID position '0-1-46,1-1-3,2-1-2,3-1-1'

2017-08-24 15:09:52 244 [Note] Slave I/O thread exiting, read up to log 'master-bin.000002', position 20618; GTID position 1-1-3,0-1-46,3-1-1,2-1-2

2017-08-24 15:09:53 248 [Note] Slave I/O thread: connected to master 'root@127.0.0.1:16060',replication starts at GTID position '1-1-3,0-1-46,3-1-1,2-1-2'

2017-08-24 15:09:53 249 [Note] Slave SQL thread initialized, starting replication in log 'master-bin.000002' at position 20618, relay log './slave-relay-bin.000001' position: 4; GTID position '0-1-46,1-1-3,2-1-2,3-1-1'

2017-08-24 15:09:53 256 [ERROR] Slave SQL: Error 'Duplicate entry '111' for key 'PRIMARY'' on query. Default database: 'test'. Query: 'INSERT INTO t3 VALUES (111, 2)', Gtid 0-1-48, Internal MariaDB error code: 1062

2017-08-24 15:09:53 256 [Warning] Slave: Duplicate entry '111' for key 'PRIMARY' Error_code: 1062

2017-08-24 15:09:53 256 [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 20788; GTID position '0-1-47,1-1-3,2-1-2,3-1-1'

2017-08-24 15:09:53 249 [Note] Error reading relay log event: slave SQL thread was killed

2017-08-24 15:09:53 249 [Note] Slave SQL thread exiting, replication stopped in log 'master-bin.000002' at position 20788; GTID position '0-1-47,1-1-3,2-1-2,3-1-1'

2017-08-24 15:09:53 260 [Note] Slave SQL thread initialized, starting replication in log 'master-bin.000002' at position 20788, relay log './slave-relay-bin.000001' position: 4; GTID position '0-1-47,1-1-3,2-1-2,3-1-1'

2017-08-24 15:09:53 260 [Note] Error reading relay log event: slave SQL thread was killed

2017-08-24 15:09:53 260 [Note] Slave SQL thread exiting, replication stopped in log 'master-bin.000002' at position 21132; GTID position '0-1-49,1-1-3,2-1-2,3-1-1'

2017-08-24 15:09:53 248 [Note] Slave I/O thread exiting, read up to log 'master-bin.000002', position 21132; GTID position 1-1-3,0-1-49,3-1-1,2-1-2

2017-08-24 15:09:53 271 [Note] Slave I/O thread: connected to master 'root@127.0.0.1:16060',replication starts at GTID position '1-1-3,0-1-49,3-1-1,2-1-2'

2017-08-24 15:09:53 272 [Note] Slave SQL thread initialized, starting replication in log 'master-bin.000002' at position 21132, relay log './slave-relay-bin.000001' position: 4; GTID position '0-1-49,1-1-3,2-1-2,3-1-1'

2017-08-24 15:09:53 272 [Note] Error reading relay log event: slave SQL thread was killed

2017-08-24 15:09:53 272 [Note] Slave SQL thread exiting, replication stopped in log 'master-bin.000002' at position 21865; GTID position '0-1-53,1-1-3,2-1-2,3-1-1'

2017-08-24 15:09:53 271 [Note] Slave I/O thread exiting, read up to log 'master-bin.000002', position 21865; GTID position 1-1-3,0-1-53,3-1-1,2-1-2

2017-08-24 15:09:53 283 [Note] Slave I/O thread: connected to master 'root@127.0.0.1:16060',replication starts at GTID position '1-1-3,0-1-53,3-1-1,2-1-2'

2017-08-24 15:09:53 284 [Note] Slave SQL thread initialized, starting replication in log 'master-bin.000002' at position 21865, relay log './slave-relay-bin.000001' position: 4; GTID position '0-1-53,1-1-3,2-1-2,3-1-1'

2017-08-24 15:09:53 284 [Note] Error reading relay log event: slave SQL thread was killed

2017-08-24 15:09:53 284 [Note] Slave SQL thread exiting, replication stopped in log 'master-bin.000002' at position 22574; GTID position '0-1-57,1-1-3,2-1-2,3-1-1'

2017-08-24 15:09:53 283 [Note] Slave I/O thread exiting, read up to log 'master-bin.000002', position 22574; GTID position 1-1-3,0-1-57,3-1-1,2-1-2

2017-08-24 15:09:53 295 [Note] Slave I/O thread: connected to master 'root@127.0.0.1:16060',replication starts at GTID position '1-1-3,0-1-57,3-1-1,2-1-2'

2017-08-24 15:09:53 296 [Note] Slave SQL thread initialized, starting replication in log 'master-bin.000002' at position 22574, relay log './slave-relay-bin.000001' position: 4; GTID position '0-1-57,1-1-3,2-1-2,3-1-1'

2017-08-24 15:09:53 296 [Note] Error reading relay log event: slave SQL thread was killed

2017-08-24 15:09:53 296 [Note] Slave SQL thread exiting, replication stopped in log 'master-bin.000002' at position 23324; GTID position '0-1-61,1-1-3,2-1-2,3-1-1'

2017-08-24 15:09:53 295 [Note] Slave I/O thread exiting, read up to log 'master-bin.000002', position 23324; GTID position 1-1-3,0-1-61,3-1-1,2-1-2

2017-08-24 15:09:53 308 [Note] Slave SQL thread initialized, starting replication in log 'master-bin.000002' at position 23324, relay log './slave-relay-bin.000001' position: 4; GTID position '0-1-61,1-1-3,2-1-2,3-1-1'

2017-08-24 15:09:53 307 [Note] Slave I/O thread: connected to master 'root@127.0.0.1:16060',replication starts at GTID position '1-1-3,0-1-61,3-1-1,2-1-2'

2017-08-24 15:09:53 309 [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-08-24 15:09:53 309 [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 837; GTID position '0-1-67,1-1-3,2-1-2,3-1-1'

2017-08-24 15:09:53 308 [Note] Error reading relay log event: slave SQL thread was killed

2017-08-24 15:09:53 308 [Note] Slave SQL thread exiting, replication stopped in log 'master-bin.000003' at position 837; GTID position '0-1-67,1-1-3,2-1-2,3-1-1'

2017-08-24 15:09:53 307 [Note] Slave I/O thread exiting, read up to log 'master-bin.000003', position 1054; GTID position 1-1-3,0-1-68,3-1-1,2-1-2

2017-08-24 15:09:54 310 [Note] Slave I/O thread: connected to master 'root@127.0.0.1:16060',replication starts at GTID position '1-1-3,0-1-68,3-1-1,2-1-2'

2017-08-24 15:09:54 311 [Note] Slave SQL thread initialized, starting replication in log 'master-bin.000003' at position 837, relay log './slave-relay-bin.000001' position: 4; GTID position '0-1-68,1-1-3,2-1-2,3-1-1'

2017-08-24 15:09:54 311 [Note] Error reading relay log event: slave SQL thread was killed

2017-08-24 15:09:54 311 [Note] Slave SQL thread exiting, replication stopped in log 'master-bin.000003' at position 1427; GTID position '0-1-70,1-1-3,2-1-2,3-1-1'

2017-08-24 15:09:54 310 [Note] Slave I/O thread exiting, read up to log 'master-bin.000003', position 1427; GTID position 1-1-3,0-1-70,3-1-1,2-1-2

2017-08-24 15:09:54 313 [Note] Slave I/O thread: connected to master 'root@127.0.0.1:16060',replication starts at GTID position '1-1-3,0-1-70,3-1-1,2-1-2'

2017-08-24 15:09:54 314 [Note] Slave SQL thread initialized, starting replication in log 'master-bin.000003' at position 1427, relay log './slave-relay-bin.000001' position: 4; GTID position '0-1-70,1-1-3,2-1-2,3-1-1'

2017-08-24 15:09:54 314 [ERROR] Slave SQL: Error 'Duplicate entry '32' for key 'PRIMARY'' on query. Default database: 'test'. Query: 'INSERT INTO t2 VALUES (32)', Gtid 0-1-71, Internal MariaDB error code: 1062

2017-08-24 15:09:54 314 [Warning] Slave: Duplicate entry '32' for key 'PRIMARY' Error_code: 1062

2017-08-24 15:09:54 314 [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 1427; GTID position '0-1-70,1-1-3,2-1-2,3-1-1'

2017-08-24 15:09:54 314 [Note] Slave SQL thread exiting, replication stopped in log 'master-bin.000003' at position 1427; GTID position '0-1-70,1-1-3,2-1-2,3-1-1'

2017-08-24 15:09:54 313 [ERROR] Error reading packet from server: Lost connection to MySQL server during query (server_errno=2013)

2017-08-24 15:09:54 313 [Note] Slave I/O thread exiting, read up to log 'master-bin.000004', position 807; GTID position 1-1-3,0-1-73,3-1-1,2-1-2

2017-08-24 15:09:54 315 [Note] Slave I/O thread: connected to master 'root@127.0.0.1:16060',replication starts at GTID position '1-1-3,0-1-70,3-1-1,2-1-2'

2017-08-24 15:09:54 316 [Note] Slave SQL thread initialized, starting replication in log 'master-bin.000003' at position 1427, relay log './slave-relay-bin.000001' position: 4; GTID position '0-1-70,1-1-3,2-1-2,3-1-1'

2017-08-24 15:09:54 317 [ERROR] Slave SQL: Error 'Duplicate entry '32' for key 'PRIMARY'' on query. Default database: 'test'. Query: 'INSERT INTO t2 VALUES (32)', Gtid 0-1-71, Internal MariaDB error code: 1062

2017-08-24 15:09:54 317 [Warning] Slave: Duplicate entry '32' for key 'PRIMARY' Error_code: 1062

2017-08-24 15:09:54 317 [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 1427; GTID position '0-1-70,1-1-3,2-1-2,3-1-1'

2017-08-24 15:09:54 316 [Note] Error reading relay log event: slave SQL thread was killed

2017-08-24 15:09:54 316 [Note] Slave SQL thread exiting, replication stopped in log 'master-bin.000003' at position 1427; GTID position '0-1-70,1-1-3,2-1-2,3-1-1'

2017-08-24 15:09:54 327 [Note] Slave SQL thread initialized, starting replication in log 'master-bin.000003' at position 1427, relay log './slave-relay-bin.000001' position: 4; GTID position '0-1-70,1-1-3,2-1-2,3-1-1'

2017-08-24 15:09:54 336 [ERROR] Slave SQL: Error 'Duplicate entry '32' for key 'PRIMARY'' on query. Default database: 'test'. Query: 'INSERT INTO t2 VALUES (32)', Gtid 0-1-71, Internal MariaDB error code: 1062

2017-08-24 15:09:54 336 [Warning] Slave: Duplicate entry '32' for key 'PRIMARY' Error_code: 1062

2017-08-24 15:09:54 336 [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 1427; GTID position '0-1-70,1-1-3,2-1-2,3-1-1'

2017-08-24 15:09:54 327 [Note] Error reading relay log event: slave SQL thread was killed

2017-08-24 15:09:54 327 [Note] Slave SQL thread exiting, replication stopped in log 'master-bin.000003' at position 1427; GTID position '0-1-70,1-1-3,2-1-2,3-1-1'

2017-08-24 15:09:54 315 [Note] Slave I/O thread exiting, read up to log 'master-bin.000004', position 807; GTID position 1-1-3,0-1-73,3-1-1,2-1-2

2017-08-24 15:09:54 338 [Note] Slave I/O thread: connected to master 'root@127.0.0.1:16060',replication starts at GTID position '1-1-3,0-1-71,3-1-1,2-1-2'

2017-08-24 15:09:54 339 [Note] Slave SQL thread initialized, starting replication in log 'master-bin.000003' at position 1427, relay log './slave-relay-bin.000001' position: 4; GTID position '0-1-71,1-1-3,2-1-2,3-1-1'

2017-08-24 15:09:54 339 [Note] Error reading relay log event: slave SQL thread was killed

2017-08-24 15:09:54 339 [Note] Slave SQL thread exiting, replication stopped in log 'master-bin.000004' at position 1167; GTID position '0-1-75,1-1-3,2-1-2,3-1-1'

2017-08-24 15:09:54 338 [Note] Slave I/O thread exiting, read up to log 'master-bin.000004', position 1167; GTID position 1-1-3,0-1-75,3-1-1,2-1-2

2017-08-24 15:09:54 350 [Note] Slave I/O thread: connected to master 'root@127.0.0.1:16060',replication starts at GTID position '1-1-3,0-1-75,3-1-1,2-1-2'

2017-08-24 15:09:54 351 [Note] Slave SQL thread initialized, starting replication in log 'master-bin.000004' at position 1167, relay log './slave-relay-bin.000001' position: 4; GTID position '0-1-75,1-1-3,2-1-2,3-1-1'

2017-08-24 15:09:55 351 [Note] Error reading relay log event: slave SQL thread was killed

2017-08-24 15:09:55 351 [Note] Slave SQL thread exiting, replication stopped in log 'master-bin.000004' at position 1550; GTID position '0-1-77,1-1-3,2-1-2,3-1-1'

2017-08-24 15:09:55 350 [Note] Slave I/O thread exiting, read up to log 'master-bin.000004', position 1550; GTID position 1-1-3,0-1-77,3-1-1,2-1-2

170824 15:09:55 [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.3.1-MariaDB-debug-log

key_buffer_size=1048576

read_buffer_size=131072

max_used_connections=7

max_threads=153

thread_count=14

It is possible that mysqld could use up to 

key_buffer_size + (read_buffer_size + sort_buffer_size)*max_threads = 61889 K  bytes of memory

Hope that's ok; if not, decrease some variables in the equation.

Thread pointer: 0x0

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 = 0x0 thread_stack 0x49000

2017-08-24 15:09:55 362 [Note] Slave I/O thread: connected to master 'root@127.0.0.1:16060',replication starts at GTID position '1-1-3,0-1-77,3-1-1,2-1-2'

/mnt/buildbot/build/mariadb-10.3.1/sql/mysqld(my_print_stacktrace+0x3b)[0x8d90d57]

2017-08-24 15:09:55 363 [Note] Slave SQL thread initialized, starting replication in log 'master-bin.000004' at position 1550, relay log './slave-relay-bin.000001' position: 4; GTID position '0-1-77,1-1-3,2-1-2,3-1-1'

/mnt/buildbot/build/mariadb-10.3.1/sql/mysqld(handle_fatal_signal+0x3cf)[0x8627bd3]

[0xb7764400]

/mnt/buildbot/build/mariadb-10.3.1/sql/mysqld(_db_flush_+0x29)[0x8db3f4b]

/mnt/buildbot/build/mariadb-10.3.1/sql/mysqld[0x8c3aa4a]

/mnt/buildbot/build/mariadb-10.3.1/sql/mysqld[0x8c4c2d5]

/mnt/buildbot/build/mariadb-10.3.1/sql/mysqld[0x8c3c2bd]

/mnt/buildbot/build/mariadb-10.3.1/sql/mysqld[0x8c4baa2]

/mnt/buildbot/build/mariadb-10.3.1/sql/mysqld[0x89c8c3a]

/mnt/buildbot/build/mariadb-10.3.1/sql/mysqld[0x89c97e4]

/mnt/buildbot/build/mariadb-10.3.1/sql/mysqld[0x8bcdefd]

/mnt/buildbot/build/mariadb-10.3.1/sql/mysqld[0x8bce822]

/mnt/buildbot/build/mariadb-10.3.1/sql/mysqld[0x8bcf0a6]

/mnt/buildbot/build/mariadb-10.3.1/sql/mysqld[0x8bcf43a]

/mnt/buildbot/build/mariadb-10.3.1/sql/mysqld[0x8bcffd6]

/mnt/buildbot/build/mariadb-10.3.1/sql/mysqld[0x8bd0538]

/mnt/buildbot/build/mariadb-10.3.1/sql/mysqld[0x8bd0c54]

/mnt/buildbot/build/mariadb-10.3.1/sql/mysqld[0x8bd0f8b]

/mnt/buildbot/build/mariadb-10.3.1/sql/mysqld[0x8bd4ce6]

/lib/i386-linux-gnu/libpthread.so.0(+0x6d4c)[0xb74ecd4c]

/lib/i386-linux-gnu/libc.so.6(clone+0x5e)[0xb72fcace]

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-------------