Support > Knowledge Base
Knowledge Base
Search the Knowledge Base: |
Search the Knowledge Base: |
Orchestrator log files
Purpose
This article discusses the content and purpose of each log file that can be collected for VMware vCenter Orchestrator.
Resolution
Each VMware vCenter Orchestrator log file serves a different purpose. Review the following to understand what each log file does.
Notes:
- The default installation path of VMware vCenter Orchestrator is C:\Program Files\VMware\Orchestrator.
- Log file paths listed are relative to the default installation path.
| File | Default Location | Explanation |
| boot.log | app-server\server\vmo\log | In this log you find details on the JBOSS boot, but nothing related to the vCO 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 vCO server. If the server booted properly it writes an entry together with the vCO version. This file can be useful as a summary of the boot of vCO 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 vCO 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. |
| server.log | app-server\server\vmo\log |
This is the main log of vCO server. It contains the same information as boot-state.log, scripts-log.log in addition to more data. Everything that happens on the vCO server is seen here. When debugging vCO or any application running on vCO (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 vCO. This is the jetty service running on the vCO server. The file request.log, in the same directory, might be more useful if you want just a history of actions taken during configuration. |
| vmware_orchestrator_installer_output.txt |
C:\tmp
Note: This path is not relative. |
This is the log file containing all the information about the installation of vCO. It shows if vCO 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 vCO and when they were done. This might be very useful to identify a change in the behavior of the vCO server after a restart. However, it does not display the value of changed parameters, only that they were changed. |
| wrapper.log | app-server\bin |
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 vCenter 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. |
Feedback
Actions
- KB Article: 1010956
- Updated: Aug 14, 2009