Alan DeKok wrote: > Roy Kartadinata wrote: >> Our radius server is currently having some memory issue where its >> memory usage would increase by 1% every 30-45 minutes. Eventually the >> server will crash and restart because of out of memory. We've been >> using freeradius for a couple of years and this just started on >> Thursday so I upgraded our radius to the latest 2.1.6 from 2.1.5 but >> the problem still there. Has anyone ever experiencing this issue >> before? > > The only thing like that I'm aware of is with the detail file, > which was fixed in 2.1.6. > > Look at the logs to see what the server is doing. What errors is > it producing? >
I didn't see any error on error log, it looks clean. But this is what the log looks like when it started to run out of memory the other night: Wed Jul 22 22:03:42 2009 : Error: Rejecting request 16183416 due to lack of any response from home server xxx.xxx.xxx.xxx port 1813 Wed Jul 22 22:03:42 2009 : Error: Rejecting request 16183418 due to lack of any response from home server xxx.xxx.xxx.xxx port 1813 Wed Jul 22 22:03:42 2009 : Error: Rejecting request 16183420 due to lack of any response from home server xxx.xxx.xxx.xxx port 1813 Wed Jul 22 22:03:42 2009 : Error: WARNING: Unresponsive child for request 16183422, in module detail component pre-proxy Wed Jul 22 22:03:42 2009 : Error: Rejecting request 16183423 due to lack of any response from home server xxx.xxx.xxx.xxx port 1813 Wed Jul 22 22:03:42 2009 : Error: WARNING: Unresponsive child for request 16183425, in module component pre-proxy Wed Jul 22 22:03:42 2009 : Error: WARNING: Unresponsive child for request 16183427, in module component pre-proxy Wed Jul 22 22:03:42 2009 : Error: WARNING: Unresponsive child for request 16183428, in module component pre-proxy Wed Jul 22 22:03:42 2009 : Error: WARNING: Unresponsive child for request 16183430, in module component pre-proxy Wed Jul 22 22:03:42 2009 : Error: WARNING: Unresponsive child for request 16183432, in module component pre-proxy Wed Jul 22 22:03:42 2009 : Error: WARNING: Unresponsive child for request 16183434, in module component pre-proxy Wed Jul 22 22:03:43 2009 : Error: WARNING: Unresponsive child for request 16183436, in module component pre-proxy Wed Jul 22 22:03:43 2009 : Error: WARNING: Unresponsive child for request 16183438, in module component pre-proxy Wed Jul 22 22:03:43 2009 : Error: WARNING: Unresponsive child for request 16183440, in module component pre-proxy Wed Jul 22 22:03:43 2009 : Error: WARNING: Unresponsive child for request 16183441, in module component pre-proxy Wed Jul 22 22:03:43 2009 : Error: WARNING: Unresponsive child for request 16183443, in module component pre-proxy Wed Jul 22 22:03:43 2009 : Error: WARNING: Unresponsive child for request 16183445, in module component pre-proxy Wed Jul 22 22:03:43 2009 : Error: WARNING: Unresponsive child for request 16183447, in module component pre-proxy And radius eventually died few seconds later. During all these, the memory usage was at around 75% but authentication which we don't proxy continued to work. My current band aid was a simple script that checks its memory usage regularly and restart after it passes certain percentage, not a good solution but this will do for now. Cheers, Roy Kartadinata - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html