Search the VMware Knowledge Base (KB)
View by Article ID
Location of vRealize Orchestrator log files (1010956)
This article discusses the content and purpose of each log file that can be collected for VMware vRealize Orchestrator (formerly known as VMware vCenter Orchestrator).
Each VMware vRealize Orchestrator (formerly known as VMware vCenter Orchestrator) log file serves a different purpose. Review the following to understand what each log file does.
- If you installed Orchestrator standalone, the default installation path is C:\Program Files\VMware\Orchestrator.
- If you installed Orchestrator with the vCenter Server installer, the default installation path is C:\Program Files\VMware\Infrastructure\Orchestrator.
- Log file paths listed are relative to the default installation path.
|boot.log||app-server\server\vmo\log||In this log you find details on the JBOSS boot, but nothing related to the vRealize Orchestrator server. It might be useful in cases where a file from JBOSS is missing or the install is corrupted. This kind of issue is very rare.|
|boot-state.log||app-server\server\vmo\log||In this log you will find the boot state of the vRealize Orchestrator server. If the server booted properly it writes an entry together with the vRealize Orchestrator version. This file can be useful as a summary of the boot of vRealize Orchestrator server. This is included by default in server.log.|
|scripts-log.log||app-server\server\vmo\log||This file contains the thread from all the executions of workflows and actions. It lets you isolate these executions from normal vRealize Orchestrator operations. You can find the same information in server.log. If you need to know which workflow was executed you need to look at server.log instead.|
This is the main log of vRealize Orchestrator server. It contains the same information as boot-state.log, scripts-log.log in addition to more data. Everything that happens on the vRealize Orchestrator server is seen here. When debugging vRealize Orchestrator or any application running on vRealize Orchestrator (such as LCM), this is the first log you should open.
|vmo-configuration.log||configuration\jetty\logs||In this log you find the configuration and validation of each component of vRealize Orchestrator. This is the jetty service running on the vRealize Orchestrator server. The file request.log, in the same directory, might be more useful if you want just a history of actions taken during configuration.|
Note: This path is not relative.
|This is the log file containing all the information about the installation of vRealize Orchestrator. It shows if vRealize Orchestrator was silently installed by vCenter or if it was an independent install. It also indicates if the configuration service was started at install or if it was left stopped for security reasons. This file is the only way to detect an issue during an installation.|
|vso.log||apps||This is the client log. It is mainly interesting for connection issues with the server and events on the client side.|
|yyyy-mm-dd.request.log||configuration\jetty\logs||This log shows all the elements that were needed to load and display the pages of the configurator. It keeps a history of which actions were taken for the configuration of vRealize Orchestrator and when they were done. This might be very useful to identify a change in the behavior of the vRealize Orchestrator server after a restart. However, it does not display the value of changed parameters, only that they were changed.|
The wrapper log contains some information that is also found in the server.log. However this is the only place you will be able to know if the VMware vRealize Orchestrator Server service was restarted by the wrapper or by a user.
|vCenter_Orchestrator_InstallLog.log||On the desktop of the user who installed Orchestrator.||This file is created if you abort an installation or the installation fails.|
Request a Product Feature
To request a new product feature or to provide feedback on a VMware product, please visit the Request a Product Feature page.