I did some more debugging and I always seem to get a segfault at the same place. Is there something I should be looking at on the LDAP backend?
[files] users: Matched entry DEFAULT at line 214 ++[files] returns ok [pap] Normalizing SSHA1-Password from base64 encoding [pap] WARNING: Auth-Type already set. Not setting to PAP ++[pap] returns noop Found Auth-Type = PAP # Executing group from file /etc/raddb/sites-enabled/virtual.amtelecom.net +- entering group PAP {...} [pap] login attempt with password "45270" [pap] Using SSHA encryption. [pap] Normalizing SSHA1-Password from base64 encoding Segmentation fault ++[files] returns ok [pap] Normalizing SSHA1-Password from base64 encoding [pap] WARNING: Auth-Type already set. Not setting to PAP ++[pap] returns noop Found Auth-Type = PAP # Executing group from file /etc/raddb/sites-enabled/virtual.amtelecom.net +- entering group PAP {...} [pap] login attempt with password "bradly" [pap] Using SSHA encryption. [pap] Normalizing SSHA1-Password from base64 encoding Segmentation fault Thanks, Chris Chris Taylor System Administrator Network Operations Eastlink chris.tay...@corp.eastlink.ca T: 519.773.1287 -----Original Message----- From: freeradius-users-bounces+chris.taylor=corp.eastlink...@lists.freeradius.org [mailto:freeradius-users-bounces+chris.taylor=corp.eastlink...@lists.freeradius.org] On Behalf Of Chris Taylor Sent: Friday, April 12, 2013 4:31 PM To: FreeRadius users mailing list Subject: RE: segfault error Yeah this is the only version of freeradius on the box the other was an rpm version that was removed before I compiled this one. -----Original Message----- From: freeradius-users-bounces+chris.taylor=corp.eastlink...@lists.freeradius.org [mailto:freeradius-users-bounces+chris.taylor=corp.eastlink...@lists.freeradius.org] On Behalf Of Alan DeKok Sent: Friday, April 12, 2013 3:45 PM To: FreeRadius users mailing list Subject: Re: segfault error Chris Taylor wrote: > Ok I have upgraded to a compiled version of freeradius 2.2.0, and I was able > to see the same result. It crashed after a few minutes with the error below. > > on-radius01 kernel: radiusd[10038]: segfault at 00007ffff3d87000 rip > 0000003c6c07b5bb rsp 00007ffff3d83c08 error 4 Check that you're really running v2.2.0. Sometimes scripts point to old installations. > I turned on core dumps to see if I could get any more details out of it, but > I could not make it crash after that. Did you follow the instructions in doc/bugs? That says how to find the bug. > Any ideas as to what this could be I can post my -X output but all it says at > the bottom when it stops working is segfault. doc/bugs has detailed instructions for just such an occasion. Alan DeKok. - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html