vCenter Server fails to start VMOMI services after upgrading vCenter Server

Products

• VMware vCenter Server

Issue/Introduction

Symptoms:

• When attempting to connect to vCenter Server using the vSphere Client, you see the error:
  
  vSphere Client could not connect with the vCenter Server
  Details: A connection failure occurred (Unable to connect to the remote server)
  
  
  
• vCenter Server fails to start VMOMI services after upgrading.
• In the C:\ProgramData\VMware\VMware VirtualCenter\Logs\vpxd.log file, you see the entries similar to:
  
  02640 info 'VmdbAdapter'] Using new VMDB VMOMI serialization format
  02640 error 'App'] [VpxdVmomi] Failed to start VMOMI services: Invalid argument : getaddrinfo returned more than one IPv4 address for addr='localhost' port=8085
  
  [<YYYY-MM-DD><time> 06216 info 'VmdbAdapter'] Using new VMDB VMOMI serialization format
  [<YYYY-MM-DD><time> 06216 error 'App'] [VpxdVmomi] Failed to start VMOMI services: Resource is already in use: 127.0.0.1:8085
  [<YYYY-MM-DD><time> 06216 info 'App'] Shutting down VMware VirtualCenter...
  [<YYYY-MM-DD><time> 06976 info 'App'] [VpxdHostCnx] Host connection reaper thread exiting
  [<YYYY-MM-DD><time> 06216 info 'App'] [VpxdServer] Exit done.
  </time></time></time></time></time>
  
  
• In the C:\ProgramData\VMware\VMware VirtualCenter\Logs\vpxd.log file on vCenter Server 5.x, you see the entries similar to:
  
  <YYYY-MM-DD><time> [01644 error 'Default'] [VpxdVmomi] Failed to start VMOMI services: Invalid argument : No IP addresses found for addr='localhost', port=8085 : (0) 'The operation completed successfully. '
  <YYYY-MM-DD><time> [01644 info 'Default'] Shutting down VMware VirtualCenter...</time></time>
  
  Note: The preceding log excerpts are only examples. Date, time, and environmental variables may vary depending on your environment.

Environment

VMware vCenter Server 5.1.x
VMware vCenter Server 6.0.x
VMware vCenter Server 4.1.x
VMware vCenter Server 5.0.x
VMware vCenter Server 5.5.x
VMware vCenter Server 4.0.x

Cause

This issue occurs because the getAddrinfo function returns more than one IP address for the localhost.

Resolution

To resolve this issue, ensure that the hosts file, located at C:\windows\system32\drivers\etc\hosts, does not contain multiple hostnames set for the 127.0.0.1 loopback.

Sometimes, administrators edit the host file and add multiple entries for localhost to block Malware and Spyware applications.

This can also be caused by the port 8085 being in use by another application or service.

To check if port 8085 is being used by another application or service:

1. Click Start > Run, type cmd and click OK.
2. Run this command to find the PID (Process ID) that is using port 8085:
   
   netstat -ano | find /N "8085"
   
   
   
3. Look for port 8085 and make a note of the PID (last column).
4. Open Task Manager and click the Services tab.
5. Find the service that has the PID noted above and either disable or change the port that is used by this service.
   
   Note: The PID column may need to be added to the view.

Additional Information

For more information on ports in use by another application, see Port already in use when installing VMware vCenter Server (4824652).
vCenter Server 在升级后无法启动 VMOMI 服务
Port already in use when installing VMware vCenter Server