For a while I've been using FreeRADIUS with a set of includes.d-style directories that I can drop modules, virtual sites, etc into. This works well - until today. So far I've only had one included policy file in use, and the stock policy.conf is commented out. Today I tried to add another new virtual site which also has a policy file. Although radiusd -X clearly shows that the new policy file is being read, my virtual server is unable to call upon policies defined in the file. On a FreeRADIUS server with no other sites/policies, the new site and policy work fine, so it appears to be some kind of namespace issue. I've been through both policy files and there are no namespace clashes. Each policy file has its own name, e.g. policy eduroam {} and policy rainbow {}. Unusually, the debug log doesn't seem to be that helpful (it says that the files have been loaded, and that the policy can't be found by name). Apologies for the naming scheme - the various sites, modules and policies we currently manage have been inherited from various authors and I'm working on overhauling it. "debug-working.log" is from a FreeRADIUS server using only the new virtual site, which works. "debug-not-working.log" is from a full development FreeRADIUS server with other sites and policies, which does not work. "policies" is the policy file used with the existing (eduroam) sites "rainbow.conf" is the new policy that works on its own, but not in conjunction with other policies. Can anyone spare a few minutes to cast an eye over the debug output and see if I've missed something? I spent all yesterday afternoon looking and this problem and didn't make much progress. Thanks, Jonathan