|
On Mon, Oct 10, 2005 at 10:21:05AM +0100, Struan Bartlett wrote:
> Hi -
>
> I'm new to this list but I hope you'll forgive me getting right to the
> point.
>
> Our organisation is testing a new version of ldirectord - version 1.77.2.6
> from Debian package 1.2.3-9sarge3 - and have encountered a serious problem
> that shows different behaviour to the previous version we used (1.26) and,
> unlike that previous version, seems to prevent it from working properly.
>
> Here is our ldirectord.cf:
>
> checktimeout=60
> checkinterval=15
> fallback=127.0.0.1
>
> virtual=217.204.41.132:80
> scheduler=wlc
> real=192.168.2.32:80 masq 1024
> real=192.168.2.52:80 masq 1024
> real=192.168.2.62:80 masq 1024
> real=192.168.2.72:80 masq 1024
> service=http
> request="/cgi/NewsNow/Status/"
> receive="ldirectord-ok-string"
> protocol=tcp
>
> Now observe the results on startup:
>
> # /etc/init.d/ldirectord start
> Starting ldirectord
>
> # ipvsadm -Ln
> IP Virtual Server version 1.0.10 (size=4096)
> Prot LocalAddress:Port Scheduler Flags
> -> RemoteAddress:Port Forward Weight ActiveConn InActConn
> TCP 217.204.41.132:80 wlc
> -> 192.168.2.62:80 Masq 1024 0 0
> -> 192.168.2.72:80 Masq 1024 0 0
> -> 192.168.2.52:80 Masq 1024 0 0
> -> 192.168.2.32:80 Masq 1024 0 0
> -> 127.0.0.1:80 Local 1 0 0
>
> As I hope you see, the failover server weight has not been switched to
> zero, which appears to continue to allow some traffic to reach the
> failover servers. I understand this is incorrect.
>
> Please could you advise: is this a known bug, an unknown bug, or an error
> in our configuration of ldirectord?
Hi Struan,
That sounds like a new bug to me, thanks for pointing it out,
I will try to find some time to look into it unless someone gets
there first.
Would it be possible to send the output of running the following
at a time when it does not work.
ldirectord -d ldirectord.cf start
> Kind regards,
>
> Struan Bartlett
>
> P.S. For your information, the situation is not the same after a reload:
>
> # /etc/init.d/ldirectord reload
>
> # ipvsadm -Ln
> IP Virtual Server version 1.0.10 (size=4096)
> Prot LocalAddress:Port Scheduler Flags
> -> RemoteAddress:Port Forward Weight ActiveConn InActConn
> TCP 217.204.41.132:80 wlc
> -> 192.168.2.62:80 Masq 1024 0 0
> -> 192.168.2.72:80 Masq 1024 0 0
> -> 192.168.2.52:80 Masq 1024 0 0
> -> 192.168.2.32:80 Masq 1024 0 0
Thanks, that is also valuable information.
--
Horms
|
