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 logging for VMware vCloud Director cells (1026815)

Last Updated: 6/1/2020Categories: InformationalTotal Views: 30654Language:
English

1 like this article

Subscribe to get an email
newsletter with new updates

1 people found this helpful Please provide article feedback:

Purpose

This article discusses the different log files in vCloud Director, their locations, the different logging levels and how to increase the log file sizes and the number of copies to keep.

Increasing the amount of diagnostic data (log file size and the number of logs to keep) may be required to troubleshoot a problem with vCloud Director.

Resolution

Log Locations

For vCloud Director version 1.5 and forward, the logs are stored in /opt/vmware/vcloud-director/logs

Configuration File

For vCloud Director version 1.5 and forward, the log configuration file is located in /opt/vmware/vcloud-director/etc/. The log configuration file is called log4j.properties.

Logging Levels

These six logging levels can be defined:

FATAL – logs very severe error events that may cause the application to fail

ERROR – logs error events that might still allow the application to continue running

WARN – logs potentially harmful situations and warnings

INFO – logs informational messages that highlight the progress of the application at a coarse-grained level

DEBUG – logs informational events that are most useful to debug an application at a fine-grained level

TRACE – logs informational events at a level more fine-grained than DEBUG logging

To change the logging level:

Caution: Before making any changes to the /opt/vmware/vcloud-director/etc/log4j.properties file, VMware recommends that you make a backup copy.

Open the /opt/vmware/vcloud-director/etc/log4j.properties file in a text editor (such as vi or nano).

Locate this section:

# Default vCloud loggers log4j.logger.com.vmware.vcloud=DEBUG log4j.logger.com.vmware.ssdc=DEBUG

Replace DEBUG and ERROR with one of the other logging levels. The following example will set vcloud and sddc to TRACE level.

For example:

log4j.logger.com.vmware.vcloud=TRACE log4j.logger.com.vmware.ssdc=TRACE

Now we need to change how the log file records information. Locate the section starting with:

# appender for all log requests with level >= DEBUG

The last line of the section configures the level of logging the file will capture. This needs to be changed to match the most verbose level. In the list of logging levels at the top of this document, TRACE is the most verbose and FATAL is the least verbose.

log4j.appender.vcloud.system.debug.threshold=TRACE

If you choose a new logging level that is more verbose, you may need to increase the number of log backups and or the size of the log files.

Locate the lines:

log4j.appender.vcloud.system.debug.MaxFileSize=
log4j.appender.vcloud.system.debug.MaxBackupIndex=

Change the default settings.

This example allows the log files to grow to 25 MB before they will rollover and keeps the last 5 logs:

log4j.appender.vcloud.system.debug.MaxFileSize=25000KB
log4j.appender.vcloud.system.debug.MaxBackupIndex=5

Save the file and the settings should be applied immediately.

The Log4J.properties does not have explicit lines for changing the size and amount of logs that are kept.

They use the following configuration properties:

vcloud.http.log.maxFileSize (default=5*1024*1024)

vcloud.http.log.maxTotalLogSize (default=10*5*1024*1024)

vcloud.http.log.retainDays (default=5)

Related Information

For information on collecting the logs, see Collecting diagnostic information for VMware vCloud Director (1026312).

Collecting diagnostic information for VMware vCloud Director 1.x / 5.x

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

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

KB
•
Download and Install VMware Fusion (2014097)

Results 1-2 of 2

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware Cloud Director

Related Versions:

Take Our Survey

Support Assistant