精华总结：MHA构建中的各种报错与解决

最新推荐文章于 2023-06-10 01:02:50 发布

原创

最新推荐文章于 2023-06-10 01:02:50 发布 · 4k 阅读

4 ·

CC 4.0 BY-SA版权

文章标签：

#数据库 #mysql #mha #mha构建报错 #mha报错解决

本文详述了在MHA构建过程中遇到的各种错误，包括奴隶节点无主配置、用户权限不足、mysqlbinlog执行失败等问题，并提供了详细的解决步骤，如配置二进制日志、添加用户权限、修正mysqlbinlog变量和修复脚本语法错误。

摘要生成于 C知道，由 DeepSeek-R1 满血版支持，前往体验 >

文章目录

前言
一：报错与解决

前言

一：报错与解决

1.1：报错： [error][/usr/local/share/perl5/MHA/MasterMonitor.pm, ln364] None of slaves can be master. Check failover configuration file or log-bin settings in my.cnf

报错描述

[root@mha_manager ~]# masterha_check_repl -conf=/etc/masterha/app1.cnf
...省略内容
Fri Jan 10 08:42:12 2020 - [error][/usr/local/share/perl5/MHA/MasterMonitor.pm, ln364] None of slaves can be master. Check failover configuration file or log-bin settings in my.cnf
Fri Jan 10 08:42:12 2020 - [error][/usr/local/share/perl5/MHA/MasterMonitor.pm, ln427] Error happened on checking configurations.  at /usr/local/bin/masterha_check_repl line 48.
Fri Jan 10 08:42:12 2020 - [error][/usr/local/share/perl5/MHA/MasterMonitor.pm, ln525] Error happened on monitoring servers.
Fri Jan 10 08:42:12 2020 - [info] Got exit code 1 (Not master dead).

MySQL Replication Health is NOT OK!

原因：

mysql集群中的slave节点中数据库配置文件/etc/my.cnf中没有配置二进制日志，只需要在所有slave节点配置二进制日志即可
```
二进制日志格式
log-bin=xxx（名称自定义）
```

解决：在所有slave节点配置二进制日志

[root@slave1 ~]# vim /etc/my.cnf
    [mysqld]段落添加
log-bin=slave1-bin	'//添加二进制日志'
所以slave节点都要配置，我就不一一展示了

1.2：报错： User myslave does not exist or does not have REPLICATION SLAVE privilege! Other slaves can not start replication from this host.

报错描述

[root@mha_manager ~]# masterha_check_repl -conf=/etc/masterha/app1.cnf
...省略内容
Fri Jan 10 09:04:53 2020 - [error][/usr/local/share/perl5/MHA/Server.pm, ln398] 192.168.79.135(192.168.79.135:3306): User myslave does not exist or does not have REPLICATION SLAVE privilege! Other slaves can not start replication from this host.
Fri Jan 10 09:04:53 2020 - [error][/usr/local/share/perl5/MHA/MasterMonitor.pm, ln427] Error happened on checking configurations.  at /usr/local/share/perl5/MHA/ServerManager.pm line 1403.
Fri Jan 10 09: