Re: ldirectord.cf configuration quesion -- how to configure 50?ports...

[Horms <horms@xxxxxxxxxxxx>]

In article <d6e10810606270659y2b472d76v8201c7d7d775bddb@xxxxxxxxxxxxxx> you 
wrote:
> Hi Joe
> 
> I have already tried out fwm for my application, so instead of
> checking 50 ports, it now only checks one to verify if my application
> is up and running, but the problem is that it seems all the
> connections are always going to one real server although I have
> already configured the rr sheduler. Hope you won't charge this
> question.
> 
> attached is my ldirectord.cf configuration:
> 
> ********************************
> checktimeout=3
> checkinterval=10
> autoreload=yes
> logfile="/var/log/ldirectord.log"
> quiescent=yes
> 
> virtual=1
>        real=10.226.193.189:0 gate
>        real=10.226.193.190:0 gate
>        service=none
>        checkport=8070
>        checktype=connect
>        scheduler=rr
>        protocol=fwm
> 
> virtual=10.226.193.230:9005
>        real=10.226.193.189:9005 gate
>        real=10.226.193.190:9005 gate
>        checktype=connect
>        service=none
>        scheduler=rr
>        protocol=tcp
> 
> virtual=10.226.193.230:9007
>        real=10.226.193.189:9007 gate
>        real=10.226.193.190:9007 gate
>        checktype=connect
>        service=none
>        scheduler=rr
>        protocol=tcp
> ********************************
> 
> and ipvsadm shows:
> 
> ********************************
> IP Virtual Server version 1.0.8 (size=65536)
> Prot LocalAddress:Port Scheduler Flags
>  -> RemoteAddress:Port           Forward Weight ActiveConn InActConn
> TCP  10.226.193.250:80 rr
>  -> 10.226.193.190:80            Route   0      0          0
>  -> 10.226.193.189:80            Local   1      0          0
> TCP  10.226.193.230:9007 rr
>  -> 10.226.193.189:9007          Local   1      0          0
>  -> 10.226.193.190:9007          Route   0      0          0
> TCP  10.226.193.230:9005 rr
>  -> 10.226.193.189:9005          Local   1      0          0
>  -> 10.226.193.190:9005          Route   0      0          0
> FWM  1 rr
>  -> 10.226.193.190:0             Route   1      0          0
>  -> 10.226.193.189:0             Local   1      0          0
> ********************************
> 
> Any ideas or if I have overlooked sth?

The weithg of 10.226.193.190 for each virtual service is 0.
This indicates that ldirectord thinks that is is down.
You should examine the checks that you are using, and make sure
that the real-servers are responding appropriately.

-- 
Horms                                           
H: http://www.vergenet.net/~horms/          W: http://www.valinux.co.jp/en/