What does "isc_socket_create: fcntl/reserved: Too many open files" mean?
- Updated on 10 Apr 2017
- 2 minutes to read
What do these named errors signify - and how should they be investigated?
10-May-2011 15:41:13.815 general: error: isc_socket_create: fcntl/reserved: Too many open files 10-May-2011 15:41:13.815 general: error: isc_socket_create: fcntl/reserved: Too many open files 10-May-2011 15:41:13.815 general: error: isc_socket_create: fcntl/reserved: Too many open files 10-May-2011 15:41:13.815 general: error: isc_socket_create: fcntl/reserved: Too many open files
These errors would typically be seen on a server which is providing recursive resolution to clients and are usually indicating that the per-process (sometimes per system - but that would be less usual) limit on the number of open file descriptors (of which sockets are one example) has been reached.
You can check the per-system use of sockets using:
You can (approximately) check named's use of sockets for DNS protocol activity using:
netstat -an|grep ":53"
And more accurately (if you have lsof), and logged in with sufficient access:
The first setting to check is your system limits on open files per process - how to do this may vary between Operating Systems.
Also check the named startup logs - depending on the BIND version and the system configuration, named's own limit on open sockets should be logged and occasionally warnings will be seen when the system limits further constrict the value that named would prefer to use.
Also looking at the logfiles - is there a pattern of other errors being reported when these errors are seen?
When these errors are being logged, check the output from rndc status - in particular the number of recursive clients . If there's a build up of recursive clients at the same time then this might explain why the limit on open files has also been reached. This could be due to a normal peak in client activity, or it might be indicative of some other problem.
If there is a build-up of recursive clients, then we recommend using rndc recursing to obtain the details of waiting clients and the queries that they have made.
If there are no resolution problems being reported and these errors are infrequent and transient, then it's likely that you're hitting a resource bottleneck periodically. We'd recommend further monitoring and investigation to understand what is happening when they are seen in case the situation deteriorates, but this wouldn't be an urgent matter.
© 2001-2018 Internet Systems Consortium For assistance with problems and questions for which you have not been able to find an answer in our Knowledge Base, we recommend searching our community mailing list archives and/or posting your question there (you will need to register there first for your posts to be accepted). The bind-users and the dhcp-users lists particularly have a long-standing and active membership. ISC relies on the financial support of the community to fund the development of its open source software products. If you would like to support future product evolution and maintenance as well having peace of mind knowing that our team of experts are poised to provide you with individual technical assistance whenever you call upon them, then please consider our Professional Subscription Support services - details can be found on our main website.