Proxy "status" (was: Proxy fixes)
p.mayers at imperial.ac.uk
Mon Jan 7 18:59:26 CET 2013
On 27/10/12 12:49, Alan DeKok wrote:
> I managed to find an hour or two in between various things. I've
> taken a look at the proxy code, and added some fixes in "master".
> To be polite, I didn't quite understand the previous code. So... I've
> deleted things, and simplified other things. The result is that the
> "zombie" home server detection should be better.
> I don't know if it fixes the "crash on dead home server" issue that
> people were seeing. I wasn't able to reproduce that. But, the relevant
> code is now different. So I hope it's fixed.
> As always, blame Arran for any bugs. :)
Just a quick note - I'm not sure the home server "status" is working
properly in the new code; I'm getting:
# radmin -d /etc/raddb3 -n eduroam -e 'show home_server list'
22.214.171.124 1812 udp auth unknown 0
126.96.36.199 1813 udp acct unknown 0
188.8.131.52 1812 udp auth unknown 0
184.108.40.206 1813 udp acct unknown 0
220.127.116.11 1812 udp auth unknown 0
18.104.22.168 1813 udp acct unknown 0
...even though the servers are up and responding to packets. Same over
the RADIUS-based stats interface (minor related note - the
"FreeRADIUS-Stats-Server-State" attribute is missing a definition for
value "3" i.e. "Unknown")
I think it might be the logic in process.c:remove_from_proxy_hash_nl -
that function seems to set the state to "UNKNOWN" if there are zero
outstanding packets, which I guess is not right?
More information about the Freeradius-Devel