The Software Client for macOS writes log files that document its processes and interactions with other services such as brokers and agents. These files are invaluale in diagnosing problems. This page describes how logs are handled and where they can be found.
Software Client for macOS log files are located within the user’s Home Library folder, which is hidden by default. The recommended way to access Home Library files is to use the macOS Console.
You can also display log files in a macOS terminal window.
To display log files using the macOS Console:
- To open the Console, go to the Applications > Utilities folder, and then double-click Console.
- In the FILES section of the Log List pane on the left, navigate to the following folder: ~/Library/Logs/Teradici/PCoIPClient
- Select the desired log file to view its contents in the main pane.
- To copy the contents:
- Click anywhere in the log contents, and then select Edit > Select All.
- Select Edit > Copy.
- Paste the contents into an email or text file.
To display log files in a macOS terminal window:
To open a terminal window, go to the Applications > Utilities folder, and then double-click Terminal.
Navigate to the PCoIP Software Client log folder by typing the following command at the command line prompt:
lsto display the list of log files.
To view the contents of a log file, use any macOS command-line editor to open it.
Log verbosity is defined by a level, respresented by an integer from 0 to 4:
0: Critical messages only
1: Error messages and higher
2: Info messages and higher (default)
3: Debug messages and higher
4: All messages (maximum verbosity)
The default setting is
2, recording informational messages and higher.
The log level can be changed in any of the following ways:
- Via command-line launch: This method provides the log level inline during a command line launch; see Log Level in the configuration section for details.
- Via the client UI:
- From the client's menu icon, click Settings.
- Set the log level as desired.
- Click Save.
Tip: Reporting issues to support
When you are reporting an issue to support, set the log level to
3 (debug) first, and then reproduce the issue and create a support bundle. This will capture much more detail than the default setting, making diagnostics more effective.