RE: ldirectord: active sessions on a dead server weighted 0

The persistence option is really there for software that won't recover
well if the connection doesn't go to the same box, like for FTP
connections... 

That's why it still tries to forward them even after the weight is zero.

You might want to look at these options
	checktype=negotiate
	request="index.php3"
	receive="some text"

Or, if you want something simpler
	checktype=connect

They would remove the server completely and avoid your problem. (as long
as persistence isn't required for your software to work)

-----Original Message-----
From: [email protected]
[mailto:[email protected]] On Behalf Of James
Ziller
Sent: Wednesday, May 24, 2006 2:03 PM
To: [email protected]
Subject: Re: ldirectord: active sessions on a dead server weighted 0

Thanks for the reply.  It surprises me that setting the persistent  
value would cause ldirectord to not failover sessions even when a  
server is completely _dead_, what good is that?  I was considering  
that this could be the issue but  it had been over ten minutes  since  
I timed the server going down(well passed the time a session should  
have been persistant,120 seconds) and certain clients were still not  
able to make an http connection...


On May 24, 2006, at 1:46 PM, Terry, Jason wrote:

> If you don't want your server to behave like this then remove this  
> line
> persistent=120
>
> But you'll lose your persistent connections if you do.  I'm not  
> sure if
> there is a "best of both worlds"...
>
> -----Original Message-----
> From: [email protected]
> [mailto:[email protected]] On Behalf Of James
> Ziller
> Sent: Wednesday, May 24, 2006 11:17 AM
> To: [email protected]
> Subject: ldirectord: active sessions on a dead server weighted 0
>
> Greetings folks,
>
> I am hoping someone here could give me advice on an issue I am having
> with ldirectord.  I am load balancing between two apache servers,
> works great except when one server goes down ipvsadm still shows
> active sessions on it even though the weight is dropped down to 0.
> When this happens, certain clients(presumably the ones with active
> sessions on the dead server) can no longer access the http server
> through the load balancer, while other clients have no problems.
> Once the dead server is brought back up all connection issues go
> away.  Any ideas why everything isnt failing over?  Another factor is
> that many of the connections are made through an ISA proxy (any
> compatibility concerns there?). Heres my config:
>
> # Global Directives
> checktimeout=10
> checkinterval=5
> fallback=127.0.0.1:80
> autoreload=no
> logfile="/var/log/ldirectord.log"
> #logfile="local0"
> quiescent=yes
>
> #incoming standard web traffic
> virtual=199.27.3.33:80
>          real=192.168.124.6:80 masq
>          real=192.168.124.7:80 masq
>          fallback=127.0.0.1:80
>          persistent=120
>          service=http
>          request="index.html"
>          receive="Test Page"
>          scheduler=wlc
>          protocol=tcp
>          checktype=negotiate
>
> Thanks,
> James
>
>
> -- 
> Ultra Monkey - http://www.ultramonkey.org/
> To UNSUBSCRIBE, email to [email protected], with a body:
> unsubscribe ultramonkey-users [email protected]
> where "[email protected]" is YOUR email address.
>
>
>
> -- 
> Ultra Monkey - http://www.ultramonkey.org/
> To UNSUBSCRIBE, email to [email protected], with a body:
> unsubscribe ultramonkey-users [email protected]
> where "[email protected]" is YOUR email address.
>


-- 
Ultra Monkey - http://www.ultramonkey.org/
To UNSUBSCRIBE, email to [email protected], with a body:
unsubscribe ultramonkey-users [email protected]
where "[email protected]" is YOUR email address.



-- 
Ultra Monkey - http://www.ultramonkey.org/
To UNSUBSCRIBE, email to [email protected], with a body:
unsubscribe ultramonkey-users [email protected]
where "[email protected]" is YOUR email address.