Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
 

show system applications (Junos OS Evolved)

Syntax

Description

This command displays application summary information in one of the following forms:

  • Shows all application summary information for all nodes.

  • Shows the application summary information for a specific application.

  • Shows the application summary information for a specific node.

Options

app app-name

(Optional) Specify application name for which you want to display application summary information.

brief

(Optional) Display brief output. This is the default format of display.

detail

(Optional) Display detailed output.

error (Optional) Display information about errors. You can specify the app, node, and detail options at the same time to further refine the list of errors, and to get more information about each one.
node node-name

(Optional) Specify node name for which you want to display application summary information.

Required Privilege Level

view

Output Fields

For a description of the output fields, see Table 1. Output fields are listed in the approximate order in which they appear.

Table 1: show system applications Output Fields

Field Name

Description

Level

Applications Information

Application

Name of the application.

Node

Name of the node the application is running on.

App State

State of the application: online, offline, failed, or active.

App Weight

A relative weight for multiple instances of the application across multiple nodes. The application instance with the higher weight provides more functionality.

App Zookeeper Session

Zookeeper session ID.

all options, except error

Object Producer details

Producer ID

Identifies which production set the object is part of.

Epoch ID

A number that identifies the current process that owns a production set. There can only be one owning process (active producer) that owns a production set at one time. The current owning process has an Epoch ID that is larger than any previous producer.

Production Topic

Hierarchical string that represents the production set.

Producer State

active or standby:

  • active indicates the application has production rights to modify the state in the production set.

  • standy means that the application is waiting to get the production right for the production set.

all options, except error

Description

A short description of the application, it also lists the systemd service file used for the application.

detail, without the error option

Loaded

A systemd state that indicates if the application is loaded in the system or not.

detail, without the error option

Run State from OS

A systemd state that indicates if the application is active or not.

detail, without the error option

Main PID

Process identifier (PID) of the application.

detail, without the error option

Command

Command line to launch the application.

detail, without the error option

ID

Name of the application.

detail, without the error option

Meta

Meta data for the application includes the following fields:

Bin path

Path to application execution.

Log file

Where logs go.

Working Dir

Working directory.

Production Set

Global or local production set. Values might be shared or local.

detail, without the error option

Resource

Resource data for the application includes the following fields:

all nodes

Does the application run on all nodes, true or false.

Max instances

How many instances of the application are there.

Max instances per node

How many instances of the application per node are there.

Run on startup

Is the application launched at bootup, true or false.

Node attributes

Typical node attributes are RE, FPC, MasterRE. You can see the node attributes by using the show system node-attributes command.

Node attribute match

What is the node attribute required to launch this application on a node? For example, if this field has the output re, Service file: lfmd, it indicates that the process lfmd will be launched on a node that has the attribute RE.

detail, without the error option

Failure

Failure data for the application includes the following fields:

Alarm color

Which alarm to be raised on failure, or none.

Alarm ID

The alarm ID.

Restart

Whether to restart the application, true or false.

detail, without the error option

Upgrade

Upgrade data for the application includes the following fields:

Upgrade parallely

Options are true or false.

Node upgrade done notify

Application requires notification when node upgrade is done. Options are true or false.

System upgrade done notify

Application requires notification when system upgrade is done. Options are true or false.

Upgrade restart node

Options are true or false.

Upgrade style

Option is stop-start.

hw sync

Application requires notification to sync hardware state during a unified in-service software upgrade (unified ISSU). Options are true or false.

wait for sw sync

Application provides notification after it has synced software state during a unified in-service software upgrade (unified ISSU). Options are true or false.

prepare to upgrade final

Application requires notification to prepare for upgrade. Options are true or false.

exits on prep final

Application exits after processing prepare to upgrade. Options are true or false.

Weight Application weight.

detail, without the error option

App-Exit

App-Exit data for the application includes the following fields:

Restart Supported

True/false. When the application exits, should the application be restarted.

Restart Node

True/false. When the application exits, should the node be rebooted.

Mark node spare

When an application exits, should the node be marked spare.

detail, without the error option

Node

Name of the node the application is running on.

error option, all combinations

Application

Name of the application.

error option, all combinations

Error Count

How many errors are on the node for the stated application.

error detail, either with or without the app or node options

Error Guids

Identifiers for particular error instances.

error detail, either with or without the app or node options

Error Number

Identifier for a particular type of error. For example, number 3 is for the error "No such process".

error detail, either with or without the app or node options

Severity

How severe the error is.

error detail, either with or without the app or node options

GUID

Identifier for a particular error instance.

error detail, either with or without the app or node options

Error Description

Text describing the error.

error detail, either with or without the app or node options

Error Module

The module causing the error.

error detail, either with or without the app or node options

Error Object Name

Name of the object causing the error.

error detail, either with or without the app or node options

Error Object Parent Name

Name of the object's parent.

error detail, either with or without the app or node options

Error Timestamp

Date and time at which the error occurred.

error detail, either with or without the app or node options

Sample Output

show system applications

show system applications error

show system applications error node node-name

show system applications error app application-name

show system applications app application-name node node-name

show system applications app application-name detail

show system applications error app application-name detail

show system applications error app application-name node node-name detail

Release Information

Command introduced in Junos OS Evolved Release 18.3R1.

error option added in Junos OS Evolved Release 22.3R1.