0x0003014A ZIP_EXECUTIVE_CODE_SECONDARY_CONTROLLER_NOT_STARTED_UP
Viewing this guide for
Applicable alarms (2)
0x0003014AZIP_EXECUTIVE_CODE_SECONDARY_CONTROLLER_NOT_STARTED_UP
Likely outcomes — click to expand
Based on 0 missions where this alarm fired in the last
90 days
(for 0x0003014A) 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 error code indicates that the the secondary controller is not yet started up (all services have not started running on Compute B ) and so the zip is not yet ready to accept missions.
Troubleshooting Steps
Section titled “Troubleshooting Steps”graph TD
are-any-of-the-following-alarms-on-the{"<small><b>Step 1</b></small><br/>Question: Are any Exec watchdog alarms set for ..."}
follow-the-steps-in-compute-b-generic-w("<small><b>Step 2</b></small><br/>Reference: For COMPUTE_B_STATUS_UNAVAILABLE and ...")
check-flight-target-command-and-state-go{"<small><b>Step 3</b></small><br/>Question: Check flight target command and state..."}
escalate-to-p2-exec-on-call{{"<small><b>Step 4</b></small><br/>Escalation: Escalate to P2 Exec On Call."}}
ssh-into-the-aircraft-and-start-the-fli["<small><b>Step 5</b></small><br/>Action: SSH into the Aircraft and start the f..."]
is-the-flight-target-running-on-both-co{"<small><b>Step 6</b></small><br/>Question: Is the flight target running on both ..."}
escalate-to-p2-embedded-platform-on-cal{{"<small><b>Step 7</b></small><br/>Escalation: Escalate to P2 Embedded Platform On C..."}}
is-the-issue-resolved{"<small><b>Step 8</b></small><br/>Question: Is the issue resolved?"}
the-aircraft-may-return-to-service("<small><b>Step 9</b></small><br/>Reference: The Aircraft may return to service.")
escalate-to-p2-exec-on-call-final{{"<small><b>Step 10</b></small><br/>Escalation: Escalate to P2 Exec On Call."}}
are-any-of-the-following-alarms-on-the -->|Yes| follow-the-steps-in-compute-b-generic-w
are-any-of-the-following-alarms-on-the -->|No| check-flight-target-command-and-state-go
check-flight-target-command-and-state-go -->|Yes| escalate-to-p2-exec-on-call
check-flight-target-command-and-state-go -->|No| ssh-into-the-aircraft-and-start-the-fli
ssh-into-the-aircraft-and-start-the-fli --> is-the-flight-target-running-on-both-co
is-the-flight-target-running-on-both-co -->|Yes| is-the-issue-resolved
is-the-flight-target-running-on-both-co -->|No| escalate-to-p2-embedded-platform-on-cal
is-the-issue-resolved -->|Yes| the-aircraft-may-return-to-service
is-the-issue-resolved -->|No| escalate-to-p2-exec-on-call-final
style are-any-of-the-following-alarms-on-the fill:#dbeafe,stroke:#3b82f6,color:#1e3a5f
style follow-the-steps-in-compute-b-generic-w fill:#f3e8ff,stroke:#a855f7,color:#581c87
style check-flight-target-command-and-state-go fill:#dbeafe,stroke:#3b82f6,color:#1e3a5f
style escalate-to-p2-exec-on-call fill:#fef3c7,stroke:#f59e0b,color:#78350f
style ssh-into-the-aircraft-and-start-the-fli fill:#dcfce7,stroke:#22c55e,color:#14532d
style is-the-flight-target-running-on-both-co fill:#dbeafe,stroke:#3b82f6,color:#1e3a5f
style escalate-to-p2-embedded-platform-on-cal fill:#fef3c7,stroke:#f59e0b,color:#78350f
style is-the-issue-resolved fill:#dbeafe,stroke:#3b82f6,color:#1e3a5f
style the-aircraft-may-return-to-service fill:#f3e8ff,stroke:#a855f7,color:#581c87
style escalate-to-p2-exec-on-call-final fill:#fef3c7,stroke:#f59e0b,color:#78350f Hover or focus a block to preview it. Select the block to keep the preview open.
1 question
Are any Exec watchdog alarms set for the Compute B heartbeat or Compute B nav outputs?
On
- COMPUTE_B_STATUS_UNAVAILABLE
On
- ZIP_LOCAL_T_ECEF_UNAVAILABLE
- LOCAL_TD_BODY_UNAVAILABLE
- NAV_STATE_FOR_CONTROLS_STATUS_UNAVAILABLE
- NAVIGATION_STATUS_UNAVAILABLE
- NAV_STATE_FOR_CONTROLS_UNAVAILABLE
- DOCK_TRANSFORMS_UNAVAILABLE
- LOCALIZATION_STATUS_UNAVAILABLE
- NAV_GPST_SYNC_UNAVAILABLE
On
/compute_a.zip_executive_v4.status, check for:- COMPUTE_B_STATUS_UNAVAILABLE
On
/compute_b.zip_executive_v4.status, check for:- ZIP_LOCAL_T_ECEF_UNAVAILABLE
- LOCAL_TD_BODY_UNAVAILABLE
- NAV_STATE_FOR_CONTROLS_STATUS_UNAVAILABLE
- NAVIGATION_STATUS_UNAVAILABLE
- NAV_STATE_FOR_CONTROLS_UNAVAILABLE
- DOCK_TRANSFORMS_UNAVAILABLE
- LOCALIZATION_STATUS_UNAVAILABLE
- NAV_GPST_SYNC_UNAVAILABLE
2 reference
For COMPUTE_B_STATUS_UNAVAILABLE and non-dock nav-output watchdog alarms, follow Embedded Linux Watchdog Alarms. For DOCK_TRANSFORMS_UNAVAILABLE, follow Dock Not Communicating with Aircraft.
3 question
Check flight target command and state. Go to Bazara Log plots apply the “Flight Target State” template. Example logs.
The topic to look at is
Is the flight target state on compute B
The topic to look at is
/compute_b.systemd_target_agent.flight_state?.statusIs the flight target state on compute B
STARTED? 4 escalation
Escalate to P2 Exec On Call.
5 action
SSH into the Aircraft and start the flight target on compute B. Restart Flight Target.
6 question
Is the flight target running on both computes A and B?
7 escalation
Escalate to P2 Embedded Platform On Call.
8 question
Is the issue resolved?
9 reference
The Aircraft may return to service.
10 escalation
Escalate to P2 Exec 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.