[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Radiusd-lucent crashing with external requests



I am replacing an OpenBSD2.8 radius server with a 3.0 build  running
radiusd-lucent-2.1p2.  Queries from 127.0.0.1 work fine (i.e. radtest
or mod_auth_radius on the local box). Any (most?) external queries
(from our routers) cause the radiusd to exit with a signal 100.  I have
been unable to find signal 100 or radiusd in the mailing list archives
or generally on google.  Any help greatly appreciated.  All other
services seem to be fine.

I have added the /var/log/radacct directory and have a full /etc/raddb
that seems to work correctly with local queries, so I do not
think the configuration is wrong in /etc/raddb.  /etc/raddb was carried
forward from the 2.8 server that was functioning fine there.



Log entries:

Dec 12 11:18:32 ns1 radius[28897]: /usr/local/sbin/radiusd: Livingston
RADIUS 2.1.va.1 2001/7/5  NDBM NOSHADOW __OpenBSD__ flat_users 
Dec 12 11:18:32 ns1 radius[28897]: proxy file /etc/raddb/proxy not
found; not using proxy 
Dec 12 11:20:36 ns1 radius[28897]: exit on signal 100 
Dec 12 11:20:36 ns1 radius[28897]: counters 1 0 / 0 0 / accept 0 reject
0 challenge 0 response 0 
Dec 12 11:20:36 ns1 radius[28897]: memory usage = pair 4/4/4  peer
0/0/0  req 1/1/1  buf 1/1/1 
Dec 12 11:20:36 ns1 radius[28897]: no entries in proxy queue 



Mike
-- 
Michael Sullenszino    /----------------------------------------\
mike_(_at_)_sullenszino_(_dot_)_org  ||  Powered by OpenBSD (www.OpenBSD.org)  ||
www.sullenszino.org   ||   & Debian GNU/Linux (www.debian.org)  ||
206.722.6539           \----------------------------------------/



Visit your host, monkey.org