[Bug 1618188] Re: systemd journal should be persistent by default: /var/log/journal should be created

[Martin Pitt]

> Where will the public policy discuss take place?

It should happen on https://lists.ubuntu.com/mailman/listinfo/ubuntu-
devel . However, I'm not going to start it now, we are past feature
freeze for yakkety and I have enough other things to work on in this
release. Feel free to start it yourself of course!

> Perhaps one possibility for a interim solution is for rsyslog to log
to journald by default

No, it's the other way around -- rsyslog should pull its data from the
journal (but that's a different topic actually). The journal already
collects all syslog() calls, it logs what rsyslog does plus a lot more.

** Also affects: ubuntu-meta (Ubuntu)
   Importance: Undecided
       Status: New

** Summary changed:

- systemd journal should be persistent by default: /var/log/journal should be created
+ systemd journal should be persistent by default: /var/log/journal should be created; remove rsyslog from default installs

** Changed in: ubuntu-meta (Ubuntu)
       Status: New => Triaged

** Changed in: ubuntu-meta (Ubuntu)
   Importance: Undecided => 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/1618188

Title:
  systemd journal should be persistent by default: /var/log/journal
  should be created; remove rsyslog from default installs

Status in systemd package in Ubuntu:
  Triaged
Status in ubuntu-meta package in Ubuntu:
  Triaged

Bug description:
  After upgrading 14.04 -> 16.04, key services are now running on
  systemd and using the systemd journal for logging. In 14.04, key
  system logs like /var/log/messages and /var/log/syslog were
  persistent, but after the upgrade to 16.04 there has a been a
  regression of sorts: Logs sent to systemd's journald are now being
  thrown away during reboots.

  This behavior is controlled by the `Storage=` option in
  `/etc/systemd/journald.conf`. The default setting is `Storage=auto`
  which will persist logs in `/var/log/journal/`, *only if the directory
  already exists*. But the directory was not created as part of the
  14.04 -> 16.04 upgrade, so logging was being lost for a while before I
  realized what was happening.

  This issue could be solved by either creating /var/log/journal or
  changing the default Storage behavior to `Storage=persistent`, which
  would create the directory if need be.

  ## Related reference

   * `systemd` currently compounds the issue by having ["journal --disk-usage" report memory usage as disk usage](https://github.com/systemd/systemd/issues/4059), giving the impression that the disk is being used for logging when it isn't. 
   * [User wonders where to find logs from previous boots, unaware that the logs were thrown away](http://askubuntu.com/questions/765315/how-to-find-previous-boot-log-after-ubuntu-16-04-restarts)

  ## Recommended fix

  Restoring persistent logging as the default is recommended.

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