Network Security Internet Technology Development Database Servers Mobile Phone Android Software Apple Software Computer Software News IT Information

In addition to Weibo, there is also WeChat

Please pay attention

WeChat public account

Shulou

How to solve the error report of keepalived startup

2025-04-05 Update From: SLTechnology News&Howtos shulou NAV: SLTechnology News&Howtos > Servers >

Share

Shulou(Shulou.com)06/01 Report--

In this issue, the editor will bring you about how to solve the keepalived startup error report. The article is rich in content and analyzes and narrates it from a professional point of view. I hope you can get something after reading this article.

Start keepalived to report error, Keepalived_vrrp: ip address associated with VRID not present in received packet

The error message in / var/log/messages is as follows:

Mar 14 01:29:21 test Keepalived_vrrp: VRRP_Instance (mysql-ha) ignoring received advertisment...

Mar 14 01:29:22 test Keepalived_vrrp [819]: ip 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: VRRP_Instance (mysql-ha) ignoring received advertisment...

Mar 14 01:29:23 test Keepalived_vrrp [819]: ip address 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!

Configuration file content:

# 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

}

}

Solution:

Change the value of virtual_router_id from 53 to 88, because there are other machines in the same network segment that have installed keepalived and set virtual_router_id=53. The problem is solved after restarting keepalived after changing to a different value.

Conclusion:

Virtual_router_id values in different keepalive clusters in the same IP address range cannot be the same.

The above is the editor for you to share the keepalived startup error how to solve, if there happen to be similar doubts, you might as well refer to the above analysis to understand. If you want to know more about it, you are welcome to follow the industry information channel.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.

Views: 0

*The comments in the above article only represent the author's personal views and do not represent the views and positions of this website. If you have more insights, please feel free to contribute and share.

Share To

Servers

Wechat

© 2024 shulou.com SLNews company. All rights reserved.

12
Report