printer Print

Customer View

ViPR SRM 4.0 | VMware vCenter Timeout reached when trying to connect to https://xxx/sdk/vimService

Article Number: 518895
Version: 4
Article Type: Break Fix
Last Published: 23 Mar 2020

- The report of VMware vCenter in the default reports is empty not showing any data 
- The discovery of the vCenter is successful without any errors
- Logs were showing the below error:
SEVERE -- [2018-03-04 09:04:24 AST] -- MobConnection::resetConnection(): Timeout reached when trying to connect to https://xxx/sdk/vimService
Perform the below steps:
1- Increased the timeout value from 180s to 360s in the file "vmware-collector.xml" allocated in /opt/APG/Collecting/VMWare-Collector/vmware-vcenter/conf 
  <connection timeout="360s">
        <connection-properties name="vcenter">xxxx</connection-properties>

2- Then go to /opt/APG/bin and execute the command  ./ service update collector-manager vmware-vcenter
3- Then start the service >> ./ service start collector-manager vmware-vcenter
4- Monitor the logs and verify that the error is gone
Article Properties
First Published Thu Mar 08 2018
14:05:37 GMT
Primary Product
ViPR SRM 4.0
ViPR SRM,ViPR SRM 4.2,ViPR SRM 4.1,ViPR SRM 4.0,Watch4net,Watch4net 6.6,Watch4net 6.5