Loading

×Sorry to interrupt
CSS Error

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

Skip to main content

My Subscriptions

Loading

Knowledge Base

Location of vRealize Orchestrator log files (1010956)

Last Updated: 7/10/2020Categories: InformationalTotal Views: 20145Language:
Chinese (Simplified)English

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Purpose

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 using a specific script or tool for each product.

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).

Resolution

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.

Notes:

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.

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 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.

server.log

app-server\server\vmo\log

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.

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 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.

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 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 stop an installation or the installation fails.

Related Information

vRealize Orchestrator 日志文件的位置

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
Chinese (Simplified)English

Attachments

Additional Resources

KB
•
End Of General Availability of the Free vSphere Hypervisor (ESXi 7.x and 8.x) (2107518)

KB
•
Download and Install VMware Fusion (2014097)

Results 1-2 of 2

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware vCenter Orchestrator

Related Versions:

VMware vCenter Orchestrator 4.2.x

VMware vCenter Orchestrator 4.1.x

VMware vCenter Orchestrator 4.0.x

Take Our Survey

Copyright © 2024 VMware, Inc. All rights reserved.

Terms of Use

Your California Privacy Rights

Privacy

Accessibility

Cookie Settings

Support Assistant