Pre-release of Version 2.1.8

[Alan DeKok]

Bjørn Mork wrote:
> Yes, I got one of those:
> 
> Tue Dec  8 08:49:22 2009 : Proxy: Marking home server 192.168.8.216 port 1812 as dead.
> Tue Dec  8 08:49:22 2009 : Error: Failed creating new proxy socket: server is too busy and home servers appear to be down

  OK.  That indicates that all 32 sockets have been allocated.  All this
means is that no *new* sockets will be allocated from now on.

> So it's possible that a few failing home servers end up tying up all
> sockets available for proxying?

  No.  See my other post for a detailed explanation.

>  Or am I misunderstanding this?  For how
> long?  The server was not responding to requests going to a proxy at all
> between 08:43:27 and 09:35:46.  That's a very long time to sit waiting
> for available resources...

  I agree.  You should use radmin to look at the server stats, to see
what it's doing.

> But I still believe sharing these resources in a way which let a few bad
> servers steal them all, is wrong.  It should be possible to isolate two
> independent realms from each other, even if they use the same proxy
> radius. 

  See my other post.  They are isolated, unless they both proxy to the
same home server.  When that happens, they share the home server state.

>>   If that works, we could do a "git bisect" to find the issue.  There
>> are only 26 commits since them, and many of those don't have code
>> changes.  It shouldn't be too hard to track down the offending commit.
> 
> Given that I can actually trigger the problem in a test enviroment.  I
> don't think I can.

  ?  You can reproduce it, but can't find the offending commit?

  Alan DeKok.