I have the proxy section commented out in radiusd.conf, occurs both ways...
I do see something in the radius.log... when the CPU pegs out (and the server stops handling requests), I see this occur in the radius.log: Tue May 23 16:37:03 2006 : Info: rlm_sql (sql): There are no DB handles to use! skipped 0, tried to connect 0 Tue May 23 16:37:03 2006 : Info: rlm_sql_mysql: Starting connect to MySQL server for #0 Before that, I have some other misc errors, but nothing that I'm too worried about. -A -----Original Message----- From: [EMAIL PROTECTED] g [mailto:[EMAIL PROTECTED] adius.org] On Behalf Of Alan DeKok Sent: Tuesday, May 23, 2006 10:49 AM To: FreeRadius users mailing list Subject: Re: FreeRadius 1.1.1 and run-away CPU "Aaron Burruss" <[EMAIL PROTECTED]> wrote: > I'm running freeraduius 1.1.1 on a FreeBSD 5.4 server. I'm using the > mysql module (mysql 4.0.24), and everything seems to be working fine... > but at random times, the CPU becomes pegged by the radiusd process, and > it will stop accepting requests from my clients. This does not (seem > to) occur when I run in debug (-X), but I obviously don't want to run it > in that mode for the long term. I've looked around, and can't seem to > find anything that might be causing this to happen. Are you proxying requests? If so, try the patch from bug #331. Alan DeKok. - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
