MHA repl报错

报错"/>

MHA repl报错

发现MHA告警：进行主从健康检查，报错如下：

masterha_check_repl --conf=/etc/mha/app1f

Fri May 20 17:25:43 2022 - [warning] Global configuration file /etc/masterha_defaultf not found. Skipping.

Fri May 20 17:25:43 2022 - [info] Reading application default configuration from /etc/mha/app1f…

Fri May 20 17:25:43 2022 - [info] Reading server configuration from /etc/mha/app1f…

Fri May 20 17:25:43 2022 - [info] MHA::MasterMonitor version 0.56.

Fri May 20 17:25:44 2022 - [error][/usr/share/perl5/vendor_perl/MHA/ServerManager.pm, ln671] Master 192.168.4.2:33006 from which slave 192.168.6.8(192.168.6.8：33006) replicates is not defined in the configuration file!

Fri May 20 17:25:44 2022 - [error][/usr/share/perl5/vendor_perl/MHA/MasterMonitor.pm, ln424] Error happened on checking configurations. at /usr/share/perl5/vendor_perl/MHA/MasterMonitor.pm line 326.

Fri May 20 17:25:44 2022 - [error][/usr/share/perl5/vendor_perl/MHA/MasterMonitor.pm, ln523] Error happened on monitoring servers.

Fri May 20 17:25:44 2022 - [info] Got exit code 1 (Not master dead).

MySQL Replication Health is NOT OK!

经过排查，192.168.6.8作为一套集群的主库，同时也是192.168.4.2的从库，正在进行主从同步，所以在进行repl检查时报如上错误。

网上的解决方案大多是因为MHA配置文件里面缺少了主库的配置

加入主库配置即可，我上面的情况只是作为一个补充，应该很少出现