(RADIATOR) AuthBy LDAP2: Hangs for 10 minutes when LDAP Server down
r.helfenberger at comlight.ch
r.helfenberger at comlight.ch
Fri Jun 28 10:07:22 CDT 2002
Hello everybody
I found a timeout problem with Radiator when the LDAP server is down. The
Radiator is completely blocked for about 13 minutes instead of the
configured 10 seconds in the configuration file. This happens when one of
the OpenLDAP serves is completely down (say LDAP_HOST1)
Configuration:
Radiator: 2.18.3
Two OpenLDAP Servers.
Configuration file:
<AuthBy LDAP2>
NoDefault
Host LDAP_HOST1
AuthDN xxxx
AuthPassword xxxx
BaseDN xxxx
UsernameAttr cn
PasswordAttr userPassword
Timeout 10
FailureBackoffTime 120
</AuthBy>
<AuthBy LDAP2>
NoDefault
Host LDAP_HOST2
AuthDN xxxx
AuthPassword xxxx
BaseDN xxxx
UsernameAttr cn
PasswordAttr userPassword
Timeout 10
FailureBackoffTime 120
</AuthBy>
What I see in the logfile:
Fri Jun 28 15:06:18 2002: DEBUG: Handling with Radius::AuthLDAP2:
Fri Jun 28 15:06:18 2002: INFO: Connecting to 192.168.190.24, port 389
Fri Jun 28 15:19:27 2002: ERR: Could not open LDAP connection to
192.168.190.24, port 389. Backing off for 120 seconds.
Fri Jun 28 15:19:27 2002: DEBUG: Handling with Radius::AuthLDAP2:
Fri Jun 28 15:19:27 2002: INFO: Connecting to 192.168.190.236, port 389
Fri Jun 28 15:19:27 2002: INFO: Attempting to bind with cn=radpay,
ou=Users, ou=Administration, ou=Sunrise, o=Sunrise, c=ch, radpay (ser
The problem: between line 2 und 3 there is a gap of 13 minutes where the
radiator was completely blocked.
Did anybody else encounter such a problem? Is there a solution?
Thank you for your help
Best regards
Ralph Helfenberger
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.open.com.au/pipermail/radiator/attachments/20020628/ee25c91e/attachment.html>
More information about the radiator
mailing list