On Tue, Sep 23, 2014 at 10:27 AM, walt <[email protected]> wrote: > > I used systemctl to stop and restart systemd-journald, thinking I might > see some useful error messages. But when systemd-journal started up > again the journal file was back in /var/log/journal where I want it :) > > No idea why rebooting the machine didn't do the same thing. >
Are you sure that it is solved, and that the problem won't recur on the next reboot? If it does, my next question (an educated guess, but a guess) would be whether you're using an initramfs, and if so which one. Dracut in particular launches journald, but it should move its output to /var/log/journal after pivoting to the new root. It is actually nice because your log contains early boot data which of course would not be present in syslog unless it ended up in the ring buffer. However, perhaps something is going wrong with that. I'd also look at anything that might be causing issues with /var/log/journal when journald is launched, such as that directory being on an unmounted filesystem and there not being some dependency that causes journald to notice. Systemd is pretty smart about spotting mount dependencies, but I've seen it make mistakes in unusual configurations and I don't know what the full logic is. -- Rich
