vCenter Server 8.x services fail to start with a timeout error due to invalid syntax typo in /etc/sysconfig/proxy

Products

• VMware vCenter Server

Issue/Introduction

1. When a proxy server is configured in the vCenter Appliance Management Interface (VAMI), running service-control --all --start on the vCenter Server Appliance (VCSA) 8.x fails and throws a timeout error similar to:
   Service-control failed. Error: Failed to start services in profile ALL. RC=1, stderr=Failed to start sps, sca, cis-license, eam, vpxd-svcs, analytics, vc-ws1a-broker, vsm services. Error: Operation timed out
2. A storage space check (df -h) confirms that all partitions have sufficient free space, and all certificates are valid and unexpired.
3. Running the vCenter Diagnostic Tool (VDT) confirms a proxy validation failure:

[FAIL]    vCenter Proxy Check (Enabled)
          There is a proxy enabled for this vCenter, but the PNID or domain has not been included in the NO_PROXY list.
          In order to avoid issues with upgrades, skyline health, etc., please see the provided article.
          NO_PROXY list: ['www.me.de', 'do.main', 'localhost']
          
          Documentation:    https://knowledge.broadcom.com/external/article?legacyId=87793

Environment

VMware vCenter Server 8.x

Cause

This issue is caused by a syntax error (a typo) in the /etc/sysconfig/proxy file on the vCenter Server. Specifically, the letter 'Y' is missing from NO_PROXY, appearing instead as NO_PROX. (User modified the proxy with an incorrect NO_PROX configuration.)

Incorrect configuration:

# Example: NO_PROXY="www.me.de, do.main, localhost"
NO_PROX="dl.broadcom.com, localhost, 127.0.0.1, .*.#######.###, .*.#######.###"

Expected configuration (correct):

# Example: NO_PROXY="www.me.de, do.main, localhost"
NO_PROXY="dl.broadcom.com, localhost, 127.0.0.1, .*.#######.###, .*.#######.###"

Resolution

To resolve this issue, you must correct the syntax attribute inside the proxy configuration file and restart all services.

1. Log in to the vCenter Server Appliance via SSH using root credentials.

2. Back up the existing proxy configuration file:

   cp /etc/sysconfig/proxy /etc/sysconfig/proxy.bak
   

3. Open /etc/sysconfig/proxy using a text editor (such as vi):

   vi /etc/sysconfig/proxy
   

4. Locate the malformed line and change NO_PROX to NO_PROXY. 

   NO_PROXY
   

5. Restart all services

   service-control --stop --all && service-control --start --all