vmware-updatemgr service continually crashes navigating to Lifecycle Manager shows: An unexpected error has occurred.

Products

• VMware vCenter Server

Issue/Introduction

Following patching to vCenter Server 8.0 Update 3g 8.0.3.00600 24853646 the vmware-updatemgr service crashes when started, users face inability to access Lifecycle Manager in the vCenter with it showing the following error in the UI An unexpected error has occurred or Problem occurred while connecting to the Lifecycle Manager server.

In the vmware-vum-server.log located at /var/log/vmware/vmware-updatemgr/vum-server you see the following error:

<time stamp>Z error vmware-vum-server[14045] [Originator@6876 sub=CertsCache] [CertsCache 360] Connecting to http://localhost:1080/idm/tenant/vsphere.local/certificates?scope=TENANT&granularity=LEAF failed, err: curl_easy_perform() failed: cURL Error: Timeout was reached, Operation too slow. Less than 1 bytes/sec transferred the last 5 seconds
<time stamp>Z error vmware-vum-server[14045] [Originator@6876 sub=CertsCache] [CertsCache 561] Error encountered while downloading and parsing certificates

In the vsphere_client_virgo.log located at /var/log/vmware/vsphere-ui/logs you see the error:

[<time stamp>Z] [WARN ] -nio-127.0.0.1-5090-exec-164  com.vmware.vum.client.remoting.impl.VumServiceImpl                Error is not SecurityError, no re
login will be attempted com.vmware.vim.vmomi.client.common.UnexpectedStatusCodeException: Unexpected status code: 503

Environment

vSphere vCenter Server 8.0.x

Cause

Misconfiguration of the proxy settings on the vCenter server.

Specifically missing comma between FQDN's detailed in the NO_PROXY section of the proxy file located at /etc/sysconfig

Example healthy file:

# Example: NO_PROXY="www.me.de, do.main, localhost"
NO_PROXY=", localhost, 127.0.0.1"

Example missing comma:

# Example: NO_PROXY="www.me.de, do.main, localhost"
NO_PROXY=", localhost 127.0.0.1"

Resolution

Option 1:

1. Log into the vCenter vami on https://vCenterfqdn:5480
2. Select the Networking tab and check the section "Hosts and IP addresses excluded from proxy" under Proxy Settings
3. Edit and ensure all FQDN entries are comma delimited.

Option 2:

1. Open an SSH session to the vCenter server.
2. Edit the proxy file located on the vCenter at /etc/sysconfig
vi /etc/sysconfig/proxy
3. Ensure there is proper comma between FQDN's separating each entry
4. Restart services using:
   service-control --stop --all && service-control --start --all