"journalctl --user" replies "No journal files were found."

Autonomous Machines Jetson & Embedded Systems Jetson Orin NX
1

On Orin 64GB Developper kit, “journalctl --user” does not keep any messages even it may be affected by the daemons on systemd for /usr/lib/systemd/users.

I tried to check the log files on /run/log/journal/xxxxx, only found system logs.

 ls -l /run/log/journal/dbfef1aa0b064bcf9d30ec3ad0886edb/
total 24576
-rw-r-----+ 1 root systemd-journal 8388608 10月  2 11:22 system.journal
-rw-r-----+ 1 root systemd-journal 8388608 10月  1 19:21 system@adf9fdfb6bed4918b79b11c160883851-0000000000000001-00061b1bd30f41a0.journal
-rw-r-----+ 1 root systemd-journal 8388608 10月  2 10:59 system@adf9fdfb6bed4918b79b11c160883851-0000000000000519-00062367af918517.journal

For the purpose of comparison, a PC based ubuntu machine has journal logs like this;

 ls -l /var/log/journal/16c57505045b40f4a57439bf13f64ae5/
total 658760
-rw-r-----+ 1 root systemd-journal 16777216 10月  2 11:25 system.journal
-rw-r-----+ 1 root systemd-journal  8388608  6月 28 14:27 system@0303b7a44129466bb7e9410d79fbbf70-0000000000026b52-00061bec8185a6b7.journal
-rw-r-----+ 1 root systemd-journal  8388608  6月 28 14:32 system@0303b7a44129466bb7e9410d79fbbf70-000000000002734d-00061bec82a08877.journal
-rw-r-----+ 1 root systemd-journal  8388608  6月 24 13:50 
(snip)
-rw-r-----+ 1 root systemd-journal 16777216  9月 19 13:38 system@cb5f3171a63b4b88b9e181a71ce8791c-0000000000072a1a-000621e2684465bb.journal
-rw-r-----+ 1 root systemd-journal  8388608  8月  9 18:18 system@d652113475c64b81874fc11b0d5562fe-000000000005376f-00061f3c9f053121.journal
-rw-r-----+ 1 root systemd-journal 25165824  8月 19 13:40 system@d652113475c64b81874fc11b0d5562fe-0000000000053e41-00061f3c9f412bc7.journal
-rw-r-----+ 1 root systemd-journal  8388608  7月 26 16:33 system@d91d4ddc1a844372845bff6dab6e2842-000000000004797f-00061e2187a2184b.journal
-rw-r-----+ 1 root systemd-journal 33554432  8月  9 18:18 system@d91d4ddc1a844372845bff6dab6e2842-0000000000048071-00061e2187e10b0f.journal
-rw-r-----+ 1 root systemd-journal  8388608  8月 30 10:37 system@f72ce6756d14483780ac057ad504da86-0000000000066990-000620dca31930c8.journal
-rw-r-----+ 1 root systemd-journal 16777216  9月  6 18:02 system@f72ce6756d14483780ac057ad504da86-0000000000067072-000620dca3539967.journal
-rw-r-----+ 1 root systemd-journal  8388608  6月 28 14:40 system@fad28e6a08ee4d15a519e03968a8d9f6-0000000000028428-00061becac333e76.journal
-rw-r-----+ 1 root systemd-journal  8388608  6月 28 14:41 system@fad28e6a08ee4d15a519e03968a8d9f6-0000000000028d6f-00061becae9c59ad.journal
-rw-r-----+ 1 root systemd-journal  8388608 10月  2 11:14 user-1000.journal
-rw-r-----+ 1 root systemd-journal  8388608  6月 28 14:33 user-1000@0303b7a44129466bb7e9410d79fbbf70-000000000002734c-00061bec829fc09e.journal
-rw-r-----+ 1 root systemd-journal  8388608  6月 26 11:22 user-1000@0f3ee2e3cf424a218130e370cccee8db-000000000001f4be-00061b9b86f8bd34.journal
(snip)
-rw-r-----+ 1 root systemd-journal  8388608  9月  6 18:02 user-1000@f72ce6756d14483780ac057ad504da86-0000000000067071-000620dca35261c9.journal
-rw-r-----+ 1 root systemd-journal  8388608  6月 28 14:42 user-1000@fad28e6a08ee4d15a519e03968a8d9f6-0000000000028d6e-00061becae9b8617.journal

Is it required some additional settings such as /etc/systemd/journald.conf ?

3

Hi,
Generally we will run the command to check nvargus-daemon log:
Camera disconnection in nvargus-daemon service - #12 by ShaneCCC

Please check which log you would like to check and set -u. To see if the log is present.

4

First of all, the systems are running under --user status as their systemd unit files are placed on /usr/lib/systemd/user/.

In other Linux machines, journal files are placed under /var/log/journal/<<some hash>>/ like;

$ ls /var/log/journal/6b926026129d4fc8bec3965d3d7d63d7/
system@000613b4705c4492-de8bb5f5d82b92ee.journal~  system@00062271b22f9436-95701deeca2cd8fa.journal~
system@00061bc68209aeb3-e8ebd48b16f92be5.journal~  system@0006227219c7ce16-6500d19a4d47065a.journal~
system@00061bc7182e878b-5822b557b1937ade.journal~  system@d9a3f87de1894f5e813b2c1b1ddf6485-0000000000000415-000613b470586bd4.journal
system@00061bc7182f5933-de07f42578a4329c.journal~  system@d9a3f87de1894f5e813b2c1b1ddf6485-0000000000009631-00061de2f4071df6.journal
system@00061bc718313366-8ecbbbc35d24897b.journal~  system@d9a3f87de1894f5e813b2c1b1ddf6485-0000000000009f94-00061e5b10510128.journal
system@00061bd957c11046-84eee5cc99c23fa3.journal~  system@d9a3f87de1894f5e813b2c1b1ddf6485-000000000000ed60-0006227219c42870.journal
system@00061bd9b75c6f51-fc2b721666b969c9.journal~  system.journal
system@00061bdaa5f547e8-f3205ead92eeeb30.journal~  user-1000@00061bc753d62bc7-a26c6e88dcd2d2d1.journal~
system@00061bec41aeae46-425d76d40a7462d2.journal~  user-1000@00061bec7fb613ec-18200d846375e350.journal~
system@00061bec5b7c1b19-03351ef815bb9313.journal~  user-1000@00061becd9849972-eb28a69f45b5ab6b.journal~
system@00061bec5b7ca6da-205f05249dc739f5.journal~  user-1000@6442ba8150134bb282b4660ecd4fd3d2-00000000000002d4-000613b46fe5ed91.journal
system@00061bec5b7cdd7b-109f739a27945d57.journal~  user-1000@6442ba8150134bb282b4660ecd4fd3d2-0000000000007685-00061becd9844060.journal
system@00061de2f40ac1b2-6b7d98ecdb3b3fdc.journal~  user-1000@6442ba8150134bb282b4660ecd4fd3d2-0000000000009f93-00061e5b104f02e9.journal
system@000621702ce32fd8-82bf56e105a13d97.journal~  user-1000@6442ba8150134bb282b4660ecd4fd3d2-000000000000c5ee-0006211fb8555747.journal
system@000622617b6fccc8-352799e1958978f1.journal~  user-1000.journal

But ORINs has /run/log/journal/<<some hash>> (it usually used for volatile area, but ORIN keeps the log file after reboot) and has only one system journal log.

$ ls /run/log/journal/dbfef1aa0b064bcf9d30ec3ad0886edb/
system.journal  system@292e0ab9131d48e2bed9e6bb57300e94-0000000000000001-00061b1bd30f5c5b.journal

I guess that ORIN’s setup of journald is intensively changed for some reason.