Unstable FreeRadius

Alan DeKok aland at nitros9.org
Wed May 17 21:14:00 CEST 2006

"George C. Kaplan" <gckaplan at ack.berkeley.edu> wrote:
> If you've got it set up right, a 'radtest' will time out
> after several seconds with a "Cannot contact any KDC..." message in
> radius.log.  If you HUP the radiusd before it times out, that should
> trigger the lockup.

  I think I know what's happening.  The HUP triggers a tear-down &
re-start of all modules.  If a module is blocked, the data structures
pointing to it will be destroyed...

  One solution would be to go to src/main/modules.c, function
setup_modules().  Comment out or delete the call to detach modules().

  That will work, but ONLY if the "radiusd.conf" file doesn't change.
If you're HUing the server to get it to re-read the "users" file,
that's OK.

  If that change fixes it for you, we should look into a better
approach to HUPing the server...

  Alan DeKok.

More information about the Freeradius-Users mailing list