strange behavior in proxy when some backend servers down

[travis+ml-freeradius-users at subspacefield.org]

Hello,

I've just been assigned a task regarding a problem with freeradius.

Bear with me if my understanding of freeradius terminology is a bit
weak, as I have just started familiarizing myself with this software
today.

The situation is that we have a freeradius instance running as a
proxy.

This instance is configured to proxy requests to a pool of four
freeradius servers.

Right now three are down, so we are testing the failover conditions.

IIUC, the desired behavior is that it tries one backend server, and
fails, marks it as a zombie, and then upon receiving another request
from the user logging in, it should try a different backend server.

What we're seeing is that once no response comes back from a server,
it marks the server as a zombie, but it marks the request as completed.

Subsequent authentication requests that come in are looked up in the
response hash, finds that the response has been completed, and ignores
the request.

I could use any help in tracking this down.  If it requires a code
change to fix, I'll be contributing that back to the project.

Does anyone have any suggestions on how to track this down?
-- 
Obama Nation | My emails do not have attachments; it's a digital signature
that your mail program doesn't understand. | http://www.subspacefield.org/~travis/ 
If you are a spammer, please email john at subspacefield.org to get blacklisted.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: <http://lists.freeradius.org/pipermail/freeradius-users/attachments/20090710/3567bb63/attachment.pgp>