Torizon Secure Offline Synchronous Updates: Aktualizr Logs displays INTERNAL_ERROR even though it worked

Technical Support
, , , ,
1

Hi Toradex Community,

I am currently working with the following configuration:

  • TorizonCore 6.1.0 Build 1
  • Apalis iMX6
  • Ixora Carrier Board v1.2
  • Image provisioned for Offline Updates

I am currently attempting to perform Secure Offline Updates. I have 3 scenarios:

  1. TorizonCore OS Update: This works correctly using Lockboxes

  2. Custom Containers Update: This works correctly using Lockboxes

  3. Synchronous updates to include (1) and (2) in the same Lockbox: This works, even though I get a Event: AllInstallsComplete, Result - INTERNAL_ERROR message in the Aktualizr logs. See below for a print.

Aktualizr Logs 
torizon@apalis-imx6-10705361:/etc/sota/conf.d$ journalctl -f -u aktualizr*
Feb 22 23:27:05 apalis-imx6-10705361 aktualizr-torizon[1043]: Adding Secondary with ECU serial: a3aa2381ee506b306ad4e02f191ab7f0d9a259c66900b2a18a770d25b73cf879 with hardware ID: docker-compose
Feb 22 23:27:05 apalis-imx6-10705361 aktualizr-torizon[1043]: Initializing torizon-generic Secondaries...
Feb 22 23:27:05 apalis-imx6-10705361 aktualizr-torizon[1043]: Use existing SQL storage: "/var/sota/storage/bootloader/sql.db"
Feb 22 23:27:05 apalis-imx6-10705361 aktualizr-torizon[1043]: No valid metadata found in storage.
Feb 22 23:27:05 apalis-imx6-10705361 aktualizr-torizon[1043]: Adding Secondary with ECU serial: ee4bf32248b2a07c1fd6fb81f78f867b5533aa485f2f1a1fd0675b68e5e06575 with hardware ID: apalis-imx6-bootloader
Feb 22 23:27:05 apalis-imx6-10705361 aktualizr-torizon[1043]: PROXY: initializing...
Feb 22 23:27:05 apalis-imx6-10705361 aktualizr-torizon[1043]: PROXY: using TCP port 8850.
Feb 22 23:27:05 apalis-imx6-10705361 aktualizr-torizon[1043]: Offline Updates are enabled
Feb 22 23:27:05 apalis-imx6-10705361 aktualizr-torizon[1043]: PROXY: starting thread.
Feb 22 23:27:05 apalis-imx6-10705361 aktualizr-torizon[1043]: PROXY: listening to connections...
Feb 22 23:27:26 apalis-imx6-10705361 aktualizr-torizon[1043]: fetchMetaOffUpd() called with source_path: "/var/rootdirs/media/update"
Feb 22 23:27:26 apalis-imx6-10705361 aktualizr-torizon[1043]: Current version for ECU ID: 0fc548ccc7280aaed554b77637c6dcfa79d7050b524a87caf6608d7a35647f17 is unknown
Feb 22 23:27:26 apalis-imx6-10705361 aktualizr-torizon[1043]: Current version for ECU ID: a3aa2381ee506b306ad4e02f191ab7f0d9a259c66900b2a18a770d25b73cf879 is unknown
Feb 22 23:27:26 apalis-imx6-10705361 aktualizr-torizon[1043]: New updates found in Director metadata. Checking Image repo metadata...
Feb 22 23:27:26 apalis-imx6-10705361 aktualizr-torizon[1043]: 2 new updates found in both Director and Image repo metadata.
Feb 22 23:27:26 apalis-imx6-10705361 aktualizr-torizon[1043]: Event: UpdateCheckComplete, Result - Updates available
Feb 22 23:27:26 apalis-imx6-10705361 aktualizr-torizon[1043]: Update available. Acquiring the update lock...
Feb 22 23:27:26 apalis-imx6-10705361 aktualizr-torizon[1043]: Current version for ECU ID: 0fc548ccc7280aaed554b77637c6dcfa79d7050b524a87caf6608d7a35647f17 is unknown
Feb 22 23:27:26 apalis-imx6-10705361 aktualizr-torizon[1043]: Current version for ECU ID: a3aa2381ee506b306ad4e02f191ab7f0d9a259c66900b2a18a770d25b73cf879 is unknown
Feb 22 23:27:26 apalis-imx6-10705361 aktualizr-torizon[1043]: curl error 6 (http code 0): Couldn't resolve host name
Feb 22 23:27:27 apalis-imx6-10705361 aktualizr-torizon[1043]: Performing a local pull from file:///var/rootdirs/media/update/images/ostree
Feb 22 23:27:27 apalis-imx6-10705361 aktualizr-torizon[1043]: curl error 6 (http code 0): Couldn't resolve host name
Feb 22 23:27:28 apalis-imx6-10705361 aktualizr-torizon[1043]: ostree-pull: Scanning metadata: 103
Feb 22 23:27:28 apalis-imx6-10705361 aktualizr-torizon[1043]: Event: DownloadProgressReport, Progress at 0%
Feb 22 23:27:28 apalis-imx6-10705361 aktualizr-torizon[1043]: curl error 6 (http code 0): Couldn't resolve host name
Feb 22 23:27:29 apalis-imx6-10705361 aktualizr-torizon[1043]: ostree-pull: Writing objects: 1
Feb 22 23:27:30 apalis-imx6-10705361 aktualizr-torizon[1043]: ostree-pull: Scanning metadata: 440
Feb 22 23:27:30 apalis-imx6-10705361 aktualizr-torizon[1043]: Event: DownloadProgressReport, Progress at 0%
Feb 22 23:27:31 apalis-imx6-10705361 aktualizr-torizon[1043]: ostree-pull: Scanning metadata: 641
Feb 22 23:27:31 apalis-imx6-10705361 aktualizr-torizon[1043]: Event: DownloadProgressReport, Progress at 0%
Feb 22 23:27:34 apalis-imx6-10705361 aktualizr-torizon[1043]: ostree-pull: 10 metadata, 2 content objects imported; 10.0 MB content written
Feb 22 23:27:34 apalis-imx6-10705361 aktualizr-torizon[1043]: Event: DownloadTargetComplete, Result - Success
Feb 22 23:27:34 apalis-imx6-10705361 aktualizr-torizon[1043]: curl error 6 (http code 0): Couldn't resolve host name
Feb 22 23:27:35 apalis-imx6-10705361 aktualizr-torizon[1043]: curl error 6 (http code 0): Couldn't resolve host name
Feb 22 23:27:36 apalis-imx6-10705361 aktualizr-torizon[1043]: curl error 6 (http code 0): Couldn't resolve host name
Feb 22 23:27:36 apalis-imx6-10705361 aktualizr-torizon[1043]: curl error 6 (http code 0): Couldn't resolve host name
Feb 22 23:27:36 apalis-imx6-10705361 aktualizr-torizon[1043]: Initiating fetching of file farastarUpdate.lock.yml-4.1.0
Feb 22 23:27:36 apalis-imx6-10705361 aktualizr-torizon[1043]: Unable to read filesystem statistics: error code -1
Feb 22 23:27:36 apalis-imx6-10705361 aktualizr-torizon[1043]: Event: DownloadProgressReport, Progress at 100%
Feb 22 23:27:37 apalis-imx6-10705361 aktualizr-torizon[1043]: curl error 6 (http code 0): Couldn't resolve host name
Feb 22 23:27:38 apalis-imx6-10705361 aktualizr-torizon[1043]: curl error 6 (http code 0): Couldn't resolve host name
Feb 22 23:27:38 apalis-imx6-10705361 aktualizr-torizon[1043]: Event: DownloadTargetComplete, Result - Success
Feb 22 23:27:38 apalis-imx6-10705361 aktualizr-torizon[1043]: Event: AllDownloadsComplete, Result - Success
Feb 22 23:27:38 apalis-imx6-10705361 aktualizr-torizon[1043]: curl error 6 (http code 0): Couldn't resolve host name
Feb 22 23:27:38 apalis-imx6-10705361 aktualizr-torizon[1043]: Current version for ECU ID: 0fc548ccc7280aaed554b77637c6dcfa79d7050b524a87caf6608d7a35647f17 is unknown
Feb 22 23:27:38 apalis-imx6-10705361 aktualizr-torizon[1043]: Current version for ECU ID: a3aa2381ee506b306ad4e02f191ab7f0d9a259c66900b2a18a770d25b73cf879 is unknown
Feb 22 23:27:38 apalis-imx6-10705361 aktualizr-torizon[1043]: Waiting for Secondaries to connect to start installation...
Feb 22 23:27:39 apalis-imx6-10705361 aktualizr-torizon[1043]: curl error 6 (http code 0): Couldn't resolve host name
Feb 22 23:27:40 apalis-imx6-10705361 aktualizr-torizon[1043]: curl error 6 (http code 0): Couldn't resolve host name
Feb 22 23:27:40 apalis-imx6-10705361 aktualizr-torizon[1043]: Event: InstallStarted
Feb 22 23:27:40 apalis-imx6-10705361 aktualizr-torizon[1043]: curl error 6 (http code 0): Couldn't resolve host name
Feb 22 23:27:41 apalis-imx6-10705361 aktualizr-torizon[1043]: Installing package using ostree package manager
Feb 22 23:27:41 apalis-imx6-10705361 aktualizr-torizon[1043]: curl error 6 (http code 0): Couldn't resolve host name
Feb 22 23:27:42 apalis-imx6-10705361 aktualizr-torizon[1043]: Commit metadata kargs=quiet logo.nologo vt.global_cursor_default=0 plymouth.ignore-serial-consoles splash fbcon=map:3
Feb 22 23:27:42 apalis-imx6-10705361 aktualizr-torizon[1043]: curl error 6 (http code 0): Couldn't resolve host name
Feb 22 23:27:52 apalis-imx6-10705361 aktualizr-torizon[1043]: curl error 6 (http code 0): Couldn't resolve host name
Feb 22 23:27:53 apalis-imx6-10705361 aktualizr-torizon[1043]: curl error 6 (http code 0): Couldn't resolve host name
Feb 22 23:27:54 apalis-imx6-10705361 aktualizr-torizon[1043]: curl error 6 (http code 0): Couldn't resolve host name
Feb 22 23:27:55 apalis-imx6-10705361 aktualizr-torizon[1043]: note: Deploying commit 359711d07befa9aa3ae756ef17a0a82aac3cd00fea6b658611895994a7d3b43c which contains content in /var/local that will be ignored.
Feb 22 23:27:58 apalis-imx6-10705361 aktualizr-torizon[1043]: Copying /etc changes: 1 modified, 2 removed, 12 added
Feb 22 23:28:04 apalis-imx6-10705361 aktualizr-torizon[1043]: curl error 6 (http code 0): Couldn't resolve host name
Feb 22 23:28:05 apalis-imx6-10705361 aktualizr-torizon[1043]: curl error 6 (http code 0): Couldn't resolve host name
Feb 22 23:28:06 apalis-imx6-10705361 aktualizr-torizon[1043]: Transaction complete; bootconfig swap: yes; bootversion: boot.0.1, deployment count change: 1
Feb 22 23:28:06 apalis-imx6-10705361 aktualizr-torizon[1043]: curl error 6 (http code 0): Couldn't resolve host name
Feb 22 23:28:09 apalis-imx6-10705361 aktualizr-torizon[1043]: Performing sync()
Feb 22 23:28:10 apalis-imx6-10705361 aktualizr-torizon[1043]: Event: InstallTargetComplete, Result - Success
Feb 22 23:28:10 apalis-imx6-10705361 aktualizr-torizon[1043]: Event: InstallStarted
Feb 22 23:28:10 apalis-imx6-10705361 aktualizr-torizon[1043]: curl error 6 (http code 0): Couldn't resolve host name
Feb 22 23:28:11 apalis-imx6-10705361 aktualizr-torizon[1043]: curl error 6 (http code 0): Couldn't resolve host name
Feb 22 23:28:12 apalis-imx6-10705361 aktualizr-torizon[1043]: curl error 6 (http code 0): Couldn't resolve host name
Feb 22 23:28:12 apalis-imx6-10705361 aktualizr-torizon[1043]: curl error 6 (http code 0): Couldn't resolve host name
Feb 22 23:28:12 apalis-imx6-10705361 aktualizr-torizon[1043]: docker-compose file matches expected digest
Feb 22 23:28:12 apalis-imx6-10705361 aktualizr-torizon[1043]: Loading metadata from tarball: /var/rootdirs/media/update/images/070f32105239ed7b5d87e0c3ed5769a0cf7bb3876fd5211948f52941389173d3.images/fa48b997c43f22919fb4d0aaa1b7382a6b9173b60b92ec09134a98cdffd381bc.tar
Feb 22 23:28:13 apalis-imx6-10705361 aktualizr-torizon[1043]: curl error 6 (http code 0): Couldn't resolve host name
Feb 22 23:28:14 apalis-imx6-10705361 aktualizr-torizon[1043]: curl error 6 (http code 0): Couldn't resolve host name
Feb 22 23:28:24 apalis-imx6-10705361 aktualizr-torizon[1043]: curl error 6 (http code 0): Couldn't resolve host name
Feb 22 23:29:02 apalis-imx6-10705361 aktualizr-torizon[1043]: curl error 6 (http code 0): Couldn't resolve host name
Feb 22 23:29:16 apalis-imx6-10705361 aktualizr-torizon[1043]: curl error 6 (http code 0): Couldn't resolve host name
Feb 22 23:29:17 apalis-imx6-10705361 aktualizr-torizon[1043]: curl error 6 (http code 0): Couldn't resolve host name
Feb 22 23:32:03 apalis-imx6-10705361 aktualizr-torizon[1113]: Loaded image: anthonyabboud1994/farastar:digest_sha256_fa48b997c43f22919fb4d0aaa1b7382a6b9173b60b92ec09134a98cdffd381bc
Feb 22 23:32:04 apalis-imx6-10705361 aktualizr-torizon[1043]: Loading of "/var/rootdirs/media/update/images/070f32105239ed7b5d87e0c3ed5769a0cf7bb3876fd5211948f52941389173d3.images/fa48b997c43f22919fb4d0aaa1b7382a6b9173b60b92ec09134a98cdffd381bc.tar" finished, code: 0, status: success
Feb 22 23:32:04 apalis-imx6-10705361 aktualizr-torizon[1043]: Loading metadata from tarball: /var/rootdirs/media/update/images/070f32105239ed7b5d87e0c3ed5769a0cf7bb3876fd5211948f52941389173d3.images/23b07bb8ec6352a36f898b7919f771968827abec4f2be6a39f6e0ed0a9ef4577.tar
Feb 22 23:32:07 apalis-imx6-10705361 aktualizr-torizon[1043]: curl error 6 (http code 0): Couldn't resolve host name
Feb 22 23:32:10 apalis-imx6-10705361 aktualizr-torizon[1043]: curl error 6 (http code 0): Couldn't resolve host name
Feb 22 23:32:11 apalis-imx6-10705361 aktualizr-torizon[1043]: curl error 6 (http code 0): Couldn't resolve host name
Feb 22 23:32:21 apalis-imx6-10705361 aktualizr-torizon[1043]: curl error 6 (http code 0): Couldn't resolve host name
Feb 22 23:32:22 apalis-imx6-10705361 aktualizr-torizon[1043]: curl error 6 (http code 0): Couldn't resolve host name
Feb 22 23:34:03 apalis-imx6-10705361 aktualizr-torizon[1386]: Loaded image: anthonyabboud1994/weston:digest_sha256_23b07bb8ec6352a36f898b7919f771968827abec4f2be6a39f6e0ed0a9ef4577
Feb 22 23:34:04 apalis-imx6-10705361 aktualizr-torizon[1043]: Loading of "/var/rootdirs/media/update/images/070f32105239ed7b5d87e0c3ed5769a0cf7bb3876fd5211948f52941389173d3.images/23b07bb8ec6352a36f898b7919f771968827abec4f2be6a39f6e0ed0a9ef4577.tar" finished, code: 0, status: success
Feb 22 23:34:04 apalis-imx6-10705361 aktualizr-torizon[1043]: Updating containers via docker-compose
Feb 22 23:34:04 apalis-imx6-10705361 aktualizr-torizon[1043]: OSTree update pending. This is a synchronous update transaction.
Feb 22 23:34:04 apalis-imx6-10705361 aktualizr-torizon[1043]: Event: InstallTargetComplete, Result - Error
Feb 22 23:34:04 apalis-imx6-10705361 aktualizr-torizon[1043]: curl error 6 (http code 0): Couldn't resolve host name
Feb 22 23:34:04 apalis-imx6-10705361 aktualizr-torizon[1043]: Event: AllInstallsComplete, Result - INTERNAL_ERROR
Feb 22 23:34:04 apalis-imx6-10705361 aktualizr-torizon[1043]: Update install completed. Releasing the update lock...
Feb 22 23:34:05 apalis-imx6-10705361 aktualizr-torizon[1043]: Exiting aktualizr so that pending updates can be applied after reboot

Following this, I need to manually reboot the system for the changes to appear. Since my containers are quite big, I had to modify some settings, as mentioned by @jeremias.tx in the following thread to make it work: Synchronous offline updates broken - #14 by jeremias.tx

See below a screenshot of my Secure Offline Updates config files.
image

So I have 3 questions that arise from this:

  1. Since the reboot isn’t automated, is that intended during synchronous updates or did my configuration changes break it?
  2. Why am I getting an Internal Error message even though it seemed to have worked?
  3. Probably unrelated, but are all those curl error 6 (http code 0): Couldn't resolve host name expected? I’m not connected to the internet and I disabled online updates in the config file.

Thank you in advance,
Anthony

2

Since the reboot isn’t automated, is that intended during synchronous updates or did my configuration changes break it?

That’s weird the reboot should happen automatically after some time even with the workaround you referenced in that other post. Your changes look okay, are you sure the reboot isn’t happening?

Why am I getting an Internal Error message even though it seemed to have worked?

This is a known issue: TorizonCore Issue Tracker

It’s just a small logging bug.

Probably unrelated, but are all those curl error 6 (http code 0): Couldn't resolve host name expected? I’m not connected to the internet and I disabled online updates in the config file.

Those curl errors can be safely ignored.

Best Regards,
Jeremias