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

The vpxa management agent fills local logs in ESXi 4.1 (1030672)

Last Updated: 3/20/2024Categories: How toTotal Views: 12087Language:
FrenchEnglish

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Symptoms

The local /var/log/messages or /scratch/log/messages log file in vSphere ESXi 4.1 may become filled with messages from the vpxa management agent similar to:

Vpxa: 2010-03-15T13:33:34.856Z [28649B90 verbose 'Default'] [VpxaHalServices] VmGuestDiskChange Event for vm(7) 32

The log messages from the hostd and vpxa management services on an ESXi host might fill up the /var/log/messages file. As a result, you might not find sufficient kernel logs to troubleshoot kernel issues.

Purpose

The vpxa management agent on VMware ESX and ESXi 3.5 and newer can be configured to direct their logs to the local syslog daemon in addition to their own local logging in the /var/log/vmware/ directory. In vSphere 4.1, the default configuration includes log messages from the vpxa management agent in syslog, and stores them in the /var/log/messages or /scratch/log/messages log files along with log messages emitted by the VMkernel and other components.

Resolution

This issue is resolved in ESXi 4.1 Update 2. For more information about this version, see the VMware ESXi 4.1 Update 2 Release Notes. You can download the latest release from the VMware downloads page.

Starting with release ESXi 4.1 Update 2, vpxa and hostd logs are not written to the /var/log/messages file. You can enable this functionality by setting logall=<non zero> in the /etc/syslog.conf file and restarting the syslogd service. For example, to revert to the previous behavior, add the option logall=1 to the /etc/syslog.conf file.

On ESXi 4.1 releases prior to ESXi 4.1 Update 2, the vpxa management agent logs verbosely. If the ESXi host has not been configured to route logs to a remote syslog collector, only the local logs are available. The local messages logs managed by syslog have a maximum size of 8 MB before rotation, which will be exhausted quickly if vpxa log messages are included. This may impair the ability to troubleshoot issues with other components.

To work around this issue on ESXi 4.1 releases prior to ESXi 4.1 Update 2, use one of these options:

Configure the ESXi 4.1 host's syslog service to route logs to a remote syslog collector.

Configure the remote syslog collector split or filter the vpxa and other log messages with an appropriate retention policy for the environment. The local syslog logs in messages contain a mixture of messages from vpxa and other components, and may not be usable for troubleshooting purposes. When troubleshooting issues, review the log messages stored by the remote syslog collector. For more information, see Enabling syslog on ESXi 3.5 and 4.x (1016621).

Configure the ESXi 4.1 host's vpxa agent to not emit logs via syslog.

The local syslog logs in messages will only contain messages from other components. The vpxa management agent stores its own log files in the /var/log/vmware/vpx/ directory, with their own retention and rotation policy. When troubleshooting issues, review the log messages saved locally. For more information, see Configuring syslog logging for hostd and vpxa management agents on ESXi/ESX (1017658).

Related Information

For more information on the layout and location of logs files in VMware ESXi, see Location of ESXi 3.5-4.1 log files (1021801).

For translated versions of this article, see:

Français: Désactivation de la sortie hostd et vpxa dans le journal /var/log/messages de l'ESXi (1037664)

Enabling syslog on ESXi 3.5 and 4.x
Configuring syslog logging for hostd and vpxa management agents on ESXi/ESX
Location of ESXi 3.5-4.1 log files
The vpxa management agent fills local logs in ESXi 4.1
Désactivation de la sortie hostd et vpxa dans le journal /var/log/messages de l'ESXi

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
FrenchEnglish

Attachments

Additional Resources

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

KB
•
Windows XP/Vista/7 上で実行される VMware Infrastructure Client を使用してリモートの CD-ROM ドライブに接続できない (1009065)

KB
•
无法使用在 XP/Vista/7 上运行的 VMware Infrastructure Client 连接到远程 CD-ROM 驱动器 (1009065)

KB
•
カスタム SSL 証明書の追加後に VMware vCenter Server プラグインが失敗する (1017577)

Results 1-4 of 4

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

Related Versions:

Take Our Survey

Support Assistant