Download the AP-Log Archive.zip file from the support settings in the Admin UI. The ZIP file contains all logs from your Unified Access Gateway appliance.

Set the Logging Level

You can manage the log level settings from the admin UI. Go to the Support Settings page and select Log Level Settings. The log levels that can be generated are INFO, WARNING, ERROR, and DEBUG. The logging level is set by default to INFO.

A description of the type of information that the log levels collect follows.

Table 1. Logging Levels

Level

Type of Information Collected

INFO

The INFO level designates information messages that highlight the progress of the service.

ERROR

The ERROR level designates error events that might still allow the service to continue running.

WARNING

The WARNING level designates potentially harmful situations but are usually recoverable or can be ignored.

DEBUG

Designates events that would generally be useful to debug problems, to view or manipulate the internal state of the appliance, and to test the deployment scenario in your environment.

Collect Logs

Download the log ZIP files from the Support Settings section of the admin UI.

These log files are collected from the /opt/vmware/gateway/logs directory on the appliance.

The following tables contain descriptions of the various files included in the ZIP file.

Table 2. Files That Contain System Information to Aid in Troubleshooting

File Name

Description

Linux Command (if applicable)

rpm-version.log

Version of the UAG appliance (2.8, 2.9, 3.0 etc).

ipv4-forwardrules

IPv4 forwarding rules configured on the appliance.

df.log

Contains information about disk space usage on the appliance.

df -a -h --total

netstat.log

Contains information on open ports and existing TCP connections.

netstat -an

netstat-s.log

Network stats (bytes sent/received etc) from the time of creation of the appliance.

netstat -s

netstat-r.log

Static routes created on the appliance.

netstat -r

uag_config.json, uag_config.ini

Entire configuration of the Unified Access Gateway appliance, showing all of the settings as a json and an ini file.

ps.log

Includes processes running at the time of downloading logs.

ps -elf --width 300

ifconfig.log

Network interface configuration for the appliance.

ifconfig -a

free.log

RAM availability at the time of downloading logs.

free

top.log

Sorted list of processes by memory usage at the time of downloading logs .

top -b -o %MEM -n 1

Table 3. Log Files for Unified Access Gateway

File Name

Description

Linux Command (if applicable)

w.log

Information about uptime, the users currently on the machine, and their processes.

w

service.log

List of services currently running on the appliance

service --status-all

supervisord.log

Supervisor (manager for the Edge Service manager, admin and a AuthBroker) log.

esmanager-x.log, esmanager-std-out.log

Edge service manager log(s), showing back end processes performed on the appliance.

authbroker.log

Contains log messages from the AuthBroker process, which handles Radius and RSA SecurID authentication.

admin.log, admin-std-out.log

Admin GUI logs. Contains log messages from the process that provides the Unified Access Gateway REST API on port 9443.

bsg.log

Contains log messages from the Blast Secure Gateway.

SecurityGateway_xxx.log

Contains log messages from the PCoIP Secure Gateway.

utserver.log

Contains log messages from the UDP Tunnel Server.

appliance-agent.log

Contains log messages from the VMware Tunnel agent (which starts up server and proxy).

haproxy.conf

Contains log messages from the HA proxy configuration for TLS port sharing, if configured.

vami.log

Contains log messages from running vami commands to set network interfaces during deployment.

aw-content-gateway.log, aw-content-gateway-wrapper.log, aw-0.content-gateway-YYYY-mm.dd.log.zip

Contains log messages from AirWatch Content Gateway.

admin-zookeeper.log

Contains log messages related to the data layer that is used to store the Unified Access Gateway configuration.

tunnel.log

Contains log messages from the tunnel process that is used as part of the XML API processing. You must have Tunnel enabled in the Horizon settings in order see this log.

The log files that end in "-std-out.log" contain the information written to stdout of various processes and are usually empty files.