Collecting debug data

If a failure occurs during deployment or lifecycle management, or an operational error is detected in the IBM Storage Scale cluster, debug logs are collected to facilitate problem resolution.

Collecting debug data for IBM Storage Scale deployment failure

IBM Storage Scale deployment process stores all the important information that is related to resource allocation and the CloudFormation stack in the customer-specified S3 bucket. It usually consists of the following information:

  • Template input values file
  • Resource allocation status file
  • IBM Storage Scale cluster blueprint
  • Deployment status file
  • Deployment log file

Collecting debug data for IBM Storage Scale operational failure

During an IBM Storage Scale operational failure, all information from the S3 bucket that is listed in the previous section must be collected. To collect all IBM Storage Scale debug information, log on to any storage node, and run the gpfs.snap command. For more information, see the gpfs.snap command section in IBM Storage Scale: Command and Programming Reference Guide.

Collecting debug data for a cluster lifecycle management failure

During a cluster lifecycle management failure, the following information must be collected:
  • All information from the S3 bucket listed in the previous section
  • Logs from the controller node, where the mmcloudworkflows command was run:
    • The log files from /var/adm/ras/ibm_cloud_workflow_logs.
    • The ansible.log from /var/logs directory, if it exists.
    • The ibm_specscale_ansible.log from the /var/logs directory, if it exists