SovLabs Support Portal will be moving soon!

SovLabs Support

Submit a Ticket My Tickets
Welcome
Login

How To: vRA vRO logging

Overview

In this how to we will cover capturing logs for your workflows, enabling enhanced logging and capturing logs from vRO and vRA

Considerations

  • Have licensed SovLabs

  • Have access to the Orchestrator client

  • Have access to the vRO Control Center (VCO)

  • Have access to the vRA appliance management console (VAMI)

Procedure

Enabling enhanced logging in vRO

SovLabs provides enhanced logging in vRO to capture extra information that can help with diagnosing issues.  This can be enabled through the HTML Orchestrator client  or through the Legacy Java Client.  We will walk through both ways.

Increasing log rotation size

  1. Log into your vRO Control Center (Address would be like https://<vroFQDN>:8283/vco-controlcenter/config/login.html)


  2. Under Log click on Configure Logs


  3. Amend the Max file size (MB) from the default value (5) to a larger value.  This can be changed back after you have completed your logging
    Click on Save


  4. Once saved you will see a green bar saying "Saved successfully"

  5. You can now log out.

Enabling enhanced logging through the HTML Orchestrator Client

  1. Log into your Orchestrator client (Address is usually like https://<vROFQDN>:8283/vco-controlcenter/client/

  2. On the left menu, click on Workflows

  3. Under workflows, search for Logging

  4. Look for the Workflow called Enable SovLabs Logging and click on Run

  5. You will see the next screen and under General you will see the workflow has a status of Completed

  6. To disabled enhanced logging, simply select the Disable SovLabs Logging and run this workflow to disable

NOTE: Enhanced logging comes up as disabled when vRO service vco-server is restarted or if the appliance is rebooted.

Enabling enhanced logging through the Legacy Orchestrator Client

  1. Log into your Legacy Orchestrator client


  2. Click on Workflows then navigate through to SovLabsvRA UtilitiesLogControlEnable SovLabs Logging

  3. Right click and select Start Workflow.

  4. Once run you can click on the workflow run and click on Logs. You will now see the log says verbose:true which means it is enabled

  5. To disabled enhanced logging, simply select the Disable SovLabs Logging and run this workflow to disable

NOTE: Enhanced logging comes up as disabled when vRO service vco-server is restarted or if the appliance is rebooted.

Checking logs in vRO for a given workflow

In the control center

  1. Log into your control center and on the left under Activity click on Workflow Runs

  2. Locate the workflow you would like to view the logs for and click on the Name

  3. You will see the workflow and the error message, click on Logs

  4. On the right click the drop down next to Severity.  This will give you several options.  You can either leave it on all or Debug.  In this example lets click Debug

  5. Now you will see the Debug logs . If you have enabled enhanced logging there will be additional information on the failure in here.  Please review this log for the failed workflow for clues as to why your deployment has failed.  You can use the errors to search our KB articles to see if we have a solution already documented.

  6. If you need to send these logs to us (Or we have requested these logs) you can click on Copy Logs and paste them into your ticket.

  7. You can also use the Copy Logs and paste them into a text editor like Notepad++ to make it easier to review

In the Legacy java client

  1. Once logged into your java client, Click on Workflows

  2. On the left under SovLabs, locate the module you want to check against, for example, ActiveDirectory, you would navigate to AD machineBuilding

  3. Scroll down to the run you wish to review the logs for and then click on the run name

  4. In the right pane, click on Logs and in the drop down, select Debug.

  5. Now you will see the Debug logs . If you have enabled enhanced logging there will be additional information on the failure in here.  Please review this log for the failed workflow for clues as to why your deployment has failed.  You can use the errors to search our KB articles to see if we have a solution already documented.

  6. If you need to send these logs to us (Or we have requested these logs) you can click on Copy Logs icon and paste them into your ticket.

  7. You can also use the Copy Logs and paste them into a text editor like Notepad++ to make it easier to review

Generating log bundles for vRA with embedded vRO

Sometimes the workflow logs even with enhanced logging don't provide enough info , so generating the vra/vro log bundle will provide the most amount of information

  1. Access your VAMI (vrealize appliance management interface).  Usually at address https://<vraserverFDQDN>:5480 and log in

  2. Click on vRA and the Logs

  3. Click on Create Support Bundle and click on OK in the pop up to generate the logs

  4. You will see that it will show as collecting logs.  Depending on your environment, this could be 5 - 10 minutes so please be patient.

  5. Once bundle is ready, click on Download log bundle

  6. The log bundle will be several hundred Megabytes through to Gigabytes, again, depending on your environment. 

    NOTE: If you are running an embedded vRO server then this log bundle will contain your vRO logs.  If you have an external vRO server then you will have to export logs from your vRO servers. Please read on for how to export logs from your vRO servers.

  7. A list of relevant logs can be found in VMWare KB https://kb.vmware.com/s/article/2141175

    Generally we suggest reviewing the following logs: :

    /storage/log/vmware/vcac/catalina.out (vRealize Automation Server log)
    /storage/log/vmware/vco/app-server/server.log (vRealize Orchestrator Server log)
    /storage/log/vmware/vco/configuration/catalina.out (vRealize Orchestrator Configuration log)

    There are generally .out files but a series of .log files that will help (of the same names). 

    vRO logs would be under vcacsupport <Data> \ var \ log \ vmware \ vco \ app-server and the logs will be of the same name as above.

Generating log bundles for an external vRO

If you are running an external vRO server you will need to generate the logs from your vRO servers (If clustered, on each server)

  1. Log into your vRO control center (Address is usually https://<vroFQDN>:8283/vco-controlcenter/config/login.html)

  2. Under Log, click on Export Logs

  3. Click on Export Logs

  4. Depending on how much information is in your vRO, this may take a few minutes to export and could be 20mb or a few hundred mb

  5. Once downloaded, this will be the logs from your vRO.  For logs that are valuable see VMWare KB https://docs.vmware.com/en/vRealize-Orchestrator/7.3/com.vmware.vrealize.orchestrator-install-config.doc/GUID-0BA1B08B-7A94-45AD-ADFF-3440529E5F59.html

    Generally the logs we recommend reviewing are as follows:

    /var/log/vco/app-server/scripting.log
    /var/log/vco/app-server/server.log
    /var/log/vco/app-server/catalina.out

    These reside in the Zip file name \ vro server name \ ServerLogs in your vRO log bundle.

Additional information

SovLabs Knowledge base : https://support.sovlabs.com/a/solutions

Did you find it helpful? Yes No

Send feedback
Sorry we couldn't be helpful. Help us improve this article with your feedback.