Unable to connect to vSphere LifeCycle Manager - " Problem occurred while connecting to the Lifecycle Manager server"
search cancel

Unable to connect to vSphere LifeCycle Manager - " Problem occurred while connecting to the Lifecycle Manager server"

book

Article ID: 345515

calendar_today

Updated On:

Products

VMware vCenter Server

Issue/Introduction

  • While trying to connect to the vSphere LifeCycle Manager, the following error occurred : " Problem occurred while connecting to the Lifecycle Manager server"

 

  • vSphere-UI is trying to connect to the vum over the port 8094 and 9099 as specified by the lookup service.

    vsphere_client_virgo.log

    YYYY-MM-DDTZhh-mm-ss] [WARN ] http-nio-5090-exec-41   com.vmware.vum.client.remoting.impl.VumServiceImpl Error is not SecurityError, no relogin will be attempted com.vmware.vim.vmomi.client.exception.ConnectionException: https://<vc-fqdn>:8094/vci
    /sdk invocation failed with "org.apache.http.conn.HttpHostConnectException: Connect to <vc-fqdn>:8094 [<vc-fqdn>/127.0.0.1] failed: Connection refused (Connection refused)"

    Example:

    root@vmware [ / ]# netstat -pano | grep 8094  ----> ( no output, hence the connection is refused on port 8094)
    root@vmware [ / ]#

     

Service registrations : 

Name: cis.updatemgr.ServiceName
Description: cis.updatemgr.ServiceDescription
Service Product: com.vmware.vum
Service Type: client
Service ID: 31xxxxx-309d-464e-9753-bxxxxxxxx
Site ID: xxxx
Node ID: 1dxxxxx-064d-11e6-8da3-0050568xxxxx
Owner ID: vpxd-extension-b644c460-064c-11e6-8555-0050568169d8@vsphere.local
Version: 7.0.3.x

 

Endpoints: 

https:/<vc-fqdn>:8094/vci/sdk
https:/<vc-fqdn>:9099/vci/downloads/vum-htmlclient.zip
https:/<vc-fqdn>:443/vci/sdk
https:/<vc-fqdn>:443/esx-lcm
https:/<vc-fqdn>:443/sca/resourcebundle/updatemgrResourceBundle.zip
http:/<vc-fqdn>:9084/vci/downloads/health.xml

 

Default endpoints for com.vmware.vum on a vCenter 7u3g :  https:/<vc-fqdn>:8094/vci/sdk 

https:/<vc-fqdn>:9087/vci/downloads/vum-htmlclient.zip
https:/<vc-fqdn>:443/esx-lcm
https:/<vc-fqdn>:443/sca/resourcebundle/updatemgrResourceBundle.zip
https:/<vc-fqdn>:443/vci/sdk
http:/<vc-fqdn>:9084/vci/downloads/health.xml

  • The vSphere-UI is trying to connect to the vum over the port 8088 and 9087 as specified by the lookup service and as mentioned in the /usr/lib/vmware-visl-integration/firstboot/ports.json. Since this is a tcp connection, envoy/reverse proxy service should be listening to accept the connection.
    Execute the command to identify which service on the vCenter is listening on:

    netstat -pano | grep <port number>

      • Example:

    root@vmware [ / ]# netstat -pano | grep 8084
    tcp        0      0 0.0.0.0:8084            0.0.0.0:*               LISTEN      46306/envoy      off (0.00/0/0)
    tcp6       0      0 :::8084               :::*                    LISTEN      46306/envoy      off (0.00/0/0)
    root@vmware [ / ]# netstat -pano | grep 8088  ----> ( no output, hence the connection is refused on port 8088)
    root@vmware [ / ]#

The vsphere_client_virgo.log shows the similar log entries mentioned below:

[YYYY-MM-DDTZhh-mm-ss] [WARN ] http-nio-5090-exec-41   com.vmware.vum.client.remoting.impl.VumServiceImpl Error is not SecurityError, no relogin will be attempted com.vmware.vim.vmomi.client.exception.ConnectionException: https://<vc-fqdn>:8088/vci
/sdk invocation failed with "org.apache.http.conn.HttpHostConnectException: Connect to <vc-fqdn>:8088 [<vc-fqdn>/127.0.0.1] failed: Connection refused (Connection refused)"
        at com.vmware.vim.vmomi.client.common.impl.ResponseImpl.setError(ResponseImpl.java:261)
        at com.vmware.vim.vmomi.client.http.impl.HttpExchangeBase.setResponseError(HttpExchangeBase.java:356)
        at com.vmware.vim.vmomi.client.http.impl.HttpExchange.invokeWithinScope(HttpExchange.java:57)
        at com.vmware.vim.vmomi.client.http.impl.TracingScopedRunnable.run(TracingScopedRunnable.java:31)
        at com.vmware.vim.vmomi.client.http.impl.HttpExchangeBase.run(HttpExchangeBase.java:57)
        at com.vmware.vim.vmomi.client.http.impl.HttpProtocolBindingBase.executeRunnable(HttpProtocolBindingBase.java:227)
        at com.vmware.vim.vmomi.client.http.impl.HttpProtocolBindingImpl.send(HttpProtocolBindingImpl.java:114)

Environment

VMware vCenter Server 7.0.x
VMware vCenter Server 8.0.x

Cause

This issue occurs when the VC tries to connect to VUM server on incorrect port such as 8094, 8088 as specified in the lookup service. However it should be listening to 8084 port.

Resolution

  • Ensure there is a valid snapshot of vCenter (s) and/or a valid backup before proceeding
  • Verify if the port number is present on any of the above files and correct the same 
    • grep -rnw /etc -e 8088 ( or 8094) 
      grep -rnw /usr -e 8088 ( or 8094)
  • Replace the port number from 8088 to 8084 on the below files using vi editor 
    • /usr/lib/vmware-updatemgr/bin/vci-integrity.xml
      /usr/lib/vmware-updatemgr/bin/extension.xml
      /usr/lib/vmware-updatemgr/config/updatemgr-config.props
      /usr/lib/vmware-updatemgr/bin/configvalues.txt
      /etc/vmware/appliance/firewall/vmware-updatemgr
      /etc/vmware/install-defaults/updatemgr.ext.soapPort
      /etc/vmware/install-defaults/appliance.net.ports
Powered by Wolken Software