Alan DeKok wrote: > [EMAIL PROTECTED] (Rainer Clasen) wrote: > > Mitchell, Michael wrote: > > > I'm currently testing freeradius-snapshot-20020114 (configured as a proxy > > > only) on Solaris 8 and running into a problem. > > > > I'm seeing similar crashes with my patched 2002-02-11 version on Solaris > > 7. > > Hmm... I'm starting to think that this may *not* be a thread > problem.
I've taken a look at the logs and there is a pattern: in both cases the only server for a realm was marked dead immediately before the crash. In both cases the Server seems to be marked dead eronously: Tue Feb 19 13:27:37 2002 : Auth: Sending request: [login@realm/password] (from NAS port 20113) proxy XX.YY.ZZ.AA ID 227 Tue Feb 19 13:27:37 2002 : Auth: Received reply: [login@realm/password] (from NAS port 20113) proxy XX.YY.ZZ.AA ID 227 Tue Feb 19 13:27:37 2002 : Auth: Login OK: [login@realm/password] (from NAS port 20113) Tue Feb 19 13:27:37 2002 : Proxy: timeout, rejecting: [login@realm/password] (from NAS port 20113) proxy XX.YY.ZZ.AA ID 228 Tue Feb 19 13:27:37 2002 : Proxy: server XX.YY.ZZ.AA for realm realm is dead The timed out request seems to be the initial accounting request - which is far younger than 8*5 seconds. We are currently using retry_delay = 5 retry_count = 8 According to the logfile there were no requests resend to the server being marked dead in both cases. > > simul_count = 0, simul_mpp = 0, finished = 1, options = 0 > ^^^^^^^^^^^^ > The request has been marked 'finished', so NOTHING should be using > any entries of the request. There should be NO threads or anything > else which is working with the request. > > > Hmm, why is request->proxy == NULL? > > Because the request is finished, and many fields can be cleaned up. Hmm, where is this cleanup done? I found only radius_free() that cleans ->proxy. But radius_free frees the complete request. Rainer -- KeyID=759975BD fingerprint=887A 4BE3 6AB7 EE3C 4AE0 B0E1 0556 E25A 7599 75BD - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
