[lvs-users] where is connection?

Gerry Reno greno at verizon.net
Thu Aug 2 14:58:58 BST 2007


Gerry Reno wrote:
> I went and established a ssh connection to my VIP and I also started a 
> web session to my VIP but when I look for connections on MASTER I do not 
> see them.  Instead I see connections on BACKUP.  Here is some output:
>
> MASTER:
> [root at grp-01-00-50 keepalived]# ipvsadm -l
> IP Virtual Server version 1.2.1 (size=4096)
> Prot LocalAddress:Port Scheduler Flags
>   -> RemoteAddress:Port           Forward Weight ActiveConn InActConn
> TCP  192.168.1.240:https rr persistent 600
>   -> 192.168.1.201:https          Route   1      0          0        
>   -> 192.168.1.200:https          Route   1      0          0        
> TCP  10.3.0.3:http wlc persistent 600
> TCP  192.168.1.240:http rr persistent 600
>   -> 192.168.1.201:http           Route   1      0          0        
>   -> 192.168.1.200:http           Route   1      0          0        
> TCP  192.168.1.240:ssh rr persistent 600
>   -> 192.168.1.201:ssh            Route   1      0          0        
>   -> 192.168.1.200:ssh            Route   1      0          0        
> [root at grp-01-00-50 keepalived]# ip addr show
> 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 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
>     inet6 ::1/128 scope host
>        valid_lft forever preferred_lft forever
> 2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast 
> qlen 1000
>     link/ether 00:0c:29:a7:c7:33 brd ff:ff:ff:ff:ff:ff
>     inet 192.168.1.150/24 brd 192.168.1.255 scope global eth0
>     inet 192.168.1.240/24 scope global secondary eth0                 
> <----------- VIP is here on MASTER
>     inet6 fe80::20c:29ff:fea7:c733/64 scope link
>        valid_lft forever preferred_lft forever
>
>
> BACKUP:
> [root at grp-01-00-51 keepalived]# ipvsadm -l
> IP Virtual Server version 1.2.1 (size=4096)
> Prot LocalAddress:Port Scheduler Flags
>   -> RemoteAddress:Port           Forward Weight ActiveConn InActConn
> TCP  192.168.1.240:https rr persistent 600
>   -> 192.168.1.201:https          Route   1      0          0        
>   -> 192.168.1.200:https          Route   1      0          0        
> TCP  192.168.1.240:http rr persistent 600
>   -> 192.168.1.201:http           Route   1      3          0           
> <------ VIP connections are here in BACKUP list
>   -> 192.168.1.200:http           Route   1      0          0        
> TCP  192.168.1.240:ssh rr persistent 600
>   -> 192.168.1.201:ssh            Route   1      1          0           
> <------ VIP connections are here in BACKUP list
>   -> 192.168.1.200:ssh            Route   1      0          0        
> [root at grp-01-00-51 keepalived]#
> [root at grp-01-00-51 keepalived]# ip addr show
> 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 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
>     inet 192.168.1.240/32 scope host lo
>     inet6 ::1/128 scope host
>        valid_lft forever preferred_lft forever
> 2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast 
> qlen 1000
>     link/ether 00:0c:29:54:ef:09 brd ff:ff:ff:ff:ff:ff
>     inet 192.168.1.151/24 brd 192.168.1.255 scope global eth0
>     inet6 fe80::20c:29ff:fe54:ef09/64 scope link
>        valid_lft forever preferred_lft forever
>
>
>
> This is confusing.
>
> Gerry
>
>
>   
Ok, last night I did this on the BACKUP:
# service keepalived reload

And in the log I see this:
Aug 1 23:43:34 grp-01-00-51 Keepalived_healthcheckers: Reloading 
Healthchecker child processi(-1) on signal
Aug 1 23:43:34 grp-01-00-51 Keepalived_healthcheckers: Using MII-BMSR 
NIC polling thread...
Aug 1 23:43:34 grp-01-00-51 Keepalived_healthcheckers: Netlink reflector 
reports IP 192.168.1.151 added
Aug 1 23:43:35 grp-01-00-51 Keepalived_healthcheckers: Registering 
Kernel netlink reflector
Aug 1 23:43:35 grp-01-00-51 Keepalived_healthcheckers: Registering 
Kernel netlink command channel
Aug 1 23:43:35 grp-01-00-51 Keepalived_vrrp: Using MII-BMSR NIC polling 
thread...
Aug 1 23:43:35 grp-01-00-51 Keepalived_vrrp: Netlink reflector reports 
IP 192.168.1.151 added
Aug 1 23:43:35 grp-01-00-51 Keepalived_vrrp: Registering Kernel netlink 
reflector
Aug 1 23:43:35 grp-01-00-51 Keepalived_vrrp: Registering Kernel netlink 
command channel
Aug 1 23:43:35 grp-01-00-51 Keepalived_vrrp: Registering gratutious ARP 
shared channel
Aug 1 23:43:35 grp-01-00-51 Keepalived_vrrp: Configuration is using : 
34706 Bytes
Aug 1 23:43:35 grp-01-00-51 Keepalived_healthcheckers: Configuration is 
using : 19895 Bytes
Aug 1 23:43:35 grp-01-00-51 Keepalived_vrrp: VRRP_Instance(VI_1) 
Entering BACKUP STATE
Aug 1 23:43:35 grp-01-00-51 Keepalived_healthcheckers: Activating 
healtchecker for service [192.168.1.200:22]
Aug 1 23:43:35 grp-01-00-51 Keepalived_vrrp: VRRP sockpool: [ifindex(2), 
proto(112), fd(8,9)]
Aug 1 23:43:35 grp-01-00-51 Keepalived_healthcheckers: Activating 
healtchecker for service [192.168.1.201:22]
Aug 1 23:43:35 grp-01-00-51 Keepalived_healthcheckers: Activating 
healtchecker for service [192.168.1.200:80]
Aug 1 23:43:35 grp-01-00-51 Keepalived_healthcheckers: Activating 
healtchecker for service [192.168.1.201:80]
Aug 1 23:43:35 grp-01-00-51 Keepalived_healthcheckers: Activating 
healtchecker for service [192.168.1.200:443]
Aug 1 23:43:35 grp-01-00-51 Keepalived_healthcheckers: Activating 
healtchecker for service [192.168.1.201:443]
Aug 1 23:43:35 grp-01-00-51 root: /etc/keepalived/manage_ip_lvs_dr 
(caller: keepalived): ip addr add 192.168.1.240/32 dev lo brd + scope host
Aug 1 23:44:52 grp-01-00-51 ntpd[1872]: Listening on interface #17 lo, 
192.168.1.240#123 Enabled
Aug 2 06:48:35 grp-01-00-51 Keepalived_healthcheckers: TCP connection to 
[192.168.1.200:443] failed !!!
Aug 2 06:48:35 grp-01-00-51 Keepalived_healthcheckers: Disabling service 
[192.168.1.200:443] from VS [192.168.1.240:443]
Aug 2 06:48:35 grp-01-00-51 Keepalived_healthcheckers: TCP connection to 
[192.168.1.200:80] failed !!!
Aug 2 06:48:35 grp-01-00-51 Keepalived_healthcheckers: Disabling service 
[192.168.1.200:80] from VS [192.168.1.240:80]
Aug 2 06:48:36 grp-01-00-51 Keepalived_healthcheckers: TCP connection to 
[192.168.1.200:22] failed !!!
Aug 2 06:48:36 grp-01-00-51 Keepalived_healthcheckers: Disabling service 
[192.168.1.200:22] from VS [192.168.1.240:22]
Aug 2 06:48:40 grp-01-00-51 Keepalived_healthcheckers: TCP connection to 
[192.168.1.200:443] success.
Aug 2 06:48:40 grp-01-00-51 Keepalived_healthcheckers: Enabling service 
[192.168.1.200:443] to VS [192.168.1.240:443]
Aug 2 06:48:40 grp-01-00-51 Keepalived_healthcheckers: TCP connection to 
[192.168.1.200:80] success.
Aug 2 06:48:40 grp-01-00-51 Keepalived_healthcheckers: Enabling service 
[192.168.1.200:80] to VS [192.168.1.240:80]
Aug 2 06:48:41 grp-01-00-51 Keepalived_healthcheckers: TCP connection to 
[192.168.1.200:22] success.
Aug 2 06:48:41 grp-01-00-51 Keepalived_healthcheckers: Enabling service 
[192.168.1.200:22] to VS [192.168.1.240:22]
Aug 2 07:11:47 grp-01-00-51 ntpd[1872]: synchronized to 192.189.54.33, 
stratum 2
Aug 2 09:24:01 grp-01-00-51 ntpd[1872]: synchronized to 193.201.52.56, 
stratum 2

So it looks at though the healthcheck failed at 06:48:35 and then 
recovered at 06:48:40 but is this related to what I'm seeing as far as 
connections going to the BACKUP?

Gerry





More information about the lvs-users mailing list