Slave IO thread is not running on问题的解决

搭建MHA最少需要3台MySQL服务器，一主两从，一从做slave，一从兼职做manager
基本环境做好
（mysql安装（同一版本）
防火墙、selinux永久关闭
配置好/etc/hosts
xtrabackup工具安装）

今天我在搭建中，不小心在主库也执行了start slave，结果在manager上执行
[root@rhel3 ~]# masterha_check_repl --conf=/etc/masterha/app1.cnf命令时出现错误，复制环境检查不成功

172.16.8.12 (current master)
 +--172.16.8.12
 +--172.16.8.13
 +--172.16.8.11

Sun Jun 23 17:45:58 2019 - [info] Checking replication health on 172.16.8.12..
Sun Jun 23 17:45:58 2019 - [error][/usr/share/perl5/vendor_perl/MHA/Server.pm, ln472] Slave IO thread is not running on 172.16.8.12(172.16.8.12:3306)
Sun Jun 23 17:45:58 2019 - [error][/usr/share/perl5/vendor_perl/MHA/ServerManager.pm, ln1429]  failed!
Sun Jun 23 17:45:58 2019 - [error][/usr/share/perl5/vendor_perl/MHA/MasterMonitor.pm, ln386] Error happend on checking configurations.  at /usr/share/perl5/vendor_perl/MHA/MasterMonitor.pm line 379
Sun Jun 23 17:45:58 2019 - [error][/usr/share/perl5/vendor_perl/MHA/MasterMonitor.pm, ln482] Error happened on monitoring servers.
Sun Jun 23 17:45:58 2019 - [info] Got exit code 1 (Not master dead).

MySQL Replication Health is NOT OK!

如上，主库是8.12，从库中也有8.12，报的错如上，从IO线程不在172.16.8.12(172.16.8.12:3306)上运行，
找到问题就好解决，
执行

mysql> reset slave all;
Query OK, 0 rows affected (0.02 sec)

再在manager上执行命令，复制环境检查成功

172.16.8.12 (current master)
 +--172.16.8.13
 +--172.16.8.11

Sun Jun 23 17:46:38 2019 - [info] Checking replication health on 172.16.8.13..
Sun Jun 23 17:46:38 2019 - [info]  ok.
Sun Jun 23 17:46:38 2019 - [info] Checking replication health on 172.16.8.11..
Sun Jun 23 17:46:38 2019 - [info]  ok.
Sun Jun 23 17:46:38 2019 - [info] Checking master_ip_failover_script status:
Sun Jun 23 17:46:38 2019 - [info]   /usr/bin/master_ip_failover --command=status --ssh_user=root --orig_master_host=172.16.8.12 --orig_master_ip=172.16.8.12 --orig_master_port=3306 
Checking the Status of the script.. OK 
Sun Jun 23 17:46:38 2019 - [info]  OK.
Sun Jun 23 17:46:38 2019 - [warning] shutdown_script is not defined.
Sun Jun 23 17:46:38 2019 - [info] Got exit code 0 (Not master dead).

MySQL Replication Health is OK.