ads_cldap_netlogon: cldap_multi_netlogon failed: NT_STATUS_TOO_MANY_OPENED_FILES

[Jeremy Allison]

On Tue, May 31, 2016 at 11:44:49AM -0700, Partha Sarathi wrote:
> Hi,
> 
> We have noticed the below error on one of our customer box SAMBA-4.3.4
> configured as member server and connected to win2k12R2, I am just curious
> was this 'NT_STATUS_TOO_MANY_OPENED_FILES'  error reported by DC or SAMBA.
> On SAMBA side there was not much file activities. Any idea what could have
> caused this to happen ?
> 
> =======
> 
> *[2016/05/31 06:50:56.143149, 2, pid=1150]
> ../source3/libads/cldap.c:346(ads_cldap_netlogon)*
> *ads_cldap_netlogon: cldap_multi_netlogon failed:
> NT_STATUS_TOO_MANY_OPENED_FILES*
> [2016/05/31 06:50:56.143386, 2, pid=1150]
> ../source3/libads/cldap.c:346(ads_cldap_netlogon)
> ads_cldap_netlogon: cldap_multi_netlogon failed:
> NT_STATUS_TOO_MANY_OPENED_FILES
> [2016/05/31 06:50:56.143527, 2, pid=1150]
> ../source3/libads/cldap.c:346(ads_cldap_netlogon)
> ads_cldap_netlogon: cldap_multi_netlogon failed:
> NT_STATUS_TOO_MANY_OPENED_FILES
> [2016/05/31 06:50:56.143635, 2, pid=1150]
> ../source3/libads/cldap.c:346(ads_cldap_netlogon)
> ads_cldap_netlogon: cldap_multi_netlogon failed:
> NT_STATUS_TOO_MANY_OPENED_FILES
> [2016/05/31 06:50:56.144014, 1, pid=1150]
> ../source3/libads/ldap.c:552(ads_find_dc)
> *ads_find_dc: name resolution for realm 'LAB.LOCAL' (domain 'LAB') failed:
> NT_STATUS_NO_LOGON_SERVERS*
> [2016/05/31 06:50:56.144641, 1, pid=1150]
> ../source3/libads/ldap.c:552(ads_find_dc)
> ads_find_dc: name resolution for realm 'LAB.LOCAL' (domain 'LAB') failed:
> NT_STATUS_NO_LOGON_SERVERS

Hmmm. Looks like the kernel ran out of fd's. What is
it configured to ?