show system applications (Junos OS Evolved)

date_range 21-Feb-25

arrow_backward

arrow_forward

Syntax

content_copy zoom_out_map
show system applications
<app app-name> 
<brief>
<detail>
<error>
<node node-name>

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.

On ACX7000 series of routers, when an application restarts for more than three times in a five-minute window, then the application and its dependent applications goes into a failure state. The reason for an application restart could be anything like an application crash, restart of other dependent applications, Routing Engine switchover, CLI induced restart, et cetera.

If an application goes into a failed state, then you need to manually recover the application by using the following CLI command:

content_copy zoom_out_map
user@host> restart app-name

You can use the show system applications command to check the status of all the applications.

You can use the following shell command to understand the reason for an application failure:

content_copy zoom_out_map
user@host:/etc/systemd/system# systemctl status app-name

The following sample output helps you to understand the reason for the evo-pfemand application failure:

content_copy zoom_out_map
user@host:/etc/systemd/system# systemctl status evo-pfemand
x evo-pfemand.service - "Evo Merchant Silicon PFE Manager Daemon"
     Loaded: loaded (/etc/systemd/system/evo-pfemand.service; static)
     Active: failed (Result: signal) since Mon 2024-09-23 22:27:13 PDT; 53min ago
    Process: 32689 ExecStartPre=/usr/sbin/evo-pfemand_prestart.sh (code=exited, status=0/SUCCESS)
    Process: 32698 ExecStart=/usr/sbin/evo-pfemand_start.sh evo-pfemand (code=killed, signal=KILL)
    Process: 2827 ExecStopPost=/usr/sbin/evo-pfemand_poststop.sh evo-pfemand (code=exited, status=0/SUCCESS)
   Main PID: 32698 (code=killed, signal=KILL)
 
Sep 23 22:27:13 host systemd[1]: evo-pfemand.service: Converting job evo-pfemand.service/restart -> evo-pfemand.service/start
Sep 23 22:27:13 host systemd[1]: evo-pfemand.service: Start request repeated too quickly.
Sep 23 22:27:13 host systemd[1]: evo-pfemand.service: Failed with result 'signal'.
Sep 23 22:27:13 host systemd[1]: evo-pfemand.service: Service restart not allowed.

The output shows that the evo-pfemand application has failed and the reason is that the application has hit the start limit. In this case, you will need to manually restart the evo-pfemand application by using the following command:

content_copy zoom_out_map
user@host> restart evo-pfemand

To know how to use shell commands on Junos OS Evolved, see Shell Commands for Junos OS Evolved.

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.

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.