[Bug 1790205] Re: systemd journals take up too much space, aren't vacuumed automatically
Tom Reynolds
1790205 at bugs.launchpad.net
Thu Mar 21 17:26:03 UTC 2019
Not breached here:
$ journalctl -b -u systemd-journald.service -n 1
-- Logs begin at Sat 2018-09-29 05:03:28 CEST, end at Thu 2019-03-21 18:18:38 CET. --
Mar 20 13:32:03 debby2017 systemd-journald[699]: System journal (/var/log/journal/f8b692c8bb791fe2804f3d5a5905148b) is 1.8G, max 1.8G, 0B free.
$ journalctl --disk-usage
Archived and active journals take up 1.8G in the file system.
However, with systemd-journald persistence enabled, and classic logging
daemons not removed (and still logging) on upgrades, you can end up with
much data stored in /var/log, a lot more than there used to be in the
past, which could cause problems, also (but not only) if combined with
bug 1785321.
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1790205
Title:
systemd journals take up too much space, aren't vacuumed automatically
Status in systemd package in Ubuntu:
Incomplete
Bug description:
After running Bionic for 3 months, I had 2.6 GB of journals.
I would not expect from a normal desktop user that they should have to
run commands like `sudo journalctl --vacuum-time=10d`.
I would nominate this command as a sane default to have running at
each reboot to ensure that logs do not exceed 500 MB:
sudo journalctl --vacuum-size=500M
Supposedly, a server should by default retain more logs, so perhaps
this should be implemented through a configuration package "systemd-
configuration-desktop" as a dependency of the ubuntu-desktop meta
package?
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1790205/+subscriptions
More information about the foundations-bugs
mailing list