Freeradius and memory usage

[Alan DeKok]

Roy Kartadinata wrote:
> 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

  Ok... so it's blocked writing to the detail file.

> 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

  Module "" means "server core".

  That's weird...

  Is the detail file on an NFS mount?  It really shouldn't block writing
to the detail file unless the underlying file system goes away.

> 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.

  Because it's going crazy, and dying...

  Alan DeKok.