You should post this message to the keepalived mailing list:
http://lists.sourceforge.net/lists/listinfo/keepalived-devel
.......................
Ian Neubert
Director of IS
TWAcomm.com, Inc.
http://www.twacomm.com/
-----Original Message-----
From: lvs-users-bounces@xxxxxxxxxxxxxxxxxxxxxx
[mailto:lvs-users-bounces@xxxxxxxxxxxxxxxxxxxxxx]On Behalf Of Dat Nguyen
Sent: Tuesday, August 05, 2003 12:16 PM
To: lvs-users@xxxxxxxxxxxxxxxxxxxxxx
Subject: Keepalive
When I start keepalived with the option -d, this is what I see in the
message.
Interface eth0 is up but somehow Keepalived thinks that it's down. What am
I doing wrong?
Aug 5 12:04:06 lvs Keepalived: Starting Keepalived v1.1.0 (24/07, 2003)
Aug 5 12:04:06 lvs Keepalived: Remove a zombie pid file
/var/run/keepalived.pid
Aug 5 12:04:06 lvs Keepalived: Remove a zombie pid file
/var/run/keepalived_vrr
p.pid
Aug 5 12:04:06 lvs Keepalived: Starting VRRP child process, pid=26443
Aug 5 12:04:06 lvs Keepalived_vrrp: Registering Kernel netlink reflector
Aug 5 12:04:06 lvs Keepalived_vrrp: Registering Kernel netlink comand
channel
Aug 5 12:04:06 lvs Keepalived_vrrp: Registering gratutious ARP shared
channel
Aug 5 12:04:06 lvs Keepalived_vrrp: Configuration is using : 123803 Bytes
Aug 5 12:04:06 lvs Keepalived_vrrp: ------< Global definitions >------
Aug 5 12:04:06 lvs Keepalived_vrrp: LVS ID = LVS_EXAMPLE_01
Aug 5 12:04:06 lvs Keepalived_vrrp: Smtp server = 172.16.0.66
Aug 5 12:04:06 lvs Keepalived_vrrp: Smtp server connection timeout = 30
Aug 5 12:04:06 lvs Keepalived_vrrp: Email notification from =
keepalived@simpl
etech.com
Aug 5 12:04:06 lvs Keepalived_vrrp: Email notification =
dnguyen@xxxxxxxxxxxxx
m
Aug 5 12:04:06 lvs Keepalived_vrrp: ------< VRRP Topology >------
Aug 5 12:04:06 lvs Keepalived_vrrp: VRRP Instance = VI_1
Aug 5 12:04:06 lvs Keepalived_vrrp: Want State = MASTER
Aug 5 12:04:06 lvs Keepalived_vrrp: Runing on device = eth1
Aug 5 12:04:06 lvs Keepalived_vrrp: Virtual Router ID = 51
Aug 5 12:04:06 lvs Keepalived_vrrp: Priority = 150
Aug 5 12:04:06 lvs Keepalived_vrrp: Advert interval = 1sec
Aug 5 12:04:06 lvs Keepalived_vrrp: Preempt Active
Aug 5 12:04:06 lvs Keepalived_vrrp: Authentication type =
SIMPLE_PASSWORD
Aug 5 12:04:06 lvs Keepalived_vrrp: Password = example
Aug 5 12:04:06 lvs Keepalived_vrrp: Virtual IP = 1
Aug 5 12:04:06 lvs Keepalived_vrrp: 172.31.0.5/32 dev eth1 scope
global
Aug 5 12:04:06 lvs Keepalived_vrrp: Using smtp notification
Aug 5 12:04:06 lvs Keepalived_vrrp: VRRP Instance = VI_GATEWAY
Aug 5 12:04:06 lvs Keepalived_vrrp: Want State = MASTER
Aug 5 12:04:06 lvs Keepalived_vrrp: Runing on device = eth0
Aug 5 12:04:06 lvs Keepalived_vrrp: Virtual Router ID = 52
Aug 5 12:04:06 lvs Keepalived_vrrp: Priority = 150
Aug 5 12:04:06 lvs Keepalived_vrrp: Advert interval = 1sec
Aug 5 12:04:06 lvs Keepalived_vrrp: Preempt Active
Aug 5 12:04:06 lvs Keepalived_vrrp: Authentication type =
SIMPLE_PASSWORD
Aug 5 12:04:06 lvs Keepalived_vrrp: Password = example
Aug 5 12:04:06 lvs Keepalived_vrrp: Virtual IP = 1
Aug 5 12:04:06 lvs Keepalived_vrrp: 172.16.25.10/32 dev eth0 scope
global
Aug 5 12:04:06 lvs Keepalived_vrrp: Using smtp notification
Aug 5 12:04:06 lvs Keepalived_vrrp: ------< VRRP Sync groups >------
Aug 5 12:04:06 lvs Keepalived_vrrp: VRRP Sync Group = VG1, BACKUP
Aug 5 12:04:06 lvs Keepalived_vrrp: monitor = VI_1
Aug 5 12:04:06 lvs Keepalived_vrrp: monitor = VI_GATEWAY
Aug 5 12:04:06 lvs Keepalived_vrrp: Watchdog: Starting listener on
/tmp/.vrrp w
dog socket
Aug 5 12:04:07 lvs Keepalived_vrrp: VRRP_Instance(VI_1) Transition to
MASTER ST
ATE
Aug 5 12:04:07 lvs Keepalived_vrrp: Kernel is reporting: interface eth0
DOWN
Aug 5 12:04:07 lvs Keepalived_vrrp: VRRP_Instance(VI_GATEWAY) Now in FAULT
stat
e
Aug 5 12:04:08 lvs Keepalived_vrrp: VRRP_Instance(VI_1) Entering MASTER
STATE
Aug 5 12:04:08 lvs Keepalived_vrrp: VRRP_Group(VG1) Syncing instances to
MASTER
state
Aug 5 12:04:08 lvs Keepalived_vrrp: VRRP_Instance(VI_GATEWAY) Transition to
MAS
TER STATE
Aug 5 12:04:08 lvs Keepalived_vrrp: Remote SMTP server [172.16.0.66:25]
connect
ed.
Aug 5 12:04:08 lvs Keepalived_vrrp: SMTP alert successfully sent.
Aug 5 12:04:10 lvs Keepalived_vrrp: Kernel is reporting: interface eth0
DOWN
Aug 5 12:04:10 lvs Keepalived_vrrp: VRRP_Instance(VI_GATEWAY) Entering
FAULT ST
ATE
Aug 5 12:04:10 lvs Keepalived_vrrp: VRRP_Instance(VI_GATEWAY) Now in FAULT
stat
e
Aug 5 12:04:10 lvs Keepalived_vrrp: VRRP_Group(VG1) Syncing instances to
FAULT
state
Aug 5 12:04:11 lvs Keepalived: Watchdog: success connecting /tmp/.vrrp wdog
soc
ket
Aug 5 12:04:11 lvs Keepalived_vrrp: VRRP_Instance(VI_1) Entering FAULT
STATE
Aug 5 12:04:11 lvs Keepalived_vrrp: VRRP_Instance(VI_1) Now in FAULT state
Here's the keepalived.conf:
! This is a comment
! Configuration File for keepalived
global_defs {
notification_email {
dnguyen@xxxxxxxxxxxxxx
}
notification_email_from keepalived@xxxxxxxxxxxxxx
smtp_server 172.16.0.66
smtp_connect_timeout 30
lvs_id LVS_EXAMPLE_01
}
vrrp_sync_group VG1 {
group {
VI_1
VI_GATEWAY
}
}
vrrp_instance VI_1 {
state MASTER
interface eth1
lvs_sync_daemon_interface eth1
virtual_router_id 51
priority 150
advert_int 1
smtp_alert
authentication {
auth_type PASS
auth_pass example
}
virtual_ipaddress {
172.31.0.5
}
}
vrrp_instance VI_GATEWAY {
state MASTER
interface eth0
lvs_sync_daemon_interface eth0
virtual_router_id 52
priority 150
advert_int 1
smtp_alert
authentication {
auth_type PASS
auth_pass example
}
virtual_ipaddress {
172.16.25.10
}
}
virtual_server 172.31.0.5 80 {
delay_loop 30
lb_algo wrr
lb_kind NAT
persistence_timeout 50
protocol TCP
real_server 172.16.0.66 80 {
weight 1
HTTP_GET {
url {
path /index.html
digest c2efaf4f443a66d6512a111a825594a1
}
connect_timeout 3
nb_get_retry 3
delay_before_retry 3
}
}
real_server 172.16.0.71 80 {
weight 1
HTTP_GET {
url {
path /index.html
digest 9f9ede7cc43d9e1a0596f621a99f6e66
}
connect_timeout 3
nb_get_retry 3
delay_before_retry 3
}
}
}
PROPRIETARY-CONFIDENTIAL INFORMATION INCLUDED
This electronic transmission, and any documents attached hereto, may contain
confidential, proprietary and/or legally privileged information. The
information is intended only for use by the recipient named above. If you
received this electronic message in error, please notify the sender and
delete the electronic message. Any disclosure, copying, distribution, or use
of the contents of information received in error is strictly prohibited, and
violators will be pursued legally.
|