Marco Steinacher <[EMAIL PROTECTED]> wrote: > >From time to time I get the following error in the radiusd logfile: > > Mon Apr 22 20:17:50 2002 : Error: WARNING: Unresponsive child (id 2051) for > request 338 > > After that warning there is a radiusd process that uses up to 99% of the cpu. > Only restarting the radiusd service cleans that.
As always, my response is "find out why the child threads are blocked." > The system is a production system and should not crash. The max_request_time > limit is set to 60 seconds. Two NAS use this radius server; a cisco and a > portmaster that are connected via fast ethernet. There are not many requests > so that I don't think that it could be a performance problem. The problem isn't the NAS. It's probably the back-end databases that the RADIUS server is talking to. Think about it for a second. It's taking SIXTY SECONDS to authenticate a user? What the heck is going on in your system? > BTW: We're talking about radiusd-0.5 Try removing modules that you don't use from 'radiusd.conf'. One report was that rlm_counter caused slowdowns. Alan DeKok. - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
