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

Table 1. Orchestrator Log Files list

File Name

Location

Description

scripting.log

  • If you installed Orchestrator standalone: install_directory\VMware\Orchestrator\app-server\logs

  • If you deployed the Orchestrator Appliance: /var/log/vco/app-server

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

server.log

  • If you installed Orchestrator standalone: install_directory\VMware\Orchestrator\app-server\logs

  • If you deployed the Orchestrator Appliance: /var/log/vco/app-server

Provides information about all activities on the Orchestrator server. Analyze the server.log file when you debug Orchestrator or any application that runs on Orchestrator.

wrapper-configuration.log

On the Orchestrator standalone: install_directory\VMware\Orchestrator\configuration\logs

Provides information about the configuration and validation of each component of Orchestrator.

catalina.out

On the Orchestrator Appliance: /var/log/vco/configuration/

Provides information about the configuration and validation of each component of Orchestrator in the Orchestrator Appliance. The file is analogous to wrapper-configuration.log in the Windows installation of Orchestrator.

vso.log

  • If you installed Orchestrator standalone: install_directory\VMware\Orchestrator\apps

  • If you installed the Orchestrator client on a Mac machine: install_directory

  • If you installed the Orchestrator client on a Linux machine: install_directory

This is the Orchestrator client log. Use this log to detect connection problems with the server and detect events on the client side. It is not available for the Orchestrator Appliance.

access.yyyy-mm-dd.log

  • If you installed Orchestrator standalone: install_directory\VMware\Orchestrator\configuration\logs

  • If you deployed the Orchestrator Appliance: /var/log/vco/app-server

This log lists the elements that are needed to load and display the pages of the Orchestrator configuration interface. It contains a history of the tasks you performed while configuring Orchestrator along with the time they were completed. However, the log does not display the value of the changed parameters. Use this log to identify changes in the behavior of the Orchestrator server after a restart.

wrapper.log

If you installed Orchestrator standalone: install_directory\VMware\Orchestrator\app-server\bin

Provides a part of the boot log information of the server. Use this log to check whether the VMware vRealize Orchestrator Server service was started by the wrapper or by a user.

metrics.log

  • If you installed Orchestrator standalone: install_directory\VMware\Orchestrator\app-server\logs

  • If you deployed the Orchestrator Appliance: /var/log/vco/app-server

Contains runtime information about the server. The information is added to this log file once every 5 minutes.

localhost_access_log.txt

  • If you installed Orchestrator standalone: install_directory\VMware\Orchestrator\app-server\logs

  • If you deployed the Orchestrator Appliance: /storage/log/vmware/vco/app-server

This is the HTTP request log of the server.