2. 程式人生 > >配置Keepalived雙實例高可用Nginx

配置Keepalived雙實例高可用Nginx

阿新 • • 發佈：2017-08-09
keepalived 雙實例 高可用nginx服務

我們知道Keepalived原生設計目的是為了高可用LVS集群的，但Keepalived除了可以高可用LVS服務之外，還可以基於vrrp_script和track_script高可用其它服務，如Nginx等。本篇主要演示如何使用Keepalived高可用Nginx服務（雙實例），關於vrrp_script、track_script的更多介紹可以見上一篇博客《Keepalived學習總結》。


實驗要求 ==> 實現Keepalived基於vrrp_script、track_script高可用Nginx服務，要求配置為雙實例，兩個vrrp實例的VIP分別為192.168.10.77、192.168.10.78，可以分別將其配置在網卡別名上。

實驗環境 ==> CentOS 7.x

實驗目的 ==> 實現Keepalived雙實例高可用Nginx服務

實驗主機 ==> 192.168.10.6（主機名：node1）、192.168.10.8（主機名：node2）

實驗前提 ==> 高可用對之間時間同步（可通過周期性任務來實現）

實驗操作如下。


1、編輯Keepalived配置文件

技術分享


2、在兩個節點上分別使用yum安裝Nginx，並啟動Web服務

(1) 在node1（192.168.10.6）上

[[email protected] ~]# yum -y install nginx
[[email protected] ~]# systemctl start nginx.service
[[email protected] ~]# ss -tnl | grep :80
LISTEN     0      128          *:80                       *:*                  
LISTEN     0      128         :::80                      :::*


(2) 在node2（192.168.10.8）上

[[email protected] ~]# yum -y install nginx
[[email protected] ~]# systemctl start nginx.service
[[email protected] ~]# ss -tnl | grep :80
LISTEN     0      128          *:80                       *:*


3、在兩個節點上分別啟動Keepalived服務

(1) 在node1（192.168.10.6）上

[[email protected] ~]# systemctl start keepalived
[[email protected] ~]# ifconfig 
ens33: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.10.6  netmask 255.255.255.0  broadcast 192.168.10.255
        ether 00:0c:29:f7:b3:4e  txqueuelen 1000  (Ethernet)
        RX packets 46064  bytes 21104876 (20.1 MiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 43548  bytes 3735943 (3.5 MiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

ens33:0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.10.77  netmask 255.255.255.255  broadcast 0.0.0.0
        ether 00:0c:29:f7:b3:4e  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 0  (Local Loopback)
        RX packets 195  bytes 12522 (12.2 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 195  bytes 12522 (12.2 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0


(2) 在node2（192.168.10.8）上

[[email protected] ~]# systemctl start keepalived
[[email protected] ~]# ifconfig 
ens34: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.10.8  netmask 255.255.255.0  broadcast 192.168.10.255
        ether 00:0c:29:ef:52:87  txqueuelen 1000  (Ethernet)
        RX packets 60646  bytes 17433464 (16.6 MiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 29539  bytes 2636829 (2.5 MiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

ens34:1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.10.78  netmask 255.255.255.255  broadcast 0.0.0.0
        ether 00:0c:29:ef:52:87  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 0  (Local Loopback)
        RX packets 319  bytes 20447 (19.9 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 319  bytes 20447 (19.9 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

可以發現，因為在第一個vrrp實例（VIP為192.168.10.77）中，node1節點為主節點，因此該VIP配置在node1上；而在第二個vrrp實例（VIP為192.168.10.78）中，node2節點為主節點，因此該VIP配置在node2上。


4、人為制造故障進行測試

(1) 在node2上殺死nginx進程，查看第二個vrrp實例的VIP（192.168.10.78）是否會漂移至node1。

[[email protected] ~]# killall nginx


#查看日誌

[[email protected] ~]# tail /var/log/messages
...（其他省略）...
Aug  8 16:29:28 node2 Keepalived_vrrp[6832]: VRRP_Script(chk_nginx) failed
Aug  8 16:29:30 node2 Keepalived_vrrp[6832]: VRRP_Instance(VI_2) Received higher prio advert
Aug  8 16:29:30 node2 Keepalived_vrrp[6832]: VRRP_Instance(VI_2) Entering BACKUP STATE
Aug  8 16:29:30 node2 Keepalived_vrrp[6832]: VRRP_Instance(VI_2) removing protocol VIPs.
Aug  8 16:29:30 node2 Keepalived_healthcheckers[6831]: Netlink reflector reports IP 192.168.10.78 removed


#查看node2上的IP地址

[[email protected] ~]# ifconfig 
ens34: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.10.8  netmask 255.255.255.0  broadcast 192.168.10.255
        ether 00:0c:29:ef:52:87  txqueuelen 1000  (Ethernet)
        RX packets 61483  bytes 17487867 (16.6 MiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 29994  bytes 2672261 (2.5 MiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

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 0  (Local Loopback)
        RX packets 323  bytes 20647 (20.1 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 323  bytes 20647 (20.1 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

可以發現第二個vrrp實例的VIP（192.168.10.78）已經從node2上移除。


#查看node1上的IP地址

[[email protected] ~]# ifconfig 
ens33: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.10.6  netmask 255.255.255.0  broadcast 192.168.10.255
        ether 00:0c:29:f7:b3:4e  txqueuelen 1000  (Ethernet)
        RX packets 46700  bytes 21146944 (20.1 MiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 44417  bytes 3794925 (3.6 MiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

ens33:0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.10.77  netmask 255.255.255.255  broadcast 0.0.0.0
        ether 00:0c:29:f7:b3:4e  txqueuelen 1000  (Ethernet)

ens33:1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.10.78  netmask 255.255.255.255  broadcast 0.0.0.0
        ether 00:0c:29:f7:b3:4e  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 0  (Local Loopback)
        RX packets 199  bytes 12722 (12.4 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 199  bytes 12722 (12.4 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

此時node1不僅是第一個vrrp實例（VIP為192.168.10.77）的主節點，還是第二個vrrp實例（VIP為192.168.10.78）的主節點。


(2) 在node1上殺死nginx進程，在node2上重新啟動nginx進程，查看第一個vrrp實例的VIP（192.168.10.77）和第二個vrrp實例的VIP（192.168.10.78）是否會漂移至node2。

#先在node2上重啟nginx進程，此時第二個vrrp實例的VIP（192.168.10.78）應該會重新漂移至node2上

[[email protected] ~]# systemctl restart nginx.service
[[email protected] ~]# ss -tnl | grep :80
LISTEN     0      128          *:80                       *:*                  
[[email protected] ~]# ifconfig 
ens34: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.10.8  netmask 255.255.255.0  broadcast 192.168.10.255
        ether 00:0c:29:ef:52:87  txqueuelen 1000  (Ethernet)
        RX packets 62438  bytes 17551143 (16.7 MiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 30145  bytes 2688809 (2.5 MiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

ens34:1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.10.78  netmask 255.255.255.255  broadcast 0.0.0.0
        ether 00:0c:29:ef:52:87  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 0  (Local Loopback)
        RX packets 331  bytes 21047 (20.5 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 331  bytes 21047 (20.5 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

果然在意料之中！


#在node1上殺死nginx進程，查看第一個vrrp實例的VIP（192.168.10.77）是否會重新漂移至node2上

[[email protected] ~]# killall nginx        # 殺死nginx進程
[[email protected] ~]# tail /var/log/messages    # 查看日誌
Aug  8 16:36:41 node1 Keepalived_vrrp[7026]: VRRP_Instance(VI_2) Sending gratuitous ARPs on ens33 for 192.168.10.78
Aug  8 16:37:10 node1 Keepalived_vrrp[7026]: VRRP_Instance(VI_2) Received higher prio advert
Aug  8 16:37:10 node1 Keepalived_vrrp[7026]: VRRP_Instance(VI_2) Entering BACKUP STATE
Aug  8 16:37:10 node1 Keepalived_vrrp[7026]: VRRP_Instance(VI_2) removing protocol VIPs.
Aug  8 16:37:10 node1 Keepalived_healthcheckers[7025]: Netlink reflector reports IP 192.168.10.78 removed
Aug  8 16:38:44 node1 Keepalived_vrrp[7026]: VRRP_Script(chk_nginx) failed
Aug  8 16:38:45 node1 Keepalived_vrrp[7026]: VRRP_Instance(VI_1) Received higher prio advert
Aug  8 16:38:45 node1 Keepalived_vrrp[7026]: VRRP_Instance(VI_1) Entering BACKUP STATE
Aug  8 16:38:45 node1 Keepalived_vrrp[7026]: VRRP_Instance(VI_1) removing protocol VIPs.
Aug  8 16:38:45 node1 Keepalived_healthcheckers[7025]: Netlink reflector reports IP 192.168.10.77 removed
[[email protected] ~]# ifconfig     # 查看IP地址
ens33: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.10.6  netmask 255.255.255.0  broadcast 192.168.10.255
        ether 00:0c:29:f7:b3:4e  txqueuelen 1000  (Ethernet)
        RX packets 47288  bytes 21191119 (20.2 MiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 45193  bytes 3854623 (3.6 MiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

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 0  (Local Loopback)
        RX packets 215  bytes 13522 (13.2 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 215  bytes 13522 (13.2 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

兩個vrrp實例的VIP都不見了。


#重新查看node2上的IP地址

[[email protected] ~]# ifconfig 
ens34: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.10.8  netmask 255.255.255.0  broadcast 192.168.10.255
        ether 00:0c:29:ef:52:87  txqueuelen 1000  (Ethernet)
        RX packets 62612  bytes 17562546 (16.7 MiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 30521  bytes 2712799 (2.5 MiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

ens34:0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.10.77  netmask 255.255.255.255  broadcast 0.0.0.0
        ether 00:0c:29:ef:52:87  txqueuelen 1000  (Ethernet)

ens34:1: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.10.78  netmask 255.255.255.255  broadcast 0.0.0.0
        ether 00:0c:29:ef:52:87  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 0  (Local Loopback)
        RX packets 335  bytes 21247 (20.7 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 335  bytes 21247 (20.7 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

兩個vrrp實例的VIP都漂移到node2去了。


當然，本配置示例中自定義的vrrp_script過於簡單，此處提供一個vrrp_script監控腳本，僅供參考。

[[email protected] ~]# vim /etc/keepalived/vrrp_script.sh 
#!/bin/bash
#
server=nginx

restart_server() {
    if ! systemctl restart $server &> /dev/null; then
        sleep 1
        return 0
    else
        exit 0
    fi
}

if ! killall -0 $server &> /dev/null; then
    restart_server
    restart_server
    restart_server
    [ $? -ne 0 ] && exit 1 || exit 0
fi

在keepalived.conf配置文件中需要指明腳本路徑。

[[email protected] ~]# vim /etc/keepalived/keepalived.conf
...（其他省略）...
vrrp_script chk_nginx {
    script "/etc/keepalived/vrrp_script.sh"
    interval 2
    weight -5
}
...（其他省略）...


實驗完成！



本文出自 “Tab” 博客，請務必保留此出處http://xuweitao.blog.51cto.com/11761672/1954608

配置Keepalived雙實例高可用Nginx

相關推薦

配置Keepalived雙實例高可用Nginx

keepalived 雙實例 高可用nginx服務我們知道Keepalived原生設計目的是為了高可用LVS集群的，但Keepalived除了可以高可用LVS服務之外，還可以基於vrrp_script和track_script高可用其它服務，如Nginx等。本篇主要演示如何使用Keepalived高可用Ngi

公司nginx keepalived tomcat cxf 搭建高可用負載均衡實戰系列1- keepalived安裝配置

技術分享 cnblogs start ges idt def auth div .cn 1，ip說明 vip 10.50.13.67 server1 10.50.13.68 server2 10.50.13.140 2

keepalived高可用nginx/htttpd,雙主模型

.com 無法訪問 訪問 keepaliv mar 雙主 eight 故障 配置文件 keepalived高可用nginx/htttpd,雙主模型Keepalived使用的vrrp協議方式，虛擬路由冗余協議 (Virtual Router Redundancy Protoc

Keepalived實現高可用Nginx反向代理

keepalived實現高可用nginx反向代理由於好久沒有接觸過負載相關的調試了復習一下實驗系統：（1）CentOS 6.5_x86_64；（2）共有二臺主機，本實驗以ip地址來命名主機，即10主機、11主機。實驗前提：防火墻和selinux都關閉，主機之間時間同步實驗軟件：nginx-1.10.2-1.e

nginx訪問日誌 logstash 配置文件實例2

windows 配置文件 request statuslog 日誌格式： log_format elk "$http_clientip | $http_x_forwarded_for | $time_local | $request | $status | $body_bytes_sent |

nginx訪問日誌 logstash 配置文件實例1

logstash日誌格式： log_format usgateway ‘$http_clientip\t$http_ServiceName\t$http_uid\t$http_sid\t[$time_local]‘ ‘\t$reques

實踐：在CentOS7.3部署 keepalived 高可用nginx（負載均衡）

高可用 nginx keepalived centos7.3 背景:既然有了Lvs+keepalived這樣高性能的組合，那為何還要有Nginx+keepalived呢，keepalived的初衷就是為了Lvs而設計的，我們都知道Lvs是一個四層的負載均衡設備，雖然有著高性能的優勢，但同時它卻

利用keepalived實現高可用nginx

keepalived 高可用nginx實驗拓撲圖（1）本次基於VMware Workstation搭建一個四臺Linux（CentOS 7.4）系統所構成的一個服務器集群，其中兩臺nginx做前端調度服務器（一臺為主機，另一臺為備機），另外兩臺作為真實的Web服務器（向外部提供http服務，這裏僅僅使用了Ce

keepalived實現nginx的高可用 + nginx負載均衡

2.6 ins 請求 原因 pid 可用 stat 根據 準備 前言 　　使用集群是網站解決高並發、海量數據問題的常用手段。當一臺服務器的處理能力、存儲空間不足時，不要企圖去換更強大的服務器，對大型網站而言，不管多麽強大的服務器，都滿足不了網站持續增長的業務需求。這種情況下

ElasticSearch單機雙實例的配置方法

.cn -m ast 雙實例 aos ren multipl pre htm ElasticSearch單機雙實例的配置方法https://knktc.com/2016/06/10/elasticsearch-multiple-instances/Don’t Cross 3

Linux環境下實現keepalive支援的LVS高可用性和NGINX的單主模型雙主模型高可用

實驗：實現高可用的LVS-DR模型  1、準備兩臺RS伺服器 2、將兩臺lVS安裝httpd或nginx，用來做sorry server 3、定義RS伺服器 在後端伺服器RS1寫配置指令碼 執行指令碼後，ifconfig 之後指令碼傳給RS2，執行此指令碼，同樣存在l

利用keepalived實現高可用nginx(修改正）

實驗拓撲圖 （1）本次基於VMware Workstation搭建一個四臺Linux（CentOS 7.5）系統所構成的一個伺服器叢集，其中兩臺nginx做前端排程伺服器（一臺為主機，另一臺為備機），另外兩臺作為真實的Web伺服器 　　（2）本次實驗設定了一個VIP（Virtual IP）為1

4、keepalived高可用nginx負載均衡

keepalived： HTTP_GET        //使用keepalived獲取後端real server健康狀態檢測 SSL_GET(https)  //這裡以為這後端使用的是http協議 TCP_CHECK   

Keepalived實現高可用Nginx

        Keepalived是一個高效能的伺服器高可用或熱備解決方案，Keepalived主要用來防止伺服器單點故障發生的問題，可以通過其與Nginix的配合來實現Web服務端的高可用。       關於安裝Keepalived我這裡就不介紹了，網上的一大堆，但是注

nginx子配置文件實例

一個 fas bmp rip 直接 lis css set swf [root@bogon conf.d]# cat /etc/nginx/conf.d/test6.conf server { listen 8085;

nginx+keepalived IP飄移（高可用）

1、安裝keepalived    yum  install -y keepalived 設定開機自啟動    systemctl enable keepalived.service  2、修改配置檔案 （1）主配置檔案 vim 

Hadoop-2.7.6雙namenode配置搭建（HA）高可用叢集部署教程

配置雙namenode的目的就是為了防錯，防止一個namenode掛掉資料丟失，具體原理本文不詳細講解，這裡只說明具體的安裝過程。Hadoop HA的搭建是基於Zookeeper的，關於Zookeeper的搭建可以檢視這裡 hadoop、zookeeper、hbase、spa

Nginx 搭建雙活、高可用 DNS 伺服器

關於 DNS 伺服器，有的公司是使用公共的 DNS，如：222.222.222.222、114.114.114.114 等，也有的公司選擇搭建自己的 DNS，能靈活更改配置來滿足公司內部的需求；我所在公司是一家做語音呼叫、轉發的客服公司，屬於中小型企業，客服人數近千人，為了滿足不同線路的需求，所以公

linux Nginx +keepalived+varnish+lamp實現高可用、負載均衡集群

lse 規則 col sys 腳本 lld keepaliv pro start 環境 需要六臺服務器:兩臺keepalived+nginx:192.168.80.100/192.168.80.101兩臺varnish:192.168.80.102/192.18.80.1

Nginx +keepalived+varnish+lamp實現高可用、負載均衡集群

負載均衡 cfb cdd .rpm fad bec 安裝mysql html root賬戶 描述：1、前端兩臺NGINX，通過keepalived虛擬IP漂移，實現前端兩臺NGINX高可用；2、利用NGINX反向代理功能對後端varnish實現高可用集群, 3、再通過var