Command: job status
The job status
command displays status information for a job.
Usage
nomad job status [options] [job]
This command accepts an optional job ID or prefix as the sole argument. If there is an exact match based on the provided job ID or prefix, then information about the specific job is queried and displayed. Otherwise, a list of matching jobs and information will be displayed.
If the ID is omitted, the command lists out all of the existing jobs and a few
of the most useful status fields for each. As of Nomad 0.7.1, alloc status also
shows allocation modification time in addition to create time. When the
-verbose
flag is not set, allocation creation and modify times are shown in a
shortened relative time format like 5m ago
.
When ACLs are enabled, this command requires a token with the read-job
and
list-jobs
capabilities for the job's namespace.
General Options
-address=<addr>
: The address of the Nomad server. Overrides theNOMAD_ADDR
environment variable if set. Defaults tohttp://127.0.0.1:4646
.-region=<region>
: The region of the Nomad server to forward commands to. Overrides theNOMAD_REGION
environment variable if set. Defaults to the Agent's local region.-namespace=<namespace>
: The target namespace for queries and actions bound to a namespace. Overrides theNOMAD_NAMESPACE
environment variable if set. If set to'*'
, job and alloc subcommands query all namespacecs authorized to user. Defaults to the "default" namespace.-no-color
: Disables colored command output. Alternatively,NOMAD_CLI_NO_COLOR
may be set.-ca-cert=<path>
: Path to a PEM encoded CA cert file to use to verify the Nomad server SSL certificate. Overrides theNOMAD_CACERT
environment variable if set.-ca-path=<path>
: Path to a directory of PEM encoded CA cert files to verify the Nomad server SSL certificate. If both-ca-cert
and-ca-path
are specified,-ca-cert
is used. Overrides theNOMAD_CAPATH
environment variable if set.-client-cert=<path>
: Path to a PEM encoded client certificate for TLS authentication to the Nomad server. Must also specify-client-key
. Overrides theNOMAD_CLIENT_CERT
environment variable if set.-client-key=<path>
: Path to an unencrypted PEM encoded private key matching the client certificate from-client-cert
. Overrides theNOMAD_CLIENT_KEY
environment variable if set.-tls-server-name=<value>
: The server name to use as the SNI host when connecting via TLS. Overrides theNOMAD_TLS_SERVER_NAME
environment variable if set.-tls-skip-verify
: Do not verify TLS certificate. This is highly not recommended. Verification will also be skipped ifNOMAD_SKIP_VERIFY
is set.-token
: The SecretID of an ACL token to use to authenticate API requests with. Overrides theNOMAD_TOKEN
environment variable if set.
Status Options
-all-allocs
: Display all allocations matching the job ID, even those from an older instance of the job.-evals
: Display the evaluations associated with the job.-short
: Display short output. Used only when a single node is being queried. Drops verbose node allocation data from the output.-verbose
: Show full information. Allocation create and modify times are shown inyyyy/mm/dd hh:mm:ss
format.
Examples
List of all jobs:
$ nomad job statusID Type Priority Status Submit Datejob1 service 80 running 07/25/17 15:47:11 UTCjob2 batch 40 complete 07/24/17 19:22:11 UTCjob3 service 50 dead (stopped) 07/22/17 16:34:48 UTC
Short view of a specific job:
$ nomad job status -short job1ID = job1Name = Test JobSubmit Date = 07/25/17 15:47:11 UTCType = servicePriority = 3Datacenters = dc1,dc2,dc3Status = pendingPeriodic = falseParameterized = false
Full status information of a job:
$ nomad job status exampleID = exampleName = exampleSubmit Date = 07/25/17 15:53:04 UTCType = servicePriority = 50Datacenters = dc1Status = runningPeriodic = falseParameterized = false SummaryTask Group Queued Starting Running Failed Complete Lostcache 0 0 1 0 0 0 Latest DeploymentID = 6294be0cStatus = successfulDescription = Deployment completed successfully DeployedTask Group Desired Placed Healthy Unhealthycache 1 1 1 0 AllocationsID Node ID Task Group Version Desired Status Created Modified478ce836 5ed166e8 cache 0 run running 5m ago 5m ago
Full status information of a periodic job:
$ nomad job status exampleID = exampleName = exampleSubmit Date = 07/25/17 15:59:52 UTCType = batchPriority = 50Datacenters = dc1Status = runningPeriodic = trueParameterized = falseNext Periodic Launch = 07/25/17 16:00:30 UTC (5s from now) Children Job SummaryPending Running Dead0 3 0 Previously Launched JobsID Statusexample/periodic-1500998400 runningexample/periodic-1500998410 runningexample/periodic-1500998420 running
Full status information of a parameterized job:
$ nomad job status exampleID = exampleName = exampleSubmit Date = 07/25/17 15:59:52 UTCType = batchPriority = 50Datacenters = dc1Status = runningPeriodic = falseParameterized = true Parameterized JobPayload = requiredRequired Metadata = fooOptional Metadata = bar Parameterized Job SummaryPending Running Dead0 2 0 Dispatched JobsID Statusexample/dispatch-1485411496-58f24d2d runningexample/dispatch-1485411499-fa2ee40e running
Full status information of a job with placement failures:
$ nomad job status exampleID = exampleName = exampleSubmit Date = 07/25/17 15:55:27 UTCType = servicePriority = 50Datacenters = dc1Status = runningPeriodic = falseParameterized = false SummaryTask Group Queued Starting Running Failed Complete Lostcache 1 0 4 0 0 0 Placement FailureTask Group "cache": * Resources exhausted on 1 nodes * Dimension "cpu" exhausted on 1 nodes Latest DeploymentID = bb4b2fb1Status = runningDescription = Deployment is running DeployedTask Group Desired Placed Healthy Unhealthycache 5 4 4 0 AllocationsID Node ID Task Group Version Desired Status Created Modified048c1e9e 3f38ecb4 cache 0 run running 5m ago 5m ago250f9dec 3f38ecb4 cache 0 run running 5m ago 5m ago2eb772a1 3f38ecb4 cache 0 run running 5m ago 5m agoa17b7d3d 3f38ecb4 cache 0 run running 5m ago 5m ago
Full status information showing evaluations with a placement failure. The in progress evaluation denotes that Nomad is blocked waiting for resources to become available so that it can place the remaining allocations.
$ nomad job status -evals exampleID = exampleName = exampleSubmit Date = 07/25/17 15:55:27 UTCType = servicePriority = 50Datacenters = dc1Status = runningPeriodic = falseParameterized = false SummaryTask Group Queued Starting Running Failed Complete Lostcache 1 0 4 0 0 0 EvaluationsID Priority Triggered By Status Placement Failurese44a39e8 50 deployment-watcher canceled false97018573 50 deployment-watcher complete trued5a7300c 50 deployment-watcher canceled falsef05a4495 50 deployment-watcher complete truee3f3bdb4 50 deployment-watcher canceled falseb5f08700 50 deployment-watcher complete true73bb867a 50 job-register blocked N/A - In Progress85052989 50 job-register complete true Placement FailureTask Group "cache": * Resources exhausted on 1 nodes * Dimension "cpu exhausted" exhausted on 1 nodes Latest DeploymentID = bb4b2fb1Status = runningDescription = Deployment is running DeployedTask Group Desired Placed Healthy Unhealthycache 5 4 4 0 AllocationsID Node ID Task Group Version Desired Status Created Modified048c1e9e 3f38ecb4 cache 0 run running 07/25/17 15:55:27 UTC 07/25/17 15:55:27 UTC250f9dec 3f38ecb4 cache 0 run running 07/25/17 15:55:27 UTC 07/25/17 15:55:27 UTC2eb772a1 3f38ecb4 cache 0 run running 07/25/17 15:55:27 UTC 07/25/17 15:55:27 UTCa17b7d3d 3f38ecb4 cache 0 run running 07/25/17 15:55:27 UTC 07/25/17 15:55:27 UTC