Certain IOFIlter Providers are showing as offline
Article ID: 318887
Updated On:
Products
VMware vCenter Server
VMware vSphere ESXi
Issue/Introduction
To get the IOfilter providers online.
Symptoms:
2019-08-12T10:59:19.997+02:00 [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-B FQDN>:9080/version.xml:9080/version.xml is offline
2019-08-12T10:59:20.000+02:00 [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
Symptoms:
- Certain IOFIlter Providers are showing as offline
- This is observed post upgrade to vCenter 6.7
- In the vCenter log: /var/log/vmware/vmware-sps/sps.log you will see entries similar to the below:
2019-08-12T10:59:19.997+02:00 [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-B FQDN>:9080/version.xml:9080/version.xml is offline
2019-08-12T10:59:20.000+02:00 [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
- The sps service is showing as green when running the below command:
- Running the command netstat -pan | grep sps does not show any entries in CLOSE_WAIT for port 9080.
Environment
VMware vSphere ESXi 7.0.x
VMware vSphere ESXi 6.7
VMware vCenter Server 7.0.x
VMware vCenter Server 6.7.x
VMware vSphere ESXi 6.7
VMware vCenter Server 7.0.x
VMware vCenter Server 6.7.x
Resolution
Ensure that wget to the URLs from vCenter server to the hosts are reachable before proceeding.
NOTE: Take a snapshot of VC, PSC and backup of postgres database before proceeding.
Un-register the IOFilter VP's using the below steps:
Log in to the following link https://<VC-IP>/sms/mob
1) Click on QueryStorageManager link
2) Click on Invoke method, then on the "storageManager" link in the Method Invocation Result
3) Click on the QueryProvider link and Invoke method
4) Click through the vasaProvider-XXX links in the Method Invocation Results one by one
5) For each vasaProvider selected click on QueryProviderInfo link and Invoke Method
6) Cross reference the result for "uid" field and note it down for each "url" entry that matches from the url's mentioned in the vCenter Storage Provider pane as showing offline.
E.g: (sms.provider.VasaProviderInfo) { dynamicType = null, dynamicProperty = null, uid = b9ac8d33-fb57-4c98-8c42-be36a633f1ce <-----
Once after noting down the uuid for all IOFilter VP, trigger unregister on them as below:
7) Go Back to the QueryStorageManager link (see step 1 and step 2)
8) Click on UnregisterProvider_Task link
9) Enter one of the the provider uid's found in step 6 and click on the invoke method.
Step 9 needs to be repeated for each of the uuid's noted in step 6 above.
##############################
# Registering IOFilter VP's: #
##############################
- Restart SPS service with these commands:
service-control --stop vmware-sps
service-control --start vmware-sps
NOTE: Take a snapshot of VC, PSC and backup of postgres database before proceeding.
Un-register the IOFilter VP's using the below steps:
Log in to the following link https://<VC-IP>/sms/mob
1) Click on QueryStorageManager link
2) Click on Invoke method, then on the "storageManager" link in the Method Invocation Result
3) Click on the QueryProvider link and Invoke method
4) Click through the vasaProvider-XXX links in the Method Invocation Results one by one
5) For each vasaProvider selected click on QueryProviderInfo link and Invoke Method
6) Cross reference the result for "uid" field and note it down for each "url" entry that matches from the url's mentioned in the vCenter Storage Provider pane as showing offline.
E.g: (sms.provider.VasaProviderInfo) { dynamicType = null, dynamicProperty = null, uid = b9ac8d33-fb57-4c98-8c42-be36a633f1ce <-----
Once after noting down the uuid for all IOFilter VP, trigger unregister on them as below:
7) Go Back to the QueryStorageManager link (see step 1 and step 2)
8) Click on UnregisterProvider_Task link
9) Enter one of the the provider uid's found in step 6 and click on the invoke method.
Step 9 needs to be repeated for each of the uuid's noted in step 6 above.
##############################
# Registering IOFilter VP's: #
##############################
- Restart SPS service with these commands:
service-control --stop vmware-sps
service-control --start vmware-sps
Feedback
Yes
No
Powered by
