Freeradius is not restarting properly (fails to quit and becomes a zombie process)

[Alan DeKok]

Jason Wittlin-Cohen <jasonwc at brandeis.edu> wrote:
> Over the last few days I've been having a recurring problem. Whenever I
> start Freeradius either with radiusd in a terminal or as a service in
> Debian, I can not restart/kill radiusd properly if it's authenticated
> any clients. Restarting the service says it's successful but the radius
> log states that port 1812 is already in use. "top" shows 100% cpu usage

  It looks like http://bugs.freeradius.org/show_bug.cgi?id=365

  The solution is to not re-initialize the modules on HUP.

  It works in *most* cases, because the code handling the HUP tries to
wait until all of the modules have stopped.  But if your back-end DB's
are slow, it doesn't have much choice but to proceed with handling the
HUP.

  Most people don't see it because the modules respond quickly.  I'd
say the first step to a work-around is to make sure none of the
modules you're using are blocking the server.

  Alan DeKok.
--
  http://deployingradius.com       - The web site of the book
  http://deployingradius.com/blog/ - The blog