[RADIATOR] clarification on AuthBy ROUNDROBIN failover

Andrew Clark adc at umn.edu
Tue Oct 26 10:38:12 CDT 2010


First one I sent to the list must've fallen through the cracks.

I'm seeking some clarification on the failover behavior of AuthBy
ROUNDROBIN and how to read the logs when servers are marked dead.  I
have three hosts in the round-robin pool (via a round-robin DNS host
name) and I can see that requests are being distributed correctly to
all three.  What is unclear is the meaning of the logs when a server
is marked out.  The three servers are of course at three different IP
addresses, but I only see log messages about one of three IP addresses
being marked down:

Tue Oct 12 16:14:52 2010: INFO: AuthRADIUS: No reply after 3
retransmissions to 134.84.119.107:1836 for foo  (). Now have 1
consecutive failures over 0 seconds. Backing off for 300 seconds
Tue Oct 12 16:14:52 2010: INFO: AuthROUNDROBIN: Retry 1,
firstHostTried 0, lastHostTried 0
Tue Oct 12 16:14:52 2010: WARNING: AuthROUNDROBIN: Request was tried
for 1 times. All alive server from the RoundRobin list were tried.
Tue Oct 12 16:14:52 2010: INFO: AuthRADIUS could not find a working
host to forward to. Ignoring
Tue Oct 12 16:14:53 2010: INFO: AuthRADIUS: No reply after 3
retransmissions to 134.84.119.107:1836 for foo  (171). Now have 1
consecutive failures over 0 seconds. Backing off for 300 seconds
Tue Oct 12 16:14:53 2010: INFO: AuthROUNDROBIN: Retry 1,
firstHostTried 0, lastHostTried 0
Tue Oct 12 16:14:53 2010: WARNING: AuthROUNDROBIN: Request was tried
for 1 times. All alive server from the RoundRobin list were tried.

-- 
Andrew D. Clark
Network Operations Engineer
University of Minnesota, Networking/Telecom Services
2218 University Ave SE
Minneapolis, MN 55414-3029
Phone: 612-626-4880


More information about the radiator mailing list