This affected me too, breaking a system in the middle of a release
upgrade.
I got out of that situation by:
1. Temporarily commenting out entries in /usr/lib/tmpfiles.d/journal-
nocow.conf
2. Running: dpkg --configure -a
3. Running: apt-get -f install
4. Running: apt full-upgrade
5. Restoring
Public bug reported:
Upgrading or reinstalling the systemd package when using rsyslogd
results in bad permissions (0755 instead of 0775) being set on
/var/log/. As a consequence of this, rsyslogd can no longer create new
files within this directory, resulting in lost log messages.
The default con
Related/similar issues: #1428540, #1687015
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1748147
Title:
Upgrading systemd sets incorrect permissions on /var/log/
To manage notifications about this
Despite this supposedly having been fixed, I still run into this on
Ubuntu 16.04.1 LTS (xenial).
This is caused by the ntp package (which comes installed by default)
placing an apparmor profile in `/etc/apparmor.d/usr.sbin.ntpd`. When
removing ntp and installing openntpd instead, the apparmor prof
