[Bug 1790205] Re: systemd journals take up too much space, aren't vacuumed automatically

[Dimitri John Ledkov]

I have filed the usability issue of --disk-usage upstream at
https://github.com/systemd/systemd/issues/12063

** Bug watch added: github.com/systemd/systemd/issues #12063
   https://github.com/systemd/systemd/issues/12063

** Summary changed:

- systemd journals take up too much space, aren't vacuumed automatically
+ systemd journals take up a lot of space, and it's not obvious how much is used, and what the upper limit is.

** Also affects: systemd via
   https://github.com/systemd/systemd/issues/12063
   Importance: Unknown
       Status: Unknown

** Description changed:

  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?
+ 
+ 
+ ..... as it turns out, it's hard to see how much disk space is used, and what the upper limit is, even when it is set and respected by default.

** Tags removed: rls-dd-incoming
** Tags added: rls-dd-notfixing

** Changed in: systemd (Ubuntu)
       Status: Incomplete => Confirmed

** Changed in: systemd (Ubuntu)
   Importance: High => Wishlist

-- 
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 a lot of space, and it's not obvious how much
  is used, and what the upper limit is.

Status in systemd:
  Unknown
Status in systemd package in Ubuntu:
  Confirmed

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?

  
  ..... as it turns out, it's hard to see how much disk space is used, and what the upper limit is, even when it is set and respected by default.

To manage notifications about this bug go to:
https://bugs.launchpad.net/systemd/+bug/1790205/+subscriptions