Skip to content

Page permalink

Always use the following permalink when referencing this page. It will remain unchanged in future help versions.

https://docs.sophos.com/nsg/sophos-firewall/19.0/Help/en-us/webhelp/onlinehelp/index.html?contextId=tools-troubleshooting-logs-report

Consolidated troubleshooting report (CTR)

To enable the support team to troubleshoot system issues, you can generate a consolidated troubleshooting report (CTR). The encrypted file includes a file with the system's current status and log files with details, such as the active processes and resource usage.

The firewall generates the file with the name: CTR_<APPKEY>_<MM_DD_YY>_<HH_MM_SS>

  • APPKEY is the device key of the device for which the report is generated.
  • MM_DD_YY is the date (month, date, year) on which the report is generated.
  • HH_MM_SS is the time (hour, minute, second) at which the report is generated.

Generate a CTR

The CTR can contain the system snapshot and all the log files. You can generate a CTR and send it to Sophos Support to diagnose and troubleshoot an issue.

To generate a CTR, do as follows:

  1. Turn on Generate CTR for.
  2. Select System snapshot to generate snapshots to show the system issues.

  3. Select Log files to generate all the log files.

    Note

    Some log files in the CTR only show the number of log lines specified on the CLI. See How to generate a CTR.

  4. Enter a reason for generating the CTR.

  5. Click Generate.

When you generate a log files CTR, all *.log files are collected, in addition to the following files:

  • access_server.log.0
  • applog.log.0
  • awarrenhttp.log.0
  • awed.log.0
  • charon.log.0
  • csc.log.0
  • garner.log.0
  • heartbeatd.log.0
  • ips.log.0
  • iview.log.0
  • msync.log.0
  • networkd.log.0
  • npu_syslog.log.0
  • nSXLd.log.0
  • postgres.log.0
  • red.log.0
  • reportdb.log.0
  • reverseproxy.log.0
  • smtpd_main.log.0
  • sslvpn.log.0
  • syslog.log.0
  • syslog-ng.log.0
  • tomcat.log.0
  • u2d.log.0
  • up2date_av.log.0
  • xgs-healthmond.log.0
  • xgs-host.log.0
  • xgs-npu-fw.log.0
  • xgs-pport-wait.log.0

Note

CTR collects all 134 .log files in SFOS 19.0 MR1.

Detailed logs

You can increase the number of log lines in the CTR for some files. You can also turn on debug mode to get debug-level logs for some files.

Log lines in CTR

By default, the CTR only includes 1,000 log lines for the service subsystem logs. You can increase this limit to 10,000 lines on the CLI. The log files and the number of lines they show in the CTR are as follows:

  • Default subsystems: These log files always include all the log lines.
  • Service subsystems: These log files are limited to the configured number of log lines.

To increase the CTR limit, sign in to the CLI, enter 4 for Device console, and enter the following command:

system diagnostics ctr-log-lines <number>

Note

The line limit in log files only applies to the CTR. You can get the complete log file from the CLI. See Log file details.

Debug-level logs

Turn on debug mode for each subsystem for which you want to generate debug-level logs.

Note

To save disk space, we recommend that you turn off debug mode after troubleshooting. See How to generate a CTR.

More resources