glite-ce-job-status

Section: User Commands (1)
Index
 

NAME

glite-ce-job-status - Displays information concerning jobs submitted to CREAM based CEs.

 

SYNOPSIS

glite-ce-job-status [options] <jobId1> <jobId2> ... <jobIdn>

 

DESCRIPTION

glite-ce-job-status is the command for getting information concerning jobs submitted to CREAM based Computing Elements.

glite-ce-job-status can monitor one or more jobs: the jobs to be checked are identified by their job identifiers (job Ids returned by glite-ce-job-submit) provided as arguments to the command and separated by a blank space.

It has to be remarked that a job can be monitored only by his/her owner (i.e. the user who submitted it). Only the ``super-users'' can check the status of jobs submitted by other persons.

If the --all option is specified, information about all the jobs submitted to the interested CREAM CE (whose endpoint must be specified with the --endpoint option, which is mandatory in this case) owned by the user issuing the command is returned. When the command is launched with the --all option, neither can a jobId be specified nor can the --input option be used.

The --input option permits to specify a file (file_name) that contains the jobIds to monitor. This file must be the one generated with the --output option of the glite-ce-job-submit or glite-ce-job-list commands. If the file_name does not represent an absolute path, it will be searched in the current working directory.

When a glite-ce-job-status request is issued, the host name and the port number to be used to contact the CREAM service(s) are retrieved from the specified jobIds (which encompass this information) unless the --endpoint option is used. As stated before, the --endpoint option is mandatory if the --all option is used.

The --level option allows setting the detail level of the returned information. This option can be specified with three values: 0, 1 and 2. The default level of verbosity (the one considered if this option is not used and if the attribute STATUS_VERBOSITY_LEVEL hasn't been specified in the CREAM CLI conf file) is 0. Please note that specifying 0 as verbosity level means calling on the CREAM service a faster operation than when using 1 or 2 as level.

Hereafter are listed the information displayed according to the verbosity level:

Verbosity level equal 0:

o JobID: the CREAM job unique identifier

o Status: the job current status

o ExitCode: the Unix exit code - if applicable

o FailureReason: the failure reason (for failed and aborted jobs)

o Description: a description, used for example to explain why a job has been killed by CREAM

Verbosity level equal 1:

o JobID: the CREAM job unique identifier

o GridJobID: the Grid (WMS) job unique identifier, for jobs submitted to CREAM via the WMS

o Current Status: the job current status

o ExitCode: the Unix exit code - if applicable

o FailureReason: the failure reason (for failed and aborted jobs)

o Description: a description, used for example to explain why a job has been killed by CREAM

o Job status changes: the status changes (along with their timestamps) occured so far for the considered job

o Issued Commands: the commands (all but the status/list operations) and the relevant results issued on this job

With a verbosity level equal 2, some additional information fields are added:

o WorkerNode: the worker node where the job is being/was executed

o LocalUser: the user name on the CE mapped to the considered Grid user

o Deleg Proxy Id: the id of the delegated user proxy

o DelegProxyInfo: information about the user proxy used for this job

o Lease ID: the id of the delegation (if the lease mechanism has been used)

o Lease Time: the lease expiration time (if the lease mechannism has been used)

o CREAM ISB URI: the URI of the CREAM directory for the InputSandbox

o CREAM OSB URI: the URI of the CREAM directory for the OutputSandbox

o JDL: the job JDL

o Issued Commands: the same information as for verbosity level 1 plus the timestamps when the commands have been processed and completed

If the user issuing the glite-ce-job-status is a ``superuser'' of that CREAM CE, also the following information is printed specifying '2' as verbosity level:

o LRMS Abs JobId: the id of the job wrt the LRMS Abstraction Layer (i.e. the BLAH job id, since BLAH us used as middleware component to interact with the underlying resource management system)

o LRMS JobId: the id of the job in the LRMS (i.e. the PBS id /the LSF id / ...)

o Working Dir: the directory used by CREAM to store information about this job. Please note that this is not the job working directory on the worker node

It is possible to specify filters on the jobs to be considered. A first type of filter is on the job status: with the --status (-s) option it is possible to specify a list of possible job states: only the jobs being in one of the listed status will be considered.

Another possible filter that can be considered is on the submission time: it is possible to select, with the --from (-f) and/or --to (-t) option a temporal interval: only jobs submitted in this time range will be considered.

 

OPTIONS

--help, -h
Displays command usage.

--conf file_name, -c file_name
Specifies the user specific configuration file.

--level verb_level, -L verb_level
Sets the detail level of information about the job displayed to the user. Possible values for verb_level are 0,1 and 2. Please note that specifying 0 as verbosity level means calling on the CREAM service a faster operation than when using 1 or 2 as level.

--status <status1>:<status2>: ... :<statusm>, -s <status1>:<status2>: ... :<statusm>
Specifies a filter on job status: only jobs being in one of the listed states will be considered; all jobs that are not in one of the specified states will be filtered out.

--from <DATE>, -f <DATE>

Specifies a filter on job submission time: only jobs submitted after the specified date will be considered. <TIME>, which must be specified wrt the local timezone, must have the format 'YYYY-MM-DD HH:mm:ss' where:

o YYYY is the year as a decimal number including the century

o MM is the month (1-12)

o DD is the day of month (1-31)

o HH, mm, ss represent respectively the hour (0-23), the minutes (0-59) and the seconds (0-59)

--to <DATE>, t <DATE>
Specifies a filter on job submission time: only jobs submitted before the specified date will be considered. <TIME>, which must be specified wrt the local timezone, must have the format 'YYYY-MM-DD HH:mm:ss' where:

o YYYY is the year as a decimal number including the century

o MM is the month (1-12)

o DD is the day of month (1-31)

o HH, mm, ss represent respectively the hour (0-23), the minutes (0-59) and the seconds (0-59)

--all, -a
Displays information about all known jobs in the specified (with the --endpoint option, which is mandatory in this case) CREAM CE, owned by the user issuing the command. This option can't be used either if one or more jobIds have been specified or if the --input option has been used.

--endpoint host[:port], -e host[:port]
Selects the endpoint of the CREAM CE to send the status request to. If this option is not specified, the endpoint will be extracted from the JobID strings. The endpoint must have the format <host>:<port> or <host>.

--donot-verify-ac-sign, -A
Allows the execution of the command even if the VO voms server certificate is not installed.

--input file_name, -i file_name
Displays information about the jobs whose Ids are contained in the file file_name. This option can't be used if the --all option has been specified as well.

--nomsg, -n
When this option is specified, any warning or info message is suppressed.

--debug, -d
When this option is specified, debugging information is displayed on the standard output and written also into the file glite-ce-job-status_CREAM_<username>_<date>_<time>.log file under (by default) the tmp/glite_cream_cli_logs directory.

--logfile file_name, -l file_name
When this option is specified, a command log file (whose pathname is file_name) is created.
    
--version, -v
Displays the version of the CREAM CLI software.

 

EXIT STATUS

glite-ce-job-status exits with a value of 0 if the status of all the specified jobs is retrieved correctly, >0 if errors occurred.

 

EXAMPLES

1. > glite-ce-job-status -L 1 https://cream-02.pd.infn.it:8443/CREAM955790315

displays the following lines:

**** JobID=[https://cream-02.pd.infn.it:8443/CREAM955790315]
 
        Current Status = [REALLY-RUNNING]
 
        Grid JobID     = [N/A]


        Job status changes:
        -------------------


        Status         = [REGISTERED] - [Fri 21 Dec 2007 17:49:38] (1198255778)


        Status         = [PENDING] - [Fri 21 Dec 2007 17:49:38] (1198255778)


        Status         = [IDLE] - [Fri 21 Dec 2007 17:49:41] (1198255781)


        Status         = [RUNNING] - [Fri 21 Dec 2007 17:49:51] (1198255791)


        Status         = [REALLY-RUNNING] - [Fri 21 Dec 2007 17:50:04] (1198255804)


        Issued Commands:
        -------------------


        *** Command Name              = [JOB_REGISTER]


            Command Category          = [JOB_MANAGEMENT]


            Command Status            = [SUCCESSFULL]


        *** Command Name              = [JOB_START]


            Command Category          = [JOB_MANAGEMENT]


            Command Status            = [SUCCESSFULL]


2. > glite-ce-job-status --endpoint grid005.pd.infn.it:8443 --all --status DONE-OK:DONE-FAILED --from '2005-07-13 10:00:00'

Status information of all jobs belonging to the user who issued the command, submitted to the specified (with the --endpoint option) CREAM CE after the specified date and time, and being in DONE-OK or in DONE-FAILED status, will be printed.

3. The following example shows a job that has been killed by CREAM because the lease time expired:

> glite-ce-job-status https://cream-03.pd.infn.it:8443/CREAM530773588

**** JobID=[https://cream-03.pd.infn.it:8443/CREAM530773588]
        Status        = [CANCELLED]
        ExitCode      = []
        Description   = [Job cancelled by Lease Manager! (try 1/3)!]

 

SEE ALSO

glite-ce-job-submit, glite-ce-job-list


 

Index

NAME
SYNOPSIS
DESCRIPTION
OPTIONS
EXIT STATUS
EXAMPLES
SEE ALSO

This document was created by man2html, using the manual pages.
Time: 13:31:39 GMT, May 02, 2011

-- MassimoSgaravatto - 2011-05-02

Topic revision: r1 - 2011-05-02 - MassimoSgaravatto
 

This site is powered by the TWiki collaboration platformCopyright © 2008-2019 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback