Greetings,
I started this email few months back but due to other projects that took
priority, I had to put this troubleshooting on hold. To recap:
1. Our radius servers are having some memory issue where its memory usage would
increase by 1% every 30 - 45 minutes until it crashes and restarts.
Roy Kartadinata wrote:
1. Our radius servers are having some memory issue where its memory
usage would increase by 1% every 30 - 45 minutes until it crashes and
restarts.
2. I created a script that will temporarily fix the issue by monitoring
its memory usage and restart after it reaches
Roy Kartadinata wrote:
Do you need any other information from me to help you with finding the
leaks?
Ideally, run it under valgrind, with options where it shows and tracks
memory usage:
$ script leak.txt
$ valgrind --tool=memcheck --leak-check=full radiusd -f
$ exit
Let it run for a few
Alan DeKok wrote:
Roy Kartadinata wrote:
Do you need any other information from me to help you with finding
the leaks?
Ideally, run it under valgrind, with options where it shows and
tracks memory usage:
$ script leak.txt
$ valgrind --tool=memcheck --leak-check=full radiusd -f $ exit
Roy Kartadinata wrote:
Alan DeKok wrote:
Will radius still be operational (taking authentication request) while
we run it under valgrind?
Yes.
Alan DeKok.
-
List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
Hi,
Will radius still be operational (taking authentication request) while
we run it under valgrind?
yes - but slower - so make sure you've got the horsepower...any time
critical things might not operate as usual.
alan
-
List info/subscribe/unsubscribe? See
Alan Buxey wrote:
Hi,
Will radius still be operational (taking authentication request)
while we run it under valgrind?
yes - but slower - so make sure you've got the horsepower...any time
critical things might not operate as usual.
Cool, I'll just do it during our slowest hour then.
Alan DeKok wrote:
Roy Kartadinata wrote:
An update on this issue, I was finally able to split the detail file
log into hourly by adding another entry to modules/detail.log file.
So far the memory usage is still increasing but in a much slower
rate.
That helps narrow it down a bit. But
Roy Kartadinata wrote:
An update on this issue, I was finally able to split the detail file log
into hourly by adding another entry to modules/detail.log file. So far
the memory usage is still increasing but in a much slower rate.
That helps narrow it down a bit. But it's still a bit
An update on this issue, I was finally able to split the detail file log
into hourly by adding another entry to modules/detail.log file. So far
the memory usage is still increasing but in a much slower rate.
Marinko Tarlac wrote:
Maybe detail file is to large ?
I had a similar problem when
Hi
Well I don't use is.. Only in case I need to debug something... I have a
small problem with triggering AccountingOff query (I don't know what
causes this) which closes all opened sessions in database... Now I found
a work around for this...
You can try to increase Interim-update
Marinko Tarlac wrote:
Hi
Well I don't use is.. Only in case I need to debug something... I
have a small problem with triggering AccountingOff query (I don't
know what causes this) which closes all opened sessions in
database... Now I found a work around for this...
You can try to
Alan DeKok wrote:
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
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
Maybe detail file is to large ?
I had a similar problem when server goes off because of this...
Alan DeKok wrote:
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
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
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
Hello,
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
[mailto:freeradius-users-bounces+rkartadinata=pocket@lists.freeradiu
s.org] On Behalf Of Marinko Tarlac
Sent: Thursday, July 23, 2009 2:17 PM
To: FreeRadius users mailing list
Subject: Re: Freeradius and memory usage
Is there anything strange in radius log files and are you sure that
freeradius
19 matches
Mail list logo
