Loading fails without reporting an error

Matthew Newton mcn4 at leicester.ac.uk
Fri Jul 12 12:24:54 CEST 2013

On Fri, Jul 12, 2013 at 11:19:00AM +0200, Alan DeKok wrote:
> Lovaas,Steven wrote:
> > Thanks, Adam... this got me looking at the right thing.
> > 
> > I had a mismatch between the type of the home_server localhost (auth), and the attribute used in one of the realms pointing to the pool that references that home server (pool, instead of auth_pool). Changing the type of the localhost home_server allowed FR to complete loading.
>   If you have a simple config that can reproduce it, I'd like to fix the
> problem.
>   It's likely just adding a printed error message in the home server
> code.  But knowing exactly where to add it would be useful.

I've sent a pull request.

It's easy to trigger - take a standard 2.x config and apply the
following patch to the config:

diff --git a/raddb/proxy.conf b/raddb/proxy.conf
index 413fc14..6ceb5cb 100644
--- a/raddb/proxy.conf
+++ b/raddb/proxy.conf
@@ -613,6 +613,7 @@ realm example.com {
        #  and "acct_pool".
        auth_pool = my_auth_failover
+       acct_pool = my_auth_failover
 #      acct_pool = acct

There are a distinct lack of errors printed out in realms.c when
it returns. I'm guessing there may be better error messages or
locations to print them, but the pull request will give the right
starting pointers :-)


Matthew Newton, Ph.D. <mcn4 at le.ac.uk>

Systems Specialist, Infrastructure Services,
I.T. Services, University of Leicester, Leicester LE1 7RH, United Kingdom

For IT help contact helpdesk extn. 2253, <ithelp at le.ac.uk>

More information about the Freeradius-Users mailing list