This bug was fixed in the package systemd - 237-3ubuntu6
---
systemd (237-3ubuntu6) bionic; urgency=medium
* Adjust the new dropin test, for v237 systemd.
* Refresh the keyring patch, to the one merged.
-- Dimitri John Ledkov Tue, 27 Mar 2018 13:40:09
+0100
** Changed in: sys
I see more chatter about journald aborting upstream and on the mailing
lists. Imho, just because journald was not scheduled to run kind of
means that maybe it has too low of a priority, or the system is
overloaded. It does not show that journald is actually at fault here,
and/or failing. Imho, one
@xnox IMO watchdogs should not care if it is a "soft" or other kind of
lockup.
I'm closing the bug because the workaround for recovering from a
potentially broken journal is working and there is no indication of a
journal which is actually broken.
** Changed in: systemd (Ubuntu Artful)
St
The watchdogs are by design. The unclean journal may not be. OTOH if
this only happens with the ephemeral journal in /run, the impact is
minor. We should check whether the unclean journal problem is
reproducible with /var/log/journal.
** Also affects: systemd (Ubuntu Artful)
Importance: High
