Re: journald deleting logs on LiveOS boots

[Chris Murphy <lists@xxxxxxxxxxxxxxxxx>]

This problem of missing early boot messages is now happening on a
default boot of Fedora Live images. I don't have to change any boot
parameters to trigger it.

This image:
https://kojipkgs.fedoraproject.org/compose/rawhide/Fedora-Rawhide-20190715.n.1/compose/Workstation/x86_64/iso/Fedora-Workstation-Live-x86_64-Rawhide-20190715.n.1.iso

Boot it in a VM, launch Terminal and:

[liveuser@localhost-live ~]$ sudo journalctl -o short-monotonic
[sudo] password for liveuser:
-- Logs begin at Tue 2019-07-16 11:58:09 EDT, end at Tue 2019-07-16
15:58:09 EDT. --
[   24.017711] localhost-live systemd[1472]: Startup finished in 293ms.
[   24.447054] localhost-live dbus-broker-launch[1496]: Service file
'/usr/share/dbus-1/servi...

And neither a forwarded to console, nor directed to kmsg, do I see
/run/log or /var/log anywhere, so quite a lot of information is not
being forwarded and is just lost because of this bug.

Further, I discovered an note in an earlier bug I filed in February
2019 about this problem: "OK I'm not seeing this with
systemd-241~rc2-2.fc30.x86_64 in the 20190211 Live media" so that
leads me to believe this is a systemd regression, but I can't prove it
because of this bug. I have no systemd debug messages available to
look at...

Fedora Basic Release Criteria
"A system logging infrastructure must be available, enabled by
default, and working." I really think logging is not working, and this
should block. But without a really specific cause + solution it's
questionable to block.


---
Chris Murphy
_______________________________________________
systemd-devel mailing list
systemd-devel@xxxxxxxxxxxxxxxxxxxxx
https://lists.freedesktop.org/mailman/listinfo/systemd-devel