github.com/ranjib/nomad@v0.1.1-0.20160225204057-97751b02f70b/website/source/docs/commands/alloc-status.html.md.erb (about)

     1  ---
     2  layout: "docs"
     3  page_title: "Commands: alloc-status"
     4  sidebar_current: "docs-commands-alloc-status"
     5  description: >
     6    Display status and metadata about existing allocations and their tasks.
     7  ---
     8  
     9  # Command: alloc-status
    10  
    11  The `alloc-status` command displays status information and metadata about an
    12  existing allocation and its tasks. It can be useful while debugging to reveal
    13  the underlying reasons for scheduling decisions or failures, as well as the
    14  current state of its tasks.
    15  
    16  ## Usage
    17  
    18  ```
    19  nomad alloc-status [options] <allocation>
    20  ```
    21  
    22  An allocation ID or prefix must be provided. If there is an exact match, the
    23  full details of the allocation will be displayed. Otherwise, a list of matching
    24  allocations and information will be displayed.
    25  
    26  ## General Options
    27  
    28  <%= general_options_usage %>
    29  
    30  ## Status Options
    31  
    32  * `-short`: Display short output. Shows only the most recent task event.
    33  * `-verbose`: Show full information.
    34  
    35  ## Examples
    36  
    37  Short status of an alloc:
    38  
    39  ```
    40  $ nomad alloc-status --short a7365fe4
    41  ID                = a7365fe4
    42  EvalID            = 44c2d9ed
    43  Name              = example.cache[0]
    44  NodeID            = e55859b1
    45  JobID             = example
    46  ClientStatus      = running
    47  NodesEvaluated    = 1
    48  NodesFiltered     = 0
    49  NodesExhausted    = 0
    50  AllocationTime    = 911.026µs
    51  CoalescedFailures = 0
    52  redis
    53  web
    54  
    55  ==> Tasks
    56  Name   State    LastEvent  Time
    57  redis  running  Started    02:29:40 11/17/15
    58  web    running  Started    02:30:41 11/17/15
    59  
    60  ==> Status
    61  Allocation "a7365fe4" status "running" (0/1 nodes filtered)
    62    * Score "e55859b1.binpack" = 10.334026
    63  ```
    64  
    65  Full status of an alloc, which shows one of the tasks dying and then being restarted:
    66  
    67  ```
    68  $ nomad alloc-status a7365fe4
    69  ID                = a7365fe4
    70  EvalID            = 44c2d9ed
    71  Name              = example.cache[0]
    72  NodeID            = e55859b1
    73  JobID             = example
    74  ClientStatus      = running
    75  NodesEvaluated    = 1
    76  NodesFiltered     = 0
    77  NodesExhausted    = 0
    78  AllocationTime    = 911.026µs
    79  CoalescedFailures = 0
    80  
    81  ==> Task "redis" is "running"
    82  Recent Events:
    83  Time               Type     Description
    84  02:29:40 11/17/15  Started  <none>
    85  
    86  ==> Task "web" is "running"
    87  Recent Events:
    88  Time               Type        Description
    89  02:30:41 11/17/15  Started     <none>
    90  02:30:02 11/17/15  Terminated  Exit Code: 137, Exit Message: "Docker container exited with non-zero exit code: 137"
    91  02:29:40 11/17/15  Started     <none>
    92  
    93  ==> Status
    94  Allocation "a7365fe4" status "running" (0/1 nodes filtered)
    95    * Score "e55859b1.binpack" = 10.334026
    96  
    97  ```