Artikelnummer: 518895

printer Druck mail E-Mail

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

Hauptprodukt: ViPR SRM 4.0

Produkt: ViPR SRM mehr …

Zuletzt veröffentlicht: 23 Mär 2020

Artikeltyp: Break Fix

Veröffentlichter Status: Online

Version: 4

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

Artikelinhalt

Problem


- 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
 
Ursache
Lösung
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">
        <url>https://xxxx/sdk/vimService</url>
        <username>xxxx</username>
        <password>xxxx</password>
        <connection-properties name="vcenter">xxxx</connection-properties>
    </connection>

2- Then go to /opt/APG/bin and execute the command  ./manage-modules.sh service update collector-manager vmware-vcenter
3- Then start the service >> ./manage-modules.sh service start collector-manager vmware-vcenter
4- Monitor the logs and verify that the error is gone
Hinweise

Problem


- 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
 
Ursache
Lösung

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">
        <url>https://xxxx/sdk/vimService</url>
        <username>xxxx</username>
        <password>xxxx</password>
        <connection-properties name="vcenter">xxxx</connection-properties>
    </connection>

2- Then go to /opt/APG/bin and execute the command  ./manage-modules.sh service update collector-manager vmware-vcenter
3- Then start the service >> ./manage-modules.sh service start collector-manager vmware-vcenter
4- Monitor the logs and verify that the error is gone

Hinweise

Article Attachments

Anhänge

Anhänge

Artikeleigenschaften

Erstveröffentlichung

Do Mär 08 2018 14:05:37 GMT

Erstveröffentlichung

Do Mär 08 2018 14:05:37 GMT

Diesen Artikel bewerten

Präzise
Nützlich
Leicht verständlich
War dieser Artikel hilfreich?
0/3000 characters