IBM Storage Scale System Problem Determination Guide

Best practices for troubleshooting
Following certain best practices makes the troubleshooting process easier.
Collecting information about an issue
To begin the troubleshooting process, collect information about the issue that the system is reporting.
Servicing log tip
This section gives information about servicing log.
IBM Storage Scale System deployment troubleshooting: Helpful podman, Ansible, and log information
This section details the following podman, Ansible®, and log information.
Debugging yum update issues from the container
During the EMS or I/O node update from the container, specifically in the yum update task, you might encounter some issues. Use the following information to resolve these issues.
GUI Issues
When troubleshooting GUI issues, it is recommended to view the logs that are located under /var/log/cnlog/mgtsrv. By default, the GUI is installed on the EMS node. It is possible that the customer installed it in another node. In such cases, the GUI logs are stored in the node where the GUI is installed.
Recovery group issues
The following sections describe the recovery group issues and their solutions for the different IBM Storage Scale System platforms.
Maintenance procedures
Very large disk systems, with thousands or tens of thousands of disks and servers, will likely experience a variety of failures during normal operation.
References
The IBM Elastic Storage Server displays a warning or error message when it encounters an issue that needs user attention. The message severity tags indicate the severity of the issue.
Contacting IBM
Specific information about a problem such as: symptoms, traces, error logs, GPFS logs, and file system status is vital to IBM® in order to resolve an IBM Storage Scale RAID problem.
Cleaning up IBM Storage Scale System environments
This section contains information for users who want to securely erase or clean up their IBM Elastic Storage® Server environments.