PowerScaleOneFS CLI Command Reference

Syntax

isi job events list
  [--job-type <string>]
  [--job-id <integer>]
  [{--begin} <timestamp>]
  [--end <timestamp>]
  [--state {failed | running | cancelled_user | succeeded | paused_user | unknown | paused_priority | cancelled_system | paused_policy | paused_system}]
  [--limit <integer>]
  [--format {table | json | csv | list}]
  [--no-header]
  [--no-footer]
  [--verbose]
	

Options

--job-type <string>

Displays all events of all instances of a specific job type (for example, SmartPools).

--job-id <integer>

Displays all events of a specific job instance.

--begin <timestamp>

Specifies the beginning of the time period for which job events should be listed. For example: --begin "2013-09-17T00:00". This means that job events beginning at the first moment of September 17, 2013 should be listed.

--end <timestamp>

Specifies the end of the time period for job events to be listed. For example, --end "2013-09-17T23:59" means that job events right up to the last minute of September 17, 2013 should be listed.

--state {failed | running | cancelled_user | succeeded | paused_user | unknown | paused_priority | cancelled_system | paused_policy |paused_system}

Specifies that events of the given state or states should be listed.

{--limit | -l} <integer>

Displays no more than the specified number of job events. If no timestamp parameters are specified, the most recent job events of the specified number are listed.

--format {table | json | csv | list}

Displays output in table (default), JavaScript Object Notation (JSON), comma-separated value (CSV), or list format.

{--no-header | -a}

Displays table and CSV output without headers.

{--no-footer | -z}

Displays table output without footers.

{--verbose | -v}

Displays more detailed information about job events.

Examples

The following command lists all FSAnalyze events that happened in the month of September.

isi job events list --job-type fsanalyze --begin "2013-09-01" --end "2013-09-30"

The system displays output similar to the following example.

Time                Message
-----------------------------------------------------
2013-09-16T22:00:21 FSAnalyze[7] Waiting             
2013-09-16T22:00:23 FSAnalyze[7] Running             
2013-09-16T22:00:25 FSAnalyze[7] Phase 1: begin scan 
2013-09-16T22:01:45 FSAnalyze[7] Phase 1: end scan   
2013-09-16T22:01:46 FSAnalyze[7] Phase 2: begin merge
2013-09-16T22:02:30 FSAnalyze[7] Phase 2: end merge  
2013-09-16T22:02:31 FSAnalyze[7] Succeeded           
2013-09-17T22:00:05 FSAnalyze[9] Waiting             
2013-09-17T22:00:08 FSAnalyze[9] Running             
2013-09-17T22:00:11 FSAnalyze[9] Phase 1: begin scan 
2013-09-17T22:01:37 FSAnalyze[9] Phase 1: end scan   
2013-09-17T22:01:38 FSAnalyze[9] Phase 2: begin merge
2013-09-17T22:02:24 FSAnalyze[9] Phase 2: end merge  
2013-09-17T22:02:26 FSAnalyze[9] Succeeded           
-----------------------------------------------------
Total: 14

The following command lists all the job events that happened on a specific day.

isi job events list --begin "2013-09-17T00:00" --end "2013-09-17T23:59"

The system displays output similar to the following example:

Time                Message                                       
------------------------------------------------------------------
2013-09-17T22:00:04 SmartPools[8] Waiting                         
2013-09-17T22:00:05 FSAnalyze[9] Waiting                          
2013-09-17T22:00:06 SmartPools[8] Running                         
2013-09-17T22:00:07 SmartPools[8] Phase 1: begin lin policy update
2013-09-17T22:00:08 FSAnalyze[9] Running                          
2013-09-17T22:00:11 FSAnalyze[9] Phase 1: begin scan              
2013-09-17T22:01:01 SmartPools[8] Phase 1: end lin policy update  
2013-09-17T22:01:03 SmartPools[8] Phase 2: begin sin policy update
2013-09-17T22:01:06 SmartPools[8] Phase 2: end sin policy update  
2013-09-17T22:01:09 SmartPools[8] Succeeded                       
2013-09-17T22:01:37 FSAnalyze[9] Phase 1: end scan                
2013-09-17T22:01:38 FSAnalyze[9] Phase 2: begin merge             
2013-09-17T22:02:24 FSAnalyze[9] Phase 2: end merge               
2013-09-17T22:02:26 FSAnalyze[9] Succeeded                        
------------------------------------------------------------------
Total: 14