Re: proxy.conf timing and fail_over

[Chris Brotsos]

At 04:41 PM 7/10/2003, you wrote:
Thanks Chris-
  I too found the "marking ...." in files.c, not proxy.c
 and the ldflag spec in mainconfig.c
I believe fail_over was functional since FR 0.4

I have specified the ldflag = fail_over simply due to a script I have 
which makes the proxy.conf file and future use of round_robin.
I will remove it, for giggles, but I must have a radiusd.conf error in timing.

But where......Hmmmmmm
I think you wrote that you've already run the server in debug mode (-x -x). 
So, run it again and see if you actually notice the "marking ...." message 
in the output. Double check that the server is not actually failing over to 
your secondary option. I pretty much kept the stock default config in the 
0.8.1 conf files, but here's some pertinent entries:
################# proxy.conf #########
proxy server {
        synchronous = no
        retry_delay = 5
        retry_count = 3
        dead_time = 10
        servers_per_realm = 15
        default_fallback = yes
}

realm brotsos.com {
        type = radius
        authhost = ipaddress:1645
        accthost = ipaddress:1646
        secret = secret
        nostrip
}
realm brotsos.com {
        type = radius
        authhost = ipaddress2:1645
        accthost = ipaddress2:1646
        secret = secret2
        nostrip
}
#######################
######### radiusd.conf ########
max_request_time = 30
* max_request_time is important because if your retry_count * retry_delay > 
max_request_time then the request will be dropped before the fail-over can 
take place.

proxy_requests = yes
$INCLUDE ${confdir}/proxy.conf
authorize {
        suffix
        files
}
###########################
And that's about all that should matter. Take a look at your 
max_request_time. Is that maybe the problem?

Regards,

Chris Brotsos



- 
List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html