A month before the release of 18.04, a change was released to make systemd journals persistent, but the setting SystemMaxUse was left unset in /etc/systemd/journald.conf
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1618188 The bug's regression analysis seems wrong, as it states: "The journald daemon has limits set for logs, meaning they will be rotated and discarded and should not cause out of disk-space errors." It also seems likely that no testers of 18.04 would discover this issue, since it requires running out of disk space after having accumulated large systemd journals over time. The documentation is here: https://www.freedesktop.org/software/systemd/man/journald.conf.html#SystemMaxUse= SystemKeepFree could be set, since it overrides the other values listed when the disk is running out of space. But I'm unsure, because if running out of disk space means that all the logs are silently truncated, then that is also a dangerous consequence on for instance a server where you could need logs to troubleshoot why disk space is running out... -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1790205 Title: systemd journals take up too much space, aren't vacuumed automatically To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1790205/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
