[systemd-devel] [PATCH] journald: Log error when failed to get machine-id on start

[Lennart Poettering]

On Thu, 12.09.13 14:37, Olivier Brunel (jjk at jjacky.com) wrote:

> Can help since the journal requires /etc/machine-id to exists in order to start,
> and will simply silently exit when it does not.
> ---
> Not sure if the behavior is known/expected or a bug, but when e.g. booting a
> system with a read-only rootfs where /etc/machine-id doesn't exist, the journal
> would just silently fail (over & over) with no indication of why (even at debug
> log_level), and regardless of the Storage option (i.e. even with Storage=none).
> 
> Again, this might be expected, so this just adds a log message to clue you in on
> why it doesn't start. (Might also be a good idea to mention this requirement in
> systemd-journald(8) ?)

We probably should already refuse the boot from PID 1 if /etc/machine-id
cannot be set up, like we already do if /etc/os-release is not
found...

Lennart

-- 
Lennart Poettering - Red Hat, Inc.