Hello,
I have updated a couple of devices to Torizon OS 7.1 (On Verdin am62 modules). Everything seems to work, but in journalctl logs i see this:
Apr 24 19:02:22 verdin-am62-15361843 tzn-mqtt[884]: 2025-04-24T19:02:22.480Z ERROR tzn_mqtt::dbus::server > Could not connect to DBus:
Apr 24 19:02:22 verdin-am62-15361843 tzn-mqtt[884]: 0: I/O error: No such file or directory (os error 2)
Apr 24 19:02:22 verdin-am62-15361843 tzn-mqtt[884]: 1: No such file or directory (os error 2)
Apr 24 19:02:22 verdin-am62-15361843 tzn-mqtt[884]: Location:
Apr 24 19:02:22 verdin-am62-15361843 tzn-mqtt[884]: /usr/src/debug/libstd-rs/1.75.0/rustc-1.75.0-src/library/core/src/convert/mod.rs:757
Apr 24 19:02:22 verdin-am62-15361843 tzn-mqtt[884]: Backtrace omitted. Run with RUST_BACKTRACE=1 environment variable to display it.
Apr 24 19:02:22 verdin-am62-15361843 tzn-mqtt[884]: Run with RUST_BACKTRACE=full to include source snippets.
Apr 24 19:02:22 verdin-am62-15361843 tzn-mqtt[884]: 2025-04-24T19:02:22.480Z INFO tzn_mqtt::dbus::server > Retrying in 3 seconds…
contents of /usr/src:
root@verdin-am62-15207026:/var/rootdirs/home/torizon# ls /usr/src/
linux.tar.bz2
dbus daemon seems to be running. Also one of our containers uses dbus for communicating with bluetooth daemon, and that seems to work fine.
From the short description in the OS7 release notes, I understood that mqtt is meant to replace http communication of remote access client? At least it seems that i can still remotely access the devices despite this error.
Hi, I’m the Toradex AI Assistant. The Toradex Support team will follow up with you shortly!
Did you like my answer?
Hello,
Thank you for reaching out with your question. Based on the available documentation, I can confirm that the Remote Access functionality in Torizon continues to operate through SSH even if there are MQTT errors. This feature utilizes a secure SSH implementation on the client-side, ensuring reliable remote access.
However, the documentation does not provide specific details about the MQTT implementation in Torizon OS 7, the relationship between MQTT and HTTP for remote access, or the specific DBus error you are encountering. If you have further questions about these topics, I recommend exploring the general capabilities of Remote Access as documented.
If you need more detailed information, please feel free to ask, and I’ll do my best to assist you within the scope of software and system configuration.
Best regards,
Toradex AI Assistant
Greetings @stasgil,
I have updated a couple of devices to Torizon OS 7.1
Could you please elaborate on this point. When you say “updated” do you mean an actual software update with Torizon Cloud? If yes, what version did you update from to 7.1?
Furthermore, regarding the actual logs you shared. We do have a tzn-mqtt.service on Torizon OS however, this service was disabled by default on 7.1, it was only enabled by default on 7.2 onward. Though you mentioned you are using remote-access, this would also invoke the tzn-mqtt service to start even if it’s disabled.
As for the actual service it’s only real purpose currently is to work with the remote-access service to optimize bandwidth use. Though it’s not strictly required for the remote-access to work it’s an optional optimization.
For reference on my side I can see the tzn-mqtt service fails and retries a several times before it successfully connects to DBus. This could also be what is happening on your side:
tzn-mqtt logs
...
Apr 24 22:58:30 apalis-imx8-06738453 tzn-mqtt[988]: 2025-04-24T22:58:30.469Z ERROR tzn_mqtt::dbus::server > Could not connect to DBus:
Apr 24 22:58:30 apalis-imx8-06738453 tzn-mqtt[988]: 0: I/O error: No such file or directory (os error 2)
Apr 24 22:58:30 apalis-imx8-06738453 tzn-mqtt[988]: 1: No such file or directory (os error 2)
Apr 24 22:58:30 apalis-imx8-06738453 tzn-mqtt[988]: Location:
Apr 24 22:58:30 apalis-imx8-06738453 tzn-mqtt[988]: /usr/src/debug/libstd-rs/1.75.0/rustc-1.75.0-src/library/core/src/convert/mod.rs:757
Apr 24 22:58:30 apalis-imx8-06738453 tzn-mqtt[988]: Backtrace omitted. Run with RUST_BACKTRACE=1 environment variable to display it.
Apr 24 22:58:30 apalis-imx8-06738453 tzn-mqtt[988]: Run with RUST_BACKTRACE=full to include source snippets.
Apr 24 22:58:30 apalis-imx8-06738453 tzn-mqtt[988]: 2025-04-24T22:58:30.469Z INFO tzn_mqtt::dbus::server > Retrying in 3 seconds...
Apr 24 22:58:33 apalis-imx8-06738453 tzn-mqtt[988]: 2025-04-24T22:58:33.471Z INFO tzn_mqtt::dbus::server > Attempting to connect to DBus
Apr 24 22:58:33 apalis-imx8-06738453 tzn-mqtt[988]: 2025-04-24T22:58:33.472Z ERROR tzn_mqtt::dbus::server > Failed to connect to DBus: InputOutput(Os { code: 2, kind: NotFound, message: "No such file or directory" })
Apr 24 22:58:33 apalis-imx8-06738453 tzn-mqtt[988]: 2025-04-24T22:58:33.472Z ERROR tzn_mqtt::dbus::server > Could not connect to DBus:
Apr 24 22:58:33 apalis-imx8-06738453 tzn-mqtt[988]: 0: I/O error: No such file or directory (os error 2)
Apr 24 22:58:33 apalis-imx8-06738453 tzn-mqtt[988]: 1: No such file or directory (os error 2)
Apr 24 22:58:33 apalis-imx8-06738453 tzn-mqtt[988]: Location:
Apr 24 22:58:33 apalis-imx8-06738453 tzn-mqtt[988]: /usr/src/debug/libstd-rs/1.75.0/rustc-1.75.0-src/library/core/src/convert/mod.rs:757
Apr 24 22:58:33 apalis-imx8-06738453 tzn-mqtt[988]: Backtrace omitted. Run with RUST_BACKTRACE=1 environment variable to display it.
Apr 24 22:58:33 apalis-imx8-06738453 tzn-mqtt[988]: Run with RUST_BACKTRACE=full to include source snippets.
Apr 24 22:58:33 apalis-imx8-06738453 tzn-mqtt[988]: 2025-04-24T22:58:33.472Z INFO tzn_mqtt::dbus::server > Retrying in 3 seconds...
Apr 24 22:58:36 apalis-imx8-06738453 tzn-mqtt[988]: 2025-04-24T22:58:36.473Z INFO tzn_mqtt::dbus::server > Attempting to connect to DBus
Apr 24 22:58:36 apalis-imx8-06738453 tzn-mqtt[988]: 2025-04-24T22:58:36.474Z ERROR tzn_mqtt::dbus::server > Failed to connect to DBus: InputOutput(Os { code: 2, kind: NotFound, message: "No such file or directory" })
Apr 24 22:58:36 apalis-imx8-06738453 tzn-mqtt[988]: 2025-04-24T22:58:36.474Z ERROR tzn_mqtt::dbus::server > Could not connect to DBus:
Apr 24 22:58:36 apalis-imx8-06738453 tzn-mqtt[988]: 0: I/O error: No such file or directory (os error 2)
Apr 24 22:58:36 apalis-imx8-06738453 tzn-mqtt[988]: 1: No such file or directory (os error 2)
Apr 24 22:58:36 apalis-imx8-06738453 tzn-mqtt[988]: Location:
Apr 24 22:58:36 apalis-imx8-06738453 tzn-mqtt[988]: /usr/src/debug/libstd-rs/1.75.0/rustc-1.75.0-src/library/core/src/convert/mod.rs:757
Apr 24 22:58:36 apalis-imx8-06738453 tzn-mqtt[988]: Backtrace omitted. Run with RUST_BACKTRACE=1 environment variable to display it.
Apr 24 22:58:36 apalis-imx8-06738453 tzn-mqtt[988]: Run with RUST_BACKTRACE=full to include source snippets.
Apr 24 22:58:36 apalis-imx8-06738453 tzn-mqtt[988]: 2025-04-24T22:58:36.474Z INFO tzn_mqtt::dbus::server > Retrying in 3 seconds...
Apr 24 22:58:39 apalis-imx8-06738453 tzn-mqtt[988]: 2025-04-24T22:58:39.475Z INFO tzn_mqtt::dbus::server > Attempting to connect to DBus
Apr 24 22:58:39 apalis-imx8-06738453 tzn-mqtt[988]: 2025-04-24T22:58:39.476Z ERROR tzn_mqtt::dbus::server > Failed to connect to DBus: InputOutput(Os { code: 2, kind: NotFound, message: "No such file or directory" })
Apr 24 22:58:39 apalis-imx8-06738453 tzn-mqtt[988]: 2025-04-24T22:58:39.476Z ERROR tzn_mqtt::dbus::server > Could not connect to DBus:
Apr 24 22:58:39 apalis-imx8-06738453 tzn-mqtt[988]: 0: I/O error: No such file or directory (os error 2)
Apr 24 22:58:39 apalis-imx8-06738453 tzn-mqtt[988]: 1: No such file or directory (os error 2)
Apr 24 22:58:39 apalis-imx8-06738453 tzn-mqtt[988]: Location:
Apr 24 22:58:39 apalis-imx8-06738453 tzn-mqtt[988]: /usr/src/debug/libstd-rs/1.75.0/rustc-1.75.0-src/library/core/src/convert/mod.rs:757
Apr 24 22:58:39 apalis-imx8-06738453 tzn-mqtt[988]: Backtrace omitted. Run with RUST_BACKTRACE=1 environment variable to display it.
Apr 24 22:58:39 apalis-imx8-06738453 tzn-mqtt[988]: Run with RUST_BACKTRACE=full to include source snippets.
Apr 24 22:58:39 apalis-imx8-06738453 tzn-mqtt[988]: 2025-04-24T22:58:39.476Z INFO tzn_mqtt::dbus::server > Retrying in 3 seconds...
Apr 24 22:58:42 apalis-imx8-06738453 tzn-mqtt[988]: 2025-04-24T22:58:42.477Z INFO tzn_mqtt::dbus::server > Attempting to connect to DBus
Apr 24 22:58:42 apalis-imx8-06738453 tzn-mqtt[988]: 2025-04-24T22:58:42.491Z INFO tzn_mqtt::dbus::server > Connected to DBus successfully
Not sure if this many attempts though are expected, I’ll check with our team on that point. Though overall you can probably disregard these logs and they should not be harmful for the overall system.
Best Regards,
Jeremias
Yes, i mean update OS package using torizon cloud.
One device went from 6.8.1 to 7.1
Two devices went from 6.7.0 to 7.1
root@verdin-am62-15361843:/var/rootdirs/home/torizon# uname -a
Linux verdin-am62-15361843 6.6.58-7.1.0-gf874412b7190 #1-Torizon SMP PREEMPT Fri Dec 6 14:07:48 UTC 2024 aarch64 GNU/Linux
Yes I was remotely accessing the devices, so i suppose that triggered the mqtt service to start.
It doesn’t seem that it harms the functionality of the system
On further investigation, this observation does not seem to be related to the update you performed. As I said prior, it seems the tzn-mqtt service fails and retries repeatedly until it finally connects to DBus. On one of my tests it took 15-20mins of looping retries before it finally connected, which is probably not intended.
That said, as we already discussed this doesn’t seem to be a critical issue that blocks anything on the system. Meaning you’re probably safe to disregard this for now. Meanwhile I’ll report the long looping retry behavior to our team for further investigation.
Best Regards,
Jeremias
