Very critical: Memory leak in freeradius-1.1.6

Phil Mayers p.mayers at imperial.ac.uk
Sun May 20 14:00:18 CEST 2007


nikitha george wrote:
> Hi Martin,
>  
> Thanks for your reply.
> The memory usage of radiusd in our system went from 6687KB to 160MB 
> which is 50.1% of memory of our system and radiusd got re-started.
>  
> I had run the Valgrind to see the resource leak. Definitely lost memory 
> was 380 Bytes but still reachable are more. I think this is the one 
> which is leaking memory. I dont have access to the log files today, i 
> will post it by tomorrow for your reference.

You seem pretty sure you've got a memory leak. As Alan has said, we're 
pretty sure there are no major leaks in the server core, so logically 
it's either your system libraries or an infrequently-used bit of the server.

We need to know/see the following:

  * What OS are you on? Versions of the OS, kernel, major libraries 
(libc, threading) and a rough idea of how many clients and requests/sec 
you're getting
  * your radiusd.conf
  * a debug output of a *few* (not thousands!) of requests from your 
server - run "radiusd -X"

A couple of wild guesses: Are you using PAM? Are you using rlm_perl or 
rlm_python? Are you using a database that's a bit too slow?

I've you've actually run the "valgrind --memcheck --leak-check=yes" then 
let's take a look at that too.



More information about the Freeradius-Users mailing list