Skip to main content
Code42 Support

View Code42 server log files

Applies to:
  • Code42 CrashPlan (previously CrashPlan PROe)

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.

Log file summary

The following table describes Code42 server log files that may help you troubleshoot your Code42 environment.

Log File Name Contents Rolls Over Versions
app.log1

Summary information about your Code42 environment that is written when the Code42 server starts

Never 1

com_backup42_app.log1

Detailed records of all Code42 server activity and backup activity

  • At 32 MB
  • When the Code42 server restarts
10
history.log1

High-level events, such as:

  • Administration console configuration changes and the user that made them
  • Device authentication attempts
  • User, organization, and device creation
  • Code42 server restarts
  • Errors
At 256 MB 2

recovery.log1

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
rest.log1

Records of Code42 API requests

Daily All
request-yyyy_mm_dd.log1 Records of web requests to the administration console Daily 365
upgrade.log2 Records all Code42 server upgrade actions, including errors Never
(subsequent upgrades are appended)
1

1 indicates the log is located in the Code42 server's log directory
2 indicates the log is located in the Code42 server's upgrade directory

Where to start
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:

  • Linux: /var/log/proserver
    Applies to Code42 servers installed as root on Ubuntu
  • Windows: C:\Program Files\CrashPlan PROe Server\logs
  • OS X: /Library/Logs/PROServer

Code42 server upgrade directories

The Code42 server's upgrade.log file is located in the Code42 server's upgrade directory:

  • Linux: /opt/proserver/upgrade
    Applies to Code42 servers installed as root on Ubuntu
  • Windows: C:\Program Files\CrashPlan PROe Server\upgrade
  • OS X: /Applications/PROServer.app/Content/Resources/Java/upgrade

View Code42 server log files

There are two ways to view Code42 server log files:

View log files from the administration console

The administration console can display the following log files:

  • com_backup42_app.log
  • history.log
  • request-yyyy_mm_dd.log
Viewing other log files
To view the other Code42 server log files, you must access them on the host server.

To view a log file in the administration console:

  1. Sign in to the administration console.
  2. Go to Settings > Server.
  3. Next to System logs, click View.
    The Logs view appears.
    Administration console logs view
  4. 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.

Managed Private Cloud customers
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 Code42 CrashPlan support or CrashPlan for Small Business (previously CrashPlan PRO) support.

View a log file

Use one of the following options if you want 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 & OS X: From the command line, use the less command to view the file:
    less <filename>
  • Windows: From PowerShell, use the Get-Content cmdlet to view the file:
    Get-Content <filename> | Out-Host -paging

View log file updates in real time

Use one of the following options if you want to print updates to a log file in real time from a command line:

  • Linux & OS X: From the terminal, use the tail command to view updates to the log file in real time:
    tail -f <filename>
  • Windows: From PowerShell, use the Get-Content cmdlet 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.