[MDEV-20141] rpl.rpl_gtid_startpos failed in buildbot with "mysqltest failed but provided no output" Created: 2019-07-23  Updated: 2023-11-29  Resolved: 2023-11-29

Status: Closed
Project: MariaDB Server
Component/s: Replication, Tests
Affects Version/s: 10.2
Fix Version/s: N/A

Type: Bug Priority: Minor
Reporter: Elena Stepanova Assignee: Andrei Elkin
Resolution: Won't Fix Votes: 0
Labels: None


 Description   

http://buildbot.askmonty.org/buildbot/builders/kvm-rpm-centos74-amd64-debug/builds/2304/steps/mtr/logs/stdio

10.2 26b594e4110b4f7e6f2bcfbdb4c87aef

rpl.rpl_gtid_startpos 'innodb,mix'       w1 [ fail ]
        Test ended at 2019-07-18 12:50:03
 
CURRENT_TEST: rpl.rpl_gtid_startpos
 
 
Server [mysqld.1 - pid: 29638, winpid: 29638, exit: 0] failed during test run
Server log from this test:
----------SERVER LOG START-----------
2019-07-18 12:49:54 140412618110720 [Note] Deleted Master_info file '/dev/shm/var/1/mysqld.1/data/master.info'.
2019-07-18 12:49:54 140412618110720 [Note] Deleted Master_info file '/dev/shm/var/1/mysqld.1/data/relay-log.info'.
2019-07-18 12:49:54 140412655568640 [Note] Start binlog_dump to slave_server(2), pos(master-bin.000001, 4)
2019-07-18 12:49:55 140412655568640 [Warning] Aborted connection 148 to db: 'unconnected' user: 'root' host: 'localhost' (Got an error writing communication packets)
2019-07-18 12:49:55 140412618413824 [Note] Start binlog_dump to slave_server(2), pos(, 4)
2019-07-18 12:49:55 140412655265536 [Note] Start binlog_dump to slave_server(2), pos(, 4)
2019-07-18 12:49:55 140412618413824 [Warning] Aborted connection 149 to db: 'unconnected' user: 'root' host: 'localhost' (A slave with the same server_uuid/server_id as this slave has co)
2019-07-18 12:49:55 140412618716928 [Note] Start binlog_dump to slave_server(2), pos(master-bin.000003, 4)
2019-07-18 12:49:55 140412655568640 [Note] Start binlog_dump to slave_server(2), pos(, 4)
2019-07-18 12:49:55 140412618716928 [Warning] Aborted connection 151 to db: 'unconnected' user: 'root' host: 'localhost' (A slave with the same server_uuid/server_id as this slave has co)
2019-07-18 12:49:56 140412655265536 [Note] Start binlog_dump to slave_server(2), pos(master-bin.000003, 716)
2019-07-18 12:49:56 140412655568640 [Warning] Aborted connection 152 to db: 'unconnected' user: 'root' host: 'localhost' (A slave with the same server_uuid/server_id as this slave has co)
2019-07-18 12:49:57 140412618413824 [Note] Start binlog_dump to slave_server(2), pos(, 4)
2019-07-18 12:49:57 140412618716928 [Note] Start binlog_dump to slave_server(2), pos(master-bin.000001, 680)
2019-07-18 12:49:57 140412655568640 [Note] Start binlog_dump to slave_server(2), pos(, 4)
2019-07-18 12:49:57 140412655265536 [Note] Start binlog_dump to slave_server(2), pos(, 4)
2019-07-18 12:49:57 140412618413824 [Note] Start binlog_dump to slave_server(2), pos(, 4)
2019-07-18 12:49:57 140412618716928 [Note] Start binlog_dump to slave_server(2), pos(master-bin.000001, 329)
2019-07-18 12:49:58 140412618716928 [Warning] Aborted connection 159 to db: 'unconnected' user: 'root' host: 'localhost' (Got an error writing communication packets)
2019-07-18 12:49:58 140412655568640 [Note] Start binlog_dump to slave_server(2), pos(, 4)
2019-07-18 12:49:58 140412655265536 [Note] Start binlog_dump to slave_server(2), pos(master-bin.000004, 594)
2019-07-18 12:49:58 140412617504512 [Note] /usr/sbin/mysqld (initiated by: unknown): Normal shutdown
2019-07-18 12:49:58 140412617504512 [Note] Event Scheduler: Purging the queue. 0 events
2019-07-18 12:49:58 140412404623104 [Note] InnoDB: FTS optimize thread exiting.
2019-07-18 12:49:58 140412617504512 [Note] InnoDB: Starting shutdown...
2019-07-18 12:49:58 140412362659584 [Note] InnoDB: Dumping buffer pool(s) to /dev/shm/var/1/mysqld.1/data/ib_buffer_pool
2019-07-18 12:49:58 140412362659584 [Note] InnoDB: Instance 0, restricted to 127 pages due to innodb_buf_pool_dump_pct=25
2019-07-18 12:49:58 140412362659584 [Note] InnoDB: Buffer pool(s) dump completed at 190718 12:49:58
2019-07-18 12:49:59 140412617504512 [Note] InnoDB: Shutdown completed; log sequence number 11163322
2019-07-18 12:49:59 140412617504512 [Note] InnoDB: Removed temporary tablespace data file: "ibtmp1"
2019-07-18 12:49:59 140412617504512 [Note] Debug sync points hit:                   58168
2019-07-18 12:49:59 140412617504512 [Note] Debug sync points executed:              0
2019-07-18 12:49:59 140412617504512 [Note] Debug sync points max active per thread: 0
2019-07-18 12:49:59 140412617504512 [Note] /usr/sbin/mysqld: Shutdown complete
 
----------SERVER LOG END-------------
mysqltest failed but provided no output
The result from queries just before the failure was:
< snip >
Using_Gtid
Current_Pos
SELECT '0-1-2' AS Gtid_Slave_Pos;
Gtid_Slave_Pos
0-1-2
UPDATE t1 SET a=9 WHERE a=10;
UPDATE t1 SET a=10 WHERE a=9;
SELECT '0-2-4' AS Gtid_Slave_Pos;
Gtid_Slave_Pos
0-2-4
include/stop_slave.inc
SET GLOBAL gtid_slave_pos='0-1-2';
Warnings:
Warning	1947	Specified GTID 0-1-2 conflicts with the binary log which contains a more recent GTID 0-2-4. If MASTER_GTID_POS=CURRENT_POS is used, the binlog position will override the new value of @@gtid_slave_pos
RESET MASTER;
SELECT '0-1-2' AS Gtid_Slave_Pos;
Gtid_Slave_Pos
0-1-2
SET GLOBAL gtid_slave_pos='0-1-2';
include/start_slave.inc


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