John Horne wrote:
> We also have the file /etc/raddb/modules-local/attr_filter which
> contains:
Have you *deleted* the default configuration for the
attr_filter.post-proxy module?
If not, you have *two* copies of the module configuration. That's why
it's having issues. It picks on the first time, and a different one the
second time.
> attr_filter attr_filter.post-proxy {
> attrsfile = ${confdir}/attrs.post-proxy
> }
>
> So when freeradius starts up it reads this file, and uses the defined
> module in preference to the one in the
> file /etc/raddb/modules/attr_filter.
OK... so why do you still have the default one in the configuration?
Delete it, or rename your module, and update the server configuration to
use the new name.
> So, I guess the question is why is freeradius reloading the post-proxy
> filter a second time after the HUP?
The question is why do you have two configurations for the same module?
The only bug here is that the server should complain if you have two
instances of the same module defined. That would prevent the server
from starting in this case, and highlight the fact that the
configuration is wrong.
Alan DeKok.
-
List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
