Logging and Troubleshooting Information for Omnissa Access

After you install Omnissa Access, you can use different approaches when you encounter issues. For example, you can troubleshoot issues by accessing the logs, you can restart a service, and you can implement the workarounds for known issues.

Omnissa Access Service Logs

This procedure provides you access to the service logs.

Procedure:

Open the Nomad interface.
Go to Jobs.
Select service.
Find Allocation ID.
Log in to the node.
Navigate to: /opt/nomad/alloc/<allocation-id>/alloc/logs.

Restart a Service

This procedure restarts the service of your choice.

Procedure:

Stop and purge job in Nomad UI
Redeploy service from the Bootstrap node:
```
wso services deploy -s <service-name>
```

A Service is in a Not Ready State

A service can enter a NOT_READY state at any time, not only during initial deployment. This can also happen after a completed deployment or during an upgrade.

If you deployed manually, see the wso access check-service-readiness step in Deploy the Omnissa Access and Infrastructure Services.

The troubleshooting steps below apply regardless of which path you used.

Problem and Cause

The specific problem and cause varies according to the service. See the solution provided below for an example of how to solve this type of issue.

Solution

The following example demonstrates how you can use Nomad to troubleshoot the greenbox service when it is listed in a NOT_READY state. Other services may store their logs under a different task name or directory, so use this as a model for the general approach rather than an exact match for what you will see in your environment.

Run from the bootstrap node the following command: sudo cat /opt/wss/<cluster_name>/cp-cluster/cp-cluster.env to reveal the Nomad URL and token, then open the Nomad UI in a browser and click Jobs.
Click greenbox-job.
Under Recent Allocations, right-click each allocation ID that appears in the ID column and select Open Link in New Tab.
For each Allocation tab opened, click the Files tab and navigate to alloc > data and open the appropriate log file, most likely the largest sized file and the most recently modified, such as greenbox_web.log.
Again, for each Allocation tab opened, click Tail, then click the play icon to stream the log live, and review the output to identify the cause of the failure.

Was this page helpful?