Hi, > unfortunately , radius wend down again. > The log is not very precise: > > Feb 20 14:22:44 radius radiusd[12700]: WARNING: Child is hung for request 988 > in component module . > Feb 20 14:22:44 radius radiusd[12700]: WARNING: Child is hung for request 990 > in component module . > Feb 20 14:22:44 radius radiusd[12700]: WARNING: Child is hung for request 992 > in component module . > Feb 20 14:22:44 radius radiusd[12700]: WARNING: Child is hung for request 994 > in component module . > Feb 20 14:22:45 radius radiusd[12700]: WARNING: Child is hung for request > 1025 in component module .
lots of records = live accounting has reached a block > i didn't comment out the "radutmp" line, because i need to have a n accounting yes - but HOW do you DO accounting? you say you need to have radutmp - but how do you use that file - are you sure you use it and not eg SQL accounting? if you have got to a stage where the accounting requirements cannot be met in real time, then you need to look at migrating to using eg detail file 'just out of live time' accounting - or moving the accounting off the live auth server and using eg decoupled accounting, or proxy to home server buffered accounting.. or even move to a more efficient method such as buffered-sql . however, the issue may also be caused by some other local issue - such as network contention (if you proxy requests), resource starvation (host is doing more than just the radiusd and doesnt have enough resource - be that CPU or disk access - to do its job), or, if virtualised, the host may not have all it needs because some other virtual host is stealing the cycles now ..or you've finally encountered a bug. does this happen with latest release (2.1.12)? alan - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
