1：masterha_check_repl 副本集方面報(bào)錯(cuò) replicates is not defined in the configuration file!

具體信息如下：

# /usr/local/bin/masterha_check_repl --conf=/etc/mha/app1.cnfThu Nov 21 15:33:15 2018 - [warning] Global configuration file /etc/masterha_default.cnf not found. Skipping.Thu Nov 21 15:33:15 2018 - [info] Reading application default configuration from /etc/mha/app1.cnf..Thu Nov 21 15:33:15 2018 - [info] Reading server configuration from /etc/mha/app1.cnf..Thu Nov 21 15:33:15 2018 - [info] MHA::MasterMonitor version 0.56.Thu Nov 21 15:33:16 2018- [error][/usr/local/share/perl5/MHA/ServerManager.pm, ln671] Master 179.179.19.179:3306 from which slave 179.179.19.180(179.179.19.180:3306) replicates is not defined in the configuration file!Thu Nov 21 15:33:16 2018 - [error][/usr/local/share/perl5/MHA/MasterMonitor.pm, ln424] Error happened on checking configurations. at /usr/local/share/perl5/MHA/MasterMonitor.pm line 326.Thu Nov 21 15:33:16 2018 - [error][/usr/local/share/perl5/MHA/MasterMonitor.pm, ln523] Error happened on monitoring servers.Thu Nov 21 15:33:16 2018 - [info] Got exit code 1 (Not master dead).MySQL Replication Health is NOT OK!

分析：MHA 漂移過(guò)后，我們知道配置信息中 主節(jié)點(diǎn)的信息就不在了，我們需要及時(shí)維護(hù)，否則/usr/local/bin/masterha_check_repl --conf=/etc/mha/XXX.cnf 檢查副本集狀態(tài)報(bào)錯(cuò)。

2. masterha_master_switch 在線切換方面 報(bào)錯(cuò) We should not start online master switch when one of connections are running long updates on the current master

具體信息如下：

# /usr/local/bin/masterha_master_switch --master_state=alive --conf=/etc/mha/app1.cnfIt is better to execute FLUSH NO_WRITE_TO_BINLOG TABLES on the master before switching. Is it ok to execute on 179.179.19.184(179.179.19.184:3306)? (YES/no): yTue Nov 19 17:19:09 2018 - [info] Executing FLUSH NO_WRITE_TO_BINLOG TABLES. This may take long time..Tue Nov 19 17:19:09 2018 - [info] ok.Tue Nov 19 17:19:09 2018 - [info] Checking MHA is not monitoring or doing failover..Tue Nov 19 17:19:09 2018 - [info] Checking replication health on 179.179.19.185..Tue Nov 19 17:19:09 2018 - [info] ok.Tue Nov 19 17:19:09 2018 - [error][/usr/local/share/perl5/MHA/MasterRotate.pm, ln161] We should not start online master switch when one of connections are running long updates on the current master(179.179.19.184(179.179.19.184:3306)). Currently 1 update thread(s) are running.Details:{’Time’ => ’12815’,’db’ => undef,’Id’ => ’1’,’User’ => ’event_scheduler’,’State’ => ’Waiting on empty queue’,’Command’ => ’Daemon’,’Info’ => undef,’Host’ => ’localhost’}Tue Nov 19 17:19:09 2018 - [error][/usr/local/share/perl5/MHA/ManagerUtil.pm, ln177] Got ERROR: at /usr/local/bin/masterha_master_switch line 53.

分析：set global event_scheduler=off; 主從都要關(guān)閉

3. masterha_master_switch 在線切換方面 報(bào)錯(cuò) Got Error: DBI .....failed: Access denied for user

# /usr/local/bin/masterha_master_switch --master_state=alive --conf=/etc/mha/app1.cnfStarting master switch from 179.179.19.185(179.179.19:3306) to 179.179.19.184(179.179.19.184:3306)? (yes/NO): yesTue Nov 19 18:52:04 2018 - [info] Checking whether 179.179.19.184(179.179.19.184:3306) is ok for the new master..Tue Nov 19 18:52:04 2018 - [info] ok.Tue Nov 19 18:52:04 2018 - [info] ** Phase 1: Configuration Check Phase completed.Tue Nov 19 18:52:04 2018 - [info] Tue Nov 19 18:52:04 2018 - [info] * Phase 2: Rejecting updates Phase..Tue Nov 19 18:52:04 2018 - [info] Tue Nov 19 18:52:04 2018 - [info] Executing master ip online change script to disable write on the current master:Tue Nov 19 18:52:04 2018 - [info] /usr/local/bin/master_ip_online_change_appuanalysis --command=stop --orig_master_host=179.179.19.185 --orig_master_ip=179.179.19.185 --orig_master_port=3306--orig_master_user=’weixinLX391P_xldbmha’ --orig_master_password=’weixinLX391P_xldbmha)qlk’ --new_master_host=179.179.19.184 --new_master_ip=179.179.19.184 --new_master_port=55988 --new_master_user=’us_mha’ --new_master_password=’weixinLX391P_xldbmha)qlk’ --orig_master_ssh_user=root --new_master_ssh_user=root Got Error: DBI connect(’;host=179.179.19.184;port=3306;mysql_connect_timeout=4’,’weixinLX391P_xldbmha’,...) failed: Access denied for user ’weixinLX391P_xldbmha’@’179.179.19.166’ (using password: YES) at /usr/local/share/perl5/MHA/DBHelper.pm line 205. at /usr/local/bin/master_ip_online_change_app1 line 119.Tue Nov 19 18:52:04 2018 - [error][/usr/local/share/perl5/MHA/ManagerUtil.pm, ln177] Got ERROR: at /usr/local/bin/masterha_master_switch line 53.

分析：賬號(hào)密碼有需要轉(zhuǎn)移字符的。app1.cnf 文件中user賬號(hào)相應(yīng)的密碼 password 不能有待轉(zhuǎn)移的字符，例如本例中的’)’，但是 賬號(hào) repl_user 相應(yīng)的密碼repl_password 沒(méi)有此限制。

4.如果使用的是xtrabackup，注意從節(jié)點(diǎn)會(huì)把event還原上去，可能會(huì)造成數(shù)據(jù)不一致，同步失敗的問(wèn)題。

如果主節(jié)點(diǎn)有event，需要手動(dòng)關(guān)閉從節(jié)點(diǎn)的event。例如，主節(jié)點(diǎn)有歸檔刪除數(shù)據(jù)的event，從節(jié)點(diǎn)需要關(guān)閉，否則報(bào)錯(cuò)。類(lèi)似如下錯(cuò)誤：

Could not execute Delete_rows event on table ????DB.*****table; Can’t find record in ’*****’, Error_code: 1032; handler error HA_ERR_KEY_NOT_FOUND; the event’s master log FIRST, end_log_pos XXXXXXX5 .GTID 模式轉(zhuǎn)換為傳統(tǒng)模式后，MHA 機(jī)制下數(shù)據(jù)庫(kù)主從檢查報(bào)錯(cuò)。

檢查的命令：

/usr/local/bin/masterha_check_repl --conf=/etc/mha/qqweixinordb.cnf

主要的報(bào)錯(cuò)信息

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 Aug 28 04:38:22 2019 - [error][/usr/local/share/perl5/MHA/MasterMonitor.pm, ln205] Slaves settings check failed!Fri Aug 28 04:38:22 2019 - [error][/usr/local/share/perl5/MHA/MasterMonitor.pm, ln413] Slave configuration failed.Fri Aug 28 04:38:22 2019 - [error][/usr/local/share/perl5/MHA/MasterMonitor.pm, ln424] Error happened on checking configurations. at /usr/local/bin/masterha_check_repl line 48.Fri Aug 28 04:38:22 2019 - [error][/usr/local/share/perl5/MHA/MasterMonitor.pm, ln523] Error happened on monitoring servers.Fri Aug 28 04:38:22 2019 - [info] Got exit code 1 (Not master dead). MySQL Replication Health is NOT OK!

解決方案--在每個(gè)DB節(jié)點(diǎn)執(zhí)行以下命令

ln -s /usr/local/mysql/bin/mysqlbinlog /usr/local/bin/mysqlbinlog ln -s /usr/local/mysql/bin/mysql /usr/local/bin/mysql

再次檢查，報(bào)錯(cuò)信息消失，OK。

6.root 賬號(hào)密碼過(guò)期

以root賬號(hào)設(shè)置的ssh免密登陸，而ssh有過(guò)期限制，則mha ssh檢查時(shí)報(bào)錯(cuò):

/usr/local/bin/masterha_check_ssh --conf=/etc/mha/qqorder.cnfThu Nov 5 10:09:09 2018 - [warning] Global configuration file /etc/masterha_default.cnf not found. Skipping.Thu Nov 5 10:09:09 2018 - [info] Reading application default configuration from /etc/mha/pms20epime.cnf..Thu Nov 5 10:09:09 2018 - [info] Reading server configuration from /etc/mha/pms20epime.cnf..Thu Nov 5 10:09:09 2018 - [info] Starting SSH connection tests..Thu Nov 5 10:09:09 2018 - [error][/usr/local/share/perl5/MHA/SSHCheck.pm, ln63]Thu Nov 5 10:09:09 2018 - [debug] Connecting via SSH from root@172.181.191.191(172.181.191.191:22) to root@172.181.191.192(172.181.191.192:22)..WARNING: Your password has expired.Password change required but no TTY available.Thu Nov 5 10:09:09 2018 - [error][/usr/local/share/perl5/MHA/SSHCheck.pm, ln111] SSH connection from root@172.181.191.191(172.181.191.191:22) to root@172.181.191.192(172.181.191.192:22) failed!Thu Nov 5 10:09:10 2018 - [error][/usr/local/share/perl5/MHA/SSHCheck.pm, ln63]Thu Nov 5 10:09:09 2018 - [debug] Connecting via SSH from root@172.181.191.192(172.181.191.192:22) to root@172.181.191.191(172.181.191.191:22)..WARNING: Your password has expired.Password change required but no TTY available.Thu Nov 5 10:09:10 2018 - [error][/usr/local/share/perl5/MHA/SSHCheck.pm, ln111] SSH connection from root@172.181.191.192(172.181.191.192:22) to root@172.181.191.191(172.181.191.191:22) failed!SSH Configuration Check Failed! at /usr/local/bin/masterha_check_ssh line 44.

另外一種表現(xiàn)，就是第二次執(zhí)行賬號(hào)切換時(shí)報(bào)錯(cuò) sudo su -

解決方案在root賬號(hào)下，執(zhí)行以下命令:

chage -M 99999 root

以上就是MySQL 有關(guān)MHA搭建與切換的幾個(gè)錯(cuò)誤log匯總的詳細(xì)內(nèi)容，更多關(guān)于MySQL MHA搭建與切換的資料請(qǐng)關(guān)注好吧啦網(wǎng)其它相關(guān)文章！