[root@192 app1]# masterha_check_ssh -conf=/etc/masterha/app1.cnf
Fri Jul 9 03:11:31 2021 - [warning] Global configuration file /etc/masterha_default.cnf not found. Skipping.
/etc/masterha/app1.cnf:
at /usr/local/share/perl5/MHA/SSHCheck.pm line 148.
Fri Jul 9 05:17:12 2021 - [info] Connecting to root@192.168.2.33(192.168.2.33:22)..
Can't exec "mysqlbinlog": No such file or directory at /usr/local/share/perl5/MHA/BinlogManager.pm line 106.
mysqlbinlog version command failed with rc 1:0, please verify PATH, LD_LIBRARY_PATH, and client options
at /usr/local/bin/apply_diff_relay_logs line 493.
Fri Jul 9 05:17:13 2021 - [error][/usr/local/share/perl5/MHA/MasterMonitor.pm, ln208] Slaves settings check failed!
Fri Jul 9 05:17:13 2021 - [error][/usr/local/share/perl5/MHA/MasterMonitor.pm, ln416] Slave configuration failed.
Fri Jul 9 05:17:13 2021 - [error][/usr/local/share/perl5/MHA/MasterMonitor.pm, ln427] Error happened on checking configurations. at /usr/local/bin/masterha_check_repl line 48.
Fri Jul 9 05:17:13 2021 - [error][/usr/local/share/perl5/MHA/MasterMonitor.pm, ln525] Error happened on monitoring servers.
Fri Jul 9 05:17:13 2021 - [info] Got exit code 1 (Not master dead).
MySQL Replication Health is NOT OK!
解决方法
ln -s /usr/local/mysql/bin/mysqlbinlog /usr/bin/mysqlbinlog
vim /etc/masterha/app1.cnf
这篇博客记录了在使用MHA(Master High Availability)进行MySQL复制监控时遇到的问题,包括找不到全局配置文件、无法执行mysqlbinlog命令以及 slave设置检查失败等错误。解决方案是创建软链接到mysqlbinlog的正确路径,并检查app1.cnf配置文件。通过这些步骤,可以解决MySQL Replication的健康问题。
1824

被折叠的 条评论
为什么被折叠?



