【Keepalived】VIP同时在主备节点出现问题排查

2024-04-10 17:28

本文主要是介绍【Keepalived】VIP同时在主备节点出现问题排查,希望对大家解决编程问题提供一定的参考价值,需要的开发者们随着小编来一起学习吧!

        在生产环境中,我们一般会使用 keepalived + nginx 来搭建一套两节点或者三节点的软件负载,nginx主要根据配置,为后端应用提供请求的反向代理和负载均衡的功能,而 keepalived 则主要用于检测nginx服务状态,并完成VIP在主、备节点之间的漂移。

        不过,在某些情况下,我们可能会遇到一个问题,就是VIP在主备节点上同时出现,这个问题一般是由于主、备节点无法正常通信,导致备节点认为主节点挂了,因此就将VIP设置给自己了。如下面所示,192.168.223.200这个VIP就在主、备节点上同时出现了。

主节点:
# systemctl status keepalived.service 
● keepalived.service - LVS and VRRP High Availability MonitorLoaded: loaded (/usr/lib/systemd/system/keepalived.service; enabled; vendor preset: disabled)Active: active (running) since 三 2024-04-10 14:49:23 CST; 22s agoDocs: man:keepalived(8)man:keepalived.conf(5)man:genhash(1)https://keepalived.orgProcess: 1080 ExecStart=/usr/local/keepalived/sbin/keepalived -f /etc/keepalived/keepalived.conf $KEEPALIVED_OPTIONS (code=exited, status=0/SUCCESS)Main PID: 1092 (keepalived)Tasks: 2CGroup: /system.slice/keepalived.service├─1092 /usr/local/keepalived/sbin/keepalived -f /etc/keepalived/keepalived.conf -D└─1097 /usr/local/keepalived/sbin/keepalived -f /etc/keepalived/keepalived.conf -D4月 10 14:49:26 vm-3rd89n7dd Keepalived_vrrp[1097]: Sending gratuitous ARP on ens33 for 192.168.223.200
4月 10 14:49:26 vm-3rd89n7dd Keepalived_vrrp[1097]: Sending gratuitous ARP on ens33 for 192.168.223.200
4月 10 14:49:26 vm-3rd89n7dd Keepalived_vrrp[1097]: Sending gratuitous ARP on ens33 for 192.168.223.200
4月 10 14:49:26 vm-3rd89n7dd Keepalived_vrrp[1097]: Sending gratuitous ARP on ens33 for 192.168.223.200
4月 10 14:49:31 vm-3rd89n7dd Keepalived_vrrp[1097]: (VI_1) Sending/queueing gratuitous ARPs on ens33 for 192.168.223.200
4月 10 14:49:31 vm-3rd89n7dd Keepalived_vrrp[1097]: Sending gratuitous ARP on ens33 for 192.168.223.200
4月 10 14:49:31 vm-3rd89n7dd Keepalived_vrrp[1097]: Sending gratuitous ARP on ens33 for 192.168.223.200
4月 10 14:49:31 vm-3rd89n7dd Keepalived_vrrp[1097]: Sending gratuitous ARP on ens33 for 192.168.223.200
4月 10 14:49:31 vm-3rd89n7dd Keepalived_vrrp[1097]: Sending gratuitous ARP on ens33 for 192.168.223.200
4月 10 14:49:31 vm-3rd89n7dd Keepalived_vrrp[1097]: Sending gratuitous ARP on ens33 for 192.168.223.200
# ip addr
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00inet 127.0.0.1/8 scope host lovalid_lft forever preferred_lft foreverinet6 ::1/128 scope host valid_lft forever preferred_lft forever
2: ens33: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000link/ether 00:0c:29:a2:1b:cf brd ff:ff:ff:ff:ff:ffinet 192.168.223.199/24 brd 192.168.223.255 scope global noprefixroute ens33valid_lft forever preferred_lft foreverinet 192.168.223.200/32 scope global ens33valid_lft forever preferred_lft foreverinet6 fe80::7565:47f4:3a2b:ae8d/64 scope link noprefixroute valid_lft forever preferred_lft forever
备节点
# systemctl status keepalived.service 
● keepalived.service - LVS and VRRP High Availability MonitorLoaded: loaded (/usr/lib/systemd/system/keepalived.service; enabled; vendor preset: disabled)Active: active (running) since 三 2024-04-10 14:51:29 CST; 3s agoDocs: man:keepalived(8)man:keepalived.conf(5)man:genhash(1)https://keepalived.orgProcess: 90867 ExecStart=/usr/local/keepalived/sbin/keepalived -f /etc/keepalived/keepalived.conf $KEEPALIVED_OPTIONS (code=exited, status=0/SUCCESS)Main PID: 90868 (keepalived)Tasks: 2CGroup: /system.slice/keepalived.service├─90868 /usr/local/keepalived/sbin/keepalived -f /etc/keepalived/keepalived.conf -D└─90869 /usr/local/keepalived/sbin/keepalived -f /etc/keepalived/keepalived.conf -D4月 10 14:51:31 vm-3f9h-45gds3nx Keepalived_vrrp[90869]: (VI_1) received an invalid passwd!
4月 10 14:51:32 vm-3f9h-45gds3nx Keepalived_vrrp[90869]: (VI_1) Receive advertisement timeout
4月 10 14:51:32 vm-3f9h-45gds3nx Keepalived_vrrp[90869]: (VI_1) Entering MASTER STATE
4月 10 14:51:32 vm-3f9h-45gds3nx Keepalived_vrrp[90869]: (VI_1) setting VIPs.
4月 10 14:51:32 vm-3f9h-45gds3nx Keepalived_vrrp[90869]: (VI_1) Sending/queueing gratuitous ARPs on ens33 for 192.168.223.200
4月 10 14:51:32 vm-3f9h-45gds3nx Keepalived_vrrp[90869]: Sending gratuitous ARP on ens33 for 192.168.223.200
4月 10 14:51:32 vm-3f9h-45gds3nx Keepalived_vrrp[90869]: Sending gratuitous ARP on ens33 for 192.168.223.200
4月 10 14:51:32 vm-3f9h-45gds3nx Keepalived_vrrp[90869]: Sending gratuitous ARP on ens33 for 192.168.223.200
4月 10 14:51:32 vm-3f9h-45gds3nx Keepalived_vrrp[90869]: Sending gratuitous ARP on ens33 for 192.168.223.200
4月 10 14:51:32 vm-3f9h-45gds3nx Keepalived_vrrp[90869]: Sending gratuitous ARP on ens33 for 192.168.223.200
# ip addr
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00inet 127.0.0.1/8 scope host lovalid_lft forever preferred_lft foreverinet6 ::1/128 scope host valid_lft forever preferred_lft forever
2: ens33: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000link/ether 00:0c:29:4a:4c:27 brd ff:ff:ff:ff:ff:ffinet 192.168.223.198/24 brd 192.168.223.255 scope global noprefixroute ens33valid_lft forever preferred_lft foreverinet 192.168.223.200/32 scope global ens33valid_lft forever preferred_lft foreverinet6 fe80::9a4b:ab8e:4493:81b0/64 scope link noprefixroute valid_lft forever preferred_lft forever

那为什么会出现主备节点无法正常通信呢?一般有以下几个原因:

1)主、备节点所在的服务器防火墙没有关闭(active-运行,inactive-关闭),可以使用下面的命令检查

systemctl status firewalld.service

2)主、备节点上的keepalived配置不一致,涉及的配置如下:

第一,检查虚拟路由配置:virtual_router_id(主、备节点配置必须一致)第二,检查主备节点的通信密码:auth_pass(主、备节点配置必须一致)

3)云上ECS服务器之间默认禁止互相通信(比如阿里云禁止组播),可以通过增加下面的单播配置来解决。

    unicast_src_ip 192.168.223.197unicast_peer {192.168.223.198192.168.223.199}

备注:197、198、199分别为集群的三个节点,unicast_src_ip 为本机IP,unicast_peer 为对端节点IP。

这篇关于【Keepalived】VIP同时在主备节点出现问题排查的文章就介绍到这儿,希望我们推荐的文章对编程师们有所帮助!



http://www.chinasem.cn/article/891683

相关文章

解决pandas无法读取csv文件数据的问题

《解决pandas无法读取csv文件数据的问题》本文讲述作者用Pandas读取CSV文件时因参数设置不当导致数据错位,通过调整delimiter和on_bad_lines参数最终解决问题,并强调正确参... 目录一、前言二、问题复现1. 问题2. 通过 on_bad_lines=‘warn’ 跳过异常数据3

解决RocketMQ的幂等性问题

《解决RocketMQ的幂等性问题》重复消费因调用链路长、消息发送超时或消费者故障导致,通过生产者消息查询、Redis缓存及消费者唯一主键可以确保幂等性,避免重复处理,本文主要介绍了解决RocketM... 目录造成重复消费的原因解决方法生产者端消费者端代码实现造成重复消费的原因当系统的调用链路比较长的时

深度解析Nginx日志分析与499状态码问题解决

《深度解析Nginx日志分析与499状态码问题解决》在Web服务器运维和性能优化过程中,Nginx日志是排查问题的重要依据,本文将围绕Nginx日志分析、499状态码的成因、排查方法及解决方案展开讨论... 目录前言1. Nginx日志基础1.1 Nginx日志存放位置1.2 Nginx日志格式2. 499

kkFileView启动报错:报错2003端口占用的问题及解决

《kkFileView启动报错:报错2003端口占用的问题及解决》kkFileView启动报错因office组件2003端口未关闭,解决:查杀占用端口的进程,终止Java进程,使用shutdown.s... 目录原因解决总结kkFileViewjavascript启动报错启动office组件失败,请检查of

SpringBoot 异常处理/自定义格式校验的问题实例详解

《SpringBoot异常处理/自定义格式校验的问题实例详解》文章探讨SpringBoot中自定义注解校验问题,区分参数级与类级约束触发的异常类型,建议通过@RestControllerAdvice... 目录1. 问题简要描述2. 异常触发1) 参数级别约束2) 类级别约束3. 异常处理1) 字段级别约束

java内存泄漏排查过程及解决

《java内存泄漏排查过程及解决》公司某服务内存持续增长,疑似内存泄漏,未触发OOM,排查方法包括检查JVM配置、分析GC执行状态、导出堆内存快照并用IDEAProfiler工具定位大对象及代码... 目录内存泄漏内存问题排查1.查看JVM内存配置2.分析gc是否正常执行3.导出 dump 各种工具分析4.

Python错误AttributeError: 'NoneType' object has no attribute问题的彻底解决方法

《Python错误AttributeError:NoneTypeobjecthasnoattribute问题的彻底解决方法》在Python项目开发和调试过程中,经常会碰到这样一个异常信息... 目录问题背景与概述错误解读:AttributeError: 'NoneType' object has no at

Spring的RedisTemplate的json反序列泛型丢失问题解决

《Spring的RedisTemplate的json反序列泛型丢失问题解决》本文主要介绍了SpringRedisTemplate中使用JSON序列化时泛型信息丢失的问题及其提出三种解决方案,可以根据性... 目录背景解决方案方案一方案二方案三总结背景在使用RedisTemplate操作redis时我们针对

Kotlin Map映射转换问题小结

《KotlinMap映射转换问题小结》文章介绍了Kotlin集合转换的多种方法,包括map(一对一转换)、mapIndexed(带索引)、mapNotNull(过滤null)、mapKeys/map... 目录Kotlin 集合转换:map、mapIndexed、mapNotNull、mapKeys、map

nginx中端口无权限的问题解决

《nginx中端口无权限的问题解决》当Nginx日志报错bind()to80failed(13:Permissiondenied)时,这通常是由于权限不足导致Nginx无法绑定到80端口,下面就来... 目录一、问题原因分析二、解决方案1. 以 root 权限运行 Nginx(不推荐)2. 为 Nginx