这期内容当中小编将会给大家带来有关keepalived启动报错该如何解决,文章内容丰富且以专业的角度为大家分析和叙述,阅读完这篇文章希望大家可以有所收获。
启动keepalived报错,Keepalived_vrrp: ip address associated with VRID not present in received packet
/var/log/messages里的报错信息如下:
Mar 14 01:29:21 test Keepalived_vrrp[819]: VRRP_Instance(mysql-ha) ignoring received advertisment…
Mar 14 01:29:22 test Keepalived_vrrp[819]: ip 活动:慈云数据爆款香港服务器,CTG+CN2高速带宽、快速稳定、平均延迟10+ms 速度快,免备案,每月仅需19元!! 点击查看address associated with VRID not present in received packet : 192.168.32.53
Mar 14 01:29:22 test Keepalived_vrrp[819]: one or more VIP associated with VRID mismatch actual MASTER advert
Mar 14 01:29:22 test Keepalived_vrrp[819]: bogus VRRP packet received on bond0 !!!
Mar 14 01:29:22 test Keepalived_vrrp[819]: VRRP_Instance(mysql-ha) ignoring received advertisment…
Mar 14 01:29:23 test Keepalived_vrrp[819]: ip addres开发云主机域名s associated with VRID not present in received packet : 192.168.32开发云主机域名.53
Mar 14 01:29:23 test Keepalived_vrrp[819]: one or more VIP associated with VRID mismatch actual MASTER advert
Mar 14 01:29:23 test Keepalived_vrrp[819]: bogus VRRP packet received on bond0 !!!
配置文件内容:
# cat /etc/keepalived/keepalived.conf
vrrp_instance mysql-ha {
state BACKUP
interface eth0
virtual_router_id 53
priority 100
advert_int 1
authentication 开发云主机域名{
auth_type PASS
auth_pass 1111
}
virtual_ipaddress {
192.168.0.1
}
}
解决方法:
修改virtual_router_id的值,从53改为88,因为之前在同一网段还有别的机器安装过keepalived,并设置了virtual_router_id=53,改成不同的值后重启keepalived后问题得到解决.
结论:
在同一网段内非同一套keepalive集群中的virtual_router_id 值不能相同。
上述就是小编为大家分享的keepalived启动报错该如何解决了,如果刚好有类似的疑惑,不妨参照上述分析进行理解。如果想知道更多相关知识,欢迎关注开发云行业资讯频道。
本文从转载,原作者保留一切权利,若侵权请联系删除。
《keepalived启动报错该如何解决》来自互联网同行内容,若有侵权,请联系我们删除!
还没有评论,来说两句吧...