vCenter Interoperability throws an error "Unable to connect to the Analytics service"

Products

• VMware vCenter Server

Issue/Introduction

Symptoms:

• Accessing vCenter Interoperability section throws an error "Unable to connect to the Analytics service. Make sure that Analytics service on this machine is running and that the healthchecks for appliance are green."
• Validating Analytics service, shows up and running
• In the var/log/vmware/analytics/analytics.log mentions entries similar to:

2024-06-29T10:39:36.252+02:00 phStageLogDrainerTaskExecutor-2  WARN  vmware.ph.upload.rest.ProxyAwareHttpExecutor Failed 3 of 3 attempts to get manifest from VMware server. The reason for the last failure was (enable 'debug' level logging to see the error of every failed attempt): com.vmware.ph.client.api.exceptions.PhClientConnectionException: org.bouncycastle.tls.TlsFatalAlert: handshake_failure(40).

Error Screenshot: 

 

Environment

VMware vCenter Server 7.0.x

Resolution

Verify if proxy server is configured by checking the /etc/sysconfig/proxy file in vCenter server. If the proxy is configured then follow below steps to add vCenter FQDN and IP address in the NO_PROXY list

• Create a backup of the proxy file:

# cp /etc/sysconfig/proxy /storage/core/proxy.bak

• Edit the file:
  

  # vi /etc/sysconfig/proxy
  
  

• Find the line starting with NO_PROXY
• Edit this line and add both the <FQDN> and <IP address> of the vCenter Server to this line

NOTE: Please be aware that the entries in NO_PROXY need to be separated by a comma followed by a single space. Only using a comma as separator is not enough.

Example of the proxy file :

# Enable a generation of the proxy settings to the profile.
# This setting allows to turn the proxy on and off while
# preserving the particular proxy setup.
#
PROXY_ENABLED="no"

# Some programs (e.g. wget) support proxies, if set in the environment.
-
-
-
-
-
NO_PROXY="localhost, 127.0.0.1, vCenter_FQDN, IP_Address"