URGENT, PLEASE READ: 9.5.0-P1 now available

[Walter Gould]

Thanks for your reply...


JINMEI Tatuya / ???? wrote:
> Can you figure out how many sockets were opened in that situation?  It
> will also help if you specify your OS and version.
>
>   
RHEL 3

> This situation could happen if named opens so many open sockets bound
> to random UDP ports simultaneously.  But as long as the query rate and
> cache hit rate are moderate, this should be a rare event in
> practice.  So my first guess is that the system default of the maximum
> allowable open sockets is too small.  Please check the value (e.g., by
> 'ulimit -n' that works for many shells), and try a larger value if
> it's too small.
>
> If it's equal to or larger than 1024 and you still see this problem,
> your operational environment might be such a rare unlucky one.  In
> that case, I'd recommend you try 9.5.1b1 (or 9.4.3b1), which handles
> such cases much better.
>
>   

# ulimit -n
1024

I increased it to 2048 - but got the same results...

I've not had this happen with any BIND versions that I've upgraded to in 
the past. Any other suggestions other than using the beta code? Thanks 
again.

Walter