[Touch-packages] [Bug 2017182] [NEW] package initramfs-tools 0.136ubuntu6.7 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status
Public bug reported: Upgrading from 18.04 to 20.04. No space left on /boot. Solved by changing compression from lz4 to xz and regenerating before reboot. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: initramfs-tools 0.136ubuntu6.7 ProcVersionSignature: Ubuntu 5.4.0-147.164-generic 5.4.231 Uname: Linux 5.4.0-147-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.26 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Apr 21 00:16:53 2023 ErrorMessage: installed initramfs-tools package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2016-03-02 (2605 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) PackageArchitecture: all Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3.2 apt 2.0.9 SourcePackage: initramfs-tools Title: package initramfs-tools 0.136ubuntu6.7 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to focal on 2023-04-20 (0 days ago) ** Affects: initramfs-tools (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal third-party-packages -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/2017182 Title: package initramfs-tools 0.136ubuntu6.7 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1 Status in initramfs-tools package in Ubuntu: New Bug description: Upgrading from 18.04 to 20.04. No space left on /boot. Solved by changing compression from lz4 to xz and regenerating before reboot. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: initramfs-tools 0.136ubuntu6.7 ProcVersionSignature: Ubuntu 5.4.0-147.164-generic 5.4.231 Uname: Linux 5.4.0-147-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.26 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Apr 21 00:16:53 2023 ErrorMessage: installed initramfs-tools package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2016-03-02 (2605 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) PackageArchitecture: all Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3.2 apt 2.0.9 SourcePackage: initramfs-tools Title: package initramfs-tools 0.136ubuntu6.7 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to focal on 2023-04-20 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2017182/+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 2017182] Re: package initramfs-tools 0.136ubuntu6.7 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1
The issue I experienced here, with ~0 bytes free on /boot, produces a more clear "no space left" error than other initramfs-tools post- installation bugs. See Df.txt; /dev/sda1 238924232193 0 100% /boot See end of DpkgTerminalLog.txt; update-initramfs: Generating /boot/initrd.img-5.4.0-147-generic cat: write error: No space left on device update-initramfs: failed for /boot/initrd.img-5.4.0-147-generic with 1. dpkg: error processing package initramfs-tools (--configure): installed initramfs-tools package post-installation script subprocess returned error exit status 1 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/2017182 Title: package initramfs-tools 0.136ubuntu6.7 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1 Status in initramfs-tools package in Ubuntu: New Bug description: Upgrading from 18.04 to 20.04. No space left on /boot. Solved by changing compression from lz4 to xz and regenerating before reboot. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: initramfs-tools 0.136ubuntu6.7 ProcVersionSignature: Ubuntu 5.4.0-147.164-generic 5.4.231 Uname: Linux 5.4.0-147-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.26 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Apr 21 00:16:53 2023 ErrorMessage: installed initramfs-tools package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2016-03-02 (2605 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) PackageArchitecture: all Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3.2 apt 2.0.9 SourcePackage: initramfs-tools Title: package initramfs-tools 0.136ubuntu6.7 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to focal on 2023-04-20 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/2017182/+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 1875407] Re: package initramfs-tools 0.136ubuntu6 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1
Like #3 experienced, logs seems to make it plausible that this is caused by inadequate storage on /boot. See Df.txt; /dev/sda1 240972190591 37940 84% /boot See end of DpkgTerminalLog.txt; update-initramfs: Generating /boot/initrd.img-5.4.0-26-generic Error 24 : Write error : cannot write compressed block E: mkinitramfs failure cpio 141 lz4 -9 -l 24 update-initramfs: failed for /boot/initrd.img-5.4.0-26-generic with 1. dpkg: error processing package initramfs-tools (--configure): installed initramfs-tools package post-installation script subprocess returned error exit status 1 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1875407 Title: package initramfs-tools 0.136ubuntu6 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1 Status in initramfs-tools package in Ubuntu: Confirmed Bug description: Received this error when doing do-release-upgrade from ubuntu 18.04.4 to 20.4 ProblemType: Package DistroRelease: Ubuntu 20.04 Package: initramfs-tools 0.136ubuntu6 ProcVersionSignature: Ubuntu 4.15.0-96.97-generic 4.15.18 Uname: Linux 4.15.0-96-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip Date: Mon Apr 27 09:59:42 2020 ErrorMessage: installed initramfs-tools package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2016-01-12 (1567 days ago) InstallationMedia: Ubuntu-Server 15.10 "Wily Werewolf" - Release amd64 (20151021) PackageArchitecture: all Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18rc1, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2 SourcePackage: initramfs-tools Title: package initramfs-tools 0.136ubuntu6 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to focal on 2020-04-27 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1875407/+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 1877181] Re: package initramfs-tools 0.136ubuntu6 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1
Seems plausible that this is caused by inadequate storage on /boot. See Df.txt; /dev/sdb2 241965 197598 31875 87% /boot See end of DpkgTerminalLog.txt; update-initramfs: Generating /boot/initrd.img-5.4.0-29-generic Error 24 : Write error : cannot write compressed block E: mkinitramfs failure cpio 141 lz4 -9 -l 24 update-initramfs: failed for /boot/initrd.img-5.4.0-29-generic with 1. dpkg: error processing package initramfs-tools (--configure): installed initramfs-tools package post-installation script subprocess returned error exit status 1 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1877181 Title: package initramfs-tools 0.136ubuntu6 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1 Status in initramfs-tools package in Ubuntu: Confirmed Bug description: Happening while trying to upgrade from 18.04 to 20.04. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: initramfs-tools 0.136ubuntu6 ProcVersionSignature: Ubuntu 5.3.0-51.44~18.04.2-generic 5.3.18 Uname: Linux 5.3.0-51-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip Date: Wed May 6 14:26:11 2020 ErrorMessage: installed initramfs-tools package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2014-03-10 (2249 days ago) InstallationMedia: Ubuntu-Server 12.04.4 LTS "Precise Pangolin" - Release amd64 (20140204) PackageArchitecture: all Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18rc1, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2 SourcePackage: initramfs-tools Title: package initramfs-tools 0.136ubuntu6 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to focal on 2020-05-06 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1877181/+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 1883391] Re: package initramfs-tools 0.136ubuntu6 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1
This one is different from other initramfs-tools post-installation errors. /boot is on / which has plenty of space, but update-initramfs is missing /boot/initrd.img-5.4.0-37-generic.new. See Df.txt; /dev/sda5 436953712 8324136 406363876 3% / /dev/sda1 523248 4523244 1% /boot/efi See end of DpkgTerminalLog.txt; update-initramfs: Generating /boot/initrd.img-5.4.0-37-generic mv: cannot stat '/boot/initrd.img-5.4.0-37-generic.new': No such file or directory dpkg: error processing package initramfs-tools (--configure): installed initramfs-tools package post-installation script subprocess returned error exit status 1 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1883391 Title: package initramfs-tools 0.136ubuntu6 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1 Status in initramfs-tools package in Ubuntu: Confirmed Bug description: None - see summary. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: initramfs-tools 0.136ubuntu6 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 Uname: Linux 5.4.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip Date: Sat Jun 13 14:09:12 2020 ErrorMessage: installed initramfs-tools package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2020-06-13 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.1 SourcePackage: initramfs-tools Title: package initramfs-tools 0.136ubuntu6 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1883391/+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 1885782] Re: package initramfs-tools 0.136ubuntu6.2 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1
Seems plausible that this is caused by inadequate storage on /boot. See Df.txt; /dev/sda1 240972 192901 35630 85% /boot See end of DpkgTerminalLog.txt; update-initramfs: Generating /boot/initrd.img-5.4.0-39-generic Error 24 : Write error : cannot write compressed block E: mkinitramfs failure cpio 141 lz4 -9 -l 24 update-initramfs: failed for /boot/initrd.img-5.4.0-39-generic with 1. dpkg: error processing package initramfs-tools (--configure): installed initramfs-tools package post-installation script subprocess returned error exit status 1 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1885782 Title: package initramfs-tools 0.136ubuntu6.2 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1 Status in initramfs-tools package in Ubuntu: Confirmed Bug description: This error occurred during and upgrade of Ubuntu Server from 18.04LTS to 20.02LTS ProblemType: Package DistroRelease: Ubuntu 20.04 Package: initramfs-tools 0.136ubuntu6.2 ProcVersionSignature: Ubuntu 4.15.0-108.109-generic 4.15.18 Uname: Linux 4.15.0-108-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 CasperMD5CheckResult: skip Date: Tue Jun 30 21:46:27 2020 ErrorMessage: installed initramfs-tools package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2014-12-28 (2011 days ago) InstallationMedia: Ubuntu-Server 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.3) PackageArchitecture: all Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18rc1, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.1 SourcePackage: initramfs-tools Title: package initramfs-tools 0.136ubuntu6.2 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to focal on 2020-06-30 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1885782/+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 1891397] Re: package initramfs-tools 0.136ubuntu6.2 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1
Seems plausible that this is caused by inadequate storage on /boot. See Df.txt; /dev/md0 235691 183367 35848 84% /boot See end of DpkgTerminalLog.txt; update-initramfs: Generating /boot/initrd.img-5.4.0-42-generic Error 24 : Write error : cannot write compressed block E: mkinitramfs failure cpio 141 lz4 -9 -l 24 update-initramfs: failed for /boot/initrd.img-5.4.0-42-generic with 1. dpkg: error processing package initramfs-tools (--configure): installed initramfs-tools package post-installation script subprocess returned error exit status 1 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1891397 Title: package initramfs-tools 0.136ubuntu6.2 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1 Status in initramfs-tools package in Ubuntu: Confirmed Bug description: was doing do-release-upgrade -d (from 18.04 to 20.04, before "proper" 20.04.1 LTS release was released) ProblemType: Package DistroRelease: Ubuntu 20.04 Package: initramfs-tools 0.136ubuntu6.2 ProcVersionSignature: Ubuntu 4.15.0-112.113-generic 4.15.18 Uname: Linux 4.15.0-112-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.6 Architecture: amd64 CasperMD5CheckResult: skip Date: Tue Aug 11 18:50:32 2020 ErrorMessage: installed initramfs-tools package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2016-01-23 (1663 days ago) InstallationMedia: Ubuntu-Server 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) PackageArchitecture: all Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18rc1, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.1 SourcePackage: initramfs-tools Title: package initramfs-tools 0.136ubuntu6.2 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to focal on 2020-08-11 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1891397/+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 1894371] Re: package initramfs-tools 0.136ubuntu6.2 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1
Seems plausible that this is caused by inadequate storage on /boot. See Df.txt; /dev/sda1 240972 191360 37171 84% /boot See end of DpkgTerminalLog.txt; update-initramfs: Generating /boot/initrd.img-5.4.0-45-generic Error 24 : Write error : cannot write compressed block E: mkinitramfs failure cpio 141 lz4 -9 -l 24 update-initramfs: failed for /boot/initrd.img-5.4.0-45-generic with 1. dpkg: error processing package initramfs-tools (--configure): installed initramfs-tools package post-installation script subprocess returned error exit status 1 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1894371 Title: package initramfs-tools 0.136ubuntu6.2 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1 Status in initramfs-tools package in Ubuntu: Confirmed Bug description: upgrading from 18.04 to 20.04 ProblemType: Package DistroRelease: Ubuntu 20.04 Package: initramfs-tools 0.136ubuntu6.2 ProcVersionSignature: Ubuntu 4.15.0-115.116-generic 4.15.18 Uname: Linux 4.15.0-115-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip Date: Sat Sep 5 15:03:23 2020 ErrorMessage: installed initramfs-tools package post-installation script subprocess returned error exit status 1 PackageArchitecture: all Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18rc1, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.1 SourcePackage: initramfs-tools Title: package initramfs-tools 0.136ubuntu6.2 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to focal on 2020-09-05 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1894371/+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 1867712] Re: package initramfs-tools 0.136ubuntu1 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 127
This seems to be caused by bad installation state of package initramfs- tools-core which should have provided file /usr/share/initramfs- tools/scripts/functions together with /usr/sbin/mkinitramfs tool. See end of DpkgTerminalLog.txt; update-initramfs: Generating /boot/initrd.img-5.4.0-14-generic /usr/sbin/mkinitramfs: 88: .: Can't open /usr/share/initramfs-tools/scripts/functions update-initramfs: failed for /boot/initrd.img-5.4.0-14-generic with 127. dpkg: error processing package initramfs-tools (--configure): installed initramfs-tools package post-installation script subprocess returned error exit status 127 Plenty of space is left on / according to Df.txt. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1867712 Title: package initramfs-tools 0.136ubuntu1 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 127 Status in initramfs-tools package in Ubuntu: Confirmed Bug description: dpkg: error processing package initramfs-tools (--configure): installed initramfs-tools package post-installation script subprocess returned error exit status 127 Processing triggers for linux-image-unsigned-5.4.0-18-generic (5.4.0-18.22) ... /etc/kernel/postinst.d/initramfs-tools: update-initramfs: Generating /boot/initrd.img-5.4.0-18-generic /usr/sbin/mkinitramfs: 88: .: Can't open /usr/share/initramfs-tools/scripts/functions update-initramfs: failed for /boot/initrd.img-5.4.0-18-generic with 127. run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 127 dpkg: error processing package linux-image-unsigned-5.4.0-18-generic (--configure): installed linux-image-unsigned-5.4.0-18-generic package post-installation script subprocess returned error exit status 1 Errors were encountered while processing: initramfs-tools linux-image-unsigned-5.4.0-18-generic ProblemType: Package DistroRelease: Ubuntu 20.04 Package: initramfs-tools 0.136ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 ApportVersion: 2.20.11-0ubuntu20 Architecture: amd64 Date: Tue Mar 17 08:59:49 2020 ErrorMessage: installed initramfs-tools package post-installation script subprocess returned error exit status 127 InstallationDate: Installed on 2020-01-09 (67 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) PackageArchitecture: all Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu1 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu2 apt 1.9.10 SourcePackage: initramfs-tools Title: package initramfs-tools 0.136ubuntu1 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 127 UpgradeStatus: Upgraded to focal on 2020-02-13 (32 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1867712/+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 1898397] Re: package initramfs-tools 0.136ubuntu6.3 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1
This particular issue seems to be caused by a mismatch between a specific software suspend partition being specified in ininitramfs-tools config and the available partitions. Not inadequate storage on /boot. See end of DpkgTerminalLog.txt; update-initramfs: Generating /boot/initrd.img-5.4.0-48-generic cryptsetup: ERROR: Couldn't resolve device UUID=9de98dcc-35fc-4259-858c-d2b97cb90e58 W: initramfs-tools configuration sets RESUME=UUID=9de98dcc-35fc-4259-858c-d2b97cb90e58 W: but no matching swap device is available. Error 24 : Write error : cannot write compressed block E: mkinitramfs failure cpio 141 lz4 -9 -l 24 update-initramfs: failed for /boot/initrd.img-5.4.0-48-generic with 1. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1898397 Title: package initramfs-tools 0.136ubuntu6.3 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1 Status in initramfs-tools package in Ubuntu: Confirmed Bug description: Error occurred during and after installing Ubuntu 20.04.1 LTS ProblemType: Package DistroRelease: Ubuntu 20.04 Package: initramfs-tools 0.136ubuntu6.3 ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60 Uname: Linux 5.4.0-48-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 CasperMD5CheckResult: skip Date: Sat Oct 3 12:44:26 2020 ErrorMessage: installed initramfs-tools package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2015-10-10 (1819 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) PackageArchitecture: all Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18rc1, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.1 SourcePackage: initramfs-tools Title: package initramfs-tools 0.136ubuntu6.3 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to focal on 2020-10-03 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1898397/+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 1801744] Re: package linux-image-4.4.0-139-generic 4.4.0-139.165 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
This is caused by insufficient disk space on /boot partition where kernels are stored, excerpts from the attachments: update-initramfs: Generating /boot/initrd.img-4.4.0-139-generic cat: write error: No space left on device Filesystem 1K-blocks Used Available Use% Mounted on /dev/sda2 241965241595 0 100% /boot Sometimes, running "sudo apt-get autoremove" will clean up old kernels and allow subsequent upgrade attempts to succeed. In some situations manual intervention is needed, see more about that at https://help.ubuntu.com/community/RemoveOldKernels. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1801744 Title: package linux-image-4.4.0-139-generic 4.4.0-139.165 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 Status in initramfs-tools package in Ubuntu: New Bug description: don't know ProblemType: Package DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-139-generic 4.4.0-139.165 ProcVersionSignature: Ubuntu 4.4.0-139.165-generic 4.4.160 Uname: Linux 4.4.0-139-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: jaideep1604 F pulseaudio /dev/snd/controlC0: jaideep1604 F pulseaudio Date: Fri Nov 2 23:55:21 2018 ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 HibernationDevice: RESUME=UUID=0dfe2ba1-25bb-463c-b5f0-85897090f1d1 InstallationDate: Installed on 2016-04-19 (930 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) MachineType: LENOVO INVALID ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-139-generic.efi.signed root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: grub-pc N/A SourcePackage: initramfs-tools Title: package linux-image-4.4.0-139-generic 4.4.0-139.165 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/30/2015 dmi.bios.vendor: LENOVO dmi.bios.version: A2CN36WW(V2.04) dmi.board.asset.tag: No Asset Tag dmi.board.name: VIUU4 dmi.board.vendor: LENOVO dmi.board.version: 3192 PRO dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: INVALID dmi.modalias: dmi:bvnLENOVO:bvrA2CN36WW(V2.04):bd04/30/2015:svnLENOVO:pnINVALID:pvrINVALID:rvnLENOVO:rnVIUU4:rvr3192PRO:cvnLENOVO:ct10:cvrINVALID: dmi.product.name: INVALID dmi.product.version: INVALID dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1801744/+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 1686470] Re: Apt updates that are uniformly spread across all timezones, with predictable application windows
Sorry, apt 1.2.24 was not a SRU so the point about it being unattended is not valid, others are. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1686470 Title: Apt updates that are uniformly spread across all timezones, with predictable application windows Status in apt package in Ubuntu: Fix Released Status in unattended-upgrades package in Ubuntu: Fix Released Status in apt source package in Xenial: Fix Released Status in unattended-upgrades source package in Xenial: Fix Released Status in apt source package in Yakkety: Won't Fix Status in unattended-upgrades source package in Yakkety: Won't Fix Status in apt source package in Zesty: Fix Committed Status in unattended-upgrades source package in Zesty: Fix Committed Status in apt source package in Artful: Fix Released Status in unattended-upgrades source package in Artful: Fix Released Status in apt package in Debian: Fix Released Status in unattended-upgrades package in Debian: Fix Released Bug description: [ Impact ] * unattended-upgrades are enabled by default in Ubuntu 16.04 and later * Currently the following three things happen as a monolithic event: - metadata updates: apt update - download of updates: apt upgrade --download-only - application of updates: apt upgrade * For the long running instances, all of the above happens at random times throughout the day. * If systems were poweredoff / suspended, this happens on boot / resume * End-users would like to have predictable timing, and control over when the updates happen. Considering all of the above, the following new behavior is proposed which should address all concerns in question. It combines all the desired properties from both end-user and mirror perspectives. [ Proposed Default Behavior ] * Decouple unattended-upgrades application, from apt update * apt update: - shall be a systemd timer based unit, triggered every 12h with a random delay of 12h, therefore executed randomly twice a day. - if unattened-upgrades (default on), or download-upgreadaeble-packages are enabled, it should result in updates being downloaded aka `apt upgrade --download-only` * unattended-upgrades: - shall be a separate systemd timer based unit triggered at 6am local time with a random delay of 1h, therefore executed between 6am and 7am local time. * On boot / resume: - if we have missed one, or more, apt update timers, apt update / download upgrades / unattended-upgrade will happen in sequence. This may result in mirror spikes, but we do want to secure cold/stale-booted systems as soon as possible. [Test Case] * Run system for more than 24h, and check that apt updates were automatically executed twice. * Check that unattended upgrades were triggered to be applied at 6am..7am window, if any. * Poweroff the machine over the period when apt-get update was scheduled, poweron and observe that apt-get update / download / unattended upgrade are all performed on boot. * Downgrade systemd to the release version of the package (from -security). Remove apt periodic stamp files rm /var/lib/apt/periodic/*. Then run 'sudo systemctl start apt-daily.service'. Confirm that the systemd package is downloaded, but not upgraded. [Regression Potential] * The newly proposed behavior is a mix of Pre-xenial behavior of "do everything at 6am..6:30am window" and the xenial+ behavior of "do everything at random times throughout the day". If there are specific deployments that rely on the previous types of behaviour they will be able to adjust manually the systemd timers with the overrides to be executed exactly as they wish; or match the .0 release behaviour that they prefer. * If timers behavior is coded wrongly the proposed behaviour might not be executed as intended, thus requiring further SRUs to bring us in-line with the great expectations. [Other Info] * Related bug reports and history: - bug #1615482 - bug #1554848 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1686470/+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 1686470] Re: Apt updates that are uniformly spread across all timezones, with predictable application windows
An annoyance about this change is that it reuses the apt-daily.timer for only download and lets the upgrade be triggered by a new apt-daily- upgrade.timer. Systems using apt <1.2.24 which were sensitive to the upgrade point of time would typically have overridden the apt-daily.timer to happen at a fixed time. After upgrade to apt 1.2.24 those systems would still have apt-daily.timer run at the time chosen by the administrator but triggering /usr/lib/apt/apt.systemd.daily update to download packages would make it bail out (as the unattended-upgrades 0.90-ubuntu0.7 which introduced the --download-only option is not a SRU). But upgrades, and effectively also download until a manual upgrade of unattended-upgrades, would happen at the default apt-daily-upgrade.timer time (06:00+random(60m)). Security updates that warps carefully scheduled and important system events like this leaves the impression that administrators are not in control of their machines. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1686470 Title: Apt updates that are uniformly spread across all timezones, with predictable application windows Status in apt package in Ubuntu: Fix Released Status in unattended-upgrades package in Ubuntu: Fix Released Status in apt source package in Xenial: Fix Released Status in unattended-upgrades source package in Xenial: Fix Released Status in apt source package in Yakkety: Won't Fix Status in unattended-upgrades source package in Yakkety: Won't Fix Status in apt source package in Zesty: Fix Committed Status in unattended-upgrades source package in Zesty: Fix Committed Status in apt source package in Artful: Fix Released Status in unattended-upgrades source package in Artful: Fix Released Status in apt package in Debian: Fix Released Status in unattended-upgrades package in Debian: Fix Released Bug description: [ Impact ] * unattended-upgrades are enabled by default in Ubuntu 16.04 and later * Currently the following three things happen as a monolithic event: - metadata updates: apt update - download of updates: apt upgrade --download-only - application of updates: apt upgrade * For the long running instances, all of the above happens at random times throughout the day. * If systems were poweredoff / suspended, this happens on boot / resume * End-users would like to have predictable timing, and control over when the updates happen. Considering all of the above, the following new behavior is proposed which should address all concerns in question. It combines all the desired properties from both end-user and mirror perspectives. [ Proposed Default Behavior ] * Decouple unattended-upgrades application, from apt update * apt update: - shall be a systemd timer based unit, triggered every 12h with a random delay of 12h, therefore executed randomly twice a day. - if unattened-upgrades (default on), or download-upgreadaeble-packages are enabled, it should result in updates being downloaded aka `apt upgrade --download-only` * unattended-upgrades: - shall be a separate systemd timer based unit triggered at 6am local time with a random delay of 1h, therefore executed between 6am and 7am local time. * On boot / resume: - if we have missed one, or more, apt update timers, apt update / download upgrades / unattended-upgrade will happen in sequence. This may result in mirror spikes, but we do want to secure cold/stale-booted systems as soon as possible. [Test Case] * Run system for more than 24h, and check that apt updates were automatically executed twice. * Check that unattended upgrades were triggered to be applied at 6am..7am window, if any. * Poweroff the machine over the period when apt-get update was scheduled, poweron and observe that apt-get update / download / unattended upgrade are all performed on boot. * Downgrade systemd to the release version of the package (from -security). Remove apt periodic stamp files rm /var/lib/apt/periodic/*. Then run 'sudo systemctl start apt-daily.service'. Confirm that the systemd package is downloaded, but not upgraded. [Regression Potential] * The newly proposed behavior is a mix of Pre-xenial behavior of "do everything at 6am..6:30am window" and the xenial+ behavior of "do everything at random times throughout the day". If there are specific deployments that rely on the previous types of behaviour they will be able to adjust manually the systemd timers with the overrides to be executed exactly as they wish; or match the .0 release behaviour that they prefer. * If timers behavior is coded wrongly the proposed behaviour might not be executed as intended, thus requiring further
[Touch-packages] [Bug 1706740] Re: ruby upgrade broke redmine dependency
** Package changed: unattended-upgrades (Ubuntu) => redmine (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1706740 Title: ruby upgrade broke redmine dependency Status in redmine package in Ubuntu: New Bug description: On a Ubuntu 16.04 system deploying a Redmine issue tracker using the Ubuntu redmine package this night's (the systemd apt-daily timer has been rescheduled to run at 00:30) unattended upgrade of USN-3365 security updates to Ruby packages (https://usn.ubuntu.com/usn/usn-3365-1/) caused the Redmine application to break. Accessing the site caused Phusion Passenger to come up with a "We're sorry, but something went wrong.". The problem was identified and notified by email during the upgrade's processing of triggers on the redmine package where it was determined that the gem dependency "webrat" somehow was unavailable. The situation was resolved by running "bundle install" in the base directory /usr/share/redmine which caused most of the gems to be updated but I feel uneasy about this being a problem at all and fear breakage on future upgrades. I'm not too familiar with ruby, gems, bundler and apt triggers, so I've been unable to grasp where things go wrong and where a remedy is best deployed. Could it be as simple as adding a bundle update/install to the redmine trigger? Besides the core dependency to webrat, I got a plugin referring to webrat also: $ grep -r webrat /var/lib/redmine/ /usr/share/redmine /var/lib/redmine/Gemfile.lock:webrat (0.7.3) /var/lib/redmine/Gemfile.lock: webrat /usr/share/redmine/plugins/redmine_timesheet_plugin/Gemfile: gem 'webrat' /usr/share/redmine/plugins/redmine_timesheet_plugin/test/test_helper.rb:require "webrat" From /var/log/unattended-upgrades/unattended-upgrades-dpkg.log Log started: 2017-07-26 00:30:16 Reading changelogs... (Reading database ... ^M(Reading database ... 5%^M(Reading database ... 10%^M(Reading database ... 15%^M(Reading database ... 20%^M(Reading database ... 25%^M(Reading database ... 30%^M(Reading database ... 35%^M(Reading database ... 40%^M(Reading database ... 45%^M(Reading database ... 50%^M(Reading database ... 55%^M(Reading database ... 60%^M(Reading database ... 65%^M(Reading database ... 70%^M(Reading database ... 75%^M(Reading database ... 80%^M(Reading database ... 85%^M(Reading database ... 90%^M(Reading database ... 95%^M(Reading database ... 100%^M(Reading database ... 286395 files and directories currently installed.) Preparing to unpack .../ruby2.3-dev_2.3.1-2~16.04.2_amd64.deb ... Unpacking ruby2.3-dev:amd64 (2.3.1-2~16.04.2) over (2.3.1-2~16.04) ... Preparing to unpack .../libruby2.3_2.3.1-2~16.04.2_amd64.deb ... Unpacking libruby2.3:amd64 (2.3.1-2~16.04.2) over (2.3.1-2~16.04) ... Preparing to unpack .../ruby2.3_2.3.1-2~16.04.2_amd64.deb ... Unpacking ruby2.3 (2.3.1-2~16.04.2) over (2.3.1-2~16.04) ... Processing triggers for libc-bin (2.23-0ubuntu9) ... Processing triggers for redmine (3.2.1-2) ... Determining localhost credentials from /etc/mysql/debian.cnf: succeeded. ESC[31mCould not find gem 'webrat' in any of the gem sources listed in your Gemfile or available on this machine.ESC[0m dpkg: error processing package redmine (--unpack): subprocess installed post-installation script returned error exit status 7 Processing triggers for man-db (2.7.5-1) ... Errors were encountered while processing: redmine Log ended: 2017-07-26 00:30:21 From /var/log/unattended-upgrades/unattended-upgrades.log 2017-07-26 00:30:11,371 INFO Starting unattended upgrades script 2017-07-26 00:30:11,371 INFO Allowed origins are: ['o=Ubuntu,a=xenial', 'o=Ubuntu,a=xenial-security', 'o=UbuntuESM,a=xenial'] 2017-07-26 00:30:15,947 INFO Packages that will be upgraded: libruby2.3 ruby2.3 ruby2.3-dev 2017-07-26 00:30:15,948 INFO Writing dpkg log to '/var/log/unattended-upgrades/unattended-upgrades-dpkg.log' 2017-07-26 00:30:21,299 ERROR Installing the upgrades failed! 2017-07-26 00:30:21,299 ERROR error message: 'installArchives() failed' 2017-07-26 00:30:21,299 ERROR dpkg returned a error! See '/var/log/unattended-upgrades/unattended-upgrades-dpkg.log' for details $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 16.04.2 LTS Release:16.04 Codename: xenial $ apt-cache policy redmine passenger redmine: Installed: 3.2.1-2 Candidate: 3.2.1-2 Version table: *** 3.2.1-2 500 500 http://dk.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages 500 http://dk.archive.ubuntu.com/ubuntu xenial/universe i386 Packages 100 /var/lib/dpkg/status passenger:
[Touch-packages] [Bug 1706740] [NEW] ruby upgrade broke redmine dependency
Public bug reported: On a Ubuntu 16.04 system deploying a Redmine issue tracker using the Ubuntu redmine package this night's (the systemd apt-daily timer has been rescheduled to run at 00:30) unattended upgrade of USN-3365 security updates to Ruby packages (https://usn.ubuntu.com/usn/usn-3365-1/) caused the Redmine application to break. Accessing the site caused Phusion Passenger to come up with a "We're sorry, but something went wrong.". The problem was identified and notified by email during the upgrade's processing of triggers on the redmine package where it was determined that the gem dependency "webrat" somehow was unavailable. The situation was resolved by running "bundle install" in the base directory /usr/share/redmine which caused most of the gems to be updated but I feel uneasy about this being a problem at all and fear breakage on future upgrades. I'm not too familiar with ruby, gems, bundler and apt triggers, so I've been unable to grasp where things go wrong and where a remedy is best deployed. Could it be as simple as adding a bundle update/install to the redmine trigger? Besides the core dependency to webrat, I got a plugin referring to webrat also: $ grep -r webrat /var/lib/redmine/ /usr/share/redmine /var/lib/redmine/Gemfile.lock:webrat (0.7.3) /var/lib/redmine/Gemfile.lock: webrat /usr/share/redmine/plugins/redmine_timesheet_plugin/Gemfile: gem 'webrat' /usr/share/redmine/plugins/redmine_timesheet_plugin/test/test_helper.rb:require "webrat" >From /var/log/unattended-upgrades/unattended-upgrades-dpkg.log Log started: 2017-07-26 00:30:16 Reading changelogs... (Reading database ... ^M(Reading database ... 5%^M(Reading database ... 10%^M(Reading database ... 15%^M(Reading database ... 20%^M(Reading database ... 25%^M(Reading database ... 30%^M(Reading database ... 35%^M(Reading database ... 40%^M(Reading database ... 45%^M(Reading database ... 50%^M(Reading database ... 55%^M(Reading database ... 60%^M(Reading database ... 65%^M(Reading database ... 70%^M(Reading database ... 75%^M(Reading database ... 80%^M(Reading database ... 85%^M(Reading database ... 90%^M(Reading database ... 95%^M(Reading database ... 100%^M(Reading database ... 286395 files and directories currently installed.) Preparing to unpack .../ruby2.3-dev_2.3.1-2~16.04.2_amd64.deb ... Unpacking ruby2.3-dev:amd64 (2.3.1-2~16.04.2) over (2.3.1-2~16.04) ... Preparing to unpack .../libruby2.3_2.3.1-2~16.04.2_amd64.deb ... Unpacking libruby2.3:amd64 (2.3.1-2~16.04.2) over (2.3.1-2~16.04) ... Preparing to unpack .../ruby2.3_2.3.1-2~16.04.2_amd64.deb ... Unpacking ruby2.3 (2.3.1-2~16.04.2) over (2.3.1-2~16.04) ... Processing triggers for libc-bin (2.23-0ubuntu9) ... Processing triggers for redmine (3.2.1-2) ... Determining localhost credentials from /etc/mysql/debian.cnf: succeeded. ESC[31mCould not find gem 'webrat' in any of the gem sources listed in your Gemfile or available on this machine.ESC[0m dpkg: error processing package redmine (--unpack): subprocess installed post-installation script returned error exit status 7 Processing triggers for man-db (2.7.5-1) ... Errors were encountered while processing: redmine Log ended: 2017-07-26 00:30:21 >From /var/log/unattended-upgrades/unattended-upgrades.log 2017-07-26 00:30:11,371 INFO Starting unattended upgrades script 2017-07-26 00:30:11,371 INFO Allowed origins are: ['o=Ubuntu,a=xenial', 'o=Ubuntu,a=xenial-security', 'o=UbuntuESM,a=xenial'] 2017-07-26 00:30:15,947 INFO Packages that will be upgraded: libruby2.3 ruby2.3 ruby2.3-dev 2017-07-26 00:30:15,948 INFO Writing dpkg log to '/var/log/unattended-upgrades/unattended-upgrades-dpkg.log' 2017-07-26 00:30:21,299 ERROR Installing the upgrades failed! 2017-07-26 00:30:21,299 ERROR error message: 'installArchives() failed' 2017-07-26 00:30:21,299 ERROR dpkg returned a error! See '/var/log/unattended-upgrades/unattended-upgrades-dpkg.log' for details $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 16.04.2 LTS Release:16.04 Codename: xenial $ apt-cache policy redmine passenger redmine: Installed: 3.2.1-2 Candidate: 3.2.1-2 Version table: *** 3.2.1-2 500 500 http://dk.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages 500 http://dk.archive.ubuntu.com/ubuntu xenial/universe i386 Packages 100 /var/lib/dpkg/status passenger: Installed: 5.0.27-2 Candidate: 5.0.27-2 Version table: *** 5.0.27-2 500 500 http://dk.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages 100 /var/lib/dpkg/status ** Affects: unattended-upgrades (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1706740 Title: ruby
[Touch-packages] [Bug 1604010] Re: sntp missing
Am affected by the missing sntp binary also. For reference the Debian bug mentioned in comment #4 is https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=793837. Also note that the workaround mentioned in #15 does not (AFAICT from https://github.com/ntp-project/ntp/blob/master/ntpdate/ntpdate.c) use the SNTP protocol, so it does not serve identical function as the sntp tool. Installing package rdate will give you the rdate tool which can retrieve time using the SNTP protocol using its -n option (-p here for just printing the retrieved date): $ rdate -n -p ntp.ubuntu.com Wed May 24 13:14:52 UTC 2017 Also note that on Ubuntu 16.04 by default time synchronization has been taken over by systemd's timesyncd (man systemd-timesyncd), so neither package ntp (with execs ntpd and missing sntp) or package ntpdate are necessary for a machine to synchronize its time against a NTP server. Read something about that in https://help.ubuntu.com/lts/serverguide/NTP.html which is a fine intermingled mess of ntpd and timesyncd instructions. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ntp in Ubuntu. https://bugs.launchpad.net/bugs/1604010 Title: sntp missing Status in ntp package in Ubuntu: Triaged Status in ntp package in Debian: Fix Released Bug description: In Ubuntu 16.04, the binary file /usr/bin/sntp is missing from the package ntp. The associated man page /usr/share/man/man1/sntp.1.gz is still included. How to reproduce: $ sudo apt-get install ntp $ dpkg-query -L ntp | grep sntp /usr/share/man/man1/sntp.1.gz Expected result: /usr/bin/sntp was included in Ubuntu 14.04: $ dpkg-query -L ntp | grep sntp /usr/bin/sntp /usr/share/man/man1/sntp.1.gz The sntp program remains a very useful tool for interactively testing on the command line the offset of the local clock to a remote NTP server (like "ntpdate -qu [ntp-server]" previously). It should be included in the same package as its man page. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ntp/+bug/1604010/+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 1646739] Re: "Use of uninitialized value" in debconf via update-manager
This happened to me yesterday on a 16.04 desktop system using update- manager. Apparently failed during setup of package unattended-upgrades. Below is apt/history.log, apt/term.log, ps and debconf version taken while the GUI has been hanging (greyed out and unresponsive) for ~15 hours. GUI screenshot as shown in attachment. $ tail -4 /var/log/apt/history.log Start-Date: 2017-05-20 21:12:22 Commandline: aptdaemon role='role-commit-packages' sender=':1.438' Upgrade: iproute:amd64 (1:4.3.0-1ubuntu3, 1:4.3.0-1ubuntu3.16.04.1), iproute2:amd64 (4.3.0-1ubuntu3, 4.3.0-1ubuntu3.16.04.1), unattended-upgrades:amd64 (0.90ubuntu0.5, 0.90ubuntu0.6), libjasper1:amd64 (1.900.1-debian1-2.4ubuntu1, 1.900.1-debian1-2.4ubuntu1.1) End-Date: 2017-05-20 21:12:29 $ tail -23 /var/log/apt/term.log Log started: 2017-05-20 21:12:22 (Reading database ... 359114 files and directories currently installed.) Preparing to unpack .../iproute2_4.3.0-1ubuntu3.16.04.1_amd64.deb ... Unpacking iproute2 (4.3.0-1ubuntu3.16.04.1) over (4.3.0-1ubuntu3) ... Preparing to unpack .../iproute_1%3a4.3.0-1ubuntu3.16.04.1_all.deb ... Unpacking iproute (1:4.3.0-1ubuntu3.16.04.1) over (1:4.3.0-1ubuntu3) ... Preparing to unpack .../libjasper1_1.900.1-debian1-2.4ubuntu1.1_amd64.deb ... Unpacking libjasper1:amd64 (1.900.1-debian1-2.4ubuntu1.1) over (1.900.1-debian1-2.4ubuntu1) ... Preparing to unpack .../unattended-upgrades_0.90ubuntu0.6_all.deb ... Unpacking unattended-upgrades (0.90ubuntu0.6) over (0.90ubuntu0.5) ... Processing triggers for man-db (2.7.5-1) ... Processing triggers for libc-bin (2.23-0ubuntu7) ... Processing triggers for systemd (229-4ubuntu17) ... Processing triggers for ureadahead (0.100.0-19) ... Setting up iproute2 (4.3.0-1ubuntu3.16.04.1) ... Setting up iproute (1:4.3.0-1ubuntu3.16.04.1) ... Setting up libjasper1:amd64 (1.900.1-debian1-2.4ubuntu1.1) ... Setting up unattended-upgrades (0.90ubuntu0.6) ... Use of uninitialized value $_[1] in join or string at /usr/share/perl5/Debconf/DbDriver/Stack.pm line 111, line 12. Use of uninitialized value $val in substitution (s///) at /usr/share/perl5/Debconf/Format/822.pm line 83, line 11. Use of uninitialized value $val in concatenation (.) or string at /usr/share/perl5/Debconf/Format/822.pm line 84, line 11. Processing triggers for libc-bin (2.23-0ubuntu7) ... Log ended: 2017-05-20 21:12:29 $ ps aux |grep update miki 5027 0.0 1.2 730908 95960 ?Sl May20 0:20 /usr/bin/python3 /usr/bin/update-manager miki 10100 0.0 0.2 591036 22164 ?Sl May20 0:01 update-notifier $ dpkg -l|grep debconf |head -1 ii debconf 1.5.58ubuntu1 all Debian configuration management system $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 16.04.2 LTS Release:16.04 Codename: xenial ** Attachment added: "Hanging GUI of update-manager" https://bugs.launchpad.net/ubuntu/+source/php7.0/+bug/1646739/+attachment/4880641/+files/Screenshot%20from%202017-05-21%2011-40-19.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to debconf in Ubuntu. https://bugs.launchpad.net/bugs/1646739 Title: "Use of uninitialized value" in debconf via update-manager Status in debconf package in Ubuntu: Confirmed Status in php7.0 package in Ubuntu: Confirmed Status in samba package in Ubuntu: Confirmed Status in update-manager package in Ubuntu: Confirmed Bug description: During a software upgrade, process was stuck on php7.0-xml configuration for 20 minutes, after that I killed the process. I am not sure what additional info are required, will be happy to provide any. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: php7.0-xml 7.0.13-0ubuntu0.16.04.1 ProcVersionSignature: Ubuntu 4.4.0-49.70-generic 4.4.30 Uname: Linux 4.4.0-49-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.2 Architecture: amd64 Date: Fri Dec 2 09:52:06 2016 ErrorMessage: subprocess installed post-installation script returned error exit status 128 InstallationDate: Installed on 2016-03-11 (265 days ago) InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Release amd64 (20151021) RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.15 SourcePackage: php7.0 Title: package php7.0-xml 7.0.13-0ubuntu0.16.04.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 128 UpgradeStatus: Upgraded to xenial on 2016-05-07 (209 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/debconf/+bug/1646739/+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 1630516] Re: Logrotate fails repeatedly with /etc/cron.daily/logrotate: error: error creating output file /var/log/... File exists run-parts: /etc/cron.daily/logrotate exited wit
I am also seing this on a 14.04 server using logrotate package version
3.8.7-1ubuntu1:
$ dpkg -l|grep logrotate
ii logrotate 3.8.7-1ubuntu1
amd64Log rotation utility
$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 14.04.5 LTS
Release:14.04
Codename: trusty
Execution of logrotate from cron.daily aborts because of an existing file. Mail
from cron below ("Filen eksisterer" is Danish for "File exists"):
/etc/cron.daily/logrotate:
error: error creating output file /var/log/syslog.1.gz: Filen eksisterer
run-parts: /etc/cron.daily/logrotate exited with return code 1
Looking at the syslog files there is both a syslog.1 and a syslog.1.gz
where the latter shouldn't exist because of delaycompress option. Also
the .gz is a compressed version of the plain file:
$ gunzip --stdout /var/log/syslog.1.gz | diff --report-identical-files -
/var/log/syslog.1
Files - and /var/log/syslog.1 are identical
This suggests that logrotate was most likely interrupted after compressing
syslog.1 to syslog.1.gz but before it was moved/rotated into syslog.2.gz. On
subsequent executions this stale file causes logrotate to abort rotation
entirely.
The issue has been addressed in recent upstream releases;
https://github.com/logrotate/logrotate/pull/23
Also discussed in https://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=734688
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to logrotate in Ubuntu.
https://bugs.launchpad.net/bugs/1630516
Title:
Logrotate fails repeatedly with /etc/cron.daily/logrotate: error:
error creating output file /var/log/... File exists run-parts:
/etc/cron.daily/logrotate exited with return code 1
Status in logrotate package in Ubuntu:
Confirmed
Status in logrotate package in Debian:
New
Bug description:
Good afternoon.
I have started seeing something very similar to Debian Dug 734688 "Logs are
not rotated for a month" but in the latest Ubuntu LTS (16.04). I seem to have
$ logrotate --version
logrotate 3.8.7
bundled in it. A few weeks ago I started getting root emails such as this:
> Subject: Cron test -x /usr/sbin/anacron || ( cd / &&
run-parts --report /etc/cron.daily )
>
> /etc/cron.daily/logrotate:
> error: error creating output file /var/log/munin/munin-node.log.1: File
exists
> run-parts: /etc/cron.daily/logrotate exited with return code 1
When I inspected the area of concern I was able to see that there was an
existing .1 file.
manager@warden:/var/log/munin$ ll
total 580
drwxr-xr-x 2 munin adm 4096 Sep 27 06:31 ./
drwxr-xr-x 13 root syslog 4096 Oct 5 06:26 ../
-rw-r--r-- 1 root root 3440 Sep 26 13:39 munin-node-configure.log
-rw-r--r-- 1 root root 490251 Oct 5 10:25 munin-node.log
-rw-r--r-- 1 root root56598 Sep 21 02:01 munin-node.log.1
-rw-r--r-- 1 root root24576 Aug 31 02:01 munin-node.log.2
-rw-r--r-- 1 root root 1906 Sep 19 06:25 munin-node.log.8.gz
The contents of the munin-node.log file seem to run from the 19th September
until today. Unlike other parts of this bug the .1 and .2 files do not seem to
be already compressed.
I deleted all but the munin-node.log file to see if it would resolve the
problem and was going to leave it at that. Then I noticed that I have had
another Ubuntu machine which has been sending similar emails for the past week:
> Subject: Cron test -x /usr/sbin/anacron || ( cd / && run-parts
--report /etc/cron.daily )
>
> /etc/cron.daily/logrotate:
> error: error creating output file /var/log/syslog.1.gz: File exists
> run-parts: /etc/cron.daily/logrotate exited with return code 1
Different file, different machine but a very similar error message.
Checking on the syslog file I can see that it better fits with other reports
on this bug as my duplicated .1 files has a corresponding .1.gz file.
manager@trac:/var/log$ ll syslog*
-rw-r- 1 syslog adm 918492 Oct 5 10:30 syslog
-rw-r- 1 syslog adm 125819 Sep 30 06:25 syslog.1
-rw-r- 1 syslog adm 20638 Oct 2 02:01 syslog.1.gz
-rw-r- 1 syslog adm 41989 Sep 30 02:00 syslog.2.gz
-rw-r- 1 syslog adm 18654 Sep 28 02:01 syslog.3.gz
-rw-r- 1 syslog adm 31720 Sep 26 06:40 syslog.4.gz
-rw-r- 1 syslog adm 33151 Sep 25 02:01 syslog.5.gz
-rw-r- 1 syslog adm 17290 Sep 23 02:01 syslog.6.gz
-rw-r- 1 syslog adm 39275 Sep 21 06:35 syslog.7.gz
There has been some speculation that a full or nearly full /var
partition would cause this issue. I can confirm that /var is part of
/ on my systems and that presently both of them have several gigabytes
of space. I run Munin an Icinga to monitor system state. Neither of
these show / being completely full in the past month. They have both
had /boot fill
[Touch-packages] [Bug 1576539] Re: package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems - leaving triggers unprocessed
Follow up to my comment #7: Inspecting log files I find what to me looks like a bad recursion in dependency checking when setting up the package gcr (GNOME crypto services). The apt-term log shows 50 of the same error message about unability to run triggers for gconf2 because python3 is unconfigured. /var/log/dist-upgrade/apt-term.log: --- Setting up dbus (1.10.6-1ubuntu3.1) ... A reboot is required to replace the running dbus-daemon. Please reboot the system when convenient. Removing obsolete conffile /etc/dbus-1/session.conf ... Removing obsolete conffile /etc/dbus-1/system.conf ... Setting up dbus-x11 (1.10.6-1ubuntu3.1) ... Setting up gcr (3.18.0-1ubuntu1) ... dpkg: dependency problems prevent processing triggers for gconf2: gconf2 depends on python3; however: Package python3 is not configured yet. * repeats 50 times dpkg: error processing package gconf2 (--configure): dependency problems - leaving triggers unprocessed dpkg: dependency problems prevent processing triggers for gconf2: gconf2 depends on python3; however: Package python3 is not configured yet. * dpkg: error processing package gconf2 (--configure): dependency problems - leaving triggers unprocessed dpkg: too many errors, stopping Errors were encountered while processing: gconf2 gconf2 gconf2 gconf2 gconf2 gconf2 gconf2 gconf2 gconf2 gconf2 gconf2 gconf2 gconf2 gconf2 gconf2 gconf2 gconf2 gconf2 gconf2 gconf2 gconf2 gconf2 gconf2 gconf2 gconf2 gconf2 gconf2 gconf2 gconf2 gconf2 gconf2 gconf2 gconf2 gconf2 gconf2 gconf2 gconf2 gconf2 gconf2 gconf2 gconf2 gconf2 gconf2 gconf2 gconf2 gconf2 gconf2 gconf2 gconf2 gconf2 gconf2 Processing was halted because there were too many errors. (Reading database ... ^M(Reading database ... 5%^M(Reading database ... 10%^M(Reading database ... 15%^M(Reading database ... 20%^M(Reading database ... 25%^M(Reading database ... 30%^M(Reading database ... 35%^M(Reading database ... 40%^M(Reading database ... 45%^M(Reading database ... 50%^M(Reading database ... 55%^M(Reading database ... 60%^M(Reading database ... 65%^M(Reading database ... 70%^M(Reading database ... 75%^M(Reading database ... 80%^M(Reading database ... 85%^M(Reading database ... 90%^M(Reading database ... 95%^M(Reading database ... 100%^M(Reading database ... 278060 files and directories currently installed.) Preparing to unpack .../gnupg2_2.1.11-6ubuntu2_amd64.deb ... --- The unconfigured gconf2 state looks like it generates a cascade of dependency errors in subsequent packages, from the main log /var/log/dist-upgrade/main.log; --- 2016-11-08 12:14:00,647 ERROR got an error from dpkg for pkg: 'gconf2': 'dependency problems - leaving triggers unprocessed' 2016-11-08 12:14:00,648 DEBUG running apport_pkgfailure() gconf2: dependency problems - leaving triggers unprocessed 2016-11-08 12:14:00,657 ERROR got an error from dpkg for pkg: 'gconf2': 'dependency problems - leaving triggers unprocessed' 2016-11-08 12:36:56,197 WARNING no activity on terminal for 300 seconds (Installed libsecret-common (amd64)) 2016-11-08 12:36:56,377 ERROR got an error from dpkg for pkg: 'gnupg2': 'dependency problems - leaving unconfigured' 2016-11-08 12:36:56,377 DEBUG running apport_pkgfailure() gnupg2: dependency problems - leaving unconfigured 2016-11-08 12:36:56,377 DEBUG dpkg error because of dependency problems, not reporting against gnupg2 2016-11-08 12:36:56,377 ERROR got an error from dpkg for pkg: 'gnupg2': 'dependency problems - leaving unconfigured' 2016-11-08 12:47:33,520 ERROR got an error from dpkg for pkg: 'gnome-keyring': 'dependency problems - leaving unconfigured' 2016-11-08 12:47:33,520 DEBUG running apport_pkgfailure() gnome-keyring: dependency problems - leaving unconfigured 2016-11-08 12:47:33,520 DEBUG dpkg error because of dependency problems, not reporting against gnome-keyring 2016-11-08 12:47:33,520 ERROR got an error from dpkg for pkg: 'gnome-keyring': 'dependency problems - leaving unconfigured' 2016-11-08 12:47:33,531 ERROR got an error from dpkg for pkg: 'evolution-data-server': 'dependency problems - leaving unconfigured' 2016-11-08 12:47:33,531 DEBUG running apport_pkgfailure() evolution-data-server: dependency problems - leaving unconfigured 2016-11-08 12:47:33,531 DEBUG dpkg error because of dependency problems, not reporting against evolution-data-server 2016-11-08 12:47:33,531 ERROR got an error from dpkg for pkg: 'evolution-data-server': 'dependency problems - leaving unconfigured' 2016-11-08 12:47:33,728 ERROR got an error from dpkg for pkg: 'libfolks-eds25': '76.5689:dependency problems - leaving unconfigured' 2016-11-08 12:47:33,728 DEBUG running apport_pkgfailure() libfolks-eds25: 76.5689:dependency problems - leaving unconfigured 2016-11-08 12:47:33,728 DEBUG dpkg error because of dependency problems, not reporting against libfolks-eds25 2016-11-08 12:47:33,728 ERROR got an error from dpkg for pkg: 'libfolks-eds25':
[Touch-packages] [Bug 1576539] Re: package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems - leaving triggers unprocessed
Hit this same problem while upgrading from 15.10 to 16.04 using the GUI distribution upgrader. During upgrade I got a dialog reporting the gconf2 dependency problem. The terminal indicates this happened on unpacking the inkscape package. See upper screenshot of attached image. The upgrade process continued but the upgrader bailed out on processing triggers for the dbus package reporting "Could not install upgrades". See lower screenshot of attached image. The terminal reported "Error in function:". After this the upgrader closed and running the update-notifier asked me to reboot the system. Manual inspection of the package state using dpkg and further dpkg --configure -a invocations persuaded me that the system was relatively intact and a reboot was done. The system booted nicely and seems fine now except I receive a CRT configuration error dialog when logging in on the display manager. Runnnig dpkg --audit returns nothing and the packages that were mentioned during upgrade seems ok: $ dpkg -l gconf2 dbus inkscape Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ NameVersion Architecture Description +++-===---=== ii dbus1.10.6-1ubuntu3. amd64simple interprocess messaging system (daemon and ut ii gconf2 3.2.6-3ubuntu6 amd64GNOME configuration database system (support tools) ii inkscape0.91-7ubuntu2amd64vector-based drawing program ** Attachment added: "Screenshots, Ubuntu 15.10 to 16.04 upgrade, gconf2 dependency and dbus trigger failure" https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/1576539/+attachment/4774449/+files/Screenshots%2C%20Ubuntu%2015.10%20to%2016.04%20upgrade%2C%20gconf2%20dependency%20and%20dbus%20trigger%20failure.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gconf in Ubuntu. https://bugs.launchpad.net/bugs/1576539 Title: package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems - leaving triggers unprocessed Status in gconf package in Ubuntu: Triaged Bug description: bug happened while i'm upgrading ubuntu version from 15.10 to 16.04 ProblemType: Package DistroRelease: Ubuntu 16.04 Package: gconf2 3.2.6-3ubuntu6 ProcVersionSignature: Ubuntu 4.4.0-22.38-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 Date: Fri Apr 29 08:16:36 2016 ErrorMessage: dependency problems - leaving triggers unprocessed InstallationDate: Installed on 2016-03-05 (54 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) RelatedPackageVersions: dpkg 1.18.4ubuntu1 apt 1.2.10ubuntu1 SourcePackage: gconf Title: package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems - leaving triggers unprocessed UpgradeStatus: Upgraded to xenial on 2016-04-29 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/1576539/+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 1626883] Re: libssl 1.0.2g-1ubuntu4.4 and 1.0.1f-1ubuntu2.20 cause PHP SSL cert validation to segfault
Thanks for the fix.
I too can verify that our system doesn't segfault on Ubuntu 14.04
(trusty) using latest libssl1.0.0 (=1.0.1f-1ubuntu2.21);
# dpkg -l |grep libssl1.0.0
ii libssl1.0.0:amd64 1.0.1f-1ubuntu2.21
amd64Secure Sockets Layer toolkit - shared libraries
# php -r "echo
gettype(openssl_x509_parse(file_get_contents('/etc/ssl/certs/ca-certificates.crt')));"
array
We'll definitely be reconsidering which systems will be applying security
upgrades unattended in the future.
This experience makes me wonder how patches for the -security suites
(default for unattended-upgrades) are tested and QA'ed. Can anything be
done to the Ubuntu process to prevent things like this happening again?
I'm unfamiliar with how this is done currently so excuse my ignorance.
But I'm wondering why there seem to be no collaboration or correlation
between Ubuntu and Debian security updates. Debian seems to have got
this one right in the first shot (DSA is here
https://www.debian.org/security/2016/dsa-3673).
BTW: the links to upstream patches on the Ubuntu CVE page
(http://people.canonical.com/~ubuntu-
security/cve/2016/CVE-2016-2182.html) are invalid caused by a version
string being appended to the commit hash (looks like borked wiki
syntax).
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssl in Ubuntu.
https://bugs.launchpad.net/bugs/1626883
Title:
libssl 1.0.2g-1ubuntu4.4 and 1.0.1f-1ubuntu2.20 cause PHP SSL cert
validation to segfault
Status in openssl package in Ubuntu:
Fix Released
Status in openssl source package in Precise:
Fix Released
Status in openssl source package in Trusty:
Fix Released
Status in openssl source package in Xenial:
Fix Released
Bug description:
Last night unattended-upgrades upgraded the openssl packages
(libssl1.0.0, libssl-dev, openssl) from version 1.0.2g-1ubuntu4.1 to
version 1.0.2g-1ubuntu4.4 on a CI build server. Then everything that
used PHP to connect to a HTTPS site started crashing when verifying
the server cert.
Like this:
```
jenkins@ubuntutemplate:/var/lib/jenkins/workspace/imt-erp-e2e-flaky/webshop/vagrant/wordpress$
DATABASE_DATABASE=wordpressmastere2e catchsegv wp plugin install --force
--activate wp-cfm
Deprecated: Methods with the same name as their class will not be
constructors in a future version of PHP; WP_Import has a deprecated constructor
in /var/lib/jenkins/workspace/imt-erp-e2e-flaky/webshop
/vagrant/wordpress/wp-content/plugins/wordpress-importer/wordpress-importer.php
on line 38
Notice: Undefined offset: 4 in
phar:///usr/local/bin/wp/php/WP_CLI/DocParser.php on line 124
Segmentation fault (core dumped)
*** Segmentation fault
Register dump:
RAX: RBX: 0001 RCX:
RDX: 000c RSI: 55665071af59 RDI:
RBP: 556650a49e4e R8 : 556652364720 R9 :
R10: R11: 7fdb3c081730 R12: 55665071af59
R13: 000c R14: R15: 7fdb39418cf0
RSP: 7ffc4bad7a08
RIP: 7fdb3bf77d16 EFLAGS: 00010293
CS: 0033 FS: GS:
Trap: 000e Error: 0004 OldMask: CR2:
FPUCW: 027f FPUSW: TAG:
RIP: RDP:
ST(0) ST(1)
ST(2) ST(3)
ST(4) ST(5)
ST(6) ST(7)
mxcsr: 1fa0
XMM0: XMM1:
XMM2: XMM3:
XMM4: XMM5:
XMM6: XMM7:
XMM8: XMM9:
XMM10: XMM11:
XMM12: XMM13:
XMM14: XMM15:
Backtrace:
/lib/x86_64-linux-gnu/libc.so.6(strlen+0x26)[0x7fdb3bf77d16]
php(add_assoc_string_ex+0x32)[0x556650677b12]
php(zif_openssl_x509_parse+0x17c)[0x5566505312ec]
php(dtrace_execute_internal+0x2a)[0x556650664b3a]
php(+0x2e37e0)[0x5566506f97e0]
php(execute_ex+0x1b)[0x5566506b4e2b]
php(dtrace_execute_ex+0xb1)[0x5566506649d1]
php(+0x2e391d)[0x5566506f991d]
php(execute_ex+0x1b)[0x5566506b4e2b]
php(dtrace_execute_ex+0xb1)[0x5566506649d1]
php(+0x2e391d)[0x5566506f991d]
php(execute_ex+0x1b)[0x5566506b4e2b]
php(dtrace_execute_ex+0xb1)[0x5566506649d1]
[Touch-packages] [Bug 1626883] Re: libssl 1.0.2g-1ubuntu4.4 and 1.0.1f-1ubuntu2.20 cause PHP SSL cert validation to segfault
Thanks @ollisa.
I had the same thoughts about 1.0.1f-1ubuntu2 so I found a downloadable
build at https://launchpad.net/ubuntu/+source/openssl/1.0.1f-
1ubuntu2.19. Installing just the ubuntu2.19 version of libssl1.0.0
solved the issue;
wget
https://launchpad.net/~ubuntu-security/+archive/ubuntu/ppa/+build/9679884/+files/libssl1.0.0_1.0.1f-1ubuntu2.19_amd64.deb
dpkg -i libssl1.0.0_1.0.1f-1ubuntu2.19_amd64.deb
Now the certs can be parsed without segfault;
# php -r "echo
gettype(openssl_x509_parse(file_get_contents('/etc/ssl/certs/ca-certificates.crt')));"
array
A good idea would be to put the package on hold to prevent further
automatic upgrades. Though you'd then need to manually verify and unhold
when a fix is out
# apt-mark hold libssl1.0.0
libssl1.0.0 set on hold.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssl in Ubuntu.
https://bugs.launchpad.net/bugs/1626883
Title:
libssl 1.0.2g-1ubuntu4.4 and 1.0.1f-1ubuntu2.20 cause PHP SSL cert
validation to segfault
Status in openssl package in Ubuntu:
Confirmed
Bug description:
Last night unattended-upgrades upgraded the openssl packages
(libssl1.0.0, libssl-dev, openssl) from version 1.0.2g-1ubuntu4.1 to
version 1.0.2g-1ubuntu4.4 on a CI build server. Then everything that
used PHP to connect to a HTTPS site started crashing when verifying
the server cert.
Like this:
```
jenkins@ubuntutemplate:/var/lib/jenkins/workspace/imt-erp-e2e-flaky/webshop/vagrant/wordpress$
DATABASE_DATABASE=wordpressmastere2e catchsegv wp plugin install --force
--activate wp-cfm
Deprecated: Methods with the same name as their class will not be
constructors in a future version of PHP; WP_Import has a deprecated constructor
in /var/lib/jenkins/workspace/imt-erp-e2e-flaky/webshop
/vagrant/wordpress/wp-content/plugins/wordpress-importer/wordpress-importer.php
on line 38
Notice: Undefined offset: 4 in
phar:///usr/local/bin/wp/php/WP_CLI/DocParser.php on line 124
Segmentation fault (core dumped)
*** Segmentation fault
Register dump:
RAX: RBX: 0001 RCX:
RDX: 000c RSI: 55665071af59 RDI:
RBP: 556650a49e4e R8 : 556652364720 R9 :
R10: R11: 7fdb3c081730 R12: 55665071af59
R13: 000c R14: R15: 7fdb39418cf0
RSP: 7ffc4bad7a08
RIP: 7fdb3bf77d16 EFLAGS: 00010293
CS: 0033 FS: GS:
Trap: 000e Error: 0004 OldMask: CR2:
FPUCW: 027f FPUSW: TAG:
RIP: RDP:
ST(0) ST(1)
ST(2) ST(3)
ST(4) ST(5)
ST(6) ST(7)
mxcsr: 1fa0
XMM0: XMM1:
XMM2: XMM3:
XMM4: XMM5:
XMM6: XMM7:
XMM8: XMM9:
XMM10: XMM11:
XMM12: XMM13:
XMM14: XMM15:
Backtrace:
/lib/x86_64-linux-gnu/libc.so.6(strlen+0x26)[0x7fdb3bf77d16]
php(add_assoc_string_ex+0x32)[0x556650677b12]
php(zif_openssl_x509_parse+0x17c)[0x5566505312ec]
php(dtrace_execute_internal+0x2a)[0x556650664b3a]
php(+0x2e37e0)[0x5566506f97e0]
php(execute_ex+0x1b)[0x5566506b4e2b]
php(dtrace_execute_ex+0xb1)[0x5566506649d1]
php(+0x2e391d)[0x5566506f991d]
php(execute_ex+0x1b)[0x5566506b4e2b]
php(dtrace_execute_ex+0xb1)[0x5566506649d1]
php(+0x2e391d)[0x5566506f991d]
php(execute_ex+0x1b)[0x5566506b4e2b]
php(dtrace_execute_ex+0xb1)[0x5566506649d1]
php(+0x2e391d)[0x5566506f991d]
php(execute_ex+0x1b)[0x5566506b4e2b]
php(dtrace_execute_ex+0xb1)[0x5566506649d1]
php(+0x2e391d)[0x5566506f991d]
php(execute_ex+0x1b)[0x5566506b4e2b]
php(dtrace_execute_ex+0xb1)[0x5566506649d1]
php(+0x2e391d)[0x5566506f991d]
php(execute_ex+0x1b)[0x5566506b4e2b]
php(dtrace_execute_ex+0xb1)[0x5566506649d1]
php(+0x2e391d)[0x5566506f991d]
php(execute_ex+0x1b)[0x5566506b4e2b]
php(dtrace_execute_ex+0xb1)[0x5566506649d1]
php(+0x2e391d)[0x5566506f991d]
php(execute_ex+0x1b)[0x5566506b4e2b]
php(dtrace_execute_ex+0xb1)[0x5566506649d1]
php(+0x2e391d)[0x5566506f991d]
php(execute_ex+0x1b)[0x5566506b4e2b]
php(dtrace_execute_ex+0xb1)[0x5566506649d1]
[Touch-packages] [Bug 1626883] Re: libssl 1.0.2g-1ubuntu4.4 causes PHP7 SSL cert validation to segfault
The issue is not limited to Ubuntu 16.04 and PHP 7.
We experience a similar issue on Ubuntu 14.04 using PHP 5.5 (se exact
system info below).
Tonight's unattended openssl update from 1.0.1f-1ubuntu2.19 to 1.0.1f-
1ubuntu2.20 (http://www.ubuntu.com/usn/usn-3087-1/,
http://changelogs.ubuntu.com/changelogs/pool/main/o/openssl/openssl_1.0
.1f-1ubuntu2.20/changelog) causes our Satis installation
(https://github.com/composer/satis) to segfault on trying to establish
HTTPS connections;
Start-Date: 2016-09-23 04:45:30
Upgrade: libssl1.0.0:amd64 (1.0.1f-1ubuntu2.19, 1.0.1f-1ubuntu2.20),
libssl-dev:amd64 (1.0.1f-1ubuntu2.19, 1.0.1f-1ubuntu2.20), libssl-doc:amd64
(1.0.1f-1ubuntu2.19, 1.0.1f-1ubuntu2.20), openssl:amd64 (1.0.1f-1ubuntu2.19,
1.0.1f-1ubuntu2.20)
End-Date: 2016-09-23 04:45:34
We have isolated it to this simple php command trying to parse the openssl
provided ca-certs also triggering the issue;
# php -r
"openssl_x509_parse(file_get_contents('/etc/ssl/certs/ca-certificates.crt'));"
Segmentation fault (core dumped)
Downgrading is only possible to 1.0.1f-1ubuntu2, which causes some dependencies
to be uninstalled which seems counterproductive;
# apt-get install libssl1.0.0=1.0.1f-1ubuntu2.19
Reading package lists... Done
Building dependency tree
Reading state information... Done
E: Version '1.0.1f-1ubuntu2.19' for 'libssl1.0.0' was not found
# apt-get install libssl1.0.0=1.0.1f-1ubuntu2
...
The following packages will be REMOVED:
libssl-dev node-gyp nodejs-dev npm php5-dev
The following packages will be DOWNGRADED:
libssl1.0.0
0 upgraded, 0 newly installed, 1 downgraded, 5 to remove and 1 not upgraded.
Why would those dependencies be removed and why can't I pinpoint that I want
1.0.1f-1ubuntu2.19 installed?
# php -v
PHP 5.5.9-1ubuntu4.19 (cli) (built: Jul 28 2016 19:31:33)
Copyright (c) 1997-2014 The PHP Group
Zend Engine v2.5.0, Copyright (c) 1998-2014 Zend Technologies
with Zend OPcache v7.0.3, Copyright (c) 1999-2014, by Zend Technologies
with Xdebug v2.2.3, Copyright (c) 2002-2013, by Derick Rethans
# lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu 14.04.5 LTS
Release:14.04
Codename: trusty
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openssl in Ubuntu.
https://bugs.launchpad.net/bugs/1626883
Title:
libssl 1.0.2g-1ubuntu4.4 causes PHP7 SSL cert validation to segfault
Status in openssl package in Ubuntu:
New
Bug description:
Last night unattended-upgrades upgraded the openssl packages
(libssl1.0.0, libssl-dev, openssl) from version 1.0.2g-1ubuntu4.1 to
version 1.0.2g-1ubuntu4.4 on a CI build server. Then everything that
used PHP to connect to a HTTPS site started crashing when verifying
the server cert.
Like this:
```
jenkins@ubuntutemplate:/var/lib/jenkins/workspace/imt-erp-e2e-flaky/webshop/vagrant/wordpress$
DATABASE_DATABASE=wordpressmastere2e catchsegv wp plugin install --force
--activate wp-cfm
Deprecated: Methods with the same name as their class will not be
constructors in a future version of PHP; WP_Import has a deprecated constructor
in /var/lib/jenkins/workspace/imt-erp-e2e-flaky/webshop
/vagrant/wordpress/wp-content/plugins/wordpress-importer/wordpress-importer.php
on line 38
Notice: Undefined offset: 4 in
phar:///usr/local/bin/wp/php/WP_CLI/DocParser.php on line 124
Segmentation fault (core dumped)
*** Segmentation fault
Register dump:
RAX: RBX: 0001 RCX:
RDX: 000c RSI: 55665071af59 RDI:
RBP: 556650a49e4e R8 : 556652364720 R9 :
R10: R11: 7fdb3c081730 R12: 55665071af59
R13: 000c R14: R15: 7fdb39418cf0
RSP: 7ffc4bad7a08
RIP: 7fdb3bf77d16 EFLAGS: 00010293
CS: 0033 FS: GS:
Trap: 000e Error: 0004 OldMask: CR2:
FPUCW: 027f FPUSW: TAG:
RIP: RDP:
ST(0) ST(1)
ST(2) ST(3)
ST(4) ST(5)
ST(6) ST(7)
mxcsr: 1fa0
XMM0: XMM1:
XMM2: XMM3:
XMM4: XMM5:
XMM6: XMM7:
XMM8: XMM9:
XMM10: XMM11:
XMM12: XMM13:
[Touch-packages] [Bug 1385537] Re: logrotate does not rotate logs (rsyslog)
I assume the affected system is a live USB/installer system? It is not
quite obvious from the description.
I am having the same issue of missing logrotation when using the Ubuntu
Desktop 14.04.3 LTS installer
(http://releases.ubuntu.com/14.04.3/ubuntu-14.04.3-desktop-amd64.iso) as
basis for a demonstration/test setup.
Seeing my logs accumulating I tried to configure logrotate but was
puzzled when seeing it already configured and cron seems to run
cron.daily according to log (.1 is caused by me running logrotate
manually):
ubuntu@ubuntu:~$ grep cron.daily /var/log/syslog*
...
/var/log/syslog.1:Jan 11 06:25:01 ubuntu CRON[19057]: (root) CMD (test -x
/usr/sbin/anacron || ( cd / && run-parts --report /etc/cron.daily ))
/var/log/syslog.1:Jan 12 06:25:01 ubuntu CRON[20265]: (root) CMD (test -x
/usr/sbin/anacron || ( cd / && run-parts --report /etc/cron.daily ))
/var/log/syslog.1:Jan 13 06:25:01 ubuntu CRON[21361]: (root) CMD (test -x
/usr/sbin/anacron || ( cd / && run-parts --report /etc/cron.daily ))
Digged a lot to find out /usr/sbin/anacron was intentionally diverted
using dpkg-divert, but haven't found out yet if and how this affects the
cron.daily execution;
ubuntu@ubuntu:~$ dpkg-divert --list|grep anacron
local diversion of /usr/sbin/anacron to /usr/sbin/anacron.distrib
ubuntu@ubuntu:~$ ls -l /usr/sbin/anacron
lrwxrwxrwx 1 root root 9 Nov 18 14:11 /usr/sbin/anacron -> /bin/true
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to logrotate in Ubuntu.
https://bugs.launchpad.net/bugs/1385537
Title:
logrotate does not rotate logs (rsyslog)
Status in logrotate package in Ubuntu:
Confirmed
Bug description:
(Expected: auth.log, kern.log, syslog rotated "daily"/"weakly"
according to /etd/..., actually: no rotation even after weeks; and
manual forcing may fail.)
Being concerned about the amount of GBs that a Lubuntu persistent
installation on a USB flash drive may write per day, I observed that
auth.log, kern.log, and syslog grow to many MB. They may get about
1000 entries a day, resulting in many GB load for the USB drive per
day. I learnt about logrotate and rsyslog and modified
/etc/logrotate.conf and /etc/logrotate.d/rsyslog. Yet none had any
effect.
I have kept USB installations of Lubuntu 14.04.1 in parallel and saved
them after some days, so I could report about a number of experiments.
E.g., I started 2014-08-31, and I have a snapshot from 2014-09-22
where I had not changed /etc/logrotate.conf, neither
/etc/logrotate.d/rsyslog ("daily", "weekly"), and the three files
still have the entries from 2014-08-31, although three "weeks" had
passed.
#51879 (2006) and #1278193 (Feb 2014) are very similar, however:
* I observed growing kern.log and syslog to more than 100MB (to "out of
memory" finally) in some installations in summer 2013; in later installations
the same year and before 14.04, the problem vanished (I watched the sizes
manually/regularly – difference to #51879: after 2006, problem recurred,
vanished, recurred).
* With Lubuntu 14.04.1 recently, I changed "weekly" into "daily" in
/etc/logratate.conf and in /etc/logrotate.d/rsyslog, but three days later
auth.log, kern.log, and syslog still had no older copies and still contained
messages from the last three days. Then I did sudo logrotate-f
/etc/logrotate.conf, which works, but still after another three days those
three logs had not been rotated.
Actually I also have tried sudo logrotate -f /etc/logrotate.d/rsyslog,
and the result has been exactly as #1258202 (2013). As opposed to the
latter report and that for #1278193, I am unable to guess from which
changes the problems might have resulted.
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: logrotate 3.8.7-1ubuntu1
ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4
Uname: Linux 3.13.0-32-generic i686
ApportVersion: 2.14.1-0ubuntu3.2
Architecture: i386
CasperVersion: 1.340
CurrentDesktop: LXDE
Date: Sat Oct 25 01:02:40 2014
LiveMediaBuild: Lubuntu 14.04.1 LTS "Trusty Tahr" - Release i386 (20140722.2)
SourcePackage: logrotate
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/logrotate/+bug/1385537/+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
