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

Skip to main content

My Subscriptions

Loading

Knowledge Base

Troubleshooting the vCenter Server Agent when it does not start (1006128)

Last Updated: 3/20/2024Categories: TroubleshootingTotal Views: 114959Language:
Chinese (Simplified)JapaneseEnglish

3 like this article

Subscribe to get an email
newsletter with new updates

3 people found this helpful Please provide article feedback:

Symptoms

Unable to connect with the VMware Infrastructure /vSphereClient to the ESX host from VirtualCenter/vCenter Server.

Unable to directly connect with the vSphere Client to the ESX host.

Purpose

The vCenter Server Agent, also referred to as vpxa or the vmware-vpxa service, is what allows a vCenter Server to connect to a ESX host. Specifically, vpxa is the communication conduit to the hostd, which in turn communicates to the ESX kernel. This article provides troubleshooting steps for when the vpxa does not start.

Resolution

Validate that each troubleshooting step below is true for your environment. Each step provides instructions or a link to a document, in order to eliminate possible causes and take corrective action as necessary. The steps are ordered in the most appropriate sequence to isolate the issue and identify the proper resolution.

Log in to the ESX host service console and acquire root privileges.

Verify that the installation of the vCenter Server agent is not corrupted. From the command-line, run:

rpm -V VMware-vpxa

There is only output from the command if errors are found. For example:

rpm -V VMware-vpxa
S.5....T /opt/vmware/vpxa/sbin/vpxa

This indicates that the Size, MD5 checksum, and Timestamp for the file /opt/vmware/vpxa/sbin/vpxa are wrong, and therefore the installation of the VMware-vpxa package is corrupt. If you do have a corrupted installation, proceed to the next step to re-install the VirtualCenter agent.

Note: The Red Hat Package Manager does not keep tabs on dynamic configuration files, so you cannot see errors about them.

Verify that the vCenter Server agent is the correct version. For more information, see Verifying and reinstalling the correct version of VMware VirtualCenter Server agent (1003714).

Verify that there is adequate disk space available on the ESX host service console. For more information, see Investigating disk space on an ESX/ESXi host (1003564).

Verify that no processes are over utilizing the resources on the ESX host service console. For more information, see Checking for resource starvation of the ESX service console (1003496).

Verify that the vpxa process is not exceeding allocated memory.

Change to the the vpxa log directory, run:

cd /var/log/vmware/vpxa

View the vpxa log file, run:

more vpxa.log

Examine the log for errors. For example:

[2007-07-28 17:57:25.416 'Memory checker' 5458864 error] Current value 143700 exceeds hard limit 128000. Shutting down process.
[2007-07-28 17:57:25.420 'Memory checker' 3076453280 info] Resource checker stopped.

These errors indicate there is not enough service console memory allocated for the vCenter Server agent. This may be due to one or more causes:

Management agents are installed in the ESX service console

Backup agents are installed in the ESX service console

To resolve this problem, increase the service console memory. For more information, see Increasing the amount of RAM assigned to the ESX Server Service Console (1003501).

Related Information

Checking for resource starvation of the ESX Service Console
Increasing the amount of RAM assigned to the ESX Server service console
Verifying and reinstalling the correct version of the VMware vCenter Server agents
vCenter Server Agent が起動しないときのトラブルシューティング
vCenter Server Agent 不启动时对其进行故障排除

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
Chinese (Simplified)JapaneseEnglish

Attachments

Additional Resources

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

Result 1 of 1

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware VirtualCenter

VMware vCenter Server

VMware ESX Server

Related Versions:

VMware VirtualCenter 2.5.x

VMware VirtualCenter 2.0.x

VMware vCenter Server 4.1.x

VMware vCenter Server 4.0.x

VMware ESX Server 3.5.x

VMware ESX Server 3.0.x

VMware ESX 4.1.x

VMware ESX 4.0.x

Take Our Survey

Was this article helpful?

YES

NO

Copyright © 2005-2024 Broadcom. All Rights Reserved. The term “Broadcom” refers to Broadcom Inc. and/or its subsidiaries.

Terms of Use

Your California Privacy Rights

Privacy

Accessibility

Cookie Settings

Support Assistant