[YYYY-MM-DDTHH:MM:SS] [pool-10-thread-5] ERROR opId=sps-Main-101761-246 com.vmware.vim.sms.provider.vasa.alarm.AlarmDispatcher -
[YYYY-MM-DDTHH:MM:SS] [pool-10-thread-1] ERROR opId=sps-Main-101761-246 com.vmware.vim.sms.provider.vasa. alarm. AlarmDispatcher - Error: org.apache.axis2.AxisFault: self signed certificate occured as provider: https://<ESXi-A FQDN>:9080/version.xml:9080/version.xml is
offline
[YYYY-MM-DDTHH:MM:SS] [pool-10-thread-4] ERROR opId=sps-Main-101761-246 com.vmware.vim.sms.provider.vasa.alarm.AlarmDispatcher - Error: org.apache.axis2.AxisFault: self signed certificate occured as provider: https://<ESXi-C FQDN>:9080/version.xml:9080/version.xml is
offline
Error: org.apache.axis2.AxisFault: self signed certificate occured as provider: https://<ESXi-A FQDN>:9080/version.xml is offline
# wget localhost:22000/sms/HealthStatus ; cat HealthStatus ; rm HealthStatus
netstat -pan | grep sps
does not show any entries in CLOSE_WAIT for port 9080.VMware vCenter Server 8.x
VMware vSphere ESXi 8.x
VMware vCenter Server 7.x
VMware vSphere ESXi 7.x
VMware vCenter Server 6.7
VMware vSphere ESXi 6.7
NOTE: Before taking the steps below, please ensure that a fresh snapshot or backup of the vCenter Server Appliance (VCSA) was created. In case the VCSA is in an Enhanced Linked Mode replication with other vCenter Servers, please be aware that offline snapshots of all ELM replication partners need to be taken, and need to be restored in case of a rollback.
Also please ensure that the IOFilter provider URLs can be reached from the vCenter, by running wget
against them. Once this was verified, please apply one of the options below:
https://<vCenter-IP>/sms/mob
(sms.provider.VasaProviderInfo) { dynamicType = null, dynamicProperty = null, uid = b9ac8d33-fb57-4c98-8c42-be36a633f1ce
# service-control --stop vmware-sps
# service-control --start vmware-sps
# Connect-VIServer --server <vCenter-FQDN>
# Get-VasaProvider | Where-Object {$_.Namespace -eq 'IOFILTERS' -and $_.Status -like 'offline'} | Remove-VasaProvider