|
It looks like the important line in the syslog is:
Jan 30 09:33:51 vespasian Keepalived: VRRP sockpool: [ifindex(2),
proto(112), fd(5)]
Can anyone tell me what this means or point me towards some documentation
that may help? I'm using LVS 1.0.7 with kernel 2.4.19 and keepalived 1.0.
-----Original Message-----
From: Bishop, Cass [mailto:cbishop@xxxxxxxxxxxxxxxxx]
Sent: Thursday, January 30, 2003 9:40 AM
To: 'keepalived-devel@xxxxxxxxxxxxxxxxxxxxx';
'lvs-users@xxxxxxxxxxxxxxxxxxxxxx'
Subject: Problem with keepalive for LVS-NAT
I am trying to use keepalive with LVS-NAT for a project. I have keepalives
failover working correctly but I cannot get it to configure the LVS portion.
Here is my config and the result of starting keepalived with the -d option.
None of the LVS Topology or the Health Checker section shows up. If I run
ipvsadm it shows nothing is configured. I can't figure out what I have
missed. Can anyone spot any problems? I am using LVS-NAT on a single
network.
global_defs {
notification_email {
me@xxxxxx
}
notification_email_from cass@xxxxxxxx
smtp_server 127.0.0.1
smtp_connect_timeout 30
lvs_id Disp_test2
}
vrrp_instance VI_A {
state MASTER
interface eth0
lvs_sync_daemon_interface eth0
virtual_router_id 1
priority 200
advert_int 1
smtp_alert
authentication {
auth_type PASS
auth_pass Disp
}
virtual_ipaddress {
172.27.7.239
}
}
virtual_server 172.27.7.239 8080{
delay_loop 6
lb_algo rr
lb_kind NAT
nat_mask 255.255.252.0
persistence_timeout 300
protocol TCP
real_server 172.27.7.24 8080 {
weight 10
TCP_CHECK {
connect_timeout 3
connect_port 8080
}
}
}
CONFIDENTIALITY NOTICE: The information in this e-mail is privileged and
confidential. Any use, copying or dissemination of any portion of this
e-mail by or to anyone other than the intended recipient(s) is unauthorized.
If you have received this e-mail in error, please reply to sender and delete
it from your system immediately.
|
