LVS
lvs-users
Google
 
Web LinuxVirtualServer.org

RE: Not understanding some behavior

To: "'LinuxVirtualServer.org users mailing list.'" <lvs-users@xxxxxxxxxxxxxxxxxxxxxx>
Subject: RE: Not understanding some behavior
From: "Randy Paries" <randy.paries@xxxxxxxxxxx>
Date: Thu, 8 Apr 2004 16:52:52 -0500
Crap sorry

# Global Directives
checktimeout=3
checkinterval=10
fallback=127.0.0.1:80
autoreload=yes
logfile="/var/log/ldirectord.log"
#logfile="local0"
quiescent=yes

# 
virtual=66.208.187.27:80
        real=192.168.0.203:80 gate
        real=192.168.0.204:80 gate
        fallback=127.0.0.1:80 gate
        service=http
        request="ldirectordping.html"
        receive="Test Page"
        scheduler=wlc
        persistent=1800
        netmask=255.255.255.0
        protocol=tcp
#SSL part
virtual=66.208.187.27:443
        real=192.168.0.203:443 gate
        fallback=127.0.0.1:80 gate
        service=https
        request="ldirectordping.html"
        receive="Test Page"
        scheduler=wlc
        persistent=1800
        netmask=255.255.255.0
        protocol=tcp
 

-----Original Message-----
From: lvs-users-bounces@xxxxxxxxxxxxxxxxxxxxxx
[mailto:lvs-users-bounces@xxxxxxxxxxxxxxxxxxxxxx] On Behalf Of Willem de
Groot
Sent: Thursday, April 08, 2004 4:24 PM
To: LinuxVirtualServer.org users mailing list.
Subject: Re: Not understanding some behavior

On Thu, 8 Apr 2004, Randy Paries wrote:

> Now if I take down the http server on krusty and do a ipvsadm --list I 
> get ipvsadm --list
>   -> RemoteAddress:Port           Forward Weight ActiveConn InActConn
>   -> local.krusty:http            Route   0      0          0
>
> But If I try to go to the web server I get page not found. But if I 
> restart ldirectord Krusty is no longer listed and I now go to flanders 
> successfully.

I guess that would be desirable behaviour. You didn't include ldirectord.cf,
but you probably have quiescent=yes in it. From the
manpage:

       quiescent = [yes|no]

       If yes, then when real or failback servers are determined to be down,
       they are not actually removed from the kernel's LVS table. Rather,
       their weight is set to zero which means that no new connections will
be
       accepted. This has the side effect, that if the real server has
persis-
       tent connections, new connections from any existing clients will con-
       tinue to be routed to the real server, until the persistant timeout
can
       expire. See ipvsadm for more information on persistant connections.

If you restart ldirectord, there's no point in adding services to the LVS
table which are not working.

Willem
_______________________________________________
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

<Prev in Thread] Current Thread [Next in Thread>