@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 matters seems to be a good practice instead of running highly loaded servers. The 3 min default timer for systemd-journald seems appropriate or even generous. -- 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
