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

Configuring syslog logging for hostd and vpxa management agents on ESXi/ESX (1017658)

Last Updated: 3/20/2024Categories: How toTotal Views: 30641Language:
Chinese (Simplified)JapaneseEnglish

1 like this article

Subscribe to get an email
newsletter with new updates

1 people found this helpful Please provide article feedback:

Purpose

The hostd and vpxa management agents on VMware ESXi/ESX 3.5 to 4.1 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.

Caution: The management agents log verbosely. Directing management agent logs to the local syslog facilities may cause /var/log/messages to fill and rotate quickly. This may impair the ability to troubleshoot issues. VMware recommends that you use this configuration only if the local syslog service on ESXi/ESX has been configured to route logging messages over the network to a remote syslog log collector.

For more information on configuring an ESXi/ESX host to log to a remote syslog collector, see Enabling syslog on ESX (1005030) or Enabling syslog on ESXi 3.5 and 4.x (1016621).

The defaults may not be appropriate under some circumstances. For example:

ESX with remote syslog services. The remote syslog service could facilitate analysis or persistent storage of management agent logs centrally, in addition to kernel logs.

ESXi with no remote syslog services. The local syslog daemon will store and rotate 8 MB of logs, which will be exhausted quickly by verbose management agent logs. For example, see The vpxa management agent fills local logs in ESXi 4.1 (1030672).

The verbosity of each component is controlled within the same configuration file. For more information on changing the logging level for management agents, see Increasing vCenter Server and ESXi/ESX logging levels (1004795).

Resolution

The routing of hostd and vpxa management agent logging to the local syslog service is controlled by a pair of configuration files.

Note: Changing the configuration requires restarting the management agents. Review Restarting the Management agents on an ESXi or ESX host (1003490) before making any configuration change.

The default configuration differs between ESX and ESXi, and between versions. The hostd management agent logs to syslog by default in ESXi 3.5 to 4.1, and does not in ESX 3.5 to 4.1. The vpxa management agent logs to syslog by default on ESXi managed by vCenter Server 4.1 and higher, and does not for earlier versions of vCenter Server or any version of ESX.

This functionality can be enabled or disabled individually for hostd and vpxa on ESXi/ESX 3.5 or higher by modifying an XML configuration file for each management agent. The configuration file can be copied off-host using the vifs.pl vSphere Command Line Interface utility, modified locally, and copied back. Alternatively, the file can be modified in-place from the console of the ESX host. For more information on the options, see Editing configuration files in VMware ESXi and ESX (1017022).

To change the configuration for one of the agents:

Open the management agent configuration file in a text editor. If you are using vCLI vifs.pl or another remote method, copy the configuration file from the ESXi/ESX host. For more information, see Editing configuration files in VMware ESXi and ESX (1017022).

hostd management agent

Configuration file is located at /etc/vmware/hostd/config.xml

Exposed via API and vCLI as /host/hostAgentConfig.xml

vpxa management agent

Configuration file is located at /etc/opt/vmware/vpxa/vpxa.cfg

Exposed via API and vCLI as /host/vpxa.cfg

Locate the <log> section within <config> in the configuration file. For example:

<config>
...
<log>
...
<level>verbose</level>
...

Add or modify 5 lines within the <log> section of the configuration file, specifying three options:

/config/log/outputToSyslog

Whether the management agent will log to syslog. Use true or false.

/config/log/syslog/ident

The service identifier which will be prefixed on each log message. Use Hostd or Vpxa.

/config/log/syslog/facility

The syslog facility that will be assigned to each log message. Use local3 for ESX 3.5, and local4 for all other versions of ESXi/ESX.

Note: On ESX 3.5, the local4 facility is utilized by storageMonitor. Use local3 instead.

Note: For agent versions which do not output to syslog by default, these tags are not present in the configuration file and must be added.

For example:

<config>
...
<log>
...
<level>verbose</level>

<outputToSyslog>true</outputToSyslog>
<syslog>
<ident>Hostd</ident>
<facility>local4</facility>
</syslog>

</log>

Save the configuration file. If you are using vCLI vifs.pl or another remote method, copy the modified configuration file back to the ESXi/ESX host.

On ESXi, the configuration change is backed up at shutdown or on the hour. To save the configuration change immediately, use the TSM console to run the command:

/sbin/auto-backup

Restart the management agent to reload the configuration. For more information, see Restarting the Management agents on an ESXi or ESX host (1003490).

Note: In ESXi 4.1 Update 2 and later releases, vpxa and hostd logs are not written to /var/log/messages . You can enable this by setting logall=non_zero_value in the file /etc/syslog.conf and restarting the syslogd service. For example, to revert to the previous behavior, add the option logall=1 to /etc/syslog.conf. For more information, see The vpxa management agent fills local logs in ESXi 4.1(1030672).

Related Information

For more information on configuring an ESXi/ESX host to log to a remote syslog collector, see Enabling syslog on ESX (1005030) or Enabling syslog on ESXi 3.5 and 4.x (1016621).

For information regarding logging in ESXi 4.1, see The vpxa management agent fills local logs in ESXi 4.1 (1030672).

Restarting the Management agents in ESXi
Increasing VMware vCenter Server and VMware ESX/ESXi logging levels
Enabling syslog on ESX
Enabling syslog on ESXi 3.5 and 4.x
Editing configuration files in VMware ESXi and ESX
The vpxa management agent fills local logs in ESXi 4.1
ESXi/ESX で hostd および vpxa 管理エージェントの syslog ログを構成する
为 ESXi/ESX 上的 hostd 和 vpxa 管理代理配置 syslog 日志记录

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
Chinese (Simplified)JapaneseEnglish

Attachments

Additional Resources

KB
•
Como verificar o espaço livre em disco suficiente para a máquina virtual ESX/ESXi (1003755)

KB
•
La pestaña Summary del host ESXi 5.0 informa la siguiente advertencia: System logging not Configured on host (2006834)

KB
•
使用准虚拟 SCSI 适配器的 Windows 2008 R2 虚拟机报告“遇到操作系统错误 1117”错误 (2004578)

KB
•
A guia Summary do host do ESXi 5.0 exibe o aviso: Logon do sistema não configurado no host (2006834)

Results 1-4 of 4

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware vSphere ESXi

VMware ESX Server

Related Versions:

VMware ESXi 4.1.x Installable

VMware ESXi 4.1.x Embedded

VMware ESXi 4.0.x Installable

VMware ESXi 4.0.x Embedded

VMware ESXi 3.5.x Installable

VMware ESXi 3.5.x Embedded

VMware ESX Server 3.5.x

VMware ESX 4.1.x

VMware ESX 4.0.x

view all

Take Our Survey

Support Assistant