Winbindd causes high CPU utilization

This topic describes the issues that can happen due to the winbindd component.

Cause

One possible reason is that winbind is not able to find domain controllers for a given domain. NT_STATUS_NO_LOGON_SERVERS is seen in log file log.winbindd-dc-connect in that case. One possible issue here is that the DNS does not provide this information. Usually the local DCs have to be configured as DNS servers on the protocol nodes, as AD stores additional information for locating DCs in the DNS.

Solution

The problem is also known to go away after upgrading to IBM Storage Scale 4.2.2 or higher versions.