> > There are a few references to Thread 6 which it is assigned to, but > > nothing in the log that lets me know what the request was or what > > happened to it... There appear to be dumps of requests in the log > > but I cannot see any relation to this info and a request number. > > That's a little difficult to track down. > > Grab the CVS snapshot tomorrow morning, and run it via: > > ./radiusd -xxxxxx > > You should see much more debug output. Look for 'modsingle', and > 'request ###' (whatever the number is). You should be able to track > down exactly which module is taking forever to respond.
I haven't needed to check the log dump yet as the problem hasn't duplicated with this new code. I guess whatever it was has been fixed at some point. One thing I did notice was that the eap module wouldn't compile from the CVS version of the code (I am not using it so was able to simply remove the module from the source), just thought I would let you know. I will keep my eye on this version of the code and see if the problem starts up again. so far it seems a lot happier. -- ----- Graeme Hinchliffe (BSc) Core Team Member Zen Internet (http://www.zen.co.uk) ICQ 3842605 (link) Direct: 0845 058 9074 Main : 0845 058 9000 Fax : 0845 058 9005 - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
