[Touch-packages] [Bug 1807627] Re: package systemd 237-3ubuntu10.9 failed to install/upgrade: installed systemd package post-installation script subprocess returned error exit status 1
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 entries in /usr/lib/tmpfiles.d/journal-nocow.conf 6. Reboot -- 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/1807627 Title: package systemd 237-3ubuntu10.9 failed to install/upgrade: installed systemd package post-installation script subprocess returned error exit status 1 Status in systemd package in Ubuntu: Confirmed Bug description: during upgrade from 16.04 to 18.04 ProblemType: Package DistroRelease: Ubuntu 18.04 Package: systemd 237-3ubuntu10.9 ProcVersionSignature: Ubuntu 4.4.0-140.166-generic 4.4.162 Uname: Linux 4.4.0-140-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 Date: Sun Dec 9 17:11:50 2018 ErrorMessage: installed systemd package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2016-09-01 (829 days ago) InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) Lsusb: Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Hewlett-Packard HP Compaq 8200 Elite SFF PC ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-140-generic root=UUID=aa4fc23f-9987-40c4-8278-a702ff0b99a3 ro RelatedPackageVersions: dpkg 1.19.0.5ubuntu2.1 apt 1.2.29 SourcePackage: systemd Title: package systemd 237-3ubuntu10.9 failed to install/upgrade: installed systemd package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to bionic on 2018-12-10 (0 days ago) dmi.bios.date: 06/20/2012 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: J01 v02.21 dmi.board.asset.tag: 2UA142177C dmi.board.name: 1495 dmi.board.vendor: Hewlett-Packard dmi.chassis.asset.tag: 2UA142177C dmi.chassis.type: 6 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvrJ01v02.21:bd06/20/2012:svnHewlett-Packard:pnHPCompaq8200EliteSFFPC:pvr:rvnHewlett-Packard:rn1495:rvr:cvnHewlett-Packard:ct6:cvr: dmi.product.name: HP Compaq 8200 Elite SFF PC dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1807627/+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
[Touch-packages] [Bug 1748147] Re: Upgrading systemd sets incorrect permissions on /var/log/
Related/similar issues: #1428540, #1687015 -- 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/1748147 Title: Upgrading systemd sets incorrect permissions on /var/log/ Status in systemd package in Ubuntu: New Bug description: 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 configuration of rsyslogd provided by Ubuntu runs the daemon as syslog:syslog and sets ownership of /var/log to syslog:adm with mode 0775. Systemd's default tmpfiles configuration sets /var/log to 0755 in /usr/lib/tmpfiles.d/var.conf, however this is overridden in /usr/lib/tmpfiles.d/00rsyslog.conf which is provided by package rsyslog. It looks as though an upgrade of the systemd package fails to take /usr/lib/tmpfiles.d/00rsyslog.conf into account, as demonstrated below. This results in /var/log receiving mode 0755 instead of the expected 0775: nick @ log2.be1.ams1:~ $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 16.04.3 LTS Release: 16.04 Codename: xenial nick @ log2.be1.ams1:~ $ apt policy systemd systemd: Installed: 229-4ubuntu21.1 Candidate: 229-4ubuntu21.1 Version table: *** 229-4ubuntu21.1 500 500 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 Packages 100 /var/lib/dpkg/status 229-4ubuntu4 500 500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages nick @ log2.be1.ams1:~ $ apt policy rsyslog rsyslog: Installed: 8.16.0-1ubuntu3 Candidate: 8.16.0-1ubuntu3 Version table: *** 8.16.0-1ubuntu3 500 500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages 100 /var/lib/dpkg/status nick @ log2.be1.ams1:~ $ grep -F /var/log /usr/lib/tmpfiles.d/var.conf d /var/log 0755 - - - f /var/log/wtmp 0664 root utmp - f /var/log/btmp 0600 root utmp - nick @ log2.be1.ams1:~ $ cat /usr/lib/tmpfiles.d/00rsyslog.conf # Override systemd's default tmpfiles.d/var.conf to make /var/log writable by # the syslog group, so that rsyslog can run as user. # See tmpfiles.d(5) for details. # Type PathMode UID GID Age Argument d /var/log 0775 root syslog - nick @ log2.be1.ams1:~ $ ls -ld /var/log drwxrwxr-x 8 root syslog 4096 Feb 7 13:45 /var/log nick @ log2.be1.ams1:~ $ sudo apt install --reinstall systemd Reading package lists... Done Building dependency tree Reading state information... Done 0 upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 7 not upgraded. Need to get 3,634 kB of archives. After this operation, 0 B of additional disk space will be used. Get:1 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 systemd amd64 229-4ubuntu21.1 [3,634 kB] Fetched 3,634 kB in 0s (24.3 MB/s) (Reading database ... 86614 files and directories currently installed.) Preparing to unpack .../systemd_229-4ubuntu21.1_amd64.deb ... Unpacking systemd (229-4ubuntu21.1) over (229-4ubuntu21.1) ... Processing triggers for dbus (1.10.6-1ubuntu3.3) ... Processing triggers for ureadahead (0.100.0-19) ... Processing triggers for man-db (2.7.5-1) ... Setting up systemd (229-4ubuntu21.1) ... addgroup: The group `systemd-journal' already exists as a system group. Exiting. nick @ log2.be1.ams1:~ $ ls -ld /var/log drwxr-xr-x 8 root syslog 4096 Feb 7 13:45 /var/log To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1748147/+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
[Touch-packages] [Bug 1748147] [NEW] Upgrading systemd sets incorrect permissions on /var/log/
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 configuration of rsyslogd provided by Ubuntu runs the daemon as syslog:syslog and sets ownership of /var/log to syslog:adm with mode 0775. Systemd's default tmpfiles configuration sets /var/log to 0755 in /usr/lib/tmpfiles.d/var.conf, however this is overridden in /usr/lib/tmpfiles.d/00rsyslog.conf which is provided by package rsyslog. It looks as though an upgrade of the systemd package fails to take /usr/lib/tmpfiles.d/00rsyslog.conf into account, as demonstrated below. This results in /var/log receiving mode 0755 instead of the expected 0775: nick @ log2.be1.ams1:~ $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 16.04.3 LTS Release:16.04 Codename: xenial nick @ log2.be1.ams1:~ $ apt policy systemd systemd: Installed: 229-4ubuntu21.1 Candidate: 229-4ubuntu21.1 Version table: *** 229-4ubuntu21.1 500 500 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 Packages 100 /var/lib/dpkg/status 229-4ubuntu4 500 500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages nick @ log2.be1.ams1:~ $ apt policy rsyslog rsyslog: Installed: 8.16.0-1ubuntu3 Candidate: 8.16.0-1ubuntu3 Version table: *** 8.16.0-1ubuntu3 500 500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages 100 /var/lib/dpkg/status nick @ log2.be1.ams1:~ $ grep -F /var/log /usr/lib/tmpfiles.d/var.conf d /var/log 0755 - - - f /var/log/wtmp 0664 root utmp - f /var/log/btmp 0600 root utmp - nick @ log2.be1.ams1:~ $ cat /usr/lib/tmpfiles.d/00rsyslog.conf # Override systemd's default tmpfiles.d/var.conf to make /var/log writable by # the syslog group, so that rsyslog can run as user. # See tmpfiles.d(5) for details. # Type PathMode UID GID Age Argument d /var/log 0775 root syslog - nick @ log2.be1.ams1:~ $ ls -ld /var/log drwxrwxr-x 8 root syslog 4096 Feb 7 13:45 /var/log nick @ log2.be1.ams1:~ $ sudo apt install --reinstall systemd Reading package lists... Done Building dependency tree Reading state information... Done 0 upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 7 not upgraded. Need to get 3,634 kB of archives. After this operation, 0 B of additional disk space will be used. Get:1 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 systemd amd64 229-4ubuntu21.1 [3,634 kB] Fetched 3,634 kB in 0s (24.3 MB/s) (Reading database ... 86614 files and directories currently installed.) Preparing to unpack .../systemd_229-4ubuntu21.1_amd64.deb ... Unpacking systemd (229-4ubuntu21.1) over (229-4ubuntu21.1) ... Processing triggers for dbus (1.10.6-1ubuntu3.3) ... Processing triggers for ureadahead (0.100.0-19) ... Processing triggers for man-db (2.7.5-1) ... Setting up systemd (229-4ubuntu21.1) ... addgroup: The group `systemd-journal' already exists as a system group. Exiting. nick @ log2.be1.ams1:~ $ ls -ld /var/log drwxr-xr-x 8 root syslog 4096 Feb 7 13:45 /var/log ** Affects: systemd (Ubuntu) Importance: Undecided Status: New -- 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/1748147 Title: Upgrading systemd sets incorrect permissions on /var/log/ Status in systemd package in Ubuntu: New Bug description: 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 configuration of rsyslogd provided by Ubuntu runs the daemon as syslog:syslog and sets ownership of /var/log to syslog:adm with mode 0775. Systemd's default tmpfiles configuration sets /var/log to 0755 in /usr/lib/tmpfiles.d/var.conf, however this is overridden in /usr/lib/tmpfiles.d/00rsyslog.conf which is provided by package rsyslog. It looks as though an upgrade of the systemd package fails to take /usr/lib/tmpfiles.d/00rsyslog.conf into account, as demonstrated below. This results in /var/log receiving mode 0755 instead of the expected 0775: nick @ log2.be1.ams1:~ $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 16.04.3 LTS Release: 16.04 Codename: xenial nick @ log2.be1.ams1:~ $ apt policy systemd systemd: Installed: 229-4ubuntu21.1 Candidate: 229-4ubuntu21.1 Version table: *** 229-4ubuntu21.1 500 500 http://archive.ubuntu.com/ubuntu xenial-updates/main