FLEET_MEDIC_REBOOT_FAILURE
Viewing this guide for
Applicable alarms (1)
FLEET_MEDIC_REBOOT_FAILURE
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”The automated reboot system wasn’t able to reboot the Aircraft.
Troubleshooting Steps
Section titled “Troubleshooting Steps”graph TD
is-the-aircraft-currently-online{"<small><b>Step 1</b></small><br/>Question: Is the Aircraft currently online?"}
is-the-aircrafts-uptime-greater-than-2{"<small><b>Step 2</b></small><br/>Question: Was the Aircraft last restarted more ..."}
power-cycle-the-aircraft-https-flyzip["<small><b>Step 3</b></small><br/>Action: Power cycle the Aircraft Power Cycl..."]
can-you-ssh-into-compute-a-via-the-dock{"<small><b>Step 4</b></small><br/>Question: SSH into both compute boards via the ..."}
aircraft-offline-in-fleetwrangler["<small><b>Step 5</b></small><br/>Action: This indicates that the Aircraft is o..."]
compute-a-has-crashed{"<small><b>Step 6</b></small><br/>Question: This indicates that one of the comput..."}
ssh-into-the-reachable-compute-board["<small><b>Step 7</b></small><br/>Action: SSH into the reachable compute board ..."]
neither-compute-board-is-reachable["<small><b>Step 8</b></small><br/>Action: This indicates that neither compute b..."]
is-the-issue-resolved{"<small><b>Step 9</b></small><br/>Question: Is the issue resolved and the Aircraf..."}
return-the-aircraft-to-service["<small><b>Step 10</b></small><br/>Action: Return the Aircraft to service."]
follow-zip-offline-to-get-the-aircraf["<small><b>Step 11</b></small><br/>Action: Follow Zip Offline/topics/asset-of..."]
is-the-aircraft-currently-online -->|Yes| is-the-aircrafts-uptime-greater-than-2
is-the-aircraft-currently-online -->|No| can-you-ssh-into-compute-a-via-the-dock
is-the-aircrafts-uptime-greater-than-2 -->|Yes| power-cycle-the-aircraft-https-flyzip
is-the-aircrafts-uptime-greater-than-2 -->|No| return-the-aircraft-to-service
power-cycle-the-aircraft-https-flyzip --> is-the-issue-resolved
can-you-ssh-into-compute-a-via-the-dock -->|Yes| aircraft-offline-in-fleetwrangler
can-you-ssh-into-compute-a-via-the-dock -->|No| compute-a-has-crashed
compute-a-has-crashed -->|Yes| ssh-into-the-reachable-compute-board
compute-a-has-crashed -->|No| neither-compute-board-is-reachable
ssh-into-the-reachable-compute-board --> is-the-issue-resolved
neither-compute-board-is-reachable --> is-the-issue-resolved
is-the-issue-resolved -->|Yes| return-the-aircraft-to-service
is-the-issue-resolved -->|No| follow-zip-offline-to-get-the-aircraf
style is-the-aircraft-currently-online fill:#dbeafe,stroke:#3b82f6,color:#1e3a5f
style is-the-aircrafts-uptime-greater-than-2 fill:#dbeafe,stroke:#3b82f6,color:#1e3a5f
style power-cycle-the-aircraft-https-flyzip fill:#dcfce7,stroke:#22c55e,color:#14532d
style can-you-ssh-into-compute-a-via-the-dock fill:#dbeafe,stroke:#3b82f6,color:#1e3a5f
style aircraft-offline-in-fleetwrangler fill:#dcfce7,stroke:#22c55e,color:#14532d
style compute-a-has-crashed fill:#dbeafe,stroke:#3b82f6,color:#1e3a5f
style ssh-into-the-reachable-compute-board fill:#dcfce7,stroke:#22c55e,color:#14532d
style neither-compute-board-is-reachable fill:#dcfce7,stroke:#22c55e,color:#14532d
style is-the-issue-resolved fill:#dbeafe,stroke:#3b82f6,color:#1e3a5f
style return-the-aircraft-to-service fill:#dcfce7,stroke:#22c55e,color:#14532d
style follow-zip-offline-to-get-the-aircraf fill:#dcfce7,stroke:#22c55e,color:#14532d Hover or focus a block to preview it. Select the block to keep the preview open.
1 question
Is the Aircraft currently online?
2 question
Was the Aircraft last restarted more than 24 hours ago?
- Last restart time is visible in FleetWrangler in the Detailed Zip Status section.
- Last restart time is visible in FleetWrangler in the Detailed Zip Status section.
3 action
Power cycle the Aircraft (Power Cycle Aircraft).
4 question
SSH into both compute boards via the Dock (SSH into Compute A/B). Can you SSH into both compute boards?
5 action
This indicates that the Aircraft is offline in FleetWrangler. Follow Asset Offline Due To Comms/Provisioning Agent Error to bring it back online.
6 question
This indicates that one of the compute boards (compute_a or compute_b) is unreachable via SSH and has likely crashed. Are either of the compute boards accessible via SSH?
7 action
SSH into the reachable compute board (compute_a or compute_b), then follow these steps to bring it back online:
1. SSH into the reachable compute board (compute_a or compute_b) via the Dock. For steps, see SSH into Compute A/B.
2. Power OFF the Aircraft. For steps, see _UMM:_ Power Off Zip Using the Dock.
3. Power ON the Aircraft. For steps, see Power ON Aircraft.
1. SSH into the reachable compute board (compute_a or compute_b) via the Dock. For steps, see SSH into Compute A/B.
2. Power OFF the Aircraft. For steps, see _UMM:_ Power Off Zip Using the Dock.
3. Power ON the Aircraft. For steps, see Power ON Aircraft.
8 action
This indicates that neither compute board (compute_a or compute_b) is reachable and the Aircraft is likely OFF. Power ON the Aircraft. For steps, see Power ON Aircraft.
9 question
Is the issue resolved and the Aircraft back online in FleetWrangler?
10 action
Return the Aircraft to service.
11 action
Follow Zip Offline to get the Aircraft back online and return the Aircraft to service.
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.