[Linux-ha-dev] ldirectord not removing ldap server from list

[Horms]

On Fri, Jul 27, 2007 at 01:50:28PM -0600, Michael Bristow wrote:
> I am running ldirectord version 1.186-ha-2.0.8 on SLES10 SP1.
>  
> 192.168.20.15 (sles101) = RealServer1
> 192.168.20.16 (sles102) = RealServer2
> 192.168.20.20 = vip
>  
> As you'll see from my ldirectord.cf file below, I am configured to load balance two real servers for LDAP. When I stop LDAP, on RealServer2, it should remove that server from the load balancer, and continue directing LDAP traffic to RealServer1. 
>  
> When I launch "ldirectord -d start"and watch the debug....  I stop LDAP on RealServer2, and only see ipvsadm remove RealServer2 on port 636. No removal is done for port 389. As a result, when I look at "ipvsadm", it shows that 636 is gone for RealServer2, and 389 still exists for RealServer2.
>  
> When I enable LDAP on RealServer2, I see it add 636 back, and also try to add 389 back.
>  
> When RealServer2 is down, LDAP calls to 636 get redirected to RealServer1 perfectly. Port 389, of course, fails 50% of the time (Round Robin) because it still believes RealServer2 on 389 is up. 

Hi Michael,

thanks for reporting this problem. Could you see if the latest version
of ldirectord resolves this problem. There is a snapshot available at

http://www.vergenet.net/linux/ldirectord/download/ldirectord.2007-05-01.e022c4b33b0e

Unless there is a problem with the paths in that file, you should
be able to just execute it from the command line to see if it
behaves any better. If not, please let me know.

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