Retrieve Aircraft Logs After an Aircraft Paraland or a Droid left Behind
After the Aircraft has paralanded/DLB, the Zip Exec is blocked in start-up task and needs to be killed to force sleep state. Since the offloader is expecting a message from Executive to know when to offload (example, not during missions), the offloader configuration must be updated to force the offload and then to restart it.
graph TD
retrieve-aircraft-logs-paraland-step1["<small><b>Step 1</b></small><br/>Action: If possible, move the Aircraft to a m..."]
retrieve-aircraft-logs-paraland-step2["<small><b>Step 2</b></small><br/>Action: Power cycle the Aircraft Power Cycl..."]
retrieve-aircraft-logs-paraland-step3["<small><b>Step 3</b></small><br/>Action: Use a smart-cart and follow the steps..."]
retrieve-aircraft-logs-paraland-step4["<small><b>Step 4</b></small><br/>Action: If offload does not start after compl..."]
retrieve-aircraft-logs-paraland-step5["<small><b>Step 5</b></small><br/>Action: After the logs are offloaded, power-d..."]
retrieve-aircraft-logs-paraland-step1 --> retrieve-aircraft-logs-paraland-step2
retrieve-aircraft-logs-paraland-step2 --> retrieve-aircraft-logs-paraland-step3
retrieve-aircraft-logs-paraland-step3 --> retrieve-aircraft-logs-paraland-step4
retrieve-aircraft-logs-paraland-step4 --> retrieve-aircraft-logs-paraland-step5
style retrieve-aircraft-logs-paraland-step1 fill:#dcfce7,stroke:#22c55e,color:#14532d
style retrieve-aircraft-logs-paraland-step2 fill:#dcfce7,stroke:#22c55e,color:#14532d
style retrieve-aircraft-logs-paraland-step3 fill:#dcfce7,stroke:#22c55e,color:#14532d
style retrieve-aircraft-logs-paraland-step4 fill:#dcfce7,stroke:#22c55e,color:#14532d
style retrieve-aircraft-logs-paraland-step5 fill:#dcfce7,stroke:#22c55e,color:#14532d Hover or focus a block to preview it. Select the block to keep the preview open.
Symptom: Log offload is blocked
$ sudo journalctl -fu log_offloader
...
Aug 07 23:05:10 zip-compute-revH-SN59-a log_offloader_zip[13312]: Offload not allowed
Aug 07 23:05:14 zip-compute-revH-SN59-a log_offloader_zip[13312]: Offload not allowedSteps to complete on A then B computers:
# connect with ssh to A then B
sudo stop-flight
# update the offloader config to force offload
sudo sh -c "echo 'LOG_OFFLOAD_MODE=always' > /flight/config/log_offloader_options.env"
# restart the offloader and order injector
sudo systemctl restart log_offloader log_order_injection blob_agent
# confirm the offload is happening
sudo journalctl -fu executive.service -u log_offloader -u blob_agent
#...
#Aug 07 23:55:23 zip-compute-revH-SN59-a blob_agent[1969]: 2025-08-07T23:55:23.767313Z INFO blob_agent::clients::http_client: Uploaded with speed 543528.9718606562 bps ...Steps to complete on the Droid (if available)
# connect with ssh to Droid
sudo stop-flight
# update the offloader config to force offload
sudo sh -c "echo 'LOG_OFFLOAD_MODE=always' > /droid/config/log_offloader_options.env"
# restart the offloader and order injector
sudo systemctl restart log_offloader log_order_injection
# confirm the offload is happening
sudo journalctl -fu executive.service -u log_offloader -u blob_agent
# ...
# Aug 07 23:55:23 droid-compute-revH-SN59-a blob_agent[1969]: 2025-08-07T23:55:23.767313Z INFO blob_agent::clients::http_client: Uploaded with speed 543528.9718606562 bps ...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.