[Touch-packages] [Bug 1696970] Re: softlockup DoS causes systemd-journald.service to abort with SIGABORT

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

[Touch-packages] [Bug 1696970] Re: softlockup DoS causes systemd-journald.service to abort with SIGABORT

** Tags added: id-5ab94cf1ab21d3c7e6eee4ec -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1696970 Title: softlockup DoS causes systemd-journald.service to abort with

[Touch-packages] [Bug 1696970] Re: softlockup DoS causes systemd-journald.service to abort with SIGABORT

@colin-king I'm thinking to make "journald" more important by setting Nice=-1, to hopefully make it prioritized more often. There are also CPUSchedulingPolicy=, CPUSchedulingPriority=, IOSchedulingClass=, IOSchedulingPriority= -> i wonder if I should be adjusting these settings too, to make

[Touch-packages] [Bug 1696970] Re: softlockup DoS causes systemd-journald.service to abort with SIGABORT

> and/or failing. Imho, one shouldn't be killing journald, when it is otherwise > obviously > operating fine (aka waiting to be run). @xnox: How do you tell if there is no live lock and it is operating fine despite it timed out on a 3 minute timer? > I'm concerned as to why there is a watchdog

[Touch-packages] [Bug 1696970] Re: softlockup DoS causes systemd-journald.service to abort with SIGABORT

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

[Touch-packages] [Bug 1696970] Re: softlockup DoS causes systemd-journald.service to abort with SIGABORT

@colin-king In this case the journal was not broken. Do you have many examples of really broken journals? If so, do you have any solution in mind that would work better in scenarios you care about but don't cause regressions? Proper infrastructure planning with (CPU) quotas in place where it

[Touch-packages] [Bug 1696970] Re: softlockup DoS causes systemd-journald.service to abort with SIGABORT

** Tags added: id-597a8343fc8685288751db7a -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1696970 Title: softlockup DoS causes systemd-journald.service to abort with

[Touch-packages] [Bug 1696970] Re: softlockup DoS causes systemd-journald.service to abort with SIGABORT

Hrm, softlockups that break the journal aren't particularly rare on highly loaded servers. I'm a little concerned that a potential user space DoS attack could cause the log to discard important information that the system admin may use to help track down misbehaving system behaviour. -- You

[Touch-packages] [Bug 1696970] Re: softlockup DoS causes systemd-journald.service to abort with SIGABORT

I suggest setting this bug Won't Fix. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1696970 Title: softlockup DoS causes systemd-journald.service to abort with SIGABORT

[Touch-packages] [Bug 1696970] Re: softlockup DoS causes systemd-journald.service to abort with SIGABORT

@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)

[Touch-packages] [Bug 1696970] Re: softlockup DoS causes systemd-journald.service to abort with SIGABORT

Note that journal too has watchdogsec limit. I do wonder if softlockup should or should not be counted towards the watchdog counter =/ -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu.

[Touch-packages] [Bug 1696970] Re: softlockup DoS causes systemd-journald.service to abort with SIGABORT

The journal restart can be observed on zesty as well. However, the journal is not corrupted, the renaming and replacing took place as a safety measure due to unclean shutdown. $ sudo journalctl --verify --file=/run/log/journal/*/* PASS:

[Touch-packages] [Bug 1696970] Re: softlockup DoS causes systemd-journald.service to abort with SIGABORT

** Changed in: systemd (Ubuntu Artful) Assignee: Canonical Foundations Team (canonical-foundations) => Balint Reczey (rbalint) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu.

[Touch-packages] [Bug 1696970] Re: softlockup DoS causes systemd-journald.service to abort with SIGABORT

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:

[Touch-packages] [Bug 1696970] Re: softlockup DoS causes systemd-journald.service to abort with SIGABORT

** Tags added: rls-aa-incoming -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1696970 Title: softlockup DoS causes systemd-journald.service to abort with SIGABORT Status