4.0

Orchestrator Log Files
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.
Table 9-2. 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 \configuratio
n\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.
vCenter Orchestrator Administration Guide
74 VMware, Inc.