Graeme Hinchliffe <[EMAIL PROTECTED]> wrote: > OK, done that and have found: > > Wed Sep 24 16:23:58 2003 : Error: WARNING: Unresponsive child (id 6151) for request > 426
Yup. The thread stops processing the request somewhere. > until: > > Wed Sep 24 16:27:18 2003 : Error: Dropping conflicting packet from client gauss:1812 > - ID: 150 due to unfinished request 426 The NAS is re-trying the request... > I have tried reading back through the logs but cannot figure out > what request 426 is, nor which log lines relate to it. The incoming packet should be just a few lines before the 'thread 6 assigned request 426' message. > 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. > Does this help point out what is wrong? Not really... > Could it be related to the NAS model? I don't see why. Alan DeKok. - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
