LVS
lvs-users
Google
 
Web LinuxVirtualServer.org

Re: [lvs-users] ldirectord feature patch - add abililitytosignalsystem m

To: "Simon Horman" <horms@xxxxxxxxxxxx>
Subject: Re: [lvs-users] ldirectord feature patch - add abililitytosignalsystem maintenance
Cc: "LinuxVirtualServer.org users mailing list." <lvs-users@xxxxxxxxxxxxxxxxxxxxxx>
From: "Robinson, Eric" <eric.robinson@xxxxxxxxx>
Date: Wed, 20 May 2009 10:54:39 -0700
Hi Horms,

I'll provide whatever information you wish. My configuration file is
quite long. It can be viewed here:

http://www.psmnv.com/downloads/ldirectord.cf

And as you can see from the following ldirectord.log snippet, servers
that go quiescent are subsequently being restored with weight 0. Note
that these servers had weights of 15, 30, or 45 before going quiescent.

[Tue May 19 08:29:32 2009|ldirectord.cf|28041] Quiescent real server:
192.168.15.84:3389 (192.168.5.100:3389) (Weight set to 0)
[Tue May 19 08:29:32 2009|ldirectord.cf|28041] emailalert: Quiescent
real server: 192.168.15.84:3389 (192.168.5.100:3389) (Weight set to 0)
[Tue May 19 08:30:00 2009|ldirectord.cf|28041] Restored real server:
192.168.15.84:3389 (192.168.5.100:3389) (Weight set to 1)
[Tue May 19 08:30:00 2009|ldirectord.cf|28041] emailalert: Restored real
server: 192.168.15.84:3389 (192.168.5.100:3389) (Weight set to 1)
[Tue May 19 09:34:56 2009|ldirectord.cf|28041] Quiescent real server:
192.168.15.84:3389 (192.168.5.100:3389) (Weight set to 0)
[Tue May 19 09:34:56 2009|ldirectord.cf|28041] emailalert: Quiescent
real server: 192.168.15.84:3389 (192.168.5.100:3389) (Weight set to 0)
[Tue May 19 09:35:21 2009|ldirectord.cf|28041] Restored real server:
192.168.15.84:3389 (192.168.5.100:3389) (Weight set to 1)
[Tue May 19 09:35:21 2009|ldirectord.cf|28041] emailalert: Restored real
server: 192.168.15.84:3389 (192.168.5.100:3389) (Weight set to 1)
[Tue May 19 12:02:24 2009|ldirectord.cf|28041] Quiescent real server:
192.168.10.35:3389 (192.168.5.100:3389) (Weight set to 0)
[Tue May 19 12:02:24 2009|ldirectord.cf|28041] emailalert: Quiescent
real server: 192.168.10.35:3389 (192.168.5.100:3389) (Weight set to 0)
[Tue May 19 12:02:31 2009|ldirectord.cf|28041] Restored real server:
192.168.10.35:3389 (192.168.5.100:3389) (Weight set to 1)
[Tue May 19 12:02:31 2009|ldirectord.cf|28041] emailalert: Restored real
server: 192.168.10.35:3389 (192.168.5.100:3389) (Weight set to 1)
[Tue May 19 12:28:23 2009|ldirectord.cf|28041] Quiescent real server:
192.168.15.84:3389 (192.168.5.100:3389) (Weight set to 0)
[Tue May 19 12:28:23 2009|ldirectord.cf|28041] emailalert: Quiescent
real server: 192.168.15.84:3389 (192.168.5.100:3389) (Weight set to 0)
[Tue May 19 12:29:07 2009|ldirectord.cf|28041] Restored real server:
192.168.15.84:3389 (192.168.5.100:3389) (Weight set to 1)
[Tue May 19 12:29:07 2009|ldirectord.cf|28041] emailalert: Restored real
server: 192.168.15.84:3389 (192.168.5.100:3389) (Weight set to 1)


--
Eric Robinson



-----Original Message-----
From: Simon Horman [mailto:horms@xxxxxxxxxxxx] 
Sent: Tuesday, May 19, 2009 4:18 AM
To: Robinson, Eric
Cc: LinuxVirtualServer.org users mailing list.
Subject: Re: [lvs-users] ldirectord feature patch - add
abililitytosignalsystem maintenance

On Sat, May 16, 2009 at 06:59:55AM -0700, Robinson, Eric wrote:
> I can verify that it is behaving as I described on my Centos 5.2 
> system running heartbeat-ldirectord-2.1.3-3.el5.centos and it did the 
> same thing with an earlier verson of ldirectord, thought I don't 
> recall the version number any more.

Hi Eric,

Unfortunately I am not able to reproduce that problem using the same
heartbeat-ldirectord package on centos.

To clarify, I ran ldirectord and observed:

IP Virtual Server version 1.2.1 (size=4096) Prot LocalAddress:Port
Scheduler Flags
  -> RemoteAddress:Port           Forward Weight ActiveConn InActConn
  TCP  192.168.6.240:80 rr
    -> 172.17.60.197:80             Route   20     0          0

I then shut down apache and observed:

IP Virtual Server version 1.2.1 (size=4096) Prot LocalAddress:Port
Scheduler Flags
  -> RemoteAddress:Port           Forward Weight ActiveConn InActConn
  TCP  192.168.6.240:80 rr
    -> 172.17.60.197:80             Route   20     0          0

And then I started up apache again and observed:

IP Virtual Server version 1.2.1 (size=4096) Prot LocalAddress:Port
Scheduler Flags
  -> RemoteAddress:Port           Forward Weight ActiveConn InActConn
  TCP  192.168.6.240:80 rr
    -> 172.17.60.197:80             Route   20     0          0

Perhaps I am misunderstanding the problem?
If not, would it be possible for you to post your configuration file,
perhaps you have something in there that triggers a bug.



Disclaimer - May 20, 2009 
This email and any files transmitted with it are confidential and intended 
solely for Simon Horman,LinuxVirtualServer.org users mailing list.. If you are 
not the named addressee you should not disseminate, distribute, copy or alter 
this email. Any views or opinions presented in this email are solely those of 
the author and might not represent those of Physician Select Management and 
Physician's Managed Care. Warning: Although Physician Select Management and 
Physician's Managed Care have taken reasonable precautions to ensure no viruses 
are present in this email, the companies cannot accept responsibility for any 
loss or damage arising from the use of this email or attachments. 
This disclaimer was added by Policy Patrol: http://www.policypatrol.com/

_______________________________________________
Please read the documentation before posting - it's available at:
http://www.linuxvirtualserver.org/

LinuxVirtualServer.org mailing list - lvs-users@xxxxxxxxxxxxxxxxxxxxxx
Send requests to lvs-users-request@xxxxxxxxxxxxxxxxxxxxxx
or go to http://lists.graemef.net/mailman/listinfo/lvs-users

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