keepalived实现Tomcat服务双机热备

项目中需要采用tomcat双机热备机制，以确保系统性能。本人通过查阅资料以及亲自实现完成，写下这篇博文，供个人读者参考。

1. 规划

1.1服务器环境规划

负载服务器master及WEB服务器1真实IP：10.10.195.53

负载服务器backup及WEB服务器2真实IP：10.10.195.190

负载服务器虚拟ip：10.10.195.212

1.2 软件环境规划

操作系统：Red Hat Enterprise Linux Server release 5.6 (Tikanga)

keepalived：keepalived-1.2.19

Java：jdk-1.7.0_79

Tomcat：apache-tomcat-7.0.64

2. 负载服务器配置

这里只叙述如何安装配置keepalived，至于java以及tomcat的安装及配置，这里不赘述。

2.1 安装keepalived

[~]tar -zxvf keepalived-1.2.19.tar.gz
[~] cd keepalived-1.2.19
[keepalived-1.2.19] ./configure --prefix=/usr/local/keepalived --disable-fwmark
#(如果直接输入./configure有可能报错：configure:error: No SO_MARK declaration in headers)
[keepalived-1.2.19] make
[keepalived-1.2.19] make install

2.2 配置keepalived服务

[keepalived-1.2.19] cp /usr/local/keepalived/sbin/keepalived /usr/sbin/
[keepalived-1.2.19] cp /usr/local/keepalived/etc/sysconfig/keepalived /etc/sysconfig/
[keepalived-1.2.19] cp /usr/local/keepalived/etc/rc.d/init.d/keepalived /etc/init.d/
[keepalived-1.2.19] mkdir /etc/keepalived
[keepalived-1.2.19] cp /usr/local/keepalived/etc/keepalived/keepalived.conf/etc/keepalived/
[keepalived-1.2.19] chkconfig --add keepalived
[keepalived-1.2.19] chkconfig keepalived on

重启\启动\关闭\查看状态keepalived

service keepalived restart

service keepalived start

service keepalived stop

service keepalived status

2.3 配置keepalived.conf文件

[~]mv /etc/keepalived/keepalived.conf/etc/keepalived/keepalived.conf.bak
[~]vi /etc/keepalived//keepalived.conf

主备机的keepalived.conf文件大致相同，只是注意红色标注的地方。

主机配置：

global_defs {
   router_id NodeA
}
vrrp_script chk_http_port {
   script "/opt/tomcat.pid"
   interval 5
   weight 2
}
vrrp_instance VI_1 {
   state MASTER
   interface eth0
   virtual_router_id 52
   priority 150
   advert_int 1

   authentication {
       auth_type PASS
       auth_pass 1111
    }

   track_script {
       chk_http_port
    }

   virtual_ipaddress {
       10.10.195.212
    }
}

备机配置：

global_defs {
   router_id NodeB
}
vrrp_script chk_http_port {
   script "/opt/tomcat.pid"
   interval 5
   weight 2
}
vrrp_instance VI_1 {
   state BACKUP
   interface eth0
   virtual_router_id 52
   priority 100
   advert_int 1

   authentication {
       auth_type PASS
       auth_pass 1111
    }

   track_script {
       chk_http_port
    }

   virtual_ipaddress {
       10.10.195.212
    }
}

2.4配置/opt/tomcat.pid

#!/bin/bash
#description: check tomcat service anddecide whether stop the keepalived or not
#edited by zzh: 2015-10-14

CATALINA_HOME=/users/shr/apache-tomcat-7.0.64
JAVA_HOME=/users/shr/util/JavaDir/jdk
export CATALINA_HOME
export JAVA_HOME

ps ax --width=1000 | grep"org.apache.catalina.startup.Bootstrap start" | grep -v"grep" | awk '{printf $1 " "}' | wc | awk '{print $2}' >tomcat_process_count.txt
read line < tomcat_process_count.txt

start_tomcat=$CATALINA_HOME/bin/startup.sh

if [ ${line} -lt 1 ]
then
       echo -n "===Starting tomcat===:"
       ${start_tomcat}
       # :sudo service tomcat start
       echo "===tomcat start ok.==="
       sleep 3

       # check the tomcat status.
       ps ax --width=1000 | grep "org.apache.catalina.startup.Bootstrapstart" | grep -v "grep" | awk '{printf $1 " "}' | wc |awk '{print $2}' > tomcat_process_count.txt
       read line2 < tomcat_process_count.txt
       if [ ${line2} -lt 1 ]
       then
                sudo service keepalived stop
       fi
fi
rm tomcat_process_count.txt
#shell end.

3. 日志查看

3.1 正常启动

输入tail -f /var/log/messages查看启动keepalived日志：

（MASTER：10.10.195.53）

Sep 29 15:49:16 shr Keepalived[5536]:Starting Keepalived v1.2.19 (09/21,2015)
Sep 29 15:49:16 shrKeepalived_healthcheckers[5538]: Netlink reflector reports IP 10.10.195.53added
Sep 29 15:49:16 shrKeepalived_healthcheckers[5538]: Netlink reflector reports IP 10.10.195.53added
Sep 29 15:49:16 shrKeepalived_healthcheckers[5538]: Registering Kernel netlink reflector
Sep 29 15:49:16 shrKeepalived_healthcheckers[5538]: Registering Kernel netlink command channel
Sep 29 15:49:16 shrKeepalived_healthcheckers[5538]: Opening file'/etc/keepalived/keepalived.conf'.
Sep 29 15:49:16 shrKeepalived_healthcheckers[5538]: Configuration is using : 6572 Bytes
Sep 29 15:49:16 shr Keepalived[5537]:Starting Healthcheck child process, pid=5538
Sep 29 15:49:16 shr Keepalived_healthcheckers[5538]:Using LinkWatch kernel netlink reflector...
Sep 29 15:49:16 shr Keepalived_vrrp[5539]:Netlink reflector reports IP 10.10.195.53 added
Sep 29 15:49:16 shr Keepalived_vrrp[5539]:Netlink reflector reports IP 10.10.195.53 added
Sep 29 15:49:16 shr Keepalived[5537]:Starting VRRP child process, pid=5539
Sep 29 15:49:16 shr Keepalived_vrrp[5539]:Registering Kernel netlink reflector
Sep 29 15:49:16 shr Keepalived_vrrp[5539]:Registering Kernel netlink command channel
Sep 29 15:49:16 shr Keepalived_vrrp[5539]:Registering gratuitous ARP shared channel
Sep 29 15:49:16 shr Keepalived_vrrp[5539]:Opening file '/etc/keepalived/keepalived.conf'.
Sep 29 15:49:16 shr Keepalived_vrrp[5539]:Configuration is using : 36541 Bytes
Sep 29 15:49:16 shr Keepalived_vrrp[5539]:Using LinkWatch kernel netlink reflector...
Sep 29 15:49:16 shr Keepalived_vrrp[5539]:VRRP sockpool: [ifindex(2), proto(112), unicast(0), fd(10,11)]
Sep 29 15:49:17 shr Keepalived_vrrp[5539]:VRRP_Instance(VI_1) Transition to MASTER STATE
Sep 29 15:49:17 shr Keepalived_vrrp[5539]:VRRP_Instance(VI_1) Received lower prio advert, forcing new election
Sep 29 15:49:18 shr Keepalived_vrrp[5539]:VRRP_Instance(VI_1) Entering MASTER STATE
Sep 29 15:49:18 shr Keepalived_vrrp[5539]:VRRP_Instance(VI_1) setting protocol VIPs.
Sep 29 15:49:18 shr Keepalived_vrrp[5539]:VRRP_Instance(VI_1) Sending gratuitous ARPs on eth0 for 10.10.195.212
Sep 29 15:49:18 shr Keepalived_vrrp[5539]:Netlink reflector reports IP 10.10.195.212 added
Sep 29 15:49:18 shrKeepalived_healthcheckers[5538]: Netlink reflector reports IP 10.10.195.212added
Sep 29 15:49:23 shr Keepalived_vrrp[5539]:VRRP_Instance(VI_1) Sending gratuitous ARPs on eth0 for 10.10.195.212

(BACKUP:10.10.195.190)

Sep 29 15:46:25 server1 Keepalived[18218]:Starting Keepalived v1.2.19 (09/25,2015)
Sep 29 15:46:25 server1Keepalived_healthcheckers[18220]: Netlink reflector reports IP 10.10.195.190added
Sep 29 15:46:25 server1Keepalived_healthcheckers[18220]: Netlink reflector reports IP 10.10.195.190added
Sep 29 15:46:25 server1Keepalived_healthcheckers[18220]: Registering Kernel netlink reflector
Sep 29 15:46:25 server1Keepalived_healthcheckers[18220]: Registering Kernel netlink command channel
Sep 29 15:46:25 server1 Keepalived_healthcheckers[18220]:Opening file '/etc/keepalived/keepalived.conf'.
Sep 29 15:46:25 server1Keepalived_healthcheckers[18220]: Configuration is using : 6682 Bytes
Sep 29 15:46:25 server1 Keepalived[18219]:Starting Healthcheck child process, pid=18220
Sep 29 15:46:25 server1 Keepalived[18219]:Starting VRRP child process, pid=18221
Sep 29 15:46:25 server1Keepalived_vrrp[18221]: Netlink reflector reports IP 10.10.195.190 added
Sep 29 15:46:25 server1Keepalived_vrrp[18221]: Netlink reflector reports IP 10.10.195.190 added
Sep 29 15:46:25 server1Keepalived_healthcheckers[18220]: Using LinkWatch kernel netlink reflector...
Sep 29 15:46:25 server1Keepalived_vrrp[18221]: Registering Kernel netlink reflector
Sep 29 15:46:25 server1Keepalived_vrrp[18221]: Registering Kernel netlink command channel
Sep 29 15:46:25 server1Keepalived_vrrp[18221]: Registering gratuitous ARP shared channel
Sep 29 15:46:25 server1Keepalived_vrrp[18221]: Opening file '/etc/keepalived/keepalived.conf'.
Sep 29 15:46:25 server1 Keepalived_vrrp[18221]:Configuration is using : 36651 Bytes
Sep 29 15:46:25 server1Keepalived_vrrp[18221]: Using LinkWatch kernel netlink reflector...
Sep 29 15:46:25 server1Keepalived_vrrp[18221]: VRRP_Instance(VI_1) Entering BACKUP STATE
Sep 29 15:46:25 server1 Keepalived_vrrp[18221]:VRRP sockpool: [ifindex(2), proto(112), unicast(0), fd(10,11)]

3.2 主备切换

l 当在主机（MASTER：10.10.195.53）中输入 sudoservice keepalived stop，此时就会进行主备切换，主机切换成备机。

主机（MASTER：10.10.195.53）输出如下

Oct 14 13:25:09 shr Keepalived_vrrp[26683]:VRRP_Instance(VI_1) sending 0 priority
Oct 14 13:25:09 shr Keepalived_vrrp[26683]:VRRP_Instance(VI_1) removing protocol VIPs.
Oct 14 13:25:09 shrKeepalived_healthcheckers[26682]: Netlink reflector reports IP 10.10.195.212removed
Oct 14 13:25:09 shr Keepalived[26681]:Stopping Keepalived v1.2.19 (09/21,2015)

备机(BACKUP:10.10.195.190)输出如下

Oct 14 13:19:58 server1Keepalived_vrrp[30890]: VRRP_Instance(VI_1) Transition to MASTER STATE
Oct 14 13:19:59 server1Keepalived_vrrp[30890]: VRRP_Instance(VI_1) Entering MASTER STATE
Oct 14 13:19:59 server1Keepalived_vrrp[30890]: VRRP_Instance(VI_1) setting protocol VIPs.
Oct 14 13:19:59 server1Keepalived_vrrp[30890]: VRRP_Instance(VI_1) Sending gratuitous ARPs on eth0 for10.10.195.212
Oct 14 13:19:59 server1 Keepalived_healthcheckers[30889]:Netlink reflector reports IP 10.10.195.212 added
Oct 14 13:19:59 server1Keepalived_vrrp[30890]: Netlink reflector reports IP 10.10.195.212 added
Oct 14 13:20:04 server1Keepalived_vrrp[30890]: VRRP_Instance(VI_1) Sending gratuitous ARPs on eth0 for10.10.195.212

l 当在主机（MASTER：10.10.195.53）中输入sudoservice keepalived start,此时就会切换成主机。备机(BACKUP:10.10.195.190)输出如下信息：

Oct 14 13:25:11 server1Keepalived_vrrp[30890]: VRRP_Instance(VI_1) Received higher prio advert
Oct 14 13:25:11 server1Keepalived_vrrp[30890]: VRRP_Instance(VI_1) Entering BACKUP STATE
Oct 14 13:25:11 server1Keepalived_vrrp[30890]: VRRP_Instance(VI_1) removing protocol VIPs.
Oct 14 13:25:11 server1Keepalived_healthcheckers[30889]: Netlink reflector reports IP 10.10.195.212removed
Oct 14 13:25:11 server1Keepalived_vrrp[30890]: Netlink reflector reports IP 10.10.195.212 removed

4. 查看虚拟ip

可以通过ip add show命令查看添加的虚拟ip：

[shr@shr bin]$ip add show
1: lo: <LOOPBACK,UP,LOWER_UP> mtu16436 qdisc noqueue
   link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
   inet 127.0.0.1/8 scope host lo
2: eth0:<BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast qlen 1000
   link/ether 00:0c:29:6b:f2:a8 brd ff:ff:ff:ff:ff:ff
   inet 10.10.195.53/24 brd 10.10.195.255 scope global eth0
   inet 10.10.195.212/32scope global eth0

5. 常见错误

5. 1常见错误一：

/var/log/messages has thousands of errorslike this:

Jun 28 09:18:32 rust Keepalived_vrrp:receive an invalid ip number count
associated with VRID!
Jun 28 09:18:32 rust Keepalived_vrrp: bogusVRRP packet received on eth0 !!!
Jun 28 09:18:32 rust Keepalived_vrrp:VRRP_Instance(VI_1) Dropping received
VRRP packet...

The backup director starts up, but doesn'tlisten on the virtual addresses
at all. Its /var/log/messages has thousands of errors like this:

Jun 28 06:25:05 stye Keepalived_vrrp:receive an invalid ip number count
associated with VRID!
Jun 28 06:25:05 stye Keepalived_vrrp: bogusVRRP packet received on eth0 !!!
Jun 28 06:25:05 stye Keepalived_vrrp:VRRP_Instance(VI_1) ignoring received
advertisment...<span style="font-family: Arial, Helvetica, sans-serif; background-color: rgb(255, 255, 255);"> </span>

解决方法：

改变配置文件/etc/keepalived/keepalived.conf中virtual_router_id为另一个值即可。

（changed the vrid to another number and it worked fine）.

5.2 常见错误二：

主机执行到VRRP_Instance(VI_1) Entering BACKUP STATE之后没有执行VRRP_Instance(VI_1)setting protocol VIPs。

解决方法：

可能是配置文件keepalived.conf中{左边没有空格。

附

linux添加tomcat服务

在/etc/init.d中输入 sudo vim tomcat

脚本具体内容如下：

#!/bin/bash
#chkconfig: 2345 10 90
#description: Starts and Stops the tomcatdaemon
#edited by ZZH: 2015-10-14

CATALINA_HOME=/users/shr/apache-tomcat-7.0.64
JAVA_HOME=/users/shr/util/JavaDir/jdk
export CATALINA_HOME
export JAVA_HOME

start_tomcat=$CATALINA_HOME/bin/startup.sh
stop_tomcat=$CATALINA_HOME/bin/shutdown.sh

if [ ! -f $CATALINA_HOME/bin/catalina.sh ]
then
         echo"===Tomcat is not available.==="
         exit
fi

start()
{
         echo-n "===Starting tomcat===:"
         ${start_tomcat}
         echo"===tomcat start ok.==="
}

stop()
{
         echo-n "===Shutting down tomcat===:"
         ${stop_tomcat}
         echo"===tomcat stop ok.==="
}

status()
{
         ps ax --width=1000 | grep"org.apache.catalina.startup.Bootstrap start" | grep -v"grep" | awk '{printf $1 " "}' | wc | awk '{print $2}'> tomcat_process_count.txt
         readline < tomcat_process_count.txt
         rmtomcat_process_count.txt
         if[ $line -gt 0 ]
                   then
                            echo-n "tomcat ( pid = "
                            ps ax --width=1000 | grep"org.apache.catalina.startup.Bootstrap start" | grep -v"grep" | awk '{printf $1 " "}' | awk '{print $1}'> tomcat_process_pid.txt
                            readpid < tomcat_process_pid.txt
                            rmtomcat_process_pid.txt
                            echo-n $pid
                            echo-n ") is running..."
                            echo
                   else
                            echo"tomcat is stopped"
         fi
}

case "$1" in
         start)
                   start
                   ;;
         stop)
                   stop
                   ;;
         restart)
                   stop
                   sleep1
                   start
                   ;;
         status)
                   status
                   ;;
         *)
                   echo"Usage:$0 {start|stop|restart}"
                   exit1
esac

exit 0
# shell end.

在终端输入:

sudo chmod 755 tomcat
sudo chkconfig --add tomcat

tomcat 启动 service tomcatstart

tomcat 关闭 service tomcatstop

tomcat 重启 service tomcatrestart

tomcat状态查看 service tomcatstatus

时间： 2024-04-08 07:09:51

keepalived实现Tomcat服务双机热备的相关文章

LVS+Keepalived实现负载均衡和双机热备

1. 说明在<keepalived实现Tomcat服务双机热备>中主要讲述如何安装及配置Keepalived来实现双机热备,主要功能是:MASTER和BACKUP两台服务器处于热备状态,对用户虚拟一个IP,屏蔽底层的真实IP地址,用户通过虚拟IP访问当前的MASTER服务器:当MASTER服务器宕机或者发生其他故障时,BACKUP自动切换为MASTER,这个过程对用户时透明的. 本文主要讲述如何安装ipvsadm.如何配置LVS+Keepalived实现

双机热备常见问题与方案选择

问题对于企业重要的应用系统而言,保证系统能持续.可靠地提供服务是非常重要的,因此就出现了对高可用性的需求和高可用性的解决方案. 对于如何选择高可用性的解决方案,特别是关于双机热备的方案选择,常见的有以下问题: Q:已经采取了RAID技术和数据备份技术,还有必要做双机吗? A:参见:双机热备与数据备份的关系 Q:高可用性的解决方案有哪些? A:从广义讲,高可用性包括一切避免系统服务中断的技术.而一般所说的系统高可用性,往往特指服务器的双机或多机热备/容错. Q:什么时候需要双机热备? A:决定是

双机热备常见问题及解决方案

对于企业重要的应用系统而言,保证系统能持续.可靠地提供服务是非常重要的,因此就出现了对高可用性的需求和高可用性的解决方案. 对于如何选择高可用性的解决方案,特别是关于双机热备的方案选择,常见的有以下问题: Q:高可用性的解决方案有哪些? A:从广义讲,高可用性包括一切避免系统服务中断的技术.而一般所说的系统高可用性,往往特指服务器的双机或多机热备/容错. Q:什么时候需要双机热备? A:决定是否使用双机热备,正确的方法是要分析一下系统的重要性以及对服务中断的容忍程度,以此决定是否使用双机热备.即

双机热备与数据备份的关系

一些用户在规划双机热备或双机备份时,会有这样的问题:我已经有了RAID,以及磁带备份,还有必须做双机吗?或者,如果我做了双机备份,还有必要做磁带备份吗? 应该说RAID和数据备份都是很重要的.但是,RAID技术只能解决硬盘的问题,备份只能解决系统出现问题后的恢复.而一旦服务器本身出现问题,不论是设备的硬件问题还是软件系统的问题,都会造成服务的中断.因此,RAID及数据备份技术不能解决避免服务中断的问题.对于需要持续可靠地提供应用服务的系统,双机还是非常重要的.只要想一想,如果你的服务器坏了,你要

双机热备中基于共享存储与纯软件方式

双机热备有两种实现模式,一种是基于共享的存储设备的方式,另一种是没有共享的存储设备的方式,一般称为纯软件方式. 基于存储共享的双机热备是双机热备的最标准方案. 对于这种方式,采用两台服务器,使用共享的存储设备(磁盘阵列柜或存储区域网SAN).两台服务器可以采用互备.主从.并行等不同的方式.在工作过程中,两台服务器将以一个虚拟的IP地址对外提供服务,依工作方式的不同,将服务请求发送给其中一台服务器承担.同时,服务器通过心跳线(目前往往采用建立私有网络的方式)侦测另一台服务器的工作状况.当一台服务器

双机热备的概念

双机热备这一概念包括了广义与狭义两种意义. 从广义上讲,就是对于重要的服务,使用两台服务器,互相备份,共同执行同一服务.当一台服务器出现故障时,可以由另一台服务器承担服务任务,从而在不需要人工干预的情况下,自动保证系统能持续提供服务. 双机热备由备用的服务器解决了在主服务器故障时服务不中断的问题.但在实际应用中,可能会出现多台服务器的情况,即服务器集群. 双机热备一般情况下需要有共享的存储设备.但某些情况下也可以使用两台独立的服务器. 实现双机热备,需要通过专业的集群软件或双机软件. 从狭义上讲

纯软件方式的双机热备方案深入分析

数据库双机热备有两种典型的方式,一种是比较标准的,两台服务器通过一个共享的存储设备(一般是共享的磁盘阵列或存储区域网SAN),并且安装双机软件,实现双机热备,称为共享方式.另一种方式是通过纯软件的方式,一般称为纯软件方式或镜像方式(Mirror). 对于共享方式,数据库放在共享的存储设备上.当一台服务器提供服务时,直接在存储设备上进行读写.而当系统切换后,另一台服务器也同样读取该存储设备上的数据. 对于纯软件的方式,通过镜像软件,将数据可以实时复制到另一台服务器上,这样同样的数据就在两台服务器上

双机热备方案及双机热备软件选择

1 什么是双机热备方案企事业机构的信息化建设已经在随着社会建设的不断推进而改进和创新.众企事业机构的决策层也愈发重视企事业机构的信息化,不同程度的运营和发展着自身的业务信息系统.但是日趋普遍的业务信息系统在为企事业机构带来利益的同时,也存在着一个不容忽视的隐患--越来越多的业务依赖于业务信息系统.如果运行着关键业务信息系统的服务器发生宕机或是因为不可控的原因而停止,从而导致整个企事业机构的信息运营系统瘫痪,将会给企事业机构带来巨大的经济损失,而由于企事业机构的业务不能正常运行也会影响企事业机构

双机热备常见问题解答

双机热备包括广义与狭义两种.从广义上讲,就是对于重要的服务,使用两台服务器,互相备份,共同执行同一服务.当一台服务器出现故障时,可以由另一台服务器承担服务任务,从而在不需要人工干预的情况下,自动保证系统能持续提供服务. 从狭义上讲,双机热备特指基于active/standby方式的服务器热备.服务器数据包括数据库数据同时往两台或多台服务器写,或者使用一个共享的存储设备.在同一时间内只有一台服务器运行.当其中运行着的一台服务器出现故障无法启动时,另一台备份服务器会通过软件诊测(一般是通过心跳诊断)