Log files can help you troubleshoot issues related to installation, display protocols, and feature components. You can create a configuration file to configure the verbosity level.

Log File Locations

Table 1. Horizon Client for Linux Log Files
Type of Logs Directory Path File Name
Installation /tmp/vmware-root/



Horizon Client UI /tmp/vmware-username/ vmware-horizon-client-pid.log
PCoIP client /tmp/teradici-username/ pcoip_client_YYYY_MM_DD_XXXXXX.log
Real-Time Audio-Video /tmp/vmware-username/ vmware-RTAV-pid.log
USB redirection /tmp/vmware-root/



VChan /tmp/vmware-username/ VChan-Client.log
Note: This log is created when you enable RDPVCBridge logs by setting " export VMW_RDPVC_BRIDGE_LOG_ENABLED=1".
Remote MKS (mouse-keyboard-screen) logs /tmp/vmware-username/




VdpService client /tmp/vmware-username/ vmware-vdpServiceClient-pid.log
Tsdr client /tmp/vmware-username/ vmware-ViewTsdr-Client-pid.log

Log File Configuration

You can use a configuration property, view.defaultLogLevel, to set the verbosity level for client log files, from 0 (collect all events) to 6 (collect only fatal events).

For USB-specific logs, you can use the following command-line commands:

vmware-usbarbitrator --verbose
vmware-view-usbd -o log:trace

Collecting a Log Bundle

The log collector is located at /usr/bin/vmware-view-log-collector. To use the log collector, you must have execute permissions. You can set permissions from the Linux command line by entering the following command:

chmod +x /usr/bin/vmware-view-log-collector

You can run the log collector from the Linux command line by entering the following command: