Updating my image through Toradex Cloud failed

Technical Support
, , ,
2

Hi, I’m the Toradex AI Assistant.

I might make mistakes. Our support team will step in if needed. If I answered your question, please tick the “Solution” checkbox. For follow-up questions to me, please use @ToradexAI in your post.

Did you like my answer? :+1: :-1:

Hello Tarek,

Thank you for your detailed description of the issue. It looks like you are experiencing repeated OTA update failures with your Apalis iMX8 board, even after troubleshooting steps like switching hardware and reconnecting to Torizon Cloud.

Given what you described, here are some steps and checks you can perform:

  1. Network Stability:
    Even if your device seems connected from your side, please make sure the board has continuous network access throughout the entire update. Intermittent network dropouts can cause the OTA update process to fail since Torizon OS devices poll for updates roughly every 5 minutes and require a stable connection during the process (Reference).

  2. System Logs:
    Collect and analyze logs from your device during and after the update attempt. You can run the following command via SSH to check logs related to the Aktualizr client (the update agent):

    journalctl -u aktualizr.service

    Also, inspect general kernel and system logs:

    dmesg
journalctl -xe

  3. Power Supply:
    Unstable power during the update process can make the device go offline and roll back the update. Please double-check your power supply for voltage drops or interruptions.

  4. Image Signature and Integrity:
    Torizon OTA requires images to be signed and verified for integrity and authenticity (Reference). If your uploaded image has expired signatures or has been corrupted, the update will fail. It is worth trying to re-upload a fresh version of your application/container to Torizon Cloud and trigger the deployment again.

  5. Device Status on Torizon Cloud:
    After a failed update, check the device status and any error messages in the Torizon Cloud web interface. Sometimes, the Cloud dashboard will show more specific logs or failure reasons.

  6. Rollback Behavior:
    When an OTA update fails, Torizon OS uses atomic updates with built-in rollback for robustness. This means failed updates won’t brick your system, but continual failures indicate an underlying issue to be resolved (Reference).

  7. Other Troubleshooting:

    • Restart the board and retry the update after a clean boot.
    • Check for firewall/proxy on your network that could interfere with TLS or HTTPS connections, which are required for secure OTA updates.
    • Confirm you are using a supported OS version and that your image is compatible with Torizon OS 6.

If you still cannot determine the cause from the steps above, please provide:

  • Any error messages from the update attempts (from system logs or Torizon Cloud dashboard)
  • The output of journalctl -u aktualizr.service
  • A description of your network setup (direct connection, behind NAT, VPN, etc.)

Here are some helpful reference links for further reading:

Let me know what you discover or if you can share more logs or information.

Best regards,
Toradex AI Assistant.