MySQL MHA 报错处理

最新推荐文章于 2024-06-06 14:07:38 发布
最新推荐文章于 2024-06-06 14:07:38 发布
阅读量1.3k 收藏 6
点赞数 2
文章标签： mysql 数据库 服务器
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。
本文链接：https://blog.csdn.net/jnrjian/article/details/128284211
版权

1、找不到mysql 命令

Sat Mar 23 07:17:50 2019 - [info] Connecting to root@192.168.32.181(server2:22)..
Checking slave recovery environment settings..
Opening /data/mysql/relay-log.info ... ok.
Relay log found at /data/mysql, up to server2-relay-bin.000005
Temporary relay log file is /data/mysql/server2-relay-bin.000005
Testing mysql connection and privileges..sh: mysql: command not found
mysql command failed with rc 127:0!

解决办法：找到MySQL 的安装目录，创建适当的软链接

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

2、脚本文件没有执行权限

Sat Mar 23 07:25:46 2019 - [error][/usr/share/perl5/vendor_perl/MHA/MasterMonitor.pm, ln424] Error happened on checking configurations. Can't exec "/usr/local/bin/master_ip_failover": Permission denied at /usr/share/perl5/vendor_perl/MHA/ManagerUtil.pm line 68.
Sat Mar 23 07:25:46 2019 - [error][/usr/share/perl5/vendor_perl/MHA/MasterMonitor.pm, ln523] Error happened on monitoring servers.
Sat Mar 23 07:25:46 2019 - [info] Got exit code 1 (Not master dead).

MySQL Replication Health is NOT OK!

解决办法：赋权

chmod +x /usr/local/bin/master_ip_failover

3、master_ip_failover脚本错误

Sat Mar 23 07:27:44 2019 - [info] Checking master_ip_failover_script status:
Sat Mar 23 07:27:44 2019 - [info] /usr/local/bin/master_ip_failover --command=status --ssh_user=root --orig_master_host=server1 --orig_master_ip=192.168.32.180 --orig_master_port=3306
/usr/local/bin/master_ip_failover: line 4: use: command not found
/usr/local/bin/master_ip_failover: line 6: use: command not found
/usr/local/bin/master_ip_failover: line 10: use: command not found
/usr/local/bin/master_ip_failover: line 14: syntax error near unexpected token `newline'
/usr/local/bin/master_ip_failover: line 14: `my ( '
Sat Mar 23 07:27:44 2019 - [error][/usr/share/perl5/vendor_perl/MHA/MasterMonitor.pm, ln226] Failed to get master_ip_failover_script status with return code 2:0.
Sat Mar 23 07:27:44 2019 - [error][/usr/share/perl5/vendor_perl/MHA/MasterMonitor.pm, ln424] Error happened on checking configurations. at /usr/bin/masterha_check_repl line 48
Sat Mar 23 07:27:44 2019 - [error][/usr/share/perl5/vendor_perl/MHA/MasterMonitor.pm, ln523] Error happened on monitoring servers.
Sat Mar 23 07:27:44 2019 - [info] Got exit code 1 (Not master dead).

解决办法：#!/usr/bin/env perl要最顶行

4、不能切换，出现 No route to host

[root@server3 ~]# masterha_manager --conf=/etc/masterha/app1.cnf
Sun Mar 24 01:49:48 2019 - [warning] Global configuration file /etc/masterha_default.cnf not found. Skipping.
Sun Mar 24 01:49:48 2019 - [info] Reading application default configuration from /etc/masterha/app1.cnf..
Sun Mar 24 01:49:48 2019 - [info] Reading server configuration from /etc/masterha/app1.cnf..
ssh: connect to host 192.168.32.180 port 22: No route to host
ssh: connect to host 192.168.32.180 port 22: No route to host
ssh: connect to host 192.168.32.180 port 22: No route to host
ssh: connect to host 192.168.32.180 port 22: No route to host
ssh: connect to host 192.168.32.180 port 22: No route to host
ssh: connect to host 192.168.32.180 port 22: No route to host

解决办法：

找到MHA的log文件，查看原因：

Sun Mar 24 01:51:43 2019 - [info] Executing secondary network check script: /usr/local/bin/masterha_secondary_check -s 192.168.32.181 -s 192.168.32.182 --user=root --master_host=server1 --master_ip=192.168.32.180 --master_port=3306 --user=root --master_host=server1 --master_ip=192.168.32.180 --master_port=3306 --master_user=monitor --master_password=mysql --ping_type=SELECT
sh: /usr/local/bin/masterha_secondary_check: No such file or directory
Sun Mar 24 01:51:43 2019 - [error][/usr/share/perl5/vendor_perl/MHA/HealthCheck.pm, ln412] Got unknown error from /usr/local/bin/masterha_secondary_check -s 192.168.32.181 -s 192.168.32.182 --user=root --master_host=server1 --master_ip=192.168.32.180 --master_port=3306 --user=root --master_host=server1 --master_ip=192.168.32.180 --master_port=3306 --master_user=monitor --master_password=mysql --ping_type=SELECT. exit.

发现是找不到文件路径，经查文件在

/usr/bin/masterha_secondary_check

修改参数文件/etc/mastermha/app.cof 的配置项secondary_check_script= /usr/bin/masterha_secondary_check -s 192.168.32.181 -s 192.168.32.182 --user=root --master_host=server1 --master_ip=192.168.32.180 --master_port=3306   

5、Failed to deactivate master IP with return code 1:0

Sun Mar 24 03:55:29 2019 - [info] ** Phase 1: Configuration Check Phase completed.
Sun Mar 24 03:55:29 2019 - [info]
Sun Mar 24 03:55:29 2019 - [info] * Phase 2: Dead Master Shutdown Phase..
Sun Mar 24 03:55:29 2019 - [info]
Sun Mar 24 03:55:29 2019 - [info] Forcing shutdown so that applications never connect to the current master..
Sun Mar 24 03:55:29 2019 - [info] Executing master IP deactivation script:
Sun Mar 24 03:55:29 2019 - [info] /etc/masterha/master_ip_failover --orig_master_host=server1 --orig_master_ip=192.168.32.180 --orig_master_port=3306 --command=stop
Got Error: Use of uninitialized value $ssh_user in concatenation (.) or string at /etc/masterha/master_ip_failover line 79.

IN SCRIPT TEST====/sbin/ifconfig eth0:1 down==/sbin/ifconfig eth0:1 192.168.32.183===

Disabling the VIP on old master: server1
Sun Mar 24 03:55:29 2019 - [error][/usr/share/perl5/vendor_perl/MHA/MasterFailover.pm, ln352] Failed to deactivate master IP with return code 1:0
Sun Mar 24 03:55:29 2019 - [error][/usr/share/perl5/vendor_perl/MHA/ManagerUtil.pm, ln177] Got ERROR: at /usr/bin/masterha_manager line 65
Sun Mar 24 03:55:29 2019 - [info]

----- Failover Report -----

app1: MySQL Master failover server1(192.168.32.180:3306)

Master server1(192.168.32.180:3306) is down!

Check MHA Manager logs at server3:/var/log/masterha/app1-manager.log for details.

Started automated(non-interactive) failover.
Failed to deactivate master IP with return code 1:0
Got Error so couldn't continue failover from here.
Sun Mar 24 03:55:29 2019 - [info] Sending mail..
Unknown option: conf

 解决办法：

这个一直说/etc/masterha/master_ip_failover line 79行错误

ssh_user没有初始化

--------------------------------

一 、MHA搭建过程中问题集合
问题一：
Fri Apr 23 11:48:54 2021 - [warning]  log-bin is not set on slave 192.168.0.189(192.168.0.189:3306). This host cannot be a master.

Fri Apr 23 11:48:54 2021 - [warning]  log-bin is not set on slave 192.168.0.190(192.168.0.190:3306). This host cannot be a master.


解决办法：

从库的各客户端应开启binlog，即log_bin=on，两个从上都开启

[root@centos7-02 ~]# vi /etc/my.cnf

 basedir = /usr/local/mysql

 datadir = /data/mysql

 socket = /tmp/mysql.sock

 server-id=189

 log_bin=on


问题二：
Can't exec "mysqlbinlog": 没有那个文件或目录 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.

解决办法：

在所有节点上执行如下命令

[root@centos7-01 ~]# ln -s /usr/local/mysql/bin/mysqlbinlog /usr/local/bin/mysqlbinlog

[root@centos7-01 ~]# ln -s /usr/local/mysql/bin/mysql /usr/local/bin/mysql

[root@centos7-02 ~]# ln -s /usr/local/mysql/bin/mysqlbinlog /usr/local/bin/mysqlbinlog

[root@centos7-02 ~]# ln -s /usr/local/mysql/bin/mysql /usr/local/bin/mysql

[root@centos7-03 ~]# ln -s /usr/local/mysql/bin/mysqlbinlog /usr/local/bin/mysqlbinlog

[root@centos7-03 ~]# ln -s /usr/local/mysql/bin/mysql /usr/local/bin/mysql



问题三：
Fri Apr 23 11:48:54 2021 - [error][/usr/local/share/perl5/MHA/MasterMonitor.pm, ln226]  Failed to get master_ip_failover_script status with return code 1:0.

Fri Apr 23 11:48:54 2021 - [error][/usr/local/share/perl5/MHA/MasterMonitor.pm, ln424] Error happened on checking configurations.  at /usr/local/bin/masterha_check_repl line 48

Thu Aug 23 05:41:59 2018 - [error][/usr/local/share/perl5/MHA/MasterMonitor.pm, ln523] Error happened on monitoring servers.

解决办法：

[root@centos7-04 ~]# vi /etc/masterha/app1.cnf

#master_ip_failover_script= /usr/local/bin/master_ip_failover            //先暂时注释这条选项，后面引入keepalived后和修改该脚本以后再开启该选项

注释：Failover有两种方式：一种是虚拟IP地址，一种是全局配置文件。MHA并没有限定使用哪一种方式，而是让用户自己选择，虚拟IP地址的方式会牵扯到其它的软件,比如keepalive软件，而且还要修改脚本master_ip_failover。
1


问题四：
Fri Apr 23 11:48:54 2021 - [error][/usr/local/share/perl5/MHA/MasterMonitor.pm, ln424] Error happened on checking configurations. Can't exec "/usr/local/bin/master_ip_failover": 权限不够 at /usr/local/share/perl5/MHA/ManagerUtil.pm line 68.

Fri Apr 23 11:48:54 2021 - [error][/usr/local/share/perl5/MHA/MasterMonitor.pm, ln523] Error happened on monitoring servers.

解决办法:

chmod +x /usr/local/bin/master_ip_failover


7
问题五：
[error][/usr/local/share/perl5/MHA/ServerManager.pm, ln492]  Server 192.168.0.190(192.168.0.190:3306) is dead, but must be alive! Check server settings.

解决办法：

[root@centos7-04 ~]# rm -rf /var/log/masterha/app1.log/app1.failover.complete        #删除MHA管理机上的这个文件 --------------切了就不会再切
 

问题六：
[error][/usr/local/share/perl5/MHA/ServerManager.pm, ln492]  Server 192.168.0.190(192.168.0.190:3306) is dead, but must be alive! Check server settings.

解决办法：

清除防火墙规则
 


问题七：
[error][/usr/local/share/perl5/MHA/ServerManager.pm, ln492]  Server 192.168.0.188(192.168.0.188:3306) is dead, but must be alive! Check server settings.

Fri Apr 23 11:48:54 2021 - [error][/usr/local/share/perl5/MHA/MasterMonitor.pm, ln424] Error happened on checking configurations.  at /usr/local/share/perl5/MHA/MasterMonitor.pm line 399

解决办法：

重启主库的mysql服务
1
 
问题八：
[error][/usr/local/share/perl5/MHA/MasterMonitor.pm, ln205] Slaves settings check failed!

解决办法：

登陆从数据库，查看主数据库是不是自己设定的

mysql> show slave status\G

Master_Server_Id: 189
1

问题九：
[error][/usr/local/share/perl5/MHA/ServerManager.pm, ln781] Multi-master configuration is detected, but two or more masters are either writable (read-only is not set) or dead! Check configurations for details. Master configurations are as below: 

Master 192.168.0.189(192.168.0.189:3306), dead

Master 192.168.0.188(192.168.0.188:3306), replicating from 192.168.0.189(192.168.0.189:3306)

解决办法：

所有从上执行

mysql -uroot -p -e "set global read_only=1"


问题十：
mysqlbinlog: unknown variable 'default-character-set=utf8'

mysqlbinlog version command failed with rc 7:0, please verify PATH, LD_LIBRARY_PATH, and client options

解决办法：

在所有从服务器上注释掉clinet段default-character-set=utf8

更改默认字符集UTF8到utf8

[client]

#default-character-set = utf8

[mysql]

default-character-set = utf8

[mysqld]

character-set-client-handshake = FALSE

character-set-server = utf8

collation-server = utf8mb4_unicode_ci

init_connect='SET NAMES utf8'

1
2
3


问题十一：
root@ubuntu:~# su - mysql -c "/usr/local/bin/masterha_check_repl --conf=/etc/mha/mysql/app.cnf"
Fri Apr 23 11:48:54 2021 - [warning] Global configuration file /etc/masterha_default.cnf not found. Skipping.
Fri Apr 23 11:48:54 2021 - [info] Reading application default configuration from /etc/mha/mysql/app.cnf..
Fri Apr 23 11:48:54 2021 - [info] Reading server configuration from /etc/mha/mysql/app.cnf..
Fri Apr 23 11:48:54 2021 - [info] MHA::MasterMonitor version 0.58.
Fri Apr 23 11:48:54 2021 - [error][/usr/local/share/perl/5.22.1/MHA/Server.pm, ln180] Got MySQL error when connecting 192.168.1.2(192.168.1.2:3306) :1045:Access denied for user 'mha'@'192.168.1.3' (using password: YES), but this is not a MySQL crash. Check MySQL server settings.
Fri Apr 23 11:48:54 2021 - [error][/usr/local/share/perl/5.22.1/MHA/Server.pm, ln180] Got MySQL error when connecting 192.168.1.1(192.168.1.1:3306) :1045:Access denied for user 'mha'@'192.168.1.3' (using password: YES), but this is not a MySQL crash. Check MySQL server settings.
Fri Apr 23 11:48:54 2021 - [error][/usr/local/share/perl/5.22.1/MHA/ServerManager.pm, ln301]  at /usr/local/share/perl/5.22.1/MHA/ServerManager.pm line 297.
Fri Apr 23 11:48:54 2021 - [error][/usr/local/share/perl/5.22.1/MHA/ServerManager.pm, ln301]  at /usr/local/share/perl/5.22.1/MHA/ServerManager.pm line 297.
Fri Apr 23 11:48:54 2021 - [error][/usr/local/share/perl/5.22.1/MHA/ServerManager.pm, ln309] Got fatal error, stopping operations
Fri Apr 23 11:48:54 2021 - [error][/usr/local/share/perl/5.22.1/MHA/MasterMonitor.pm, ln427] Error happened on checking configurations.  at /usr/local/share/perl/5.22.1/MHA/MasterMonitor.pm line 329.
Fri Apr 23 11:48:54 2021 - [error][/usr/local/share/perl/5.22.1/MHA/MasterMonitor.pm, ln525] Error happened on monitoring servers.
Fri Apr 23 11:48:54 2021 - [info] Got exit code 1 (Not master dead).

MySQL Replication Health is NOT OK!


解决办法：
mysql> grant all privileges on *.* to 'mha'@'Mysql1' identified by 'manager';
mysql> grant all privileges on *.* to 'mha'@'Mysql2' identified by 'manager';
mysql> grant all privileges on *.* to 'mha'@'Mysql3' identified by 'manager';
mysql> flush privileges;

1
2
3
4

问题十二：
[root@mysql3 ~]# /usr/local/mysql/scripts/mysql_install_db \
> --basedir=/usr/local/mysql \
> --datadir=/usr/local/mysql/data \
> --user=mysql
bash: /usr/local/mysql/scripts/mysql_install_db: /usr/bin/perl: bad interpreter: No such file or directory


解决办法：
yum -y install autoconf


问题十三：
Fri Apr 23 11:48:54 2021 - [error][/usr/local/share/perl5/MHA/ServerManager.pm, ln671] Master 192.168.221.20:3306 from which slave 192.168.221.110(192.168.221.110:3306) replicates is not defined in the configuration file!
Fri Apr 23 11:48:54 2021 - [error][/usr/local/share/perl5/MHA/MasterMonitor.pm, ln427] Error happened on checking configurations.  at /usr/local/share/perl5/MHA/MasterMonitor.pm line 329.
Fri Apr 23 11:48:54 2021 - [error][/usr/local/share/perl5/MHA/MasterMonitor.pm, ln525] Error happened on monitoring servers.
Fri Apr 23 11:48:54 2021 - [info] Got exit code 1 (Not master dead).

MySQL Replication Health is NOT OK!

是因为MHA配置文件里面缺少了主库的配置
加入
[server1]
hostname=192.168.142.11
port=3306
1 

jnrjian
关注
MySQL 主从脑裂_完美起航-数据库之MHA高可用集群部署及故障切换
weixin_35738619的博客
02-27 1091
一、MHA概念MHA(MasterHigh Availability)是一套优秀的MySQL高可用环境下故障切换和主从复制的软件。MHA 的出现就是解决MySQL 单点的问题。MySQL故障切换过程中，MHA能做到0-30秒内自动完成故障切换操作。MHA能在故障切换的过程中最大程度上保证数据的一致性，以达到真正意义上的高可用。1、MHA 的组成MHA Node(数据节点)MHA Node 运行在每...
心态炸裂，搭建mha时，在测试主从复制时候报错MySQL Replication Health is NOT OK！！！有点慌！慢慢盘吧！
guguai7的博客
07-31 1662
MHA时测试主从复制报错MySQL Replication Health is NOT OK! 具体报错信息 [root@manager bin]# masterha_check_repl -conf=/etc/masterha/app1.cnf Sat Jul 31 05:23:03 2021 - [warning] Global configuration file /etc/masterha_default.cnf not found. Skipping. Sat Jul 31 05:23:03 20
mysql replication health is not ok_mha0.56版本安装使用排错
weixin_35798040的博客
02-07 903
1.master_check_ssh --conf=/etc/app1.conf这个检查就报错的我觉得百分之九十都是ssh之间连接问题。务必要保证各节点之间都可以免秘钥访问！2.master_check_repl --conf=/etc/app1.conf(1)报错代码：类似就是说什么copyuser复制用户在节点没有权限的代码，解决方法是每个节点创建这个用户即可。要是主从复制已经开启，记得节点先...
mha检测mysql状况方式_【MySQL】MHA源代码之监控检查(一)
weixin_35411438的博客
01-28 739
一、前言弄完了MHA+Consul架构(包括程序要写的示例代码)，在研究的同时，把MHA的源代码也翻阅了一遍，现在准备把MHA一些重要内容梳理一下，既然是高可用工具，那么健康检测是一个基础工作，只有正确检测了数据库的故障，才能进行数据库的切换;而MHA的布局亦如此：二、MHA健康检查核心调用函数链注意我这里的函数调用链的规则是文件名|方法名，方法名中的或者表示的是，通过读取配置文件，执行其中的一个...
mha检测mysql报错_MySQL MHA 报错处理
weixin_39844549的博客
01-27 374
安装环境：CentOS 6.5 MySQL 5.7.22 MHA 0.561、找不到mysql 命令Sat Mar 23 07:17:50 2019 - [info] Connecting to root@192.168.32.181(server2:22)..Checking slave recovery environment settings..Opening /data/mysql/rel...
mysql replication health is not ok_mysql配置mha高可用防火墙未关闭报错
weixin_39765697的博客
01-20 313
##########################################################################l 问题背景：检查主从复制之后做高可用报错[root@db03 oldboy]# masterha_check_repl --conf=/etc/mha/app1.cnfThu May 4 21:52:24 2017 - [info] GTID (...
MHA常见报错（FQA）
wuds_158的博客
06-10 682
Thu Aug 23 18:17:14 2018 - [error][/usr/local/share/perl5/MHA/MasterMonitor.pm, ln424] Error happened on checking configurations. Can't exec "/usr/local/bin/master_ip_failover": 权限不够 at /usr/local/share/perl5/MHA/ManagerUtil.pm line 68.在所有节点上执行如下命令。
MySQL 8.0 部署MHA报错：There is no alive server. We can't do failover
wangbin9536的博客
02-05 2240
环境：基于MySQL 8.0安装部署MHA集群 在检查主从时报错： [root@mysql-105 mha]# masterha_check_repl --conf=/etc/mha/mysql-mha.conf Tue Feb 4 22:14:13 2020 - [warning] Global configuration file /etc/masterha_default.cnf not ...
mha检测mysql报错_mysql 高可用架构 mha 之七 masterha_check_repl 报错
weixin_29369347的博客
02-07 491
os: ubuntu 16.04db: mysql 5.7.25mha: 0.58mysql master 关闭后，发生 failover 到另外一台机器上，这时再启动 mysql 后，执行 masterha_check_repl 报错如下$ masterha_check_repl --conf=/etc/mha/mysql/app.cnfWed Jul 15 14:43:43 2020 - [w...
MySQL MHA 部署
m0_59430185的博客
11-03 498
文章目录引言一、什么是 MHA二、MHA 的组成三、MHA 的特点 引言 一、什么是 MHA MHA（MasterHigh Availability）是一套优秀的MySQL高可用环境下故障切换和主从复制的软件。 MHA 的出现就是解决MySQL 单点故障的问题。 MySQL故障切换过程中，MHA能做到0-30秒内自动完成故障切换操作。 MHA能在故障切换的过程中最大程度上保证数据的一致性，以达到真正意义上的高可用。 二、MHA 的组成 MHA Node（数据节点） MHA Node 运行在每台 MyS
【ubuntu22.04~mysql-MHA-mycat】
qq_44637753的博客
06-06 873
#三台服务器之间相互免密。
Mysql MHA搭建
u010648194的博客
04-06 2679
MHA是一种方便简单可靠的MySQL高可用架构 该软件由两部分组成：MHA Manager（管理节点）和MHA Node（数据节点） MHA Manager可以单独部署在一台独立的机器上管理多个master-slave集群，也可以部署在一台slave节点上。MHA Node运行在每台MySQL服务器上，MHA Manager会定时探测集群中的master节点，当master出现故障时，它可以自动将最新数据的slave提升为新的master，然后将所有其他的slave重新指向新的master。整个故障转移
我配置的Mha检查时出现的情况分析及解决如下
火麒马
06-13 5281
​
无法启用mha
oldbob2020的博客
07-10 240
Fri Jul 9 05:33:44 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 ver...
mha搭建问题解决一览，你犯过的错误我全都有
weixin_45829963的博客
09-06 995
业务需要部署一套mha高可用架构，这里记录下搭建过程中遇到的坑。 本文主要记录安装过程中的问题，对于前期环境准备问题略过。 首先要在集群的机器上 部署ssh互信， 过程略 配置一主俩从 过程略 安装依赖 yum install perl-DBD-MySQL \ perl-Config-Tiny \ perl-Time-HiRes \ perl-Mail-Sender \ perl-Mail-Sendmail \ perl-MIME-Base32 \ perl-MIME-Charset \ perl-MI
MySQL MHA部署实战
NNNathan的博客
10-09 1637
MySQL MHA部署 环境：CentOS7 master 192.168.1.4 slave1 192.168.1.5 slave2 192.168.1.2 mha 192.168.1.7 安装依赖 yum install perl-DBD-MySQL perl-Config-Tiny perl-Log-Dispatch perl-Parallel-ForkManager perl-ExtUtils-CBuilder perl-ExtUtils-MakeMaker perl-CPA
MHA排障报错——[error][/usr/local/share/perl5/……at /usr/local/bin/masterha_check_repl line 48.
CN_LiTianpeng的博客
09-19 1441
报错原因 在master_ip_failover脚本文件中有一些内容是我们不需要的，因此需要注释掉 [root@localhost ~]# masterha_check_repl -conf=/etc/masterha/app1.cnf //检查MHA状况 …… Sun Sep 20 01:05:06 2020 - [error][/usr/local/share/perl5/MHA/MasterMonitor.pm, ln229] Failed to get master_ip_failover_s
报错解决方案Use of uninitialized value $dir in concatenation (.) or string
Larry Chow
05-29 3500
报错信息：Use of uninitialized value $dir in concatenation (.) or string at
mysql mha keepalived_MHA+keepalived 高可用MYSQL集群(续)
weixin_31458459的博客
01-19 764
一、恢复背景二、修复故障节点及MHA集群三、提升已修复的节点为master四、注意事项一、恢复背景1、设备清单2、：percona-xtrabackup-2.3.2(注：生产环境应定时备份；不应等到数据库DOWN后才备份，以免加剧集群的压力)备份数据库操作：[root@jev72 ~]#innobackupex --user=root --password=centos /data/。 。 。xt...
mha 报错Access denied for user 'mha'@'mgt' (using password: YES)
最新发布
07-02
这个报错信息是MySQL服务器返回的，意思是用户'mha'尝试从主机'mgt'连接到数据库，但是连接被拒绝，因为用户没有权限或者提供的密码不正确。具体分析如下： 1. **权限不足**：用户'mha'可能没有在'mgt'这个数据库或相应的数据库表中设置足够的访问权限。 2. **密码错误**：用户在尝试登录时输入的密码与实际保存的密码不符。 3. **远程访问限制**：数据库服务器可能配置为只允许本地连接，不允许从外部IP地址（如'mgt'）登录。 为了解决这个问题，你可以执行以下步骤： - **检查用户名和密码**：确认你输入的用户名和密码是否正确。 - **检查数据库权限**：确保用户'mha'在'mgt'数据库上有正确的读写权限。 - **修改服务器配置**：如果允许远程连接，需要在MySQL的my.cnf文件或者运行时设置中开启remote_login_password_file参数。 - **使用SSL/TLS**：如果数据库有启用SSL/TLS，可能需要提供正确的证书来完成身份验证。 如果你是系统管理员，还需要考虑安全因素，谨慎授权，避免账户滥用。
评论
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付：10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明：

1.余额是钱包充值的虚拟货币，按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载，可以购买VIP、付费专栏及课程。

余额充值