I am sure I am doing something wrong. We have all our user data in "authorize" and a HUP doesn't reread the file in 3.0.9. That version added the feature of ignoring a HUP unless a file had changed. It seems to recognize that a file has changed but it doesn't actually reload. After a HUP in 3.0.8: server inner-tunnel { # from file /usr/local/freeradius/etc/raddb/sites-enabled/inner-tunnel # Loading authenticate {...} # Loading authorize {...} # Loading session {...} # Loading post-proxy {...} # Loading post-auth {...} } # server inner-tunnel Ready to process requests 3.0.9: Listening on proxy address * port 53399 Ready to process requests Ready to process requests Received HUP signal HUP - No files changed. Ignoring <-- "authorize" changed here Ready to process requests Ready to process requests Received HUP signal HUP - Files loaded by a module have changed. Ready to process requests <-- no indication of an actual reload At this point radiusd doesn't answer queries with the new information in "authorize." -- Jay Rouman (jsr@dexter.mi.org jsr@edzone.net) Gratiot/Isabella RESD, Ithaca, Michigan
On Sep 2, 2015, at 12:15 PM, Jay Rouman <jsr@dex.edzone.net> wrote:
I am sure I am doing something wrong. We have all our user data in "authorize" and a HUP doesn't reread the file in 3.0.9. That version added the feature of ignoring a HUP unless a file had changed. It seems to recognize that a file has changed but it doesn't actually reload.
Yes, that's an issue. We fixed a bunch of things related to HUP in v3. That had the side effect of causing this problem.
At this point radiusd doesn't answer queries with the new information in "authorize."
You can do: $ radmin -e "hup files" to HUP just the "files" module. We're working on fixing it for 3.0.10 Alan DeKok.
participants (2)
-
Alan DeKok -
Jay Rouman