Description of problem:
When booting from live
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Boot Fedora-Workstation-Live-x86_64-Rawhide-20190201.n.0.iso in a VM using default settings (this is a UEFI VM, not sure if it matters)
2. Check the journal
[liveuser@localhost-live ~]$ sudo journalctl -b -o short-monotonic
-- Logs begin at Mon 2019-02-11 20:57:59 EST, end at Tue 2019-02-12 01:58:00 EST. --
[ 78.230893] localhost systemd: Listening on Sound System.
[ 78.475652] localhost systemd: Listening on Multimedia System.
[ 78.477425] localhost systemd: Starting D-Bus User Message Bus Socket.
[ 78.478991] localhost systemd: Reached target Paths.
[ 78.479593] localhost systemd: Started Mark boot as successful after the user session has run 2 minutes.
[ 78.479940] localhost systemd: Reached target Timers.
[ 78.481715] localhost systemd: Listening on D-Bus User Message Bus Socket.
[ 78.482135] localhost systemd: Reached target Sockets.
[ 78.482404] localhost systemd: Reached target Basic System.
[ 78.507095] localhost systemd: Starting Sound Service...
[ 79.561659] localhost systemd: Starting D-Bus User Message Bus...
[ 80.098700] localhost systemd: Started D-Bus User Message Bus.
Should start with 0.000000, same as dmesg contents.
Created attachment 1533861 [details]
Created attachment 1533878 [details]
This is in a virt-manager VM, so I added 'systemd.log_level=debug systemd.log_target=console console=ttyS0,38400 console=tty1' to boot parameters. I don't know why but the virt-manager console shows a bunch of stuff that's not going to what I captured and am attaching by using 'sudo virsh console <VMname>'
The first instance of systemd-journald is:
[ 22.719371] audit: type=1130 audit(1549939070.979:3): pid=1 uid=0 auid=4294967295 ses=4294967295 subj=kernel msg='unit=systemd-journald comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
In the log I see several instances of
systemd-journald.service: Received EPOLLHUP on stored fd 55 (stored), closing.
I see nothing in this console log about the switch from /run to /var and flushing the journal to persistent media. Maybe that happens before 78s monotonic time and is just lost in the journal, but I'd think a reference to this event should be captures in the console log - but it's not here.
Same problem with selinux=0
Problem doesn't happen on the installed system, only when booting live media. The attached system.journal file was found in /var/log/journal - not on /run/ so I'm guessing either the flush to persistent media didn't happen, or possibly some problem with the initial journal setup on /run/ ?
OK I'm not seeing this with systemd-241~rc2-2.fc30.x86_64 in the 20190211 Live media.
I spaced this out and started bug 1715699. I'm closing this one, as the other has more troubleshooting info thus far.
*** This bug has been marked as a duplicate of bug 1715699 ***