I’ve followed the steps to update the dockercompose using TorizonOta, but the TorizonOta is presenting error and does not update the Toradex Verdin Imx8mm
I’ve stopped all the containers through the command docker stop docker stop $(docker ps -a -q), then I’ve executed the steps below:
- I’ve add the toradex into TorizonOTA webpage
- I’ve used the default docker-compose-example-arm64
- I’ve tried to update the Toradex, but no success.
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
959d245aef22 torizon/torizon-provisioner:0.0.11 “/bin/sh” 11 minutes ago Exited (0) 11 minutes ago interesting_khayyam
8886edc4b3bb torizon/kiosk-mode-browser:2 “/usr/bin/start-brow…” About an hour ago Exited (0) About an hour ago torizon_kiosk_1
d759ddf193a2 torizon/weston-vivante:2 “/usr/bin/entry.sh -…” About an hour ago Exited (143) About an hour ago torizon_weston_1
5952b775253b vdalmeida/arm64estufanodejs “docker-entrypoint.s…” About an hour ago Exited (1) About an hour ago arm64estufanodejs
5b3d274d4b2f vdalmeida/arm64ihmestufaip “/usr/sbin/nginx -g …” About an hour ago Exited (0) About an hour ago arm64ihmestufaip
verdin-imx8mm-06827717:~$
Questions
- Should I delete all the images ? Why ?
- What more else can I do instead of performing the recovery mode ?
Hi @V_D_ALMEIDA ,
What exactly happens when you try updating your device? Does the device status in the webpage indicate ‘Update Failed’? Did you receive any error message at all?
What TorizonCore version is in the module? You can check it by running cat /etc/os-release
.
In any case, go to the website and try to update your device again with the same docker-compose.yml, but after doing so go to your device and run journalctl -f -u aktualizr*
. The terminal will continuously output aktualizr logs, which is the software responsible to check and apply any pending updates for the device.
Wait for around 5 minutes and see what happens when it tries getting and applying the update. Post the results here. You can press ctrl+c
in the terminal to stop outputting the logs.
With this we can have a better idea about what’s going on with your SoM.
Best regards,
Lucas Akira
Hello Lucas, thanks for helping me again bro !
I’ve performed the actions as it follows below:
What exactly happens when you try updating your device?
Just appear Update Failed
Does the device status in the webpage indicate ‘Update Failed’?
Yes
Did you receive any error message at all?
No
What TorizonCore version is in the module? You can check it by running cat /etc/os-release
.
verdin-imx8mm-06827717:~$ cat /etc/os-release
ID=torizon
NAME=“TorizonCore”
VERSION=“5.6.0+build.13 (dunfell)”
VERSION_ID=5.6.0-build.13
PRETTY_NAME=“TorizonCore 5.6.0+build.13 (dunfell)”
DISTRO_CODENAME=“dunfell”
BUILD_ID=“13”
ANSI_COLOR=“1;34”
VARIANT=“Docker”
In any case, go to the website and try to update your device again with the same docker-compose.yml, but after doing so go to your device and run journalctl -f -u aktualizr*
. The terminal will continuously output aktualizr logs, which is the software responsible to check and apply any pending updates for the device.
Wait for around 5 minutes and see what happens when it tries getting and applying the update. Post the results here. You can press ctrl+c
in the terminal to stop outputting the logs.
With this we can have a better idea about what’s going on with your SoM.
verdin-imx8mm-06827717:~$ journalctl -f -u aktualizr*
– Logs begin at Thu 1970-01-01 00:00:05 UTC. –
Jul 12 20:21:57 verdin-imx8mm-06827717 aktualizr-torizon[861]: curl error 6 (htt p code 0): Couldn’t resolve host name
Jul 12 20:21:58 verdin-imx8mm-06827717 aktualizr-torizon[861]: curl error 6 (htt p code 0): Couldn’t resolve host name
Jul 12 20:21:58 verdin-imx8mm-06827717 aktualizr-torizon[861]: Put manifest requ est failed: 6 Couldn’t resolve host name HTTP 0
Jul 12 20:21:58 verdin-imx8mm-06827717 aktualizr-torizon[861]: Error sending man ifest!
Jul 12 20:21:58 verdin-imx8mm-06827717 aktualizr-torizon[861]: curl error 6 (htt p code 0): Couldn’t resolve host name
Jul 12 20:21:59 verdin-imx8mm-06827717 aktualizr-torizon[861]: curl error 6 (htt p code 0): Couldn’t resolve host name
Jul 12 20:22:00 verdin-imx8mm-06827717 aktualizr-torizon[861]: curl error 6 (htt p code 0): Couldn’t resolve host name
Jul 12 20:22:00 verdin-imx8mm-06827717 aktualizr-torizon[861]: curl error 6 (htt p code 0): Couldn’t resolve host name
Jul 12 20:22:01 verdin-imx8mm-06827717 aktualizr-torizon[861]: curl error 6 (htt p code 0): Couldn’t resolve host name
Jul 12 20:22:04 verdin-imx8mm-06827717 aktualizr-torizon[861]: Event: UpdateChec kComplete, Result - No updates available
Jul 12 20:27:03 verdin-imx8mm-06827717 aktualizr-torizon[861]: PROXY: sending de vice data to Torizon OTA.
Jul 12 20:27:05 verdin-imx8mm-06827717 aktualizr-torizon[861]: Event: SendDevice DataComplete
Jul 12 20:27:19 verdin-imx8mm-06827717 aktualizr-torizon[861]: Current versions in storage and reported by OSTree do not match
Jul 12 20:27:20 verdin-imx8mm-06827717 aktualizr-torizon[861]: Connectivity is r estored.
Jul 12 20:27:23 verdin-imx8mm-06827717 aktualizr-torizon[861]: Current version f or ECU ID: 935e3227018b556823a426e87efcf0db9e336bdbaadc66a4c9a2a2660c076aa4 is u nknown
Jul 12 20:27:23 verdin-imx8mm-06827717 aktualizr-torizon[861]: New updates found in Director metadata. Checking Image repo metadata…
Jul 12 20:27:25 verdin-imx8mm-06827717 aktualizr-torizon[861]: Image repo Snapsh ot verification failed: Snapshot metadata hash verification failed
Jul 12 20:27:27 verdin-imx8mm-06827717 aktualizr-torizon[861]: Signature verific ation for Image repo Targets metadata failed
Jul 12 20:27:27 verdin-imx8mm-06827717 aktualizr-torizon[861]: Image repo Target verification failed: Hash metadata mismatch
Jul 12 20:27:28 verdin-imx8mm-06827717 aktualizr-torizon[861]: 1 new update foun d in both Director and Image repo metadata.
Jul 12 20:27:28 verdin-imx8mm-06827717 aktualizr-torizon[861]: Event: UpdateChec kComplete, Result - Updates available
Jul 12 20:27:28 verdin-imx8mm-06827717 aktualizr-torizon[861]: Update available. Acquiring the update lock…
Jul 12 20:27:28 verdin-imx8mm-06827717 aktualizr-torizon[861]: Current version f or ECU ID: 935e3227018b556823a426e87efcf0db9e336bdbaadc66a4c9a2a2660c076aa4 is u nknown
Jul 12 20:27:31 verdin-imx8mm-06827717 aktualizr-torizon[861]: Event: DownloadPr ogressReport, Progress at 100%
Jul 12 20:27:31 verdin-imx8mm-06827717 aktualizr-torizon[861]: Event: DownloadTa rgetComplete, Result - Success
Jul 12 20:27:31 verdin-imx8mm-06827717 aktualizr-torizon[861]: Event: AllDownloa dsComplete, Result - Success
Jul 12 20:27:31 verdin-imx8mm-06827717 aktualizr-torizon[861]: Current version f or ECU ID: 935e3227018b556823a426e87efcf0db9e336bdbaadc66a4c9a2a2660c076aa4 is u nknown
Jul 12 20:27:31 verdin-imx8mm-06827717 aktualizr-torizon[861]: Waiting for Secon daries to connect to start installation…
Jul 12 20:27:32 verdin-imx8mm-06827717 aktualizr-torizon[861]: Failed to update Director metadata: Rollback attempt
Jul 12 20:27:32 verdin-imx8mm-06827717 aktualizr-torizon[861]: Sending metadata to 935e3227018b556823a426e87efcf0db9e336bdbaadc66a4c9a2a2660c076aa4 failed: “VER IFICATION_FAILED”:3 Failed to update Director metadata: Rollback attempt
Jul 12 20:27:32 verdin-imx8mm-06827717 aktualizr-torizon[861]: Event: AllInstall sComplete, Result - docker-compose:VERIFICATION_FAILED
Jul 12 20:27:32 verdin-imx8mm-06827717 aktualizr-torizon[861]: Update install co mpleted. Releasing the update lock…
Jul 12 20:27:32 verdin-imx8mm-06827717 aktualizr-torizon[861]: Current versions in storage and reported by OSTree do not match
Jul 12 20:27:33 verdin-imx8mm-06827717 aktualizr-torizon[861]: Event: PutManifes tComplete, Result - Success
Thanks for sending the logs! I’ll check internally here for further analysis.
In the meantime could you do a few more tests?
-
Try to update the operating system via the OTA platform: when selecting the component to update choose verdin-imx8mm
instead of docker-compose
.
-
You can select one of our monthly releases, for instance:
– Package: dunfell/verdin-imx8mm/torizon/torizon-core-docker/monthly
– Version: 5.7.0-devel-202206+build.24
-
See if the updates completes successfully or fails like the docker-compose.
-
Try to remove the docker-compose-example-arm64.yml in the OTA platform, all versions if you have more than one, and then add it again and try to update the device like you did before.
Just to be sure, is this the docker-compose that you’ve used?
docker-compose-example-arm64.yml (1.5 KB)
I successfully did an OTA update with the above file on a Verdin iMX8M Mini with a Dahlia Carrier Board.
Best regards,
Lucas Akira
I’ve performed a recovery mode in the Toradex, after that I update two different packages of DockerCompose, both worked.
If I face this issues again, I will perform these tests and send the feedback to you.
Thanks for all bro !
Glad things worked out for you!
Best regards,
Lucas Akira