Viewing ScaleILM application logs

The following section describes how to view the ScaleILM Data Mover application logs.

About this task

Follow the procedure to view the ScaleILM Data Mover application logs.

Procedure

  1. Run the following command: 
    oc -n ibm-data-cataloging logs deployment/isd-scaleilmdatamover
  2. Any failures that occur while the files are processed for tiering by ScaleILM Data Mover application, are logged in the application log file. A sample error log from the ScaleILM Data Mover application logs is shown in the following section. These error logs occur when the file is not on the specified 'source_connection' while the application is processing the Tiering policy. 
    2020-04-28 14:44:36,439 - __main__ - ERROR - File not found: /ibm/scale0/unicode_test/migrateDir.popFSDir.19824/unicodedir/test010.\n.test
2020-04-28 14:44:36,440 - __main__ - ERROR - File not found: /ibm/scale0/unicode_test/migrateDir.popFSDir.19824/unicodedir/test137..test
2020-04-28 14:44:36,440 - __main__ - ERROR - File not found: /ibm/scale0/unicode_test/migrateDir.popFSDir.19824/unicodedir/test147..test
2020-04-28 14:44:36,440 - __main__ - ERROR - File not found: /ibm/scale0/unicode_test/migrateDir.popFSDir.19824/unicodedir/test157..test
    A sample error log from the ScaleILM Data Mover application logs for an invalid 'destination_tier', is shown in the following section:
    2020-04-28 14:35:39,566 - __main__ - ERROR - Invalid destination_tier: 'gold:abcd'.
    A sample error log from the ScaleILM Data Mover application logs when the 'destination_tier' does not exist on the IBM Storage Scale connection, is shown in the following section:
    2020-05-12 14:32:38,436 - __main__ - ERROR - Provided internal pool goldflower does not exist on system: 9.11.212.29
  3. Run the following command to view policy engine pod logs: 
    oc -n ibm-data-cataloging logs deployment/isd-policyengine
    A sample policy engine pod log is shown in the following section. This log shows information that is received from the ScaleILM Data Mover application. It describes errors that are encountered while a Tiering policy is processed and when a file is not found on the specified 'source_connection':
    2020-04-28 14:44:37,455 - policy.policyapiservice - ERROR - [policy_id: scale-tier-unicode-modevvm19-pol]: Agent reported 'status: failed' for fkey: 'modevvm19.tuc.stglabs.ibm.comscale0121547', path: '/ibm/scale0/unicode_test/migrateDir.popFSDir.19824/unicodedir/test237..test', reason: 'File not found: /ibm/scale0/unicode_test/migrateDir.popFSDir.19824/unicodedir/test237..test', errno: 'ENOENT'
2020-04-28 14:44:37,455 - policy.policyapiservice - ERROR - [policy_id: scale-tier-unicode-modevvm19-pol]: Agent reported 'status: failed' for fkey: 'modevvm19.tuc.stglabs.ibm.comscale0121557', path: '/ibm/scale0/unicode_test/migrateDir.popFSDir.19824/unicodedir/test247..test', reason: 'File not found: /ibm/scale0/unicode_test/migrateDir.popFSDir.19824/unicodedir/test247..test', errno: 'ENOENT'
    A sample error log from the Policy engine pod logs for an invalid 'destination_tier', is shown in the following section:
    2020-04-28 14:35:40,064 - policy.policyapiservice - ERROR - [policy_id: scale-tier-modevvm19-invalid-destn-pol]: Agent reported 'status: failed' for fkey:  'modevvm19.tuc.stglabs.ibm.comscale0300770', path: '/ibm/scale0/covid-19-dataset/inference/NWPU-Chest-X-Ray/2b16346f-8fe4-45ee-b3c7-eaa46fd26041.png', reason: 'Invalid destination_tier: 'gold:abcd'.', errno: 'EINVAL'
    A sample error log from the Policy engine pod logs when the 'destination_tier' does not exist on the IBM Storage Scale connection, is shown in the following section:
    2020-05-12 07:40:34,819 - policy.policyapiservice - ERROR - [policy_id: scale-tier-pol]: Agent reported 'status: failed' for fkey: 'nikkogpfs26728', path: '/ibm/gpfs2/scale0/customer_e2e/financial_report_file6.pdf', reason: 'Provided internal pool goldflower does not exist on system: 9.11.212.29', errno: 'EINVAL'
2020-05-12 07:40:34,819 - policy.policyapiservice - ERROR - [policy_id: scale-tier-pol]: Agent reported 'status: failed' for fkey: 'nikkogpfs26748', path: '/ibm/gpfs2/scale0/customer_e2e/HR_report_US_file6.pdf', reason: 'Provided internal pool goldflower does not exist on system: 9.11.212.29', errno: 'EINVAL'