|
On Sat, May 16, 2009 at 06:59:55AM -0700, Robinson, Eric wrote:
> I can verify that it is behaving as I described on my Centos 5.2 system
> running heartbeat-ldirectord-2.1.3-3.el5.centos and it did the same
> thing with an earlier verson of ldirectord, thought I don't recall the
> version number any more.
Hi Eric,
Unfortunately I am not able to reproduce that problem
using the same heartbeat-ldirectord package on centos.
To clarify, I ran ldirectord and observed:
IP Virtual Server version 1.2.1 (size=4096)
Prot LocalAddress:Port Scheduler Flags
-> RemoteAddress:Port Forward Weight ActiveConn InActConn
TCP 192.168.6.240:80 rr
-> 172.17.60.197:80 Route 20 0 0
I then shut down apache and observed:
IP Virtual Server version 1.2.1 (size=4096)
Prot LocalAddress:Port Scheduler Flags
-> RemoteAddress:Port Forward Weight ActiveConn InActConn
TCP 192.168.6.240:80 rr
-> 172.17.60.197:80 Route 20 0 0
And then I started up apache again and observed:
IP Virtual Server version 1.2.1 (size=4096)
Prot LocalAddress:Port Scheduler Flags
-> RemoteAddress:Port Forward Weight ActiveConn InActConn
TCP 192.168.6.240:80 rr
-> 172.17.60.197:80 Route 20 0 0
Perhaps I am misunderstanding the problem?
If not, would it be possible for you to post your configuration file,
perhaps you have something in there that triggers a bug.
_______________________________________________
Please read the documentation before posting - it's available at:
http://www.linuxvirtualserver.org/
LinuxVirtualServer.org mailing list - lvs-users@xxxxxxxxxxxxxxxxxxxxxx
Send requests to lvs-users-request@xxxxxxxxxxxxxxxxxxxxxx
or go to http://lists.graemef.net/mailman/listinfo/lvs-users
|
