Alan,
More information for you: On the 0.3 binary, the process jumps
between each CPU. (it's a dual 800). Watching it in top will show CPU0
100% idle, then CPU1 at 100% idle as CPU0 jumps to 0% idle. The
priority for the process goes from 19 down to about 16 before it flips
over to the other processor.
Does that help at all? :)
If I knew how to use gdb, I'd get a capture for ya.
> -----Original Message-----
> From: Jason Lixfeld [mailto:[EMAIL PROTECTED]]
> Sent: October 24, 2001 3:59 PM
> To: '[EMAIL PROTECTED]'
> Subject: RE: Problems starting radiusd
>
>
> Alan, I tried the latest CVS version and it crashes
> regardless (-s flag or no -s flag):
>
> I start up the new server (used the same ./configure flags so
> no arguments were required to load successfully, all values
> are compiled in) with -xx:
>
> <snip>
> Listening on IP address *, ports 1645/udp and 1646/udp.
> Ready to process requests.
> Thread 1 waiting to be assigned a request
> </snip>
>
> As SOON as I send it a request (radtest), it fails and I get this:
>
> rad_recv: Access-Request packet from host 127.0.0.1:32786,
> id=56, length=56 Thread 1 assigned request 0
> --- Walking the entire request list ---
> Thread 1 handling request 0, (1 handled so far)
> User-Name = "adrianb"
> Password = "tRL\246\347z\3558\032\244)\204\3257\300\357"
> NAS-IP-Address = 255.255.255.255
> NAS-Port-Id = "0"
> modcall: entering group authorize
> CHILD: exit on signal (11)
> [root@industry main]#
>
> What be signal (11)?!
>
> -------Original Message-----
> > From: Jason Lixfeld [mailto:[EMAIL PROTECTED]]
> > Sent: October 24, 2001 3:32 PM
> > To: '[EMAIL PROTECTED]'
> > Subject: RE: Problems starting radiusd
> >
> >
> > > Which version of the server are you running? The CVS
> snapshot has
> > > a lot of bugs fixed over older versions.
> >
> > radiusd: FreeRADIUS Version 0.3, for host i686-pc-linux-gnu,
> > built on Oct 19 2001 at 14:22:32
> >
> > > 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.
> >
> > I'll try the latest CVS.
> >
> > > 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.
> >
> > I know that being exact helps. It is infact radiusd
> > (lowercase r), except with this version of outlook, it
> > capitalizes the first letter of a new sentence, hence the R
> > in radius :)
> >
> > > 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.
> >
> > Yeah, well apparently it works with -s :)
> >
> > > 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?
> >
> > See above for radiusd -v output.
> >
>
-
List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
