printer Imprimir

Visión de los clientes


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

Número de artículo: 518895
Versión: 4
Tipo de artículo: Break Fix
Última publicación: 23 Mar 2020
Resumen:
Problema


- 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
 
Causa
Resolución
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
Notas
Archivos adjuntos
Propiedades del artículo
Fecha de la primera publicación Thu Mar 08 2018
14:05:37 GMT
Producto principal
ViPR SRM 4.0
Producto
ViPR SRM,ViPR SRM 4.2,ViPR SRM 4.1,ViPR SRM 4.0,Watch4net,Watch4net 6.6,Watch4net 6.5