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

Enabling syslog on ESX (1005030)

Last Updated: 2/27/2013Categories: How toTotal Views: 27494Language:
Chinese (Simplified)JapaneseEnglish

2 like this article

Subscribe to get an email
newsletter with new updates

2 people found this helpful Please provide article feedback:

Purpose

All ESX/ESXi hosts run a syslog service (syslogd) which logs messages from the VMkernel and other system components to a file.

Note: In ESX, you must modify the remote host option in the /etc/syslog.conf file. The remote host options are:

Log file path – Specifies a datastore path to the file where syslogd logs all messages.

Remote host – Specifies a remote host to which syslog messages are forwarded. To receive the forwarded syslog messages, your remote host must have a syslog service installed.

Remote port – Specifies the port used by the remote host to receive syslog messages.

Resolution

To log events from an ESX host to a remote syslog server:

Log in to the ESX host as root using an SSH client.

Open the /etc/syslog.conf file using a text editor.

Add this entry at the end of the file:

*.* @IP_address_of_syslog-server

For example:

*.* @192.1.68.1

Note: If you are changing from the default syslog port 514 to a different port, the entry should appear similar to:

*.* @192.1.68.1:Port_Number

For example, if you are changing the port to 520, the entry should be:

*.* @192.1.68.1:520

It is not absolutely necessary to send all messages to a remote syslog server. Instead of using *.* in the example above, one could use *.warning or *.crit to only send messages of a certain level or higher.

The various syslog levels and their description are:

emerg – System is or will be unusable if situation is not resolved

alert – Immediate action required

crit – Critical situations

warning – Recoverable errors

notice – Unusual situation that merits investigation; a significant event that is typically part of normal day-to-day operation

info – Informational messages

debug – Verbose data for debugging

Restart the syslog daemon using the command:

service syslog restart

Run this command to check if the ESX firewall has been opened for the syslog traffic:

esxcfg-firewall -q|grep syslog

If the firewall is open, you see an output similar to:

syslog : port 514 udp.out

If the firewall is closed, you do not see any output.

To open the firewall on the ESX host for syslog traffic and to refresh the firewall, run this command:

esxcfg-firewall -o 514,udp,out,syslog && esxcfg-firewall -l

Related Information

Enabling syslog on ESXi 3.5 and 4.x
Configuring syslog on ESXi
ESX での syslog の有効化
在 ESX 上启用 syslog

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)

KB
•
Red Hat 仮想マシンでの VMware Tools の実行が次のエラーによって失敗した: upgrader.create に対して既存の RPC 登録を上書きしようとしています中断 (2011101)

KB
•
Yum リポジトリを使用した RHEL 6 での VMware Tools のインストールが失敗する (1036099)

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 ESX Server

Related Versions:

VMware ESX Server 3.5.x

VMware ESX Server 3.0.x

VMware ESX Server 2.5.x

VMware ESX Server 2.1.x

VMware ESX Server 2.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