File Descriptor limit and malfunction bind

[Kevin Darcy]

What's your hard limit (ulimit -n -H)?

named seems to use, by default, the OS hard limit on file descriptors, 
even though the ARM says "The default is |unlimited|. ". When it starts 
up as superuser, in theory it should be able to set both the hard and 
soft limit to "infinity", but it doesn't appear to be doing that, at 
least it doesn't on Solaris.

If you want to raise the limit on files, the recommended way is to use a 
"files" clause in the options statement. This might not work too well, 
however, if you try to raise the limit beyond the OS-defined hard limit, 
on a running named process which has dropped its superuser privileges. 
You'd need to restart in that case.

                                                                         
                                       - Kevin
**
Ram Akuka wrote:
> Hi ,
> i have a high load DNS server running bind 9.4.3 on RH -
> yesterday we experienced a problem with the bind  (the bind froze) , 
> and when looking at the logs i saw the following error :
> named error: socket: file descriptor exceeds limit (4096/4096)
> i looked at my OS file descriptor limit and using ulimit -n   - 1024 .
> where the number 4096 come from?
>
> BTW
> the named i'm running using 7 cpus (-n 7 when start).
>
>
>
> please advice ,
>
>
> --
> Ram
> ------------------------------------------------------------------------
>
> _______________________________________________
> bind-users mailing list
> bind-users at lists.isc.org
> https://lists.isc.org/mailman/listinfo/bind-users