vCenter skyline health is not working, showing below error in vSphere client:
When we look at the /var/log/vmware/sps.log file, we may see the below entries:
YYYY-MM-DDTXX:XX:XX.278Z [pool-20-thread-1] DEBUG opId=sps-PSVDCleanup-999147-409 com.vmware.vim.sms.policy.PolicyManagerImpl - Waiting for 1000 millisecs till all the providers are loaded...
.450Z [pool-24-thread-2] DEBUG opId=dam-auto-generated: StorageProvidersViewMediator:dr-2365:SmsPropertyProvider:200073:105321-598590-ngc:70017925 com.vmware.vim.storage.common.security.CommonActivationValidator - Validating session using session cookie...YYYY-MM-DD
TXX:XX:XX
.480Z [pool-22-thread-2] DEBUG opId=dam-auto-generated: StorageProvidersViewMediator:dr-2365:SmsPropertyProvider:200073:105321-598590-ngc:70017925 com.vmware.vim.sms.StorageManagerImpl - [queryArray] Received API Call: queryArrayYYYY-MM-DD
TXX:XX:XX
.481Z [pool-22-thread-2] DEBUG opId=dam-auto-generated: StorageProvidersViewMediator:dr-2365:SmsPropertyProvider:200073:105321-598590-ngc:70017925 com.vmware.vim.sms.StorageManagerImpl - ProviderLoader initialization is ongoing.YYYY-MM-DD
TXX:XX:XX
.481Z [pool-22-thread-2] ERROR opId=dam-auto-generated: StorageProvidersViewMediator:dr-2365:SmsPropertyProvider:200073:105321-598590-ngc:70017925 com.vmware.vim.sms.StorageManagerImpl - [queryArray] Operation queryArray failedYYYY-MM-DD
TXX:XX:XX(sms.fault.ServiceNotInitialized) {
faultCause = null,
faultMessage = null
Also, you will see an event for setContext for iofiltervpd provider, but it will not complete.
:00.006Z [Thread-9] DEBUG opId=sps-Main-999074-744 com.vmware.vim.storage.common.util.SimpleTimeCounter - TIMERYYYY-MM-DD
TXX:XX:XXSTARTED: VasaClientImpl : setContext for provider: https://hostname.com:9080/version.xml
Note: The preceding log excerpts are only examples. Date, time, and environmental variables may vary depending on your environment.
vCenter server version: 7.0.3.01900, Build 23788036
vCenter Storage Monitoring Service (com.vmware.vim.sms) was not running.
Rebuild the missing service using lsdoctor -r option using this KB: 320837
Lookup Service Doctor (lsdoctor) is a tool used to address issues with data stored in the PSC database, as well as data local to a vCenter (regardless of whether the PSC is external or embedded). The tool can be used to detect and correct problems that could cause failures in topology changes (converge, repoint, etc.), upgrades, or failures incurred as a result of maintenance (e.g. incorrectly applying new SSL certificates). This article will outline its functions and use.
This option is used when rebuilding one or all service registrations for a given node. This action performs the most significant changes, and extra care should be taken to ensure a safe rollback is possible (see Impact/Risks section).