In my named logs, I'm frequently seeing maximum number of FD events (64) received - is this cause for concern?
Answer:maximum number of FD events
means that when checking to see if any sockets are ready to be read from, there were more than 64 of them. As commented in the code, this isn't an error, but it is unexpectedly high. If the message is logged frequently and persists for a long period of time, then It may be that recompiling with a higher value of ISC_SOCKET_MAXEVENTS
will make this message disappear. But if there is another underlying problem that isn't diagnosed and addressed, the you may still reach the maximum number of events, no matter how high the limit is set.
On larger machines that have high query rates, increasing this setting can be done when you build the named binary by setting ISC_SOCKET_MAXEVENTS when invoking configure. For example:
Please also see:
What to do with a misbehaving BIND server
Background info about 'maximum number of FD events' log messages
© 2001-2017 Internet Systems ConsortiumFor 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.