Offline lockbox failing

[ToradexAI]

Hi, I’m the Toradex AI Assistant. The Toradex Support team will follow up with you shortly!

Did you like my answer?

---

Hello Mike,

Thank you for reaching out with your issue regarding the installation of a lockbox via USB on your Toradex Apalis iMX8 device. The error message “The root metadata was expired” indicates that the metadata used for the offline update is outdated. Here are some steps you can take to resolve this:

1. Update Metadata: Ensure that the metadata files in your lockbox are current. Metadata expiration is a security measure to prevent the use of outdated data.

2. Regenerate the Lockbox: Try creating a new lockbox with the latest data from the Torizon Platform:

   • Re-define the lockbox in the Torizon Platform Web UI to include the latest software and metadata.
   • Use the torizoncore-builder platform lockbox command to download the updated lockbox.

3. Provisioning Data: Verify that your device is provisioned with the latest root metadata. Ensure the provisioning data is correctly extracted into /var/sota/import/ on your device. Re-provision the device if necessary.

4. Configuration Check: Confirm that your device is set up to accept offline updates. Check the configuration files in /etc/sota/conf.d/ to ensure offline updates are enabled and correctly configured.

5. Credential Verification: Double-check that the credentials used for accessing the Torizon Platform are up-to-date and correctly applied. Ensure the credentials.zip file is the latest version and properly used in the lockbox creation process.

6. Log Monitoring: Continue to monitor the logs for any additional errors or warnings that might provide further insight into the issue.

By following these steps, you should be able to resolve the expired metadata issue and successfully perform the offline update. If you have any further questions, feel free to ask.

Best regards,
Toradex AI Assistant

Please, also check if these links can help you solve your problem:

Issues with private docker registries using torizoncore-builder 3.7.0+early-access

Hello, I am trying to create lockboxes on the torizon web platform. I ran into an issue with canonicalizing docker-compose files from a private registry. Based on the advice here: TCB cannot do "platform push" if private docker registry I downloaded the early access version of torizoncore-builder that implemented --login and --login-to for platform push. This successfully builds my canocalized docker-compose file when I use" --login" with my dockerhub credentials. This is uploaded to the toriz…

[aktualizr, offline updates] Found in archive a file with bad file type: 40960.