CRITICAL_SERVICE_NOT_RUNNING
Viewing this guide for
Applicable alarms (1)
CRITICAL_SERVICE_NOT_RUNNING
Likely outcomes — click to expand
Based on 0 missions where this alarm fired in the last 90 days as of 2026-10-13
Aggregated from fleet operations and refreshed daily. Individual outcomes may vary by site and configuration.
Background
Section titled “Background”This alarm occurs when a critical service has crashed or was manually stopped. When this alarm occurs, it will set the Operations mode to DEGRADED.
Troubleshooting Steps
Section titled “Troubleshooting Steps”graph TD
open-the-discrepancy-in-zerp-and-review["<small><b>Step 1</b></small><br/>Action: Open the discrepancy in Zerp and revi..."]
click-on-view-to-open-the-alarm-report["<small><b>Step 2</b></small><br/>Action: Click on “View” to open the alarm rep..."]
does-it-say-status-message-stale-adc-ma{"<small><b>Step 3</b></small><br/>Question: Does it say “status_message_stale”: “..."}
is-this-an-ev3-dock{"<small><b>Step 4</b></small><br/>Question: Is this an EV3 Dock?"}
in-baraza-find-the-time-when-the-dock-t["<small><b>Step 5</b></small><br/>Action: In Baraza, find the time when the doc..."]
do-you-see-a-sudo-systemctl-message-des{"<small><b>Step 6</b></small><br/>Question: Do you see a sudo systemctl message..."}
this-was-caused-by-a-user-sshing-into-t["<small><b>Step 7</b></small><br/>Action: This was caused by a user sshing into..."]
close-out-the-discrepancy-without-escal["<small><b>Step 8</b></small><br/>Action: Close out the discrepancy without esc..."]
this-alarm-indicates-a-software-issue-e{{"<small><b>Step 9</b></small><br/>Escalation: This alarm indicates a software issue..."}}
open-the-discrepancy-in-zerp-and-review --> click-on-view-to-open-the-alarm-report
click-on-view-to-open-the-alarm-report --> does-it-say-status-message-stale-adc-ma
does-it-say-status-message-stale-adc-ma -->|Yes| is-this-an-ev3-dock
does-it-say-status-message-stale-adc-ma -->|No| in-baraza-find-the-time-when-the-dock-t
is-this-an-ev3-dock -->|Yes| close-out-the-discrepancy-without-escal
is-this-an-ev3-dock -->|No| in-baraza-find-the-time-when-the-dock-t
in-baraza-find-the-time-when-the-dock-t --> do-you-see-a-sudo-systemctl-message-des
do-you-see-a-sudo-systemctl-message-des -->|Yes| this-was-caused-by-a-user-sshing-into-t
do-you-see-a-sudo-systemctl-message-des -->|No| this-alarm-indicates-a-software-issue-e
style open-the-discrepancy-in-zerp-and-review fill:#dcfce7,stroke:#22c55e,color:#14532d
style click-on-view-to-open-the-alarm-report fill:#dcfce7,stroke:#22c55e,color:#14532d
style does-it-say-status-message-stale-adc-ma fill:#dbeafe,stroke:#3b82f6,color:#1e3a5f
style is-this-an-ev3-dock fill:#dbeafe,stroke:#3b82f6,color:#1e3a5f
style in-baraza-find-the-time-when-the-dock-t fill:#dcfce7,stroke:#22c55e,color:#14532d
style do-you-see-a-sudo-systemctl-message-des fill:#dbeafe,stroke:#3b82f6,color:#1e3a5f
style this-was-caused-by-a-user-sshing-into-t fill:#dcfce7,stroke:#22c55e,color:#14532d
style close-out-the-discrepancy-without-escal fill:#dcfce7,stroke:#22c55e,color:#14532d
style this-alarm-indicates-a-software-issue-e fill:#fef3c7,stroke:#f59e0b,color:#78350f Hover or focus a block to preview it. Select the block to keep the preview open.
1 action
Open the discrepancy in Zerp and review the “Alarms & Errors” section.
2 action
Click on “View” to open the alarm report for
CRITICAL_SERVICE_NOT_RUNNING. 3 question
Does it say “status_message_stale”: “adc_manager?”
4 question
Is this an EV3 Dock?
5 action
In Baraza, find the time when the dock transitioned from operations mode
STANDARD to DEGRADED. Open Journalctl logs at this time and open a process called session-XX.scope. If you don’t see session-XX.scope, open dock_executive.. Look for a message like sudo systemctl stop ... or sudo systemctl restart .... 6 question
Do you see a
sudo systemctl message described above in the logs? 7 action
This was caused by a user sshing into the dock and manually restarting a service. This should only be done when the dock has been put into diagnostic mode.
Clear the discrepancy.
Clear the discrepancy.
8 action
Close out the discrepancy without escalating. This is a known issue under investigation.
9 escalation
This alarm indicates a software issue. Escalate to P2 Dock Embedded On Call.
Resolution note
This plaintext block is ready to paste into the Resolution Note field on the ZERP issue you're working. The permalink below gives engineering review access to the full step-by-step timeline including any back-navigation; share it if the case needs a deeper look.
Permalink:
Session is too large to fit in a URL. Use Download session JSON to share the timeline out-of-band.
Did this guide help you get unblocked?
Open suggestions
There are no open suggestions.
Open pull requests
There are no open pull requests.