VMware Technical Support routinely requests diagnostic information from you when a support request is handled. This diagnostic information contains product-specific logs and configuration files from the host on which the product is run. The information is gathered by using a specific script tool for each product.

Orchestrator Log Files

Filename

Location

Description

boot.log

install_directory\app-server\server\vmo\log

Provides details about the boot state of the JBoss server. Check the boot.log file when a file from JBoss is missing or the installation is corrupted.

boot-state.log

install_directory\app-server\server\vmo\log

Provides details about the boot state of the vCO server. If the server boots properly, an entry about the vCO server version is written. By default, this information is also included in the server.log file.

script-logs.log

install_directory\app-server\server\vmo\log

Provides a list of the completed workflows and actions. The scripts-logs.log file lets you isolate workflow runs and actions runs from normal vCO operations. This information is also included in the server.log file.

server.log

install_directory\app-server\server\vmo\log

Provides information about everything that happens on the vCO server. It contains the entries from the boot-state.logfile and script-logs.log file, as well as other information. Check the server.log file when you debug vCO or any application that runs on vCO.

vco-configuration.log

install_directory\configuration\jetty\logs

Provides information about the configuration and validation of each component of vCO. This is the jetty service running on the vCO server. The request.log file in the same folder might be more useful to view the history of actions taken during the configuration of vCO.

vso.log

install_directory\apps

This is the vCO client log. Use this log to detect connection issues with the server and events on the client side.

yyyy-mm-dd.request.log

install_directory\configuration\jetty\logs

This log lists the elements that are needed to load and display the pages of the vCO configuration interface. It keeps a history of the actions that were taken during the configuration of vCO and the time when they were completed. Use this log to identify changes in the behavior of the vCO server after a restart. However, the log does not display the value of the changed parameters.

wrapper.log

install_directory\app-server\bin

Provides information from the server.log file. Use this log to check whether the VMware vCenter Orchestrator Server service was started by the wrapper or by a user.

vCenter_Orchestrator_InstallLog.log

Check file location in the message.

This log is created when you cancel the vCO installation or when the installation fails.