Hello,

We are using FreeRadius version 0.5 with LDAP (Windows 2000 AD) and have
found that the server will stop responding or crash if the connection
with the LDAP servers is broken. Eg: if the network cable is unplugged
and then replugged in for the radius server, it will log an error
"Error: rlm_ldap: ldap_search() failed: Can't contact LDAP server", if
it doen't crash with no error or "Info: MASTER: exit., Error: CHILD:
exit on signal (11)" then it is non resposive until you restart
FreeRadius.

Below is the ldap module from our radiusd.conf

ldap {
                server = "ldap.xxxx.xxxx.xxxx ldap1.xxxx.xxxx.xxxx
ldap2.xxxx.xxxx.xxxx"
                basedn = "ou=People,ou=Internet Service
Provider,ou=Globe.Net Communications Ltd,dc=xxxx,dc=xxxx,dc=xxxx"
                #filter = "(uid=%u)" # This is for User Name, we are
using realms and require Stripped User name.
                filter = "(uid=%U)"
                start_tls = no
                access_attr = "radiusNPAllowDialin"
                # default_profile = "cn=radprofile,ou=dialup,o=My
Org,c=UA"
                # profile_attribute = "radiusProfileDn"
                dictionary_mapping = ${raddbdir}/ldap.attrmap
                # ldap_cache_timeout = 120
                # ldap_cache_size = 0
                ldap_connections_number = 15
                # groupname_attribute = cn
                # groupmembership_filter =
"(|(&(objectClass=GroupOfNames)(member=%{Ldap-UserDn}))(&(objectClass=Gr
oupOfUniqueNames$
                timeout = 4
                timelimit = 3
                net_timeout = 1
}

We have ldap.xxxx.xxxx.xxxx setup as a DNS roundrobin to
ldap1.xxxx.xxxx.xxxx and ldap2.xxxx.xxxx.xxxx, could this cause any
problems?


This is a bit of one of the log files:

WORKING AT THIS POINT!!
Mon Jul  1 09:49:11 2002 : Info: Sending duplicate authentication reply
to client ak-tnt1:7017 - ID: 164
on Jul  1 11:53:27 2002 : Error: rlm_ldap: ldap_search() failed: Can't
contact LDAP server
Mon Jul  1 11:54:12 2002 : Error: rlm_ldap: ldap_search() failed:
Invalid syntax
Mon Jul  1 12:10:13 2002 : Error: rlm_ldap: ldap_search() failed: Can't
contact LDAP server
Mon Jul  1 12:56:37 2002 : Error: rlm_ldap: ldap_search() failed: Can't
contact LDAP server
Mon Jul  1 13:51:54 2002 : Error: rlm_ldap: ldap_search() failed: Can't
contact LDAP server
Mon Jul  1 14:14:41 2002 : Error: rlm_ldap: ldap_search() failed: Can't
contact LDAP server
Mon Jul  1 14:47:46 2002 : Error: rlm_ldap: ldap_search() failed:
Invalid syntax
Mon Jul  1 14:48:40 2002 : Error: rlm_ldap: ldap_search() failed:
Invalid syntax
Mon Jul  1 14:52:22 2002 : Error: rlm_ldap: ldap_search() failed: Bad
search filter
Mon Jul  1 15:00:10 2002 : Error: rlm_ldap: ldap_search() failed:
Invalid syntax
Mon Jul  1 15:00:58 2002 : Error: rlm_ldap: ldap_search() failed:
Invalid syntax
Mon Jul  1 15:12:36 2002 : Error: rlm_ldap: ldap_search() failed:
Invalid syntax
Mon Jul  1 15:12:56 2002 : Error: rlm_ldap: ldap_search() failed:
Invalid syntax
Mon Jul  1 15:36:17 2002 : Error: rlm_ldap: ldap_search() failed: Can't
contact LDAP server
Mon Jul  1 16:09:49 2002 : Error: rlm_ldap: ldap_search() failed: Can't
contact LDAP server
Mon Jul  1 16:31:46 2002 : Error: rlm_ldap: ldap_search() failed: Can't
contact LDAP server
FREERADIUS HAS NOW CRASHED!!!

Is this a bug?, if so what can I do about it?

Is their anything I can do to stop any of the above happening?

Any help would be great, thanks.

Allister P Maguire

-
List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html

Reply via email to