vSAN health report FileServersAreComparativelyOverloadedOnThisHost under InfrastructureHealth and FileServerIs(Re)Starting under FileServerConnectivity repeatedly

Products

• VMware vSAN

Issue/Introduction

Symptoms:

• vSAN health reports FileServersAreComparativelyOverloadedOnThisHost under InfrastructureHealth
• and some time later or the same time vSAN health reports FileServerIs(Re)Starting under FileServerConnectivity repeatedly
• Container is destroyed repeated
  

  vsanfs.mgmt[2102981]: [2103119] [VDFSEndpointContainerDocker::Destroy] FS Container hqnc-file-8 is destroyed
  vsanfs.mgmt[2102981]: [2103129] [VDFSEndpointContainerDocker::Destroy] FS Container hqnc-file-9 is destroyed
  vsanfs.mgmt[2102981]: [2103000] [VDFSEndpointContainerDocker::Destroy] FS Container hqnc-file-8 is destroyed
   vsanfs.mgmt[2102981]: [2103124] [VDFSEndpointContainerDocker::Destroy] FS Container hqnc-file-9 is destroyed
  vsanfs.mgmt[2102981]: [2103129] [VDFSEndpointContainerDocker::Destroy] FS Container hqnc-file-8 is destroyed
  vsanfs.mgmt[2102981]: [2103124] [VDFSEndpointContainerDocker::Destroy] FS Container hqnc-file-9 is destroyed

• WinbindHealthTest failed 
  

  vsanfs.mgmt[2102780]: [2102917] [VDFSEndpointMonitorContainer::_CheckContainerHealthItem] CONT: Error running WinbindHealthTest on container <IP of Container>: error, checking the NETLOGON for domain[DomainName] dc connection to "" failed`

• In log.wb-WATERMELON under container's samba/samba_logs,  NT_STATUS_NO_TRUST_SAM_ACCOUNT is reported
  

  L3, pid=181, cls=winbind] _wbint_PingDc(line 821)  could not open handle to NETLOGON pipe: NT_STATUS_NO_TRUST_SAM_ACCOUNT

Environment

vSAN File Service

Cause

AD user permission issue.

Resolution

If SMB is not used in vSAN file service,  AD Domain setting can be unset.
If SMB is used, please try our AD user with correct permission.