Re: Verifying ldirectord

[James Bowling <james@xxxxxxxxxxx>]

Check your web server logs.  You should see the request for the 
testServices.cfm in the access logs.
Dan Baughman wrote:
> I have a fairfly simple lvs conf.  One linux LB, two 2k3 real servers. 
> Works
> great.  Now I want to enable teh fail over.
>
> Did a little homework, was intimidated by the length of the keepalived 
> conf
> files, so went with ldirectord.  Came up with this as a cf file.
> I run ldirectord start, and the log file doesn't get any entries 
> indicating
> a successful start, and I dont see any thing indicating the testing is
> actually taking place.  Other than simulating a fail on a server, how 
> can I
> verifty the ldirector is monitoring?  If i throw bogus arguments at 
> it, it
> does generate error messages in the log file, so I think i'm looking 
> at the
> right file.  Anyone already have this figured out?
>
> # Global Directives
> checktimeout=10
> checkinterval=2
> #fallback=127.0.0.1:80
> autoreload=no
> #logfile="/var/log/ldirectord.log"
> logfile="local0"
> quiescent=yes
>
> # Virtual Server for HTTP
> virtual=63.247.194.221:80
>        real=63.247.194.210:80 masq
>        service=http
>        request="testServices.cfm"
>        receive="success"
>        scheduler=rr
>        #persistent=600
>        protocol=tcp
>        checktype=negotiate
>
> # Virtual Server for HTTP
> virtual=63.247.194.222:80
>        real=63.247.194.210:80 masq
>        service=http
>        request="testServices.cfm"
>        receive="success"
>        scheduler=rr
>        #persistent=600
>        protocol=tcp
>        checktype=negotiate
> _______________________________________________
> LinuxVirtualServer.org mailing list - lvs-users@xxxxxxxxxxxxxxxxxxxxxx
> Send requests to lvs-users-request@xxxxxxxxxxxxxxxxxxxxxx
> or go to http://www.in-addr.de/mailman/listinfo/lvs-users
--
Regards,
James Bowling <james@xxxxxxxxxxx>
Director of Network Operations
Alchemy Communications, Inc.
818-206-9260 x4043