This bug was fixed in the package systemd - 234-2ubuntu12.3
---------------
systemd (234-2ubuntu12.3) artful; urgency=medium
[ Dimitri John Ledkov ]
* Fix test-functions failing with Ubuntu units. LP: #1750608
* tests: switch to using ext4 by default, instead of ext3. LP: #1750608
* Fix kdump service not starting, due to systemd not loading dropins.
Cherrypick a fix from upstream. (LP: #1708409)
* systemd-fsckd: Fix ADT tests to work on s390x too. (LP: #1736955)
* netwokrd: add support for RequiredForOnline stanza. (LP: #1737570)
* resolved.service: set DefaultDependencies=no (LP: #1734167)
* systemd.postinst: enable persistent journal. (LP: #1618188)
* core: add support for non-writable unified cgroup hierarchy for container
support.
Rebase and de-fuzz. (LP: #1734410)
* Prevent MemoryDenyWriteExecution policy bypass, by disallowing
pkey_mprotect when mprotect is disallowed.
CVE-2017-15908 (LP: #1725348)
* networkd: enable promote_secondaries on networkd managed dhcp links.
This fixes failing to renew DHCP lease, on networkd managed devices.
(LP: #1721223)
[ Kleber Sacilotto de Souza ]
* systemd-rfkill service times out when a new rfkill device is added
- rfkill-fix-erroneous-behavior-when-polling-the-udev-.patch: Comparing
udev_device_get_sysname(device) and sysname will always return true. We
need to
check the device received from udev monitor instead.
- rfkill-fix-typo.patch: Fix typo in rfkill log message. (LP: #1734908)
-- Dimitri John Ledkov <x...@ubuntu.com> Tue, 20 Feb 2018 16:11:58
+0000
** Changed in: systemd (Ubuntu Artful)
Status: Fix Committed => Fix Released
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2017-15908
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, 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
Status in systemd package in Ubuntu:
Fix Released
Status in systemd source package in Xenial:
In Progress
Status in systemd source package in Zesty:
Won't Fix
Status in systemd source package in Artful:
Fix Released
Status in systemd source package in Bionic:
Fix Released
Bug description:
[Impact]
* System logs are lost across reboots because they are not stored
persistently.
[Test Case]
* Fresh installations, or upgrades to this version of systemd, should create
/var/log/journal and trigger automatic persistent logs.
* Users may choose to remove said directory, or disable persistent logging
in /etc/systemd/journald.conf
[Regression Potential]
* Persistent logging by default will cause logs to be flushed from
/run to /var/log, meaning there will be less RAM used (/run is tmpfs
backed), but increased disk usage (in /var/log). The journald daemon
has limits set for logs, meaning they will be rotated and discarded
and should not cause out of disk-space errors.
[Other Info]
* Original bug report
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
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
