Arch Linux

pkill

Member

Registered: 2019-08-16

Posts: 6

Systemd Journal: No Early Boot Messages as User

I cant see any any early boot messages as user:

As root:

$ sudo journalctl | head -n 5
-- Logs begin at Sat 2019-08-24 06:26:12 CEST, end at Sat 2019-08-24 07:25:35 CEST. --
Aug 24 06:26:12 archlinux kernel: Linux version 5.2.9-arch1-1-ARCH (builduser@heftig-119803) (gcc version 9.1.0 (GCC)) #1 SMP PREEMPT Fri Aug 16 11:29:43 UTC 2019
Aug 24 06:26:12 archlinux kernel: Command line: BOOT_IMAGE=/vmlinuz-linux root=/dev/mapper/vg0-root rw consoleblank=0 systemd.show_status=1 iommu=pt quiet
Aug 24 06:26:12 archlinux kernel: KERNEL supported cpus:
Aug 24 06:26:12 archlinux kernel:   Intel GenuineIntel

As User:

$ journalctl | head -n 5
-- Logs begin at Sat 2019-08-24 06:26:20 CEST, end at Sat 2019-08-24 07:25:35 CEST. --
Aug 24 06:26:20 wl systemd-journald[230]: Received SIGTERM from PID 1 (systemd).
Aug 24 06:26:20 wl kernel: printk: systemd: 20 output lines suppressed due to ratelimiting
Aug 24 06:26:20 wl systemd[1]: systemd 242.84-2-arch running in system mode. (+PAM +AUDIT -SELINUX -IMA -APPARMOR +SMACK -SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD +IDN2 -IDN +PCRE2 default-hierarchy=hybrid)
Aug 24 06:26:20 wl systemd[1]: Detected architecture x86-64.

journalcl(1) states:

All users are granted access to their private per-user journals. However, by default, only root and users who are members of a few special groups are granted access to the system journal and the journals of other users. Members of the groups "systemd-journal", "adm", and "wheel" can read all journal files. Note that the two latter groups traditionally have additional privileges specified by the distribution. Members of the "wheel" group can often perform administrative tasks.

Which is the case:

$ id
uid=1000(fsn) gid=1000(fsn) groups=1000(fsn),976(sudo),977(ras),982(systemd-journal-remote),984(systemd-journal),985(users),998(wheel),999(adm)

Kernel Messages are not restricted:

$ sysctl kernel.dmesg_restrict
kernel.dmesg_restrict = 0

Any Ideas?

Last edited by pkill (2019-08-24 05:50:06)

jasonwryan

Anarchist

From: .nz

Registered: 2009-05-09

Posts: 30,426

Website

Re: Systemd Journal: No Early Boot Messages as User

Not an Installation issue, moving to NC...

---

Arch + dwm   •   Mercurial repos  •   Surfraw

Registered Linux User #482438

summerer

Member

From: Germany

Registered: 2014-01-25

Posts: 54

Re: Systemd Journal: No Early Boot Messages as User

Did you log yourself out and back in after adding your account to a user group?

It just seems like you are on a fresh setup as the log is only an hour long.