Log files reference
StorageGRID provides logs that are used to capture events, diagnostic messages, and error conditions. You might be asked to collect log files and forward them to technical support to assist with troubleshooting.
The logs are categorized as follows:
The details provided for each log type are for reference only. The logs are intended for advanced troubleshooting by technical support. Advanced techniques that involve reconstructing the problem history using the audit logs and the application log files are beyond the scope of these instructions. |
Access the logs
To access the logs, you can collect log files and system data from one or more nodes as a single log file archive. Or, if the primary Admin Node is unavailable or unable to reach a specific node, you can access individual log files for each grid node as follows:
-
Enter the following command:
ssh admin@grid_node_IP
-
Enter the password listed in the
Passwords.txt
file. -
Enter the following command to switch to root:
su -
-
Enter the password listed in the
Passwords.txt
file.
Export logs to the syslog server
Exporting the logs to the syslog server provides these capabilities:
-
Receive a list of all Grid Manager and Tenant Manager requests, in addition to S3 and Swift requests.
-
Better visibility into S3 requests that return errors, without the performance impact caused by audit logging methods.
-
Access to HTTP-layer requests and error codes that are easy to parse.
-
Better visibility into requests that were blocked by traffic classifiers at the load balancer.
To export the logs, refer to Configure audit messages and log destinations.
Log file categories
The StorageGRID log file archive contains the logs described for each category and additional files that contain metrics and debug command output.
Archive location | Description |
---|---|
|
Audit messages generated during normal system operation. |
|
Base operating system information, including StorageGRID image versions. |
|
Global configuration information (bundles). |
|
Cassandra database information and Reaper repair logs. |
|
VCSs information about the current node and EC group information by profile ID. |
|
General grid logs including debug ( |
|
Grid configuration file shared across all nodes. Additionally, |
|
High availability groups metrics and logs. |
|
|
|
Logs related to the S3 Select proxy request. |
|
Debug messages related to log collection. |
|
Service logs for Grafana, Jaeger, node exporter, and Prometheus. |
|
Miscd access and error logs. |
|
The mariaDB database configuration and related logs. |
|
Logs generated by networking-related scripts and the Dynip service. |
|
Load balancer and grid federation configuration files and logs. Also includes Grid Manager and Tenant Manager traffic logs. |
|
|
|
NTP configuration file and logs. |
Orphaned objects |
Logs pertaining to orphaned objects. |
|
Node and grid state file, including services |
|
Log files under |
|
Peformance information for CPU, networking, and disk I/O. |
|
Current Prometheus metrics, if the log collection includes Prometheus data. |
|
Logs related to grid provisioning process. |
|
Logs from Raft cluster used in platform services. |
|
Logs related to SSH configuration and service. |
|
SNMP agent configuration used for sending SNMP notifications. |
|
Sockets data for network debug. |
|
Output of StorageGRID container commands. Contains system information, such as networking and disk usage. |
|
Related to maintaining consistency of the latest Recovery Package across all Admin Nodes and Storage Nodes that host the ADC service. |