View Code42 server log files
Overview
Code42 server log files contain information that can help you troubleshoot problems in your Code42 environment. You can also use log files to determine what actions were taken by Code42 servers, devices, administrators, and users. This article describes the Code42 server log files and how to view them.
Code42 server log files
Code42 server log files record events that occur in day-to-day operation.
Log files roll over
To keep log file sizes under control, some log files "roll over" into a new log file after they reach a certain size, a specified length of time has passed, or the Code42 server is restarted.
- Logs appended with .0 represent the current version of the file.
- When logs roll over, the Code42 server increments the appended digit. For example, history.log.0 is the most recent history log, and history.log.1 is the previous version.
- For the request.log, previous versions append the date to the file name, formatted as request-yyyy_mm_dd.log. The request.log is the current version of the file.
Log file summary
The following table describes Code42 server log files that may help you troubleshoot your Code42 environment. Logs are located in the Code42 server's log directory.
| Log File Name | Contents | Rolls Over | Versions |
|---|---|---|---|
| app.log |
Summary information about your Code42 environment that is written when the Code42 server starts |
Never | 1 |
|
com_backup42_app.log |
|
10 | |
| history.log | At 256 MB | 2 | |
|
recovery.log (Versions earlier than 6.5 only) |
Changes made to the database; if the current database is lost, you may be able to recover using this log and the most recent database dump | At 128 MB | 2 |
| request.log | Daily | 365 | |
| stats.log |
|
32 MB | 9 |
| support_event.log (Versions7.0 and later) |
|
Daily | 365 |
| upgrade.log1 | Records all Code42 server upgrade actions, including errors | Never (subsequent upgrades are appended) |
1 |
1 The log is located in the Code42 server's upgrade directory.
When you're troubleshooting an issue, we recommend starting with history.log. If you need more information, try com_backup42_app.log next.
Log file directories
Most Code42 server log files are located in the Code42 server's log directory. The upgrade.log file is located in the Code42 server's upgrade directory.
Code42 server log directories
Code42 server log files are located in the log directory on the host server:
Code42 server upgrade directories
The Code42 server's upgrade.log file is located in the Code42 server's upgrade directory:
View Code42 server log files
There are two ways to view Code42 server log files:
View log files from the Code42 console
The Code42 console can display the following log files:
- com_backup42_app.log
- history.log
- request.log
To view the other Code42 server log files, you must access them on the host server.
To view a log file in the Code42 console:
- Sign in to the Code42 console.
- Go to Settings > Logs.
The Logs view appears.
3.png?revision=1&size=bestfit&width=1392&height=912)
- Select the log file that you want to view.
View log files on the host server
Code42 server log files are located on the host server.
You cannot access the file system of a managed appliance. If you need to view Code42 server logs to perform troubleshooting, contact our Customer Champions for support.
View a log file
Use one of the following options to view the state of the log file for a given point in time:
- All operating systems: Open the log file in the plain text editor of your choice.
- Linux: From the command line, use the
lesscommand to view the file:less <filename>
- Windows: From PowerShell, use the
Get-Contentcmdlet to view the file:Get-Content <filename> | Out-Host -paging
View log file updates in real time
Use one of the following options to print updates to a log file in real time from a command line:
- Linux: From the terminal, use the
tailcommand to view updates to the log file in real time:tail -f <filename>
- Windows: From PowerShell, use the
Get-Contentcmdlet to view updates to the log file in real time:Get-Content <filename> -Tail 10 -Wait
Send logs to a syslog server
If you prefer to centrally aggregate logs in your Code42 environment, you can configure your Code42 server to send logs to a syslog server.