Configuring MC Settings > Managing MC Logs
Managing MC Logs
The MC VERSION page displays the version of the MC that you are currently running and also lets you select the level of diagnostic logging for the MC. You can access this page by clicking SETTINGS from the MC's top menu and then clicking the VERSION menu in the left pane.
Note: The MC release version is also displayed on the dashboard.
Figure 6-5: MANAGEMENT CONSOLE VERSION and DIAGNOSTIC LOGGING Page
Locating the MC's Log Files
All MC logs are located in the MC's VM in its /opt/teradici/log directory. You can access these files by logging in to your MC VM console using vSphere Client or an SSH client.
The MCS's log directory contains the following files:
- console.log: Logs information about the MC's front-end console. In this release, its level is set to Info and cannot be changed.
- daemon.log.<date>: Logs information about the MC's back-end daemon. You can set a diagnostic log level for the MC's daemon process.
- daemon-startup.log: Logs information about when the MC's daemon starts up or stops.
- daemon.log.<date>.gz: Contains a gzip archive file for any daemon.log file that has reached 100 MB. These files are zipped to save space on the VM.
Setting the MC's Diagnostic Log Level
The MC's daemon process has two log levels that you can set:
- Info: Logs informational messages and events at a coarse-grained level.
- Trace: Logs finer-grained informational messages and events.