[systemd-devel] journalctl and entries from the initramfs

Malte Starostik lists at malte.homeip.net
Tue Oct 2 16:01:55 PDT 2012


Am Dienstag, 2. Oktober 2012, 17:12:00 schrieb Lennart Poettering:
> On Thu, 27.09.12 01:49, Malte Starostik (lists at malte.homeip.net) wrote:
> > after upgrading from 189 to 192, I noticed journalctl will no longer
> > include the journal entries from the initramfs bootup unless -m is
> > passed.> 
> > Assuming this is caused by this 190-change:
> >         * journalctl will only show local log output by default
> >         
> >           now. Use --merge (-m) to show remote log output, too.
> > 
> > makes me wonder if that's an intended side effect or more of a bug?  i.e.
> > is early userspace officially included in "remote" or should its
> > ephemeral machine- id maybe be special cased to show up even without -m?
> > I guess building the initramfs as hostonly would fix this surprise as
> > /etc/machine-id is then copied from the host, but hostonly implies many
> > unwanted things.
> 
> Hmm, let me understand this right: do you use persistent journal logging
> (i.e. do you have /var/log/journal around?). If so journald should have
> flushed *all* of /run/log/journal to /var/log/journal after /var became
> available.

D'oh!  With a persistent journal, all is well.  In order not to litter the 
journal files with messages from all kinds of test runs, I had that disabled 
but didn't consider it a cause for the above.

> If you are not using persistent logging, then I grok the problem, but in
> that case maybe the fix is to simply enable persistent logging?

Indeed, thanks for the nudge in the right direction.

Malte


More information about the systemd-devel mailing list