How to enable Aria Automation Orchestrator SSL debug logging.

Products

• VCF Operations/Automation (formerly VMware Aria Suite)

Issue/Introduction

In a situation where a connection to an external host (like REST or PowerShell) has failed with insufficient information. Then it may be required to enable wire debug logging to get more details to why the connection has failed.

Environment

Aria Automation Orchestrator 8.x

Resolution

To enable debug logging for Aria Automation Orchestrator

1. Ensure a valid Backup / Snapshot has been taken before proceeding further
2. Connect to the Aria Automation Orchestrator or Aria Automation host via SSH (For a cluster the configuration is only required once)
3. Open the editor to update the deployment: 

   kubectl edit deployment -n prelude vco-app

4. Find the section of JVM_OPTS
5. Append the section using a new line with this parameter, use whitespace as separator:

   -Djavax.net.debug=all

   

6. Once completed exit the editor by entering :wq This will restart the Orchestrator Service!
7. Use this command to monitor the service restart is completed: 

   kubectl -n prelude get pods -l app=vco-app --wo wide

8. Once completed to monitor the logs use this command: 

   kubectl -n prelude logs -l app=vco-app -c vco-server-app -f

9. To revert the change remove the parameter reverting steps 3-6 or use the re-deploy all services using the below script: This will restart all services and the portal will be unavailable until completed! 

   /opt/scripts/deploy.sh

 

For more information on how to read the logging please refer to this Oracle Java documentation: Debugging SSL/TLS Connections

 

The JVM_OPTS parameter can be adjusted to only track SSL related message:

-Djavax.net.debug=ssl:handshake:record:session:trustmanager:verbose

To read more about all available parameters please refer to this Oracle Java documentation: Debugging Utilities