Remote Access (rac) too much logs

Technical Support
, , ,
1

Hello Toradex team,

I hope you are all doing great!

Hardware:

uname:

  • Linux verdin-imx8mp-14777482 5.15.129-6.4.0+git.67c3153d20ff #1-TorizonCore SMP PREEMPT Wed Sep 27 12:30:36 UTC 2023 aarch64 aarch64 aarch64 GNU/Linux

Images tested:

  • torizon-core-docker-verdin-imx8mp-Tezi_6.4.0+build.5.tar (STABLE Release)

Guest OS:

  • macOS (M1 Pro ARM64)
  • Linux ubuntu (VM x86_64)

Issue:
So first thank you for giving me access to the beta of Remote Access. It’s working great ! I still have one issue, the journalctl logs, the rac write logs every 3 seconds just to tell me that No remote session found for device.

The problem is that the journalctl of other services such as the docker has been wipped for memory reason:

Dec 09 13:53:17 verdin-imx8mp-XXXXXXXXX rac[1383]: [2023-12-09T12:53:17Z INFO ] No remote session found for device
Dec 09 13:53:20 verdin-imx8mp-XXXXXXXXX rac[1383]: [2023-12-09T12:53:20Z INFO ] No remote session found for device
Dec 09 13:53:23 verdin-imx8mp-XXXXXXXXX rac[1383]: [2023-12-09T12:53:23Z INFO ] No remote session found for device
Dec 09 13:53:26 verdin-imx8mp-XXXXXXXXX rac[1383]: [2023-12-09T12:53:26Z INFO ] No remote session found for device
Dec 09 13:53:29 verdin-imx8mp-XXXXXXXXX rac[1383]: [2023-12-09T12:53:29Z INFO ] No remote session found for device
Dec 09 13:53:32 verdin-imx8mp-XXXXXXXXX rac[1383]: [2023-12-09T12:53:32Z INFO ] No remote session found for device
Dec 09 13:53:35 verdin-imx8mp-XXXXXXXXX rac[1383]: [2023-12-09T12:53:35Z INFO ] No remote session found for device
Dec 09 13:53:38 verdin-imx8mp-XXXXXXXXX rac[1383]: [2023-12-09T12:53:38Z INFO ] No remote session found for device
Dec 09 13:53:41 verdin-imx8mp-XXXXXXXXX rac[1383]: [2023-12-09T12:53:41Z INFO ] No remote session found for device
Dec 09 13:53:44 verdin-imx8mp-XXXXXXXXX rac[1383]: [2023-12-09T12:53:44Z INFO ] No remote session found for device
Dec 09 13:53:47 verdin-imx8mp-XXXXXXXXX rac[1383]: [2023-12-09T12:53:47Z INFO ] No remote session found for device
Dec 09 13:53:50 verdin-imx8mp-XXXXXXXXX rac[1383]: [2023-12-09T12:53:50Z INFO ] No remote session found for device
Dec 09 13:53:53 verdin-imx8mp-XXXXXXXXX rac[1383]: [2023-12-09T12:53:53Z INFO ] No remote session found for device
Dec 09 13:53:57 verdin-imx8mp-XXXXXXXXX rac[1383]: [2023-12-09T12:53:57Z INFO ] No remote session found for device

Is there a way to set the log LEVEL to ERROR or WARNING only to avoid this kind of unwanted messages ? I checked the CONFIG_FILE=/etc/rac/client.toml but there is no such thing.

Best regards,
M

2

Hi,

I hope you are all doing great!

We are doing pretty well :smiley: Hope you’re doing great as well

Is there a way to set the log LEVEL to ERROR or WARNING only to avoid this kind of unwanted messages ? I checked the CONFIG_FILE=/etc/rac/client.toml but there is no such thing.

This is a perfectly sensible request. I brought this up with the team that builds rac and they agree it would be pretty ergonomic to set the log level from the config file, but for the meantime, the nicest solution we could come up with was creating a systemd override like so:

sudo mkdir /etc/systemd/system/remote-access.service.d

and create the override file with vi or nano

torizon@verdin-am62-15133479:~$ cat /etc/systemd/system/remote-access.service.d/override.conf 
[Service]
Environment="RUST_LOG=rac=off"

To modify the log level, just change the off parameter which can be one of the following [0]:

error
warn
info
debug
trace
off (pseudo level to disable all logging for the target)

I hope this is helpful,

Cheers!

[0] env_logger - Rust

1 Like
3

Hello @leon.tx,

Thank you for your quick response !

I can confirm that you work around works. I’ll update my build to make it work like your example, that would be perfect for now.

Do you think you can update me, or point me where I can follow, whenever the team update the log level in the config file ? To make the code more clean.

Best regards,
M

1 Like
4

Yep, I’ll add this community thread to the internal ticketing system.

1 Like
5

Hello,

Has this issue been addressed? Seems like there are no log options in remote access .toml files, so is the workaround posted in this thread the way to go ?

6

Dear @stasgil,

Thank you for bringing this up again. As far as I can see there is currently no implementation available aside from the workaround mentioned above. I am however in contact with our TorizonOS team and will write you again, should any update arise.

Best regards,
Collin

7

Dear @stasgil,

I wanted to quickly inform you, that the feedback has been captured as a Github issue on the remote-access client repository here:

Best regards,
Collin

8

Thanks for the update Collin. Just to add, my issue with rac log pollution is with different log messages:

Dec 31 16:22:11 verdin-am62-15645518 rac[1315]: Backtrace omitted. Run with RUST_BACKTRACE=1 environment variable to display it.
Dec 31 16:22:11 verdin-am62-15645518 rac[1315]: Run with RUST_BACKTRACE=full to include source snippets.
Dec 31 16:22:14 verdin-am62-15645518 rac[1315]: [2025-12-31T16:22:14Z WARN ] could not connect to dbus:
Dec 31 16:22:14 verdin-am62-15645518 rac[1315]: 0: I/O error: No such file or directory (os error 2)
Dec 31 16:22:14 verdin-am62-15645518 rac[1315]: 1: No such file or directory (os error 2)
Dec 31 16:22:14 verdin-am62-15645518 rac[1315]:
Dec 31 16:22:14 verdin-am62-15645518 rac[1315]: Backtrace omitted. Run with RUST_BACKTRACE=1 environment variable to display it.
Dec 31 16:22:14 verdin-am62-15645518 rac[1315]: Run with RUST_BACKTRACE=full to include source snippets.
Dec 31 16:22:17 verdin-am62-15645518 rac[1315]: [2025-12-31T16:22:17Z WARN ] could not connect to dbus:
Dec 31 16:22:17 verdin-am62-15645518 rac[1315]: 0: I/O error: No such file or directory (os error 2)
Dec 31 16:22:17 verdin-am62-15645518 rac[1315]: 1: No such file or directory (os error 2)
Dec 31 16:22:17 verdin-am62-15645518 rac[1315]:
Dec 31 16:22:17 verdin-am62-15645518 rac[1315]: Backtrace omitted. Run with RUST_BACKTRACE=1 environment variable to display it.
Dec 31 16:22:17 verdin-am62-15645518 rac[1315]: Run with RUST_BACKTRACE=full to include source snippets.
Dec 31 16:22:20 verdin-am62-15645518 rac[1315]: [2025-12-31T16:22:20Z WARN ] could not connect to dbus:
Dec 31 16:22:20 verdin-am62-15645518 rac[1315]: 0: I/O error: No such file or directory (os error 2)
Dec 31 16:22:20 verdin-am62-15645518 rac[1315]: 1: No such file or directory (os error 2)
Dec 31 16:22:20 verdin-am62-15645518 rac[1315]:
Dec 31 16:22:20 verdin-am62-15645518 rac[1315]: Backtrace omitted. Run with RUST_BACKTRACE=1 environment variable to display it.
Dec 31 16:22:20 verdin-am62-15645518 rac[1315]: Run with RUST_BACKTRACE=full to include source snippets.
Dec 31 16:22:23 verdin-am62-15645518 rac[1315]: [2025-12-31T16:22:23Z WARN ] could not connect to dbus:
Dec 31 16:22:23 verdin-am62-15645518 rac[1315]: 0: I/O error: No such file or directory (os error 2)
Dec 31 16:22:23 verdin-am62-15645518 rac[1315]: 1: No such file or directory (os error 2)
Dec 31 16:22:23 verdin-am62-15645518 rac[1315]:
Dec 31 16:22:23 verdin-am62-15645518 rac[1315]: Backtrace omitted. Run with RUST_BACKTRACE=1 environment variable to display it.
Dec 31 16:22:23 verdin-am62-15645518 rac[1315]: Run with RUST_BACKTRACE=full to include source snippets.
Dec 31 16:22:26 verdin-am62-15645518 rac[1315]: [2025-12-31T16:22:26Z WARN ] could not connect to dbus:
Dec 31 16:22:26 verdin-am62-15645518 rac[1315]: 0: I/O error: No such file or directory (os error 2)
Dec 31 16:22:26 verdin-am62-15645518 rac[1315]: 1: No such file or directory (os error 2)
Dec 31 16:22:26 verdin-am62-15645518 rac[1315]:
Dec 31 16:22:26 verdin-am62-15645518 rac[1315]: Backtrace omitted. Run with RUST_BACKTRACE=1 environment variable to display it.
Dec 31 16:22:26 verdin-am62-15645518 rac[1315]: Run with RUST_BACKTRACE=full to include source snippets.
Dec 31 16:22:29 verdin-am62-15645518 rac[1315]: [2025-12-31T16:22:29Z WARN ] could not connect to dbus:
Dec 31 16:22:29 verdin-am62-15645518 rac[1315]: 0: I/O error: No such file or directory (os error 2)
Dec 31 16:22:29 verdin-am62-15645518 rac[1315]: 1: No such file or directory (os error 2)

9

Hmm those logs aren’t what are normally seen when using the remote access client. Is remote access actually working properly on your device?

Best Regards,
Jeremias

10

It seems to. It takes longer that pre OS7 from Initiating connection on the website to actually connecting to the device, but i thought it’s because of the changes to the remote-access tool.

11

What version of the OS are you on specifically?

I checked on my setup and with the latest release at the time (7.4.0). These are what my logs look like with the remote access client running idly in the background:

Jan 07 18:40:10 verdin-am62-15133500 systemd[1]: Torizon Remote Access Client was skipped because no trigger condition checks were met.
Jan 07 18:42:45 verdin-am62-15133500 systemd[1]: Starting Torizon Remote Access Client...
Jan 07 18:42:45 verdin-am62-15133500 sudo[1345]:     root : PWD=/ ; USER=torizon ; COMMAND=/usr/bin/mkdir -p /home/torizon/run/rac
Jan 07 18:42:45 verdin-am62-15133500 systemd[1]: Started Torizon Remote Access Client.
Jan 07 18:42:46 verdin-am62-15133500 rac[1353]: [2026-01-07T18:42:46Z INFO ] RAC/0.1.0 (3200bfc; 1970-01-01T00:00:00Z; rustc-1.75.0-aarch64-tdx-linux-gnu) started
Jan 07 18:42:46 verdin-am62-15133500 rac[1353]: [2026-01-07T18:42:46Z INFO ] Config file set to /etc/rac/client.toml
Jan 07 18:42:46 verdin-am62-15133500 rac[1353]: [2026-01-07T18:42:46Z INFO ] Dropped privileges to torizon:torizon
Jan 07 18:42:46 verdin-am62-15133500 rac[1353]: [2026-01-07T18:42:46Z WARN ] Could not read private key, generated a new key: SHA256:tXGo8l4P/aJp89V/i8JDoyl9nenwltENpEMRBbqeGlY
Jan 07 18:42:46 verdin-am62-15133500 rac[1353]: [2026-01-07T18:42:46Z INFO ] Adding device public key to ras: SHA256:tXGo8l4P/aJp89V/i8JDoyl9nenwltENpEMRBbqeGlY
Jan 07 18:42:46 verdin-am62-15133500 rac[1353]: [2026-01-07T18:42:46Z INFO ] subscribed to dbus signals
Jan 07 18:42:46 verdin-am62-15133500 rac[1353]: [2026-01-07T18:42:46Z INFO ] No remote session found for device
Jan 07 18:42:46 verdin-am62-15133500 rac[1353]: [2026-01-07T18:42:46Z INFO ] no sessions available in RAS
Jan 07 18:43:17 verdin-am62-15133500 rac[1353]: [2026-01-07T18:43:17Z INFO ] No remote session found for device
Jan 07 18:43:17 verdin-am62-15133500 rac[1353]: [2026-01-07T18:43:17Z INFO ] no sessions available in RAS
Jan 07 18:43:47 verdin-am62-15133500 rac[1353]: [2026-01-07T18:43:47Z INFO ] No remote session found for device
Jan 07 18:43:47 verdin-am62-15133500 rac[1353]: [2026-01-07T18:43:47Z INFO ] no sessions available in RAS
Jan 07 18:44:17 verdin-am62-15133500 rac[1353]: [2026-01-07T18:44:17Z INFO ] No remote session found for device
Jan 07 18:44:17 verdin-am62-15133500 rac[1353]: [2026-01-07T18:44:17Z INFO ] no sessions available in RAS
Jan 07 18:44:48 verdin-am62-15133500 rac[1353]: [2026-01-07T18:44:48Z INFO ] No remote session found for device
Jan 07 18:44:48 verdin-am62-15133500 rac[1353]: [2026-01-07T18:44:48Z INFO ] no sessions available in RAS
Jan 07 18:45:18 verdin-am62-15133500 rac[1353]: [2026-01-07T18:45:18Z INFO ] No remote session found for device
Jan 07 18:45:18 verdin-am62-15133500 rac[1353]: [2026-01-07T18:45:18Z INFO ] no sessions available in RAS
Jan 07 18:45:48 verdin-am62-15133500 rac[1353]: [2026-01-07T18:45:48Z INFO ] No remote session found for device
Jan 07 18:45:48 verdin-am62-15133500 rac[1353]: [2026-01-07T18:45:48Z INFO ] no sessions available in RAS
Jan 07 18:46:18 verdin-am62-15133500 rac[1353]: [2026-01-07T18:46:18Z INFO ] No remote session found for device
Jan 07 18:46:18 verdin-am62-15133500 rac[1353]: [2026-01-07T18:46:18Z INFO ] no sessions available in RAS
Jan 07 18:46:49 verdin-am62-15133500 rac[1353]: [2026-01-07T18:46:49Z INFO ] No remote session found for device
Jan 07 18:46:49 verdin-am62-15133500 rac[1353]: [2026-01-07T18:46:49Z INFO ] no sessions available in RAS
Jan 07 18:47:19 verdin-am62-15133500 rac[1353]: [2026-01-07T18:47:19Z INFO ] No remote session found for device
Jan 07 18:47:19 verdin-am62-15133500 rac[1353]: [2026-01-07T18:47:19Z INFO ] no sessions available in RAS
Jan 07 18:47:50 verdin-am62-15133500 rac[1353]: [2026-01-07T18:47:50Z INFO ] No remote session found for device
Jan 07 18:47:50 verdin-am62-15133500 rac[1353]: [2026-01-07T18:47:50Z INFO ] no sessions available in RAS

This is more what I would expect to see compared to the logs you shared. Meaning something is likely strange about your setup to cause this difference. If you’re on an older version could have been an old bug or behavior that got fixed/improved in later versions.

Best Regards,
Jeremias