Re: Freeradius possible memory leak

2009-09-08 Thread Szymon Roczniak
On Fri, Sep 04, 2009 at 02:27:13PM +0200, Alan DeKok wrote: Can you re-build the rlm_sql module with debugging symbols? (-g, and DELETE any -O2 flags you find). That way, it will print out line numbers like the following: I can't make valgrind print file lines from modules for some reason.

Re: Freeradius possible memory leak

2009-09-08 Thread Alan DeKok
Szymon Roczniak wrote: The one that uses leaking memory returns Auth-Type : Accept from : ? What's that? authorize_check_query = SELECT 1,'notused','Auth-Type','Accept',':' FROM That's the issue. The operator is wrong. Use :=, not : It shouldn't leak memory, so that still needs to

Re: Freeradius possible memory leak

2009-09-08 Thread Alan DeKok
Szymon Roczniak wrote: It's odd, but it looks like it doesn't matter what operator is used in this place. In fact it still works even without one (I've just tested it with some random 'operators' and with the operator field set to ). Yes... I saw that, and just fixed it. There are some

Re: Freeradius possible memory leak

2009-09-08 Thread Szymon Roczniak
On Tue, Sep 08, 2009 at 01:59:05PM +0200, Alan DeKok wrote: Szymon Roczniak wrote: authorize_check_query = SELECT 1,'notused','Auth-Type','Accept',':' FROM That's the issue. The operator is wrong. Use :=, not : That's an error, the production configuration has ':=' in the operator

Re: Freeradius possible memory leak

2009-09-04 Thread Szymon Roczniak
On Thu, Sep 03, 2009 at 03:02:23PM +0200, Alan DeKok wrote: You should add -m to the radiusd command line, so that it will try to clean up as much memory as possible before exiting. Output with -m and some more debugging information: 34,944 bytes in 112 blocks are definitely lost in loss

Re: Freeradius possible memory leak

2009-09-04 Thread Alan DeKok
Szymon Roczniak wrote: Output with -m and some more debugging information: OK, that helps... 34,944 bytes in 112 blocks are definitely lost in loss record 38 of 44 at 0x4C20809: malloc (vg_replace_malloc.c:149) by 0x4E38DCE: pairalloc (in

Freeradius possible memory leak

2009-09-03 Thread Szymon Roczniak
Hi, This could be related to a similar problem reported a couple of weeks ago. We have a FreeRADIUS 2.1.6 installation running on 64bit CentOS 5.3. The radiusd process is allocating more and more memory with time (around 0.5GB a day). There are only around 5-6 requests/s and other than chewing

Re: Freeradius possible memory leak

2009-09-03 Thread Alan DeKok
Szymon Roczniak wrote: I've followed the advise from the previous thread and run radiusd under valgrind for around 10-15 minutes with some generated traffic and the output is: valgrind --tool=memcheck --leak-check=full /usr/sbin/radiusd -f You should add -m to the radiusd command line, so