Operations Mode = DEGRADED
Applicable alarms (1)
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”A Dock is in the Degraded operations mode when:
- The tower has been lowered, or
- One or more processes have reported a fault, and
- The Dock has NOT been commanded into Diagnostic mode.
This results in the Dock being ineligible for docking.
Troubleshooting Steps
Section titled “Troubleshooting Steps”graph TD
review-the-zerp-discrepancy-and-alarms["<small><b>Step 1</b></small><br/>Action: For dock degraded auto-discrepancies ..."]
place-the-dock-into-diagnostic-mode["<small><b>Step 2</b></small><br/>Action: Place the Dock into diagnostic mode..."]
trigger-a-log-offload["<small><b>Step 3</b></small><br/>Action: Trigger a log offload/procedures/l..."]
go-to-baraza-and-search-journalctl-for["<small><b>Step 4</b></small><br/>Action: Go to Baraza and search journalctl fo..."]
in-fleet-wrangler-check-the-docks-detai["<small><b>Step 5</b></small><br/>Action: In Fleet Wrangler, check the Dock’s *..."]
review-service-states-and-related-alarms["<small><b>Step 6</b></small><br/>Action: If one of the **service states** matc..."]
review-the-zerp-discrepancy-and-alarms --> place-the-dock-into-diagnostic-mode
place-the-dock-into-diagnostic-mode --> trigger-a-log-offload
trigger-a-log-offload --> go-to-baraza-and-search-journalctl-for
go-to-baraza-and-search-journalctl-for --> in-fleet-wrangler-check-the-docks-detai
in-fleet-wrangler-check-the-docks-detai --> review-service-states-and-related-alarms
style review-the-zerp-discrepancy-and-alarms fill:#dcfce7,stroke:#22c55e,color:#14532d
style place-the-dock-into-diagnostic-mode fill:#dcfce7,stroke:#22c55e,color:#14532d
style trigger-a-log-offload fill:#dcfce7,stroke:#22c55e,color:#14532d
style go-to-baraza-and-search-journalctl-for fill:#dcfce7,stroke:#22c55e,color:#14532d
style in-fleet-wrangler-check-the-docks-detai fill:#dcfce7,stroke:#22c55e,color:#14532d
style review-service-states-and-related-alarms fill:#dcfce7,stroke:#22c55e,color:#14532d Hover or focus a block to preview it. Select the block to keep the preview open.
CRITICAL_STATUS_MESSAGE_STALE, NON_CRITICAL_STATUS_MESSAGE_STALE, CRITICAL_SERVICE_NOT_RUNNING, and/or NON_CRITICAL_SERVICE_NOT_RUNNING are expected if a service is restarted manually.
If a service was stopped/restarted manually without putting the Dock into Diagnostic Operations Mode first, the auto-discrepancy can be closed and the Dock returned to service.
You can see if the service was stopped/restarted manually by looking at the journalctl logs in Baraza. You can see commands run by an ssh user.
sudo systemctl ….
.For more information, see Detailed Dock Status and Alarms View.
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.