Loading

×Sorry to interrupt
CSS Error

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

My Subscriptions

Loading

Knowledge Base

vCenter Server fails to start VMOMI services after upgrading vCenter Server (1013240)

Last Updated: 3/1/2017Categories: TroubleshootingTotal Views: 19084Language:
Chinese (Simplified)English

1 like this article

Subscribe to get an email
newsletter with new updates

1 people found this helpful Please provide article feedback:

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.

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:

Click Start > Run, type cmd and click OK.

Run this command to find the PID (Process ID) that is using port 8085:

netstat -ano | find /N "8085"

Look for port 8085 and make a note of the PID (last column).

Open Task Manager and click the Services tab.

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.

Related 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

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
Chinese (Simplified)English

Attachments

Additional Resources

KB
•
End Of General Availability of the Free vSphere Hypervisor (ESXi 7.x and 8.x) (2107518)

KB
•
打开虚拟机控制台失败并出现错误：无法连接到 MKS: 连接到 /bin/vmx 进程时出错。 (2065135)

KB
•
vCenter Server および vmkernel ログで次のメッセージが報告される: RAM ディスク 'root' がいっぱいです (2033073)

Results 1-3 of 3

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware vCenter Server

Related Versions:

VMware vCenter Server 6.0.x

VMware vCenter Server 5.5.x

VMware vCenter Server 5.1.x

VMware vCenter Server 5.0.x

VMware vCenter Server 4.1.x

VMware vCenter Server 4.0.x

Take Our Survey

Support Assistant