keepalived 自生存活监测

最新推荐文章于 2024-02-20 09:48:40 发布
最新推荐文章于 2024-02-20 09:48:40 发布
阅读量1.3k 收藏 1
点赞数
文章标签： 数据库 开发工具 运维
原文链接：http://blog.51cto.com/11886307/2406628
版权

keepalived 自生存活监测

vrrp script

keepalived调用外部的辅助脚本进行资源监控，并根据监控的结果状态能实现优先动态调整。也就是keepalived监测自身，当自身挂了之后主动让出VIP。
需要对
vrrp_script:自定义资源监控脚本，vrrp实例根据脚本返回值进行下一步操作，脚本可被多个实例调用。
track_script:调用vrrp_script定义的脚本去监控资源，定义在实例之内，调用事先定义的vrrp_script

vrrp_script

vrrp_script <SCRIPT_NAME> {         #定义 名称
    script <STRING>|<QUOTED-STRING> #定义脚本所在的位置
    interval <INTEGER>              #间隔多久执行一次脚本
    timeout <INTEGER>               #多久么有返回值就失败
    weight <INTEGER:-254..254>      #权重-254到254，如果监测失败则当前优先权减去次权重，如果
    rise <INTEGER>                  #服务器下线了开始监测多少测成功则上线             
    fall <INTEGER>                  #服务器连续检测多少测都失败，则标记为失败
    user USERNAME [GROUPNAME]       #一般为root
    init_fail                       #在未进行监测时，默认为失败。
}

keepalived+lvs实现自生存活监测

由于lvs没有进程，所以只能使用脚本去访问第三方的设备来探测自己是否存活，比如本机的端口，或者网关。

配置方法1

1.创建出一个ping脚本

[root@s1 ~]# vim /etc/keepalived/ping.sh
#!/bin/bash
ping -c 2 172.20.0.1 &> /dev/null
if [ $? -eq 0 ];then
    exit 0
else
    exit 2
fi

2.修改keepalived配置文件

vrrp_script check {                     #定义脚本
        script /etc/keepalived/ping.sh
        interval 2
        weight -50
        fall 3
        rise 5
        timeout 2
}

vrrp_instance VI_1 {
    state Master
    interface ens33
    virtual_router_id 27
    priority 100
    advert_int 2
    authentication {
        auth_type PASS
        auth_pass 1111
    }
    unicast_src_ip 172.20.27.10
    unicast_peer {
    172.20.27.11
    }
    virtual_ipaddress {
        172.20.27.100 dev ens33 label ens33:0
    }
    track_script {              #调用脚本
        check
    }
}
#在另一台主机上也执行相同的配置

3.重启服务后查看vip

[root@s1 ~]# ifconfig
ens33: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 172.20.27.10  netmask 255.255.0.0  broadcast 172.20.255.255
        inet6 fe80::20c:29ff:fec5:123c  prefixlen 64  scopeid 0x20<link>
        ether 00:0c:29:c5:12:3c  txqueuelen 1000  (Ethernet)
        RX packets 540749  bytes 43766835 (41.7 MiB)
        RX errors 0  dropped 12  overruns 0  frame 0
        TX packets 78080  bytes 11718371 (11.1 MiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

ens33:0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 172.20.27.100  netmask 255.255.255.255  broadcast 0.0.0.0
        ether 00:0c:29:c5:12:3c  txqueuelen 1000  (Ethernet)
#vip在当前的主机上

4.测试
更改ping.sh脚本中的地址到一个不存在的地址，并对keepalived日志进行跟踪

[root@s1 ~]# tail -f /var/log/messages 
Jun  8 15:48:37 s1 Keepalived_healthcheckers[10792]: SMTP alert successfully sent.
Jun  8 15:50:05 s1 Keepalived_vrrp[10793]: /etc/keepalived/ping.sh exited due to signal 15          #脚本监测失败
Jun  8 15:50:07 s1 Keepalived_vrrp[10793]: /etc/keepalived/ping.sh exited due to signal 15          #脚本监测失败
Jun  8 15:50:09 s1 Keepalived_vrrp[10793]: VRRP_Script(check) timed out                             #连续三次次超时
Jun  8 15:50:09 s1 Keepalived_vrrp[10793]: VRRP_Instance(VI_1) Changing effective priority from 100 to 50       #优先级从100降低到50
Jun  8 15:50:09 s1 Keepalived_vrrp[10793]: /etc/keepalived/ping.sh exited due to signal 15          #脚本监测失败
Jun  8 15:50:11 s1 Keepalived_vrrp[10793]: VRRP_Instance(VI_1) Received advert with higher priority 80, ours 50     #发现备节点的优先级比本机高，主动让出vip

查看vip是否在s2节点上

[root@s2 ~]# ifconfig
ens33: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 172.20.27.11  netmask 255.255.0.0  broadcast 172.20.255.255
        inet6 fe80::20c:29ff:fe4d:1ce3  prefixlen 64  scopeid 0x20<link>
        ether 00:0c:29:4d:1c:e3  txqueuelen 1000  (Ethernet)
        RX packets 535679  bytes 43641678 (41.6 MiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 36428  bytes 3457323 (3.2 MiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

ens33:0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 172.20.27.100  netmask 255.255.255.255  broadcast 0.0.0.0
        ether 00:0c:29:4d:1c:e3  txqueuelen 1000  (Ethernet)
#VIP在备节点上

配置方法2

在脚本中判断lvs后端的服务器是否存在，如果存不存在，则创建一个文件
在vrrp_script中判断文件是否存在如果文件存在，则表示自己挂了，将自己的优先级减低让出vip

script "/bin/bash -c '[[ -f /etc/keepalived/down ]]' && exit 7 || exit 0"

HAProxy+keepalived的检测机制

HAProxy+keepalived的检测方式可以使用curl HAProxy的状态页面，或者使用killall -0对HAProxy发送一个信号，如果进程存在则返回值为0，如果进程不存在则返回值为非0

配置方法1

1.创建检测脚本

[root@s1 ~]# vim /etc/keepalived/curl.sh
#!/bin/bash
curl -I http://172.20.27.10:9000/haproxy-status &> /dev/null
if [ $? -eq 0 ];then
    exit 0
else
    exit 2
fi

2.修改keepalived配置文件定义vrrp_script和调用

root@s1 ~]# cat /etc/keepalived/keepalived.conf 
! Configuration File for keepalived

global_defs {
   notification_email {
    root@mylinuxops.com
   }
   notification_email_from root@mylinuxops.com
   smtp_server 127.0.0.1
   smtp_connect_timeout 30
   router_id s1.mylinuxops.com
   vrrp_skip_check_adv_addr
   #vrrp_strict
   vrrp_iptables
   vrrp_garp_interval 0
   vrrp_gna_interval 0
}

vrrp_script check {                         #定义脚本名
    script /etc/keepalived/curl.sh          #定义脚本路径
    interval 2
    weight -50
    fall 3
    rise 5
    timeout 2
}

vrrp_instance VI_1 {
    state Master
    interface ens33
    virtual_router_id 27
    priority 100
    advert_int 2
    authentication {
        auth_type PASS
        auth_pass 1111
    }
    unicast_src_ip 172.20.27.10
    unicast_peer {
    172.20.27.11
    }
    virtual_ipaddress {
    172.20.27.100 dev ens33 label ens33:0
    }
    track_script {
    check                               #调用脚本
    }
}
#另一台服务器也执行相同的操作

3.重启服务后查看vip是否存在

[root@s1 ~]# ifconfig
ens33: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 172.20.27.10  netmask 255.255.0.0  broadcast 172.20.255.255
        inet6 fe80::20c:29ff:fec5:123c  prefixlen 64  scopeid 0x20<link>
        ether 00:0c:29:c5:12:3c  txqueuelen 1000  (Ethernet)
        RX packets 639634  bytes 52435377 (50.0 MiB)
        RX errors 0  dropped 12  overruns 0  frame 0
        TX packets 103375  bytes 13944325 (13.2 MiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

ens33:0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 172.20.27.100  netmask 255.255.255.255  broadcast 0.0.0.0
        ether 00:0c:29:c5:12:3c  txqueuelen 1000  (Ethernet)

lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
        inet 127.0.0.1  netmask 255.0.0.0
        inet6 ::1  prefixlen 128  scopeid 0x10<host>
        loop  txqueuelen 1000  (Local Loopback)
        RX packets 4511  bytes 317479 (310.0 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 4511  bytes 317479 (310.0 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

4.停止haproxy并追踪日志

[root@s1 ~]# tail -f /var/log/messages 
Jun  8 17:15:16 s1 Keepalived_vrrp[16954]: /etc/keepalived/curl.sh exited with status 2
Jun  8 17:15:18 s1 Keepalived_vrrp[16954]: /etc/keepalived/curl.sh exited with status 2
Jun  8 17:15:20 s1 Keepalived_vrrp[16954]: /etc/keepalived/curl.sh exited with status 2     #连续3次无法curl到页面
Jun  8 17:15:20 s1 Keepalived_vrrp[16954]: VRRP_Script(check) failed
Jun  8 17:15:20 s1 Keepalived_vrrp[16954]: VRRP_Instance(VI_1) Changing effective priority from 100 to 50       #自动将优先级降低50
Jun  8 17:15:22 s1 Keepalived_vrrp[16954]: VRRP_Instance(VI_1) Received advert with higher priority 80, ours 50     #发现备的优先级比自己高
Jun  8 17:15:22 s1 Keepalived_vrrp[16954]: VRRP_Instance(VI_1) Entering BACKUP STATE        #自己转为备
Jun  8 17:15:22 s1 Keepalived_vrrp[16954]: VRRP_Instance(VI_1) removing protocol VIPs.
Jun  8 17:15:22 s1 Keepalived_vrrp[16954]: /etc/keepalived/curl.sh exited with status 2
Jun  8 17:15:24 s1 Keepalived_vrrp[16954]: /etc/keepalived/curl.sh exited with status 2

配置方法2

使用killall -0 haproxy对进程发起信号
1.安装killall

[root@s1 ~]# yum install psmisc -y

2.修改配置文件

[root@s1 ~]# vim /etc/keepalived/keepalived.conf 

! Configuration File for keepalived

global_defs {
   notification_email {
        root@mylinuxops.com
   }
   notification_email_from root@mylinuxops.com
   smtp_server 127.0.0.1
   smtp_connect_timeout 30
   router_id s1.mylinuxops.com
   vrrp_skip_check_adv_addr
   #vrrp_strict
   vrrp_iptables
   vrrp_garp_interval 0
   vrrp_gna_interval 0
}

vrrp_script check {                         #定义脚本名称
        script "killall -0 haproxy"         #由于脚本中只有一条命令，直接写在这里就行，无需再写脚本
        interval 2
        weight -50
        fall 3
        rise 5
        timeout 2
}

vrrp_instance VI_1 {
    state Master
    interface ens33
    virtual_router_id 27
    priority 100
    advert_int 2
    authentication {
        auth_type PASS
        auth_pass 1111
    }
    unicast_src_ip 172.20.27.10
    unicast_peer {
    172.20.27.11
    }
    virtual_ipaddress {
        172.20.27.100 dev ens33 label ens33:0
    }
    track_script {
        check                               #调用脚本
    }
}

3.重启服务后查看vip是否存在

[root@s1 ~]# ifconfig
ens33: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 172.20.27.10  netmask 255.255.0.0  broadcast 172.20.255.255
        inet6 fe80::20c:29ff:fec5:123c  prefixlen 64  scopeid 0x20<link>
        ether 00:0c:29:c5:12:3c  txqueuelen 1000  (Ethernet)
        RX packets 639634  bytes 52435377 (50.0 MiB)
        RX errors 0  dropped 12  overruns 0  frame 0
        TX packets 103375  bytes 13944325 (13.2 MiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

ens33:0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 172.20.27.100  netmask 255.255.255.255  broadcast 0.0.0.0
        ether 00:0c:29:c5:12:3c  txqueuelen 1000  (Ethernet)

lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
        inet 127.0.0.1  netmask 255.0.0.0
        inet6 ::1  prefixlen 128  scopeid 0x10<host>
        loop  txqueuelen 1000  (Local Loopback)
        RX packets 4511  bytes 317479 (310.0 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 4511  bytes 317479 (310.0 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

4.停止haproxy并追踪日志

[root@s1 ~]# tail -f /var/log/messages 
Jun  8 17:30:53 s1 Keepalived_vrrp[18639]: /usr/bin/killall -0 haproxy exited with status 1
Jun  8 17:30:55 s1 Keepalived_vrrp[18639]: /usr/bin/killall -0 haproxy exited with status 1
Jun  8 17:30:57 s1 Keepalived_vrrp[18639]: /usr/bin/killall -0 haproxy exited with status 1
Jun  8 17:30:57 s1 Keepalived_vrrp[18639]: VRRP_Script(check) failed                            #连续监测3次失败
Jun  8 17:30:57 s1 Keepalived_vrrp[18639]: VRRP_Instance(VI_1) Changing effective priority from 100 to 50           #优先级降低为50
Jun  8 17:30:59 s1 Keepalived_vrrp[18639]: VRRP_Instance(VI_1) Received advert with higher priority 80, ours 50     #发现有优先级比当前高的主机
Jun  8 17:30:59 s1 Keepalived_vrrp[18639]: VRRP_Instance(VI_1) Entering BACKUP STATE                                #自动将为备
Jun  8 17:30:59 s1 Keepalived_vrrp[18639]: VRRP_Instance(VI_1) removing protocol VIPs.                              #移除vip
Jun  8 17:30:59 s1 Keepalived_vrrp[18639]: /usr/bin/killall -0 haproxy exited with status 1
Jun  8 17:31:01 s1 Keepalived_vrrp[18639]: /usr/bin/killall -0 haproxy exited with status 1
Jun  8 17:31:03 s1 Keepalived_vrrp[18639]: /usr/bin/killall -0 haproxy exited with status 1

转载于:https://blog.51cto.com/11886307/2406628

weixin_34038652
关注
  • 0
    点赞
  • 踩
  • 1
    收藏
    觉得还不错? 一键收藏
  • 0
    评论
Ubuntu环境keepalived+Apache双活机制配置参考
02-06
在构建高可用性Web服务时，`Ubuntu`环境下的`Keepalived`和`Apache`双活机制是一种常用的方法。这种配置确保了即使一台服务器出现故障，另一台服务器也能无缝接管，保持服务的连续性和稳定性。以下是详细的配置步骤...
keepalived离线安装包
08-21
《keepalived离线安装包详解》 在IT领域，特别是在服务器高可用性与负载均衡的解决方案中，Keepalived是一款至关重要的工具。本篇将详细介绍Keepalived 2.0.19版本的离线安装包，以及如何在没有网络连接的环境下...
linux下配置nginx+keepalived高可用的各种问题以及解决办法
heiYeBuZaiLai的博客
05-26 5025
本人的环境Centos 7 + nginx 1.12.2 + keepalived 1.3.5 nginx 主机 192.168.26.26 备机 192.168.26.126 安装： 在俩台服务器上安装nginx,keepalived yum -y install keepalived : 安装keepalived rpm -q -a keepalived: 查看安装版本号 keepalived配置文件:/etc/keepalived/keepalived.conf 替换/etc/keepalived/
【博客688】如何实现keepalived vip监控与告警
qq_43684922的博客
08-05 916
如何实现keepalived vip监控与告警。
keepalived监控服务
laoyishujiaa的博客
02-20 347
keepalived监控服务
结合keepalived实现redis群集高可用故障自动切换
weixin_34297300的博客
04-24 139
系统架构图:我们所要实现的目的很简单,104,107 为keepalive和redis主从架构，其余服务器比如105、106均为redis从库并且挂在vip 192.168.56.180下面。主keepalive负责主要日常工作，从keepalive担任备机角色，一旦主keepalive挂掉，从keepalive服务器立即使从redis转变角色切换成master状态开...
keepalived安装包
05-26
keepalived安装包内容： keepalived-2.2.7.tar.gz keepalived-1.4.5.tar.gz keepalived-2.0.20.tar.gz keepalived-2.1.5.tar.gz
keepalived实现MYSQL双活高可用
09-24
7. **监控与告警**：完善的监控系统和告警机制是双活架构的关键，需要实时监测MySQL和keepalived的状态，以便快速响应异常。 8. **性能优化**：双活架构可能导致额外的网络延迟和数据同步开销，因此需要进行性能...
keepalived 监测mysql&&redis 高可用配置和脚本
06-27
本教程将深入探讨如何使用Keepalived来监测和管理MySQL及Redis服务，以构建高可用的数据库环境。 **Keepalived简介** Keepalived基于VRRP（Virtual Router Redundancy Protocol）协议，它的主要作用是在多台服务器...
VRRP script
wdirdo的博客
11-11 2377
VRRP script VRRP的检测脚本 1）在keepalived学习总结中已经说过，keepalived只是提供一个VIP，但高可用的是服务，因此keepalived一般会与lvs、nginx、haproxy、mysql…等服务器联合使用，以实现服务的高可用，但是若keepalived与之联合使用的服务异常时，此处keepalived提供的VIP也就没有任何意义了，因此此时的VIP我们...
Keepalived监测脚本一直不执行
緑水長流*z
05-22 8716
Keepalived检查脚本一直不执行 今天在搭建Nginx+Keepalived集群时，启动Keepalievd发现检查脚本不执行，脚本本身是没有问题的。 1.1 监测脚本 脚本如下： A=`ps -C nginx --no-header |wc -l` if [ $A -eq 0 ];then /root/nginx/sbin/nginx if [ `ps -C nginx --no-header |wc -l` -eq 0 ];then killall keepalived fi fi
keepalived问题汇总及解决方法
guiripei的专栏
12-16 5859
系统追求高可用，采用 keepalived + nginx 实现前置代理主机互备，部署过程中踩了几个坑，折腾了两天才搞定。现将问题及解决方法整理如下，供老铁们参考。 主机环境是CentOS Linux release 7.9.2009 (Core)，以root用户全程操作，采用yum -y install keepalived 命令安装keepalived。 keepalived运行状态查看及启停命令为： systemctl status keepalived systemctl stop keepa.
Keepalived健康检查
最新发布
a17783481239的博客
02-20 328
【代码】Keepalived健康检查。
Shell 脚本中的exit状态解释
Linuxprobe18的博客
04-02 1692
导读 命令的返回值是其退出状态，退出状态用于检查命令执行的结果（成功/失败）。如果退出状态为0，则命令执行成功。如果命令失败，则退出状态为非零。 下面表格中是返回值对应着退出状态的解释： 返回值 退出状态 0 成功 非0状态 失败 2 用法不正确 126 不是可执行文件 127 没有找到指令 $?特殊变量 shell中的变量名$?是一个特殊的内置变量，可以获取最后一次执行命令的退出状态。 在执行shell函数后，$?返回函数中最后一
keepalived无法执行vrrp_script配置中的脚本
zhuchunyan_aijia的博客
09-08 754
keepalived无法执行vrrp_script配置中的脚本
python windows环境报错cl.exe failed with exit status 2通用解决方法
热门推荐
鲨鱼儿的博客
07-21 3万+
在此网站下载对应的包使用pip安装即可： https://www.lfd.uci.edu/~gohlke/pythonlibs/
keepalived实现haproxy负载均衡高可用
George的博客
10-09 502
keepalived实现haproxy负载均衡高可用
Keepalived双主模型中vrrp_script中权重改变故障排查
weixin_34410662的博客
11-23 553
故障重现 keepalived配置如下 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 ...
keepalived双活配置详细信息
12-19
以下是keepalived双活配置的详细信息： 1. 安装keepalived ```shell yum install keepalived ``` 2. 配置keepalived主机 - 编辑主配置文件 ```shell vi /etc/keepalived/keepalived.conf ``` - 配置主机为MASTER ```shell vrrp_instance VI_1 { state MASTER interface eth0 virtual_router_id 51 priority 101 advert_int 1 authentication { auth_type PASS auth_pass 1111 } virtual_ipaddress { 192.168.1.1 } } ``` 3. 配置keepalived备用主机 - 编辑主配置文件 ```shell vi /etc/keepalived/keepalived.conf ``` - 配置备用主机为BACKUP ```shell vrrp_instance VI_1 { state BACKUP interface eth0 virtual_router_id 51 priority 100 advert_int 1 authentication { auth_type PASS auth_pass 1111 } virtual_ipaddress { 192.168.1.1 } } ``` 4. 配置故障通知脚本 ```shell notify_fault "/usr/local/keepalived/etc/keepalived/notify.sh fault" ``` 5. 启动/停止keepalived ```shell systemctl start keepalived systemctl stop keepalived ```

“相关推荐”对你有帮助么？

  • 非常没帮助
  • 没帮助
  • 一般
  • 有帮助
  • 非常有帮助
提交
评论
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

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

抵扣说明：

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

余额充值