Ransomware attackers specifically target and attempt to destroy backup systems to increase the probability of payment. Hardening your system is critical. Please ensure you have reviewed your platform security using the Security Hardening Checklist
Cohesity

COHESITY Documentation

Explore our documentation to get started, discover products & new features, access troubleshooting guides, register sources, platforms support.

Products
Data Security Alliance
Visit Cohesity.com
Demos
Support
Blogs
Developers
Partner Portals
Cohesity Community
© 2026 Cohesity, Inc. All Rights Reserved.
Terms of Use|
Privacy Policy|
Legal|
  1. Home
  2. IT Analytics Help
  3. Section XVI. System Administration
  4. Working with Log Files
  5. Portal log files

Portal log files

Key log files are managed by a logging subsystem, which manages the log size, and rolls and deletes old files. Log files are used only as an audit trail for troubleshooting, so they can be deleted safely.

Locations in this table represent the default locations, but these may have been modified for your environment.

Table: Portal Log Files

Log File Name

Default Location

Description

access.log

C:\opt\apache\logs

/opt/apache/logs

Standard Web server access log.Use this log to analyze request processing time, request method, page hit count, and session activity.

itanalyticsagent-access*.log

C:\opt\apache\logs

/opt/apache/logs

Standard Web Server access log. Logs all http transactions between the Data Collector and the Web Server.

itanalyticsagent-error*.log

C:\opt\apache\logs

/opt/apache/logs

/opt/tomcat/logs

Standard Web Server error log file. Logs http transaction errors between the Data Collector and the Web Server.

itanalyticsportal-access*.log

C:\opt\apache\logs

/opt/apache/logs

Standard Web Server access log. Logs all http transactions between the browser based Portal application and the Web Server.

itanalyticsportal-error*.log

C:\opt\apache\logs

/opt/apache/logs

Standard Web Server error log file. Logs http transaction errors between the browser-based Portal application and the Web Server.

itanalyticsStartup.log

/opt/aptare/logs

Contains startup and shutdown information for the Portal services (e.g., from running /opt/aptare/bin/xxx start|stop), If a service fails to start, check this log file for details.

audit.log

C:\opt\tomcat\logs\

/opt/tomcat/logs/

By default, logs portal login requests and user impersonations in the Portal web browser window. Modifications can be made to log additional user activity.

See Logging user activity in audit.log.

catalina.out

C:\opt\tomcat\aptare-instances\portal\logs

/opt/tomcat/aptare-instances/portal/logs

For Tomcat, this is the standard destination log file for System.out and System.err console messaging.

datarcvr*.log

C:\opt\tomcat\logs

/opt/tomcat/logs

Detailed logging for the data receiver - the servlet that receives data from the Data Collectors on the Primary Server(s). Logs Data Collector connection requests/issues, data received, and database interaction.

See Portal and data collector log files - reduce logging.

error.log

C:\opt\apache\logs

/opt/apache/logs

Standard Web Server error log file.

portal*.log

C:\opt\tomcat\logs\

/opt/tomcat/logs/

Detailed logging for the Portal servlet. Logs portal login requests, user impersonations, portal reports that are run - basically all actions in the Portal web browser window. Database problems are displayed as SQL exceptions and often list the associated Oracle error number (ORA nnn).

See Portal and data collector log files - reduce logging.

stderr.log

C:\opt\tomcat\logs\

/opt/tomcat/logs/

High-level log messaging for Tomcat.

Tomcat Standard Log Files (Portal)

admin*.log

C:\opt\tomcat\aptare-instances\portal\logs

/opt/tomcat/aptare-instances/portal/logs

Apache Tomcat provides several file handlers that write messages to application-specific log files. The date is appended to admin in the name of the file.

catalina*.log

C:\opt\tomcat\aptare-instances\portal\logs

/opt/tomcat/aptare-instances/portal/logs

Apache Tomcat provides several file handlers that write messages to application-specific log files. The date is appended to catalina in the name of the file.

host-manager*.log

C:\opt\tomcat\aptare-instances\portal\logs

/opt/tomcat/aptare-instances/portal/logs

Apache Tomcat provides several file handlers that write messages to application-specific log files. The date is appended to host-manager in the name of the file.

manager*.log

C:\opt\tomcat\aptare-instances\portal\logs

/opt/tomcat/aptare-instances/portal/logs

Apache Tomcat provides several file handlers that write messages to application-specific log files. The date is appended to manager in the name of the file.

Tomcat Standard Log Files (Data Receiver)

admin*.log

C:\opt\tomcat\aptare-instances\agent\logs

/opt/tomcat/aptare-instances/agent/logs

Apache Tomcat provides several file handlers that write messages to application-specific log files. The date is appended to admin in the name of the file.

catalina*.log

C:\opt\tomcat\aptare-instances\agent\logs

/opt/tomcat/aptare-instances/agent/logs

Apache Tomcat provides several file handlers that write messages to application-specific log files. The date is appended to catalina in the name of the file.

host-manager*.log

C:\opt\tomcat\aptare-instances\agent\logs

/opt/tomcat/aptare-instances/agent/logs

Apache Tomcat provides several file handlers that write messages to application-specific log files. The date is appended to host-manager in the name of the file.

manager*.log

C:\opt\tomcat\aptare-instances\agent\logs

/opt/tomcat/aptare-instances/agent/logs

Apache Tomcat provides several file handlers that write messages to application-specific log files. The date is appended to manager in the name of the file.

Feedback

Was this page helpful?
Previous

Find the event / meta collector ID

Next

Managing Apache Log Files

Feedback

Was this page helpful?