Too many open files

Cricket Liu cricket at nxdomain.com
Fri Feb 21 21:11:34 UTC 2003


On Friday, February 21, 2003, at 01:22  PM, chad kellerman wrote:

>      I have a strange problem.  I have a combination web server /name 
> server
> that I upgrade from a RedHat 6.2 server running a 2.2.19 Kernel with 
> Bind
> 8.2.3 to a RedHat 7.3 server running a 2.4.19 Kernel with Bind 8.3.3.
>
>      The ulimits match.  I have approximately 500 ips bound to the 
> server.
> Running 6.2 the name server ran like a champ.
>
>   But now When I start the name server after about the 494 listening 
> on [ip
> address] in named.log I get:
>
> 21-Feb-2003 14:08:13.349 default: notice: fcntl(fd, F_DUPFD, 20): Too 
> many
> open files
> 21-Feb-2003 14:08:13.349 default: error: socket(SOCK_DGRAM): Too many 
> open
> files
> 21-Feb-2003 14:08:13.349 default: notice: deleting interface 
> [$ipaddr].53
> 21-Feb-2003 14:08:13.349 default: notice: fcntl(fd, F_DUPFD, 20): Too 
> many
> open files
> 21-Feb-2003 14:08:13.349 default: error: socket(SOCK_DGRAM): Too many 
> open
> files
>
> The only way to stop this is to put the listening on directive in 
> named.conf.
>
> I did not have to do this with an older version of the Kernel, Bind, 
> and
> RedHat.  So why is this happening now.
>
> I have raised all of the ulimits to higher numbers even increase
> /proc/sys/fs/file-max
>
> but still the errors happen.
>
> Can anyone point me in the right direction to fix this issue?

You've got the right fix:  Use the listen-on options substatement to 
tell the
name server not to bother listening on all the IP address aliases on the
box.  You don't need it to listen on all those addresses, do you?

cricket

The DNS and BIND Cookbook, now available!
http://www.oreilly.com/catalog/dnsbindckbk/



More information about the bind-users mailing list