Re: radius crash

Michael Griego Tue, 17 May 2005 16:41:18 -0700

What you're likely seeing is something that has already been fixed in the CVS snapshots. Previously, if one of the worker threads died, it could go into a segfault loop that would block the server and send the CPU to near 100%. That was fixed a while back in CVS. I'm not sure if it's included in 1.0.2 or not...

--Mike


Simon Allard wrote:

What versions are you guys running?

I am running 1.0.0-pre3 and have exactly the same problem. I am in the
process of upgrading to 1.0.2, but I am starting to wonder if that is going
to actually fix the problem.

What I see is the radius server is still running, but using a lot of CPU
(70-90%). It doesn't responds to any packets and the only way to kill it is
to kill -9 it. When I run it in debug mode it doesn't happen (typical!).

-----Original Message-----
From: [EMAIL PROTECTED] [mailto:freeradius-
[EMAIL PROTECTED] On Behalf Of Lucas Aimaretto
Sent: Saturday, 14 May 2005 3:21 a.m.
To: freeradius-users@lists.freeradius.org
Subject: RE: radius crash

you mean radiusd -X? Can this full debug information somehow be saved in a file instead of dirrectly on the console?

Edgars,

you can try 'radiusd -X > radius.log 2>&1 &'

with this you're a redirecting everything to radius.log.

please, let us know how did you do, because yesterday I had same
problem. Radius stoped working, but I could see the listening sockets
when 'netstat -putan' was executed. But, when I send to radius an
access-request with nt-radping ( app to test radius ) I had no answer
from it ... and it kind of worried me ...

Regards,

Lucas

--
No virus found in this outgoing message.
Checked by AVG Anti-Virus.
Version: 7.0.308 / Virus Database: 266.11.9 - Release Date: 12/05/2005

- List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html

Re: radius crash

Reply via email to