Alan, remember this glitch from a couple weeks ago? It's back! For the last week, I've been running the server -X to debug this latest auth problem that Mitry's patch fixed. Now, getting ready to drop this into production, I ran the server with no flags and again it authenticated the first user, then the CPU shot up to 99%. Running the server with -s (or -X which is also single threaded mode, I assume) works fine; that is I can authenticate users until the cows come home with no problems.
I'm going to dig around in my notes and see if I can find the gdb syntax I was given those two weeks ago. I'll run it again and post the output, I'm just letting you know that this is happening again. FYI: Kernel 2.4.9 SMP. HW: Dell PowerEdge 2450, Dual PIII-800, 768MB RAM, 5x32GB SCSI in RAID5, Dell Raid Controller 3/Si (rev2), EXT3 FS. > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED]] On Behalf Of > [EMAIL PROTECTED] > Sent: October 24, 2001 3:18 PM > To: [EMAIL PROTECTED] > Subject: Re: Problems starting radiusd > > > "Jason Lixfeld" <[EMAIL PROTECTED]> wrote: > > I've done a little digging but I can't find the answer. Radiusd > > starts fine in all circumstances. It will authenticate only one > > session, and then the CPU will spike to 100% and radtest > will just run > > through it's 10 cycles and timeout. > > Which version of the server are you running? The CVS > snapshot has a lot of bugs fixed over older versions. > > If you see a bug in an older version, you should upgrade to > the latest CVS snapshot, and see if the bug is there, too. > > > This happens when I run radiusd in any of the following ways: > > > > Radiusd > > Radiusd -f > > Uh, no. I like to be *exact* about what's going on. The > server does NOT use a capital 'R' for it's name. It's name > is "radiusd". > > It's a small point, but being exact helps. > > > It runs just fine when I run radiusd with the -s flag in any of the > > top examples. Any one know why this might be happening? > > With -s, it's running in single user mode. Without it, > it's using multiple threads or processes. > > I would STRONGLY recommend using threads. If you turn > those off, then there's no telling what the server will do. > > > FYI: If I run -fxx, I get no debugging information from > the server at > > all, so unfortunately it's not going to be any help :( > > Then something else strange is going on. When run via > 'radiusd -X', (or -xx', the server produces debugging information. > > Are you sure that the server binary is FreeRADIUS? > > 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
