MHA監控檢測報錯

MHA安裝之后一直正常運行，中間也有出現過切換的情況，不過都正常進行，后有其他dba在mha自動切換后做過一些操作，但并未說做了哪些操作。我再查看狀態時，發現監控沒有在運行，于是手工啟動，結果就報以下錯誤：

Mon?Nov?20?17:15:11?2017?-?[info]?MHA::MasterMonitor?version?0.56.
Mon?Nov?20?17:15:12?2017?-?[info]?GTID?failover?mode?=?0
Mon?Nov?20?17:15:12?2017?-?[info]?Dead?Servers:
Mon?Nov?20?17:15:12?2017?-?[info]?Alive?Servers:
Mon?Nov?20?17:15:12?2017?-?[info]???192.168.2.211(192.168.2.211:3206)
Mon?Nov?20?17:15:12?2017?-?[info]???192.168.2.212(192.168.2.212:3206)
Mon?Nov?20?17:15:12?2017?-?[info]???192.168.2.213(192.168.2.213:3206)
Mon?Nov?20?17:15:12?2017?-?[info]?Alive?Slaves:
Mon?Nov?20?17:15:12?2017?-?[info]???192.168.2.212(192.168.2.212:3206)??Version=5.6.24-log?(oldest?major?version?between?slaves)?log-bin:enabled
Mon?Nov?20?17:15:12?2017?-?[info]?????Replicating?from?192.168.2.211(192.168.2.211:3206)
Mon?Nov?20?17:15:12?2017?-?[info]?????Primary?candidate?for?the?new?Master?(candidate_master?is?set)
Mon?Nov?20?17:15:12?2017?-?[info]???192.168.2.213(192.168.2.213:3206)??Version=5.6.24-log?(oldest?major?version?between?slaves)?log-bin:enabled
Mon?Nov?20?17:15:12?2017?-?[info]?????Replicating?from?192.168.2.211(192.168.2.211:3206)
Mon?Nov?20?17:15:12?2017?-?[info]?????Not?candidate?for?the?new?Master?(no_master?is?set)
Mon?Nov?20?17:15:12?2017?-?[info]?Current?Alive?Master:?192.168.2.211(192.168.2.211:3206)
Mon?Nov?20?17:15:12?2017?-?[info]?Checking?slave?configurations..
Mon?Nov?20?17:15:12?2017?-?[warning]??relay_log_purge=0?is?not?set?on?slave?192.168.2.213(192.168.2.213:3206).
Mon?Nov?20?17:15:12?2017?-?[info]?Checking?replication?filtering?settings..
Mon?Nov?20?17:15:12?2017?-?[info]??binlog_do_db=?,?binlog_ignore_db=
Mon?Nov?20?17:15:12?2017?-?[info]??Replication?filtering?check?ok.
Mon?Nov?20?17:15:12?2017?-?[info]?GTID?(with?auto-pos)?is?not?supported
Mon?Nov?20?17:15:12?2017?-?[info]?Starting?SSH?connection?tests..
Mon?Nov?20?17:15:15?2017?-?[info]?All?SSH?connection?tests?passed?successfully.
Mon?Nov?20?17:15:15?2017?-?[info]?Checking?MHA?Node?version..
Mon?Nov?20?17:15:15?2017?-?[error][/usr/local/share/perl5/MHA/ManagerUtil.pm,?ln122]?Got?error?when?getting?node?version.?Error:
Mon?Nov?20?17:15:15?2017?-?[error][/usr/local/share/perl5/MHA/ManagerUtil.pm,?ln123]
bash:?apply_diff_relay_logs:?command?not?found
Mon?Nov?20?17:15:15?2017?-?[error][/usr/local/share/perl5/MHA/ManagerUtil.pm,?ln150]?node?version?on?192.168.2.212?not?found!?Is?MHA?Node?package?installed??
?at?/usr/local/share/perl5/MHA/MasterMonitor.pm?line?374.
Mon?Nov?20?17:15:15?2017?-?[error][/usr/local/share/perl5/MHA/MasterMonitor.pm,?ln424]?Error?happened?on?checking?configurations.?node?version?on?192.168.2.212?not?found!?Is?MHA?Node?package?installed??
?at?/usr/local/share/perl5/MHA/MasterMonitor.pm?line?374.
????????...propagated?at?/usr/local/share/perl5/MHA/ManagerUtil.pm?line?151.
Mon?Nov?20?17:15:15?2017?-?[error][/usr/local/share/perl5/MHA/MasterMonitor.pm,?ln523]?Error?happened?on?monitoring?servers.
Mon?Nov?20?17:15:15?2017?-?[info]?Got?exit?code?1?(Not?master?dead).

提示到不到命令，同時提示我是否節點2是否沒有安裝node包，我做過以下嘗試：

1）嘗試配置環境變量路徑，錯誤依舊。

2）嘗試重新安裝node包，錯誤依舊。

網上也查找過報錯信息，但都是千篇一律，一篇文章轉來轉去，沒有對應的解決方法。

后來空了又仔細看了下，問題解決掉了，解決方法如下：

[root@kxt-mha-03?~]#?find?/?-name?apply_diff_relay_logs
/usr/local/bin/apply_diff_relay_logs
[root@kxt-mha-03?~]#?ln?-s?/usr/local/bin/apply_diff_relay_logs??/usr/bin/
[root@kxt-mha-03?~]#?ln?-s?/usr/local/bin/save_binary_logs???/usr/bin/
[root@kxt-mha-02?~]#?ln?-s?/usr/local/bin/apply_diff_relay_logs??/usr/bin/
[root@kxt-mha-02?~]#?ln?-s?/usr/local/bin/save_binary_logs???/usr/bin/
[root@kxt-mha-01?~]#?ln?-s?/usr/local/bin/apply_diff_relay_logs??/usr/bin/
[root@kxt-mha-01?~]#?ln?-s?/usr/local/bin/save_binary_logs???/usr/bin/
再次做檢測：
Wed?Feb?28?10:48:40?2018?-?[warning]?Global?configuration?file?/etc/masterha_default.cnf?not?found.?Skipping.
Wed?Feb?28?10:48:40?2018?-?[info]?Reading?application?default?configuration?from?/etc/mha/conf/app1.cnf..
Wed?Feb?28?10:48:40?2018?-?[info]?Reading?server?configuration?from?/etc/mha/conf/app1.cnf..
Wed?Feb?28?10:48:40?2018?-?[info]?MHA::MasterMonitor?version?0.56.
Wed?Feb?28?10:48:41?2018?-?[info]?GTID?failover?mode?=?0
Wed?Feb?28?10:48:41?2018?-?[info]?Dead?Servers:
Wed?Feb?28?10:48:41?2018?-?[info]?Alive?Servers:
Wed?Feb?28?10:48:41?2018?-?[info]???192.168.2.211(192.168.2.211:3206)
Wed?Feb?28?10:48:41?2018?-?[info]???192.168.2.212(192.168.2.212:3206)
Wed?Feb?28?10:48:41?2018?-?[info]???192.168.2.213(192.168.2.213:3206)
Wed?Feb?28?10:48:41?2018?-?[info]?Alive?Slaves:
Wed?Feb?28?10:48:41?2018?-?[info]???192.168.2.212(192.168.2.212:3206)??Version=5.6.24-log?(oldest?major?version?between?slaves)?log-bin:enabled
Wed?Feb?28?10:48:41?2018?-?[info]?????Replicating?from?192.168.2.211(192.168.2.211:3206)
Wed?Feb?28?10:48:41?2018?-?[info]?????Primary?candidate?for?the?new?Master?(candidate_master?is?set)
Wed?Feb?28?10:48:41?2018?-?[info]???192.168.2.213(192.168.2.213:3206)??Version=5.6.24-log?(oldest?major?version?between?slaves)?log-bin:enabled
Wed?Feb?28?10:48:41?2018?-?[info]?????Replicating?from?192.168.2.211(192.168.2.211:3206)
Wed?Feb?28?10:48:41?2018?-?[info]?????Not?candidate?for?the?new?Master?(no_master?is?set)
Wed?Feb?28?10:48:41?2018?-?[info]?Current?Alive?Master:?192.168.2.211(192.168.2.211:3206)
Wed?Feb?28?10:48:41?2018?-?[info]?Checking?slave?configurations..
Wed?Feb?28?10:48:41?2018?-?[warning]??relay_log_purge=0?is?not?set?on?slave?192.168.2.213(192.168.2.213:3206).
Wed?Feb?28?10:48:41?2018?-?[info]?Checking?replication?filtering?settings..
Wed?Feb?28?10:48:41?2018?-?[info]??binlog_do_db=?,?binlog_ignore_db=?
Wed?Feb?28?10:48:41?2018?-?[info]??Replication?filtering?check?ok.
Wed?Feb?28?10:48:41?2018?-?[info]?GTID?(with?auto-pos)?is?not?supported
Wed?Feb?28?10:48:41?2018?-?[info]?Starting?SSH?connection?tests..
Wed?Feb?28?10:48:44?2018?-?[info]?All?SSH?connection?tests?passed?successfully.
Wed?Feb?28?10:48:44?2018?-?[info]?Checking?MHA?Node?version..
Wed?Feb?28?10:48:44?2018?-?[info]??Version?check?ok.
Wed?Feb?28?10:48:44?2018?-?[info]?Checking?SSH?publickey?authentication?settings?on?the?current?master..
Wed?Feb?28?10:48:44?2018?-?[info]?HealthCheck:?SSH?to?192.168.2.211?is?reachable.
Wed?Feb?28?10:48:45?2018?-?[info]?Master?MHA?Node?version?is?0.56.
Wed?Feb?28?10:48:45?2018?-?[info]?Checking?recovery?script?configurations?on?192.168.2.211(192.168.2.211:3206)..
Wed?Feb?28?10:48:45?2018?-?[info]???Executing?command:?save_binary_logs?--command=test?--start_pos=4?--binlog_dir=/data/mysql/data?--output_file=/etc/mha/app1/save_binary_logs_test?--manager_version=0.56?--start_file=mysql-bin.013591?
Wed?Feb?28?10:48:45?2018?-?[info]???Connecting?to?root@192.168.2.211(192.168.2.211:22)..?
??Creating?/etc/mha/app1?if?not?exists..????ok.
??Checking?output?directory?is?accessible?or?not..
???ok.
??Binlog?found?at?/data/mysql/data,?up?to?mysql-bin.013591
Wed?Feb?28?10:48:45?2018?-?[info]?Binlog?setting?check?done.
Wed?Feb?28?10:48:45?2018?-?[info]?Checking?SSH?publickey?authentication?and?checking?recovery?script?configurations?on?all?alive?slave?servers..
Wed?Feb?28?10:48:45?2018?-?[info]???Executing?command?:?apply_diff_relay_logs?--command=test?--slave_user='root'?--slave_host=192.168.2.212?--slave_ip=192.168.2.212?--slave_port=3206?--workdir=/etc/mha/app1?--target_version=5.6.24-log?--manager_version=0.56?--relay_dir=/data/mysql/data?--current_relay_log=mysql-relay-bin.000091??--slave_pass=xxx
Wed?Feb?28?10:48:45?2018?-?[info]???Connecting?to?root@192.168.2.212(192.168.2.212:22)..?
??Checking?slave?recovery?environment?settings..
????Relay?log?found?at?/data/mysql/data,?up?to?mysql-relay-bin.000091
????Temporary?relay?log?file?is?/data/mysql/data/mysql-relay-bin.000091
????Testing?mysql?connection?and?privileges..Warning:?Using?a?password?on?the?command?line?interface?can?be?insecure.
?done.
????Testing?mysqlbinlog?output..?done.
????Cleaning?up?test?file(s)..?done.
Wed?Feb?28?10:48:46?2018?-?[info]???Executing?command?:?apply_diff_relay_logs?--command=test?--slave_user='root'?--slave_host=192.168.2.213?--slave_ip=192.168.2.213?--slave_port=3206?--workdir=/etc/mha/app1?--target_version=5.6.24-log?--manager_version=0.56?--relay_dir=/data/mysql/data?--current_relay_log=mysql-relay-bin.020034??--slave_pass=xxx
Wed?Feb?28?10:48:46?2018?-?[info]???Connecting?to?root@192.168.2.213(192.168.2.213:22)..?
??Checking?slave?recovery?environment?settings..
????Relay?log?found?at?/data/mysql/data,?up?to?mysql-relay-bin.020034
????Temporary?relay?log?file?is?/data/mysql/data/mysql-relay-bin.020034
????Testing?mysql?connection?and?privileges..Warning:?Using?a?password?on?the?command?line?interface?can?be?insecure.
?done.
????Testing?mysqlbinlog?output..?done.
????Cleaning?up?test?file(s)..?done.
Wed?Feb?28?10:48:46?2018?-?[info]?Slaves?settings?check?done.
Wed?Feb?28?10:48:46?2018?-?[info]?
192.168.2.211(192.168.2.211:3206)?(current?master)
?+--192.168.2.212(192.168.2.212:3206)
?+--192.168.2.213(192.168.2.213:3206)
Wed?Feb?28?10:48:46?2018?-?[info]?Checking?replication?health?on?192.168.2.212..
Wed?Feb?28?10:48:46?2018?-?[info]??ok.
Wed?Feb?28?10:48:46?2018?-?[info]?Checking?replication?health?on?192.168.2.213..
Wed?Feb?28?10:48:46?2018?-?[info]??ok.
Wed?Feb?28?10:48:46?2018?-?[warning]?master_ip_failover_script?is?not?defined.
Wed?Feb?28?10:48:46?2018?-?[warning]?shutdown_script?is?not?defined.
Wed?Feb?28?10:48:46?2018?-?[info]?Got?exit?code?0?(Not?master?dead).
MySQL?Replication?Health?is?OK.

至此問題解決。