nikitha george wrote:
On 5/23/07, nikitha george [EMAIL PROTECTED] wrote:
Please find the valgrind output below. It shows so much memory is still
reachable.
That's because the server doesn't clean up memory on exit. Run it
with the -m flag on the command line, and it will try to clean up
On 5/23/07, nikitha george [EMAIL PROTECTED] wrote:
Please find the valgrind output below. It shows so much memory is still
reachable.
I guess we are not cleaning up the all the expired cached session at
regular interval.
==21844== 7,456 bytes in 29 blocks are still reachable in loss record
nikitha george wrote:
On 5/20/07, Alan DeKok [EMAIL PROTECTED] wrote:
If valgrind doesn't say that the memory is lost, then the memory is
very likely still being used. i.e. It's likely needed for something.
something..?
Did you read my earlier explanations?
Why do radiusd need to hold
Do you have any idea what kind of malloc/free implementation on our system
will work out in this scenario?
Thanks,
Nikitha
On 5/19/07, Alan DeKok [EMAIL PROTECTED] wrote:
nikitha george wrote:
So why is it happening in my case then? I can see all the requests gets
cleaned up ( log message
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
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
nikitha george wrote:
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.
160Mb does sound like a lot.
I had run the Valgrind to see the resource leak. Definitely lost memory
was 380 Bytes but still
On 5/20/07, Alan DeKok [EMAIL PROTECTED] wrote:
If valgrind doesn't say that the memory is lost, then the memory is
very likely still being used. i.e. It's likely needed for something.
something..?
Why do radiusd need to hold the memory even after cleaning up the request?
Even after stopping
nikitha george wrote:
I am seeing a very serious memory leak issue with freeradius-1.1.6. The
memory usage of freeradius gone from 3386Byte to 64MB when i was trying
to connect 16 clients with roaming interval of 1 second. More
Access-Requests are coming and we keep saving those requests until
So why is it happening in my case then? I can see all the requests gets
cleaned up ( log message was put) but still so much memory is consumed by
radiusd.
You want me post the huge log file..? I badly need this fix now..
Configuration wise i am using the default configuration except users and
nikitha george wrote:
So why is it happening in my case then? I can see all the requests gets
cleaned up ( log message was put) but still so much memory is consumed
by radiusd.
When the server caches the requests, it uses memory to do that. When
it frees the requests, the memory does *not*
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
nikitha george wrote:
So why is it happening in my case then? I can see all the requests gets
cleaned up ( log message was put) but still so much memory is consumed
by radiusd.
Memory usage under Linux is a tricky thing.
It depends if you're
12 matches
Mail list logo
