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 shouldn't be killing journald, when it is
otherwise obviously operating fine (aka waiting to be run).
I'm concerned as to why there is a watchdog on journald now. It should
be rocksolid, and either work or crash, there is no need to crash it on
a fixed schedule just because.
** Also affects: systemd (Ubuntu Bionic)
Importance: High
Assignee: Balint Reczey (rbalint)
Status: Opinion
** Changed in: systemd (Ubuntu Bionic)
Status: Opinion => Confirmed
** Changed in: systemd (Ubuntu Bionic)
Assignee: Balint Reczey (rbalint) => (unassigned)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1696970
Title:
softlockup DoS causes systemd-journald.service to abort with SIGABORT
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1696970/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
