- This is a known issue found in vCenter Server Appliance for 6.7 Update 1 and 6.5 Update 2d.
- This issue has been resolved in VMware vCenter Server 6.7 Update 1b Build 11726888
- In the VMware vCenter Server 6.5 , the issue resolved in the 6.5 U3
Workaround:
Note: If you need assistance with this procedure contact support.
To work around this issue:
In the /usr/lib/vmware-vpx/vsan-health/pyMoVsan/VsanVcExtension.py on the VCSA locate the following sections:
conn = SoapStubAdapterForLocalhost('localhost', 443,
version='vim.version.version11', path='/sdk',
soapStubAdapater=HostdSoapStubAdapter)
and
conn = SoapStubAdapterForLocalhost('localhost', port,
version=GetVcVmodlVersion(),
path='/sdk',
httpConnectionTimeout=timeout)
In these add the line
poolSize=0, so they read as follows:
conn = SoapStubAdapterForLocalhost('localhost', 443,
version='vim.version.version11', path='/sdk',
poolSize=0,
soapStubAdapater=HostdSoapStubAdapter)
and
conn = SoapStubAdapterForLocalhost('localhost', port,
version=GetVcVmodlVersion(),
path='/sdk',
poolSize=0,
httpConnectionTimeout=timeout)
- Save the python file.
- Start the service: service-control --start vmware-vsan-health
- Restart vSAN management server using the command: /usr/lib/vmware-vmon/vmon-cli -r vsan-health. This will re-validate if the services are starting properly.
- Verify that the total opened file handlers for vSAN management server are normal (default maximum limit is 1024).
lsof -p $(cat /var/log/vmware/vsan-health/vmware-vsan-health.pid) | wc -l