Re: radiusd exiting with status 0xb...

William Bulley (web@merit.edu)
Thu, 15 Feb 1996 10:33:00 -0500 (EST)

According to Matt Zimmerman:
>
> Our radiusd (Merit 2.4.16, running via inetd) seems to be aborting
> frequently with an exit status (as reported by inetd) of 0xb...according
> to the manpage, this is nonsensical...is inetd munging the exit code; if
> so, what error is actually being reported? Nothing is logged to
> .../raddb/logfile or syslog.

I was not aware that inetd(8) presented exit codes in hexadecimal (I seem
to remember it being decimal exit codes) so this is one source of confusion.

If the reported (are you sure?) 0xb exit code is from Merit RADIUS (which
seems odd since they are all negative -- don't ask...) it may be that some
one has taken to converting the -11 (socket BIND error) code to +11 (0xb)
but that seems very unlikely. Although you could check to see if some one
else is holding the 1645 UDP port when you try to start the Merit server.

I would use netstat or lsof to do this...

What is the platform? What is the operating system? Is this inetd(8) or
xinetd(8)? Is the Merit server statically linked or dynamically linked?

Regards,

web...

-- 
William Bulley, N8NXN              Senior Systems Research Programmer
Merit Network Inc.                 Domain: web@merit.edu
4251 Plymouth Road                 MaBell: (313) 764-9993
Ann Arbor, Michigan  48105-2785    Fax:    (313) 747-3185