gtid集群搭建好后，检测通过不了，哪位大师帮我分析一下原因

来源：5-8 MySQL复制性能优化

宝慕林2132329

2020-01-29

老师，问题我201数据库是可以访问的呀，下面是201的状态，为什么通过脚本检查显示不可用？
mysql> show slave status \G
*************************** 1. row ***************************
Slave_IO_State: Waiting for master to send event
Master_Host: 192.168.0.200
Master_User: rep
Master_Port: 3306
Connect_Retry: 60
Master_Log_File: master-bin.000009
Read_Master_Log_Pos: 194
Relay_Log_File: relay-bin.000003
Relay_Log_Pos: 409
Relay_Master_Log_File: master-bin.000009
Slave_IO_Running: Yes
Slave_SQL_Running: Yes
Replicate_Do_DB:
Replicate_Wild_Ignore_Table: Last_Errno: 0 Last_Error: Skip_Counter: 0
200主库配置如下
[mysqld]
server_id=200
log_bin=/var/lib/mysql/master-bin
gtid_mode=on
enforce-gtid-consistency=on
datadir=/var/lib/mysql
socket=/var/lib/mysql/mysql.sock
relay_log=/var/lib/mysql/relay-bin
master_info_repository=table
relay_log_info_repository=table
201从库配置如下
[mysqld]
datadir=/var/lib/mysql
socket=/var/lib/mysql/mysql.sock
server_id=201
read_only=on
gtid_mode=on
enforce-gtid-consistency=on
log_bin=master-bin2
skip-slave-start = 1
relay_log=/var/lib/mysql/relay-bin
202 my.cnf配置如下
datadir=/var/lib/mysql
socket=/var/lib/mysql/mysql.sock
server_id=202
gtid_mode=on
enforce_gtid_consistency=on
relay_log=/var/lib/mysql/relay-bin
master_info_repository=table
log_bin=master-bin3
read_only=on
master_ip_failover 文件如下

my $vip = ‘192.168.0.220/24’;
my $key = ‘1’;
my $ssh_start_vip = "sudo /sbin/ifconfig enp0s3:$ key $vip";
my $ssh_stop_vip = "sudo /sbin/ifconfig enp0s3:$ key down";
my $ssh_Bcast_arp= “sudo /sbin/arping -I bond0 -c 3 -A 192.168.0.220”;
检测信息
[root@rep3 bin]# masterha_check_repl --conf=/etc/mha/mha_mysql.cnf
Tue Jan 28 23:52:04 2020 - [info] MHA::MasterMonitor version 0.57.
Tue Jan 28 23:52:05 2020 - [info] GTID failover mode = 1
Tue Jan 28 23:52:05 2020 - [info] Dead Servers:
Tue Jan 28 23:52:05 2020 - [info] 192.168.0.201(192.168.0.201:3306)
Tue Jan 28 23:52:05 2020 - [info] Alive Servers:
Tue Jan 28 23:52:05 2020 - [info] 192.168.0.200(192.168.0.200:3306)
Tue Jan 28 23:52:05 2020 - [info] 192.168.0.202(192.168.0.202:3306)
Tue Jan 28 23:52:05 2020 - [info] Alive Slaves:
Tue Jan 28 23:52:05 2020 - [info] 192.168.0.202(192.168.0.202:3306) Version=5.7.29-log (oldest major version between slaves) log-bin:enabled
Tue Jan 28 23:52:05 2020 - [info] GTID ON
Tue Jan 28 23:52:05 2020 - [info] Replicating from 192.168.0.200(192.168.0.200:3306)
Tue Jan 28 23:52:05 2020 - [info] Not candidate for the new Master (no_master is set)
Tue Jan 28 23:52:05 2020 - [info] Current Alive Master: 192.168.0.200(192.168.0.200:3306)
Tue Jan 28 23:52:05 2020 - [info] Checking slave configurations…
Tue Jan 28 23:52:05 2020 - [info] Checking replication filtering settings…
Tue Jan 28 23:52:05 2020 - [info] binlog_do_db= , binlog_ignore_db=
Tue Jan 28 23:52:05 2020 - [info] Replication filtering check ok.
Tue Jan 28 23:52:05 2020 - [error][/usr/share/perl5/vendor_perl/MHA/MasterMonitor.pm, ln364] None of slaves can be master. Check failover configuration file or log-bin settings in my.cnf
Tue Jan 28 23:52:05 2020 - [error][/usr/share/perl5/vendor_perl/MHA/MasterMonitor.pm, ln427] Error happened on checking configurations. at /usr/bin/masterha_check_repl line 48.
Tue Jan 28 23:52:05 2020 - [error][/usr/share/perl5/vendor_perl/MHA/MasterMonitor.pm, ln525] Error happened on monitoring servers.
Tue Jan 28 23:52:05 2020 - [info] Got exit code 1 (Not master dead).