CRITICAL: VIP 192.168.1.100 not found on Master!

1、环境描述
MHA
MariaDB 10.1

2、报错信息
MHA管理报错信息如下:
tail -f /var/log/masterha/manager.log
CRITICAL: VIP 192.168.1.100 not found on Master!
Mon Sep 10 10:08:01 2018 - [error][/usr/local/share/perl5/MHA/MasterMonitor.pm, ln226] Failed to get master_ip_failover_script status with return code 1:0.
Mon Sep 10 10:08:01 2018 - [error][/usr/local/share/perl5/MHA/MasterMonitor.pm, ln424] Error happened on checking configurations. at /usr/local/bin/masterha_manager line 50
Mon Sep 10 10:08:01 2018 - [error][/usr/local/share/perl5/MHA/MasterMonitor.pm, ln523] Error happened on monitoring servers.
Mon Sep 10 10:08:01 2018 - [info] Got exit code 1 (Not master dead).

3、处理方法
查看网卡接口,确认VIP,执行以下命令。
ip addr add 192.168.56.105/32 dev eth1

4、再次查看日志

tail -f /var/log/masterha/manager.log
部分略.................
Mon Sep 10 10:16:05 2018 - [info] Slaves settings check done.
Mon Sep 10 10:16:05 2018 - [info]
master(192.168.56.101:3306) (current master)
+--slave1(192.168.56.102:3306)
+--slave2(192.168.56.103:3306)

Mon Sep 10 10:16:05 2018 - [info] Checking master_ip_failover_script status:
Mon Sep 10 10:16:05 2018 - [info] /usr/local/bin/master_ip_failover --command=status --ssh_user=root --orig_master_host=master --orig_master_ip=192.168.56.101 --orig_master_port=3306
inet 192.168.56.105/32 scope global eth1
INFO: VIP 192.168.1.100 found on Master
Mon Sep 10 10:16:05 2018 - [info] OK.
Mon Sep 10 10:16:05 2018 - [warning] shutdown_script is not defined.
Mon Sep 10 10:16:05 2018 - [info] Set master ping interval 1 seconds.
Mon Sep 10 10:16:05 2018 - [warning] secondary_check_script is not defined. It is highly recommended setting it to check master reachability from two or more routes.
Mon Sep 10 10:16:05 2018 - [info] Starting ping health check on master(192.168.56.101:3306)..
Mon Sep 10 10:16:05 2018 - [info] Ping(CONNECT) succeeded, waiting until MySQL doesn‘t respond..

原文地址:http://blog.51cto.com/roidba/2173114

时间: 2024-10-11 11:38:38

CRITICAL: VIP 192.168.1.100 not found on Master!的相关文章

请问192.168.10.100/25与192.168.10.200/25是否在同一个网域内

鸟哥的一个题 192.168.10.100/25 , ip是class C,Net_ID 占24位,题目要求为25,即Host_ID借1给Net_ID 192      |      168     |     10       |      100 11000000   10100000   00001010  01100100 下面开始计算Network 与boardcast 11000000   10100000   0000101 0|0 | 1100100 --------------

hadoop启动之后出现错误:Retrying connect to server: hadoop/192.168.73.100:9000. Already tried 0 time(s);

INFO ipc.Client: Retrying connect to server: hadoop/192.168.73.100:9000. Already tried 0 time(s); retry policy is RetryUpToMaximumCountWithFixedSleep(maxRetries=10, sleepTime=1 SECONDS) INFO ipc.Client: Retrying connect to server: hadoop/192.168.73.1

解决“出现Unable to retrieve 192.168.0.100/var/www/html/images/install.img错误”

分析:我们必须了解这个错误出现在哪个阶段才能正确找到错误原因,出现这个错误时已经是在开机PXE引导顺利从dhcp server中获得了ip,(或者 光盘引导)均正常,而且正常的读取了ks文件,正确的找到了安装源,否则不会提示无法获取install.img文件.一般无法获取某个文件,不是该文件损坏就是网络不通的问题. 解决办法: 1)我们先证明安装源服务器是正常的,我们用其他机器下载install.img文件,使用下面的命令: wget http://192.168.0.100/var/www/h

docker maven 出错:Failed to execute goal com.spotify:docker-maven-plugin:...: Request error: POST https://192.168.99.100:2376/build?t=

Spring Boot项目构建docker镜像,出错Failed to execute goal com.spotify:docker-maven-plugin:0.4.13:build (default-cli) on project SpringBoot2: Exception caught: Request error: POST https://192.168.99.100:2376/build?t=mytest/SpringBoot2: 500: HTTP 500 Internal S

TQ2440使用NFS挂载时,卡在server 192.168.1.100 not responding,still trying

问题如下: 解决办法:(仅针对TQ2440开发板) 注释掉NFS文件系统下的etc/init.d/rcS中,#net_set &即可.

Call From master/192.168.128.135 to master:8485 failed on connection exception: java.net.ConnectException: Connection refused

hadoop集群搭建了ha,初次启动正常,最近几天启动时偶尔发现,namenode1节点启动后一段时间(大约10几秒-半分钟左右),namenode1上namenode进程停掉,查看日志: 1 2017-08-28 21:54:37,617 INFO org.apache.hadoop.ipc.Client: Retrying connect to server: slave1/192.168.128.136:8485. Already tried 9 time(s); retry policy

Linux中mysql进入命令行报错:MYSQL ERROR 2003 (HY000): Can't connect to MySQL server on '192.168.99.192' (111)

场景:在Linux中安装mysql01和mysql02,通过VIP虚出一个VIP=192.168.99.192,mysql01为主ip为192.168.99.153,mysql02为备机ip为192.168.99.154 此时VIP在mysql01上通过 mysql01上连接VIP :mysql -h 192.168.99.192 -P 3306   结果是可以正常进入mysql命令行: 通过mysql02上远程连接VIP 会在界面上报错:mysql error 2003(HY000):Can'

客户端不能连接MySQL - 2003-Can't connect to MySQL server on '192.168.43.180'(10060 "Unknown error")

客户端不能连接MySQL 场景: 数据库(此处以MySQL为例)安装在虚拟机里面,在宿主机上进行连接数据库的时候始终不能连接,但在虚拟机中使用正常. 针对上面的场景: 1. 在虚拟机里面可以正常使用MySQL 2. 在宿主机上进行连接的时候,始终不能连接 解决方案: 第一步:检查账号是否支持远程链接? 相关操作指令: # mysql -uroot -p  使用root用户链接mysql # show databases             查看已有的数据框(主要是为了找:mysql 这个数据

三种方法告诉你项目超过255个摄像机怎么设置IP?为什么IP地址通常以192.168开头?

我们做弱电的,与ip地址接触最多,无论是弱电的哪方面,都需要跟ip地址打交道,通常我们也会经常听到公网.内网?那什么是公网ip地址呢?什么是私网ip地址呢?为什么我们常见到的ip地址以192.168开头呢? 还有就是一个网段只能容纳254个摄像机,但是我现在项目比较大,都有300多个摄像机了,该咋分配IP地址呢? 我们今天统统来了解一下. 首先关于内.外网的定义:内.外网是相对于防火墙而言的,在防火墙内部叫做内网,反之就是外网.在一定程度上外网等同于公网,内网等同于私网. 一.特殊的IP地址 1