|
hi guys. i've been running an lvs test web farm for a few months now with
very few problems. recently, though, i had to reboot my load balancer
(yeah, i've only got one) and now the load balancer won't distribute my
http requests. i'm using heartbeat+ldirectord from the 0.4.8-1 rpm and i'm
pretty sure i'm using direct routing. here are the relevant conf files:
/etc/ha.d/haresources:
susan.webslingerZ.com IPaddr::206.66.49.220 ldirectord::www
susan.webslingerZ.com IPaddr::206.66.49.154 ldirectord::www
/etc/ha.d/conf/www:
timeout = 10
checkinterval = 10
virtual = 206.66.49.220:80
service = http
protocol = tcp
scheduler = rr
request = "/testpage.txt"
receive = "test page"
real = 192.168.1.2:80 gate 5
real = 192.168.1.3:80 gate 5
virtual = 206.66.49.154:80
service = http
protocol = tcp
scheduler = rr
request = "/testpage.txt"
receive = "test page"
real = 192.168.1.2:80 gate 5
real = 192.168.1.3:80 gate 5
ipvsadm tells me:
[root@susan resource.d]# ipvsadm --list --numeric
IP Virtual Server version 0.9.11 (size=4096)
Prot LocalAddress:Port Scheduler Flags
-> RemoteAddress:Port Forward Weight ActiveConn InActConn
TCP 206.66.49.220:80 rr
TCP 206.66.49.154:80 rr
on the face of it, i'd say that the ipvsadm hasn't been initialized
properly, but i can't figure why not or how to fix it. clues are
appreciated. ldirectord is running, and the logs on the real servers
indicate that it's indeed asking for /testpage.txt just like it ought to.
however, when i telnet to port 80 on any of the managed ip addresses, i
get a connection refused. what gives?
also, just thought i'd mention - frequently, when heartbeat is starting up
and is setting up ip address aliases, it seems to get into a race
condition in which more than one ip address tries to grab the same network
interface alias - eth0:0 for instance - so only some ip addresses get
fired up properly.
- donald
|
