(RADIATOR) Radiator 3.9 halting after LDAP error
Vangelis Kyriakakis
vkyriak at forthnet.gr
Mon Oct 11 02:04:20 CDT 2004
Hello,
Our Radiator Server (3.7.1) has the same behavior on a "ldap search
failed with error LDAP_OPERATIONS_ERROR", but we use the restartwrapper
so it is just restarted without any other problems. We use
perl-ldap-0.29, but it had happened with previous versions of perl-ldap too.
Regards
Vangelis
Mike McCauley wrote:
>Hello Josh,
>
>
>On Saturday 09 October 2004 02:29, Ward, Josh wrote:
>
>
>>Hello,
>>
>>I am having a problem with Radiator 3.9 on Redhat EL3 with the radius
>>server dying after an LDAP error. I saw a thread in the archives about
>>this in August, but no resolution posted. As you can see from the logs,
>>after getting this error, the server just halts. You can also see where
>>I restarted the server after ~20 minutes of downtime.
>>
>>
>
>Are you using the latest 3.9 patches?
>How often does it happen?
>Did you get any error message printed on stdout when it stopped?
>
>Cheers.
>
>
>
>
>>I am seeing this error (at log-level4):
>>Thu Oct 7 19:58:59 2004: DEBUG: Handling with Radius::AuthLDAP2:
>>PMS_LDAP_WCC
>>Thu Oct 7 19:58:59 2004: ERR: ldap search failed with error
>>LDAP_OPERATIONS_ERROR.
>>Thu Oct 7 19:58:59 2004: ERR: Disconnecting from LDAP server (server
>>132.241.82.11:389).
>>Thu Oct 7 20:17:18 2004: DEBUG: Reading users file /etc/radius/isdn
>>Thu Oct 7 20:17:18 2004: DEBUG: Reading users file
>>/etc/radius/users.pms
>>Thu Oct 7 20:17:18 2004: DEBUG: Reading users file
>>/etc/radius/users.fsms
>>Thu Oct 7 20:17:19 2004: DEBUG: Reading users file
>>/etc/radius/users.pppoe
>>Thu Oct 7 20:17:19 2004: DEBUG: Reading users file /etc/radius/users
>>Thu Oct 7 20:17:19 2004: DEBUG: Finished reading configuration file
>>'/etc/radiator/radius.cfg'
>>Thu Oct 7 20:17:19 2004: DEBUG: Reading dictionary file
>>'/etc/radius/dictionary'
>>Thu Oct 7 20:17:19 2004: DEBUG: Creating authentication port
>>0.0.0.0:1645
>>Thu Oct 7 20:17:19 2004: DEBUG: Creating accounting port 0.0.0.0:1646
>>Thu Oct 7 20:17:19 2004: NOTICE: Server started: Radiator 3.9 on zapp
>>
>>Here is the config for that handler:
>><Handler Called-Station-Id = "898XXXX", Realm=cns> #PMS_WCC
>> RewriteUsername s/^([^@]+).*/$1/
>> RewriteUsername tr/A-Z/a-z/
>> RewriteUsername s/\s+//g
>> SessionDatabase PMS-SessionCheck
>>
>> AuthByPolicy ContinueUntilReject
>> <AuthBy LDAP2>
>> DefaultSimultaneousUse 1
>> Identifier PMS_LDAP_WCC
>> FailureBackoffTime 30
>> #Host 132.241.82.11
>> Host 132.241.82.11
>>
>> AuthDN uid=XXXXXXXXXX
>> AuthPassword XXXXXXXXXX
>>
>> BaseDN ou=XXXXXXXXXXXXX
>>
>> UsernameAttr uid
>> PasswordAttr userpassword
>>
>> AuthAttrDef nop02, X-User-MST, request
>> AuthAttrDef uid, Service-Type, request
>>
>> PostSearchHook sub {\
>> if ($_[4]->get_value('nop02') & 1) {\
>> &main::log($main::LOG_DEBUG,"PMS(6500): got correct
>>service for client");\
>> &main::log($main::LOG_DEBUG,"AUTHDEBUG\: Got for
>>$_[1]");\
>> }\
>> else {\
>> &main::log($main::LOG_DEBUG,"PMS(6500): got no
>>service for client");\
>> &main::log($main::LOG_DEBUG,"AUTHDEBUG\: Got for
>>$_[1]");\
>> $_[3]->get_check->add_attr('X-User-MST', "Denied: No
>>Wildcat Dialup Access"); \
>> }\
>> }
>> </AuthBy>#END PMS_LDAP_WCC
>></Handler>
>>
>>
>>Any ideas why the server is halting with this error? It seems to me
>>that it should simply reconnect if it experiences and LDAP issue and
>>continue operating.
>>
>>-Josh
>>Network Operations
>>California State University, Chico
>>
>>--
>>Archive at http://www.open.com.au/archives/radiator/
>>Announcements on radiator-announce at open.com.au
>>To unsubscribe, email 'majordomo at open.com.au' with
>>'unsubscribe radiator' in the body of the message.
>>
>>
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.open.com.au/pipermail/radiator/attachments/20041011/5cd8c2d9/attachment.html>
More information about the radiator
mailing list