[Touch-packages] [Bug 2063533] Re: package systemd-resolved 255.4-1ubuntu8 failed to install/upgrade: installed systemd-resolved package post-installation script subprocess returned error exit status
*** This bug is a duplicate of bug 2047975 *** https://bugs.launchpad.net/bugs/2047975 cainmp@svr-ns1:~$ cat /etc/resolv.conf # This is /run/systemd/resolve/resolv.conf managed by man:systemd-resolved(8). # Do not edit. # # This file might be symlinked as /etc/resolv.conf. If you're looking at # /etc/resolv.conf and seeing this text, you have followed the symlink. # # This is a dynamic resolv.conf file for connecting local clients directly to # all known uplink DNS servers. This file lists all configured search domains. # # Third party programs should typically not access this file directly, but only # through the symlink at /etc/resolv.conf. To manage man:resolv.conf(5) in a # different way, replace this symlink by a static file or a different symlink. # # See man:systemd-resolved.service(8) for details about the supported modes of # operation for /etc/resolv.conf. nameserver 172.16.*.* nameserver 172.16.*.* search *.* cainmp@svr-ns1:~$ * are all sanitized values -- 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/2063533 Title: package systemd-resolved 255.4-1ubuntu8 failed to install/upgrade: installed systemd-resolved package post-installation script subprocess returned error exit status 1 [cp: '/etc/resolv.conf' and '/run/systemd/resolve/stub-resolv.conf' are the same file] Status in systemd package in Ubuntu: New Bug description: Trying to update 22.04.4 to 24.04 ProblemType: Package DistroRelease: Ubuntu 24.04 Package: systemd-resolved 255.4-1ubuntu8 ProcVersionSignature: Ubuntu 6.5.0-28.29~22.04.1-generic 6.5.13 Uname: Linux 6.5.0-28-generic x86_64 ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CloudArchitecture: x86_64 CloudID: none CloudName: none CloudPlatform: none CloudSubPlatform: config Date: Thu Apr 25 23:05:36 2024 ErrorMessage: installed systemd-resolved package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2024-04-09 (16 days ago) InstallationMedia: Ubuntu-Server 22.04.4 LTS "Jammy Jellyfish" - Release amd64 (20240216.1) Python3Details: /usr/bin/python3.12, Python 3.12.3, python3-minimal, 3.12.3-0ubuntu1 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.22.6ubuntu6 apt 2.7.14build2 SourcePackage: systemd Title: package systemd-resolved 255.4-1ubuntu8 failed to install/upgrade: installed systemd-resolved package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to noble on 2024-04-26 (0 days ago) mtime.conffile..etc.init.d.apport: 2024-04-18T19:50:32 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2063533/+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 2063533] Re: package systemd-resolved 255.4-1ubuntu8 failed to install/upgrade: installed systemd-resolved package post-installation script subprocess returned error exit status
*** This bug is a duplicate of bug 2047975 *** https://bugs.launchpad.net/bugs/2047975 Per here: https://www.turek.dev/posts/disable-systemd-resolved-cleanly/ and the "Clean" solution -- 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/2063533 Title: package systemd-resolved 255.4-1ubuntu8 failed to install/upgrade: installed systemd-resolved package post-installation script subprocess returned error exit status 1 [cp: '/etc/resolv.conf' and '/run/systemd/resolve/stub-resolv.conf' are the same file] Status in systemd package in Ubuntu: New Bug description: Trying to update 22.04.4 to 24.04 ProblemType: Package DistroRelease: Ubuntu 24.04 Package: systemd-resolved 255.4-1ubuntu8 ProcVersionSignature: Ubuntu 6.5.0-28.29~22.04.1-generic 6.5.13 Uname: Linux 6.5.0-28-generic x86_64 ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CloudArchitecture: x86_64 CloudID: none CloudName: none CloudPlatform: none CloudSubPlatform: config Date: Thu Apr 25 23:05:36 2024 ErrorMessage: installed systemd-resolved package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2024-04-09 (16 days ago) InstallationMedia: Ubuntu-Server 22.04.4 LTS "Jammy Jellyfish" - Release amd64 (20240216.1) Python3Details: /usr/bin/python3.12, Python 3.12.3, python3-minimal, 3.12.3-0ubuntu1 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.22.6ubuntu6 apt 2.7.14build2 SourcePackage: systemd Title: package systemd-resolved 255.4-1ubuntu8 failed to install/upgrade: installed systemd-resolved package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to noble on 2024-04-26 (0 days ago) mtime.conffile..etc.init.d.apport: 2024-04-18T19:50:32 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2063533/+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 2063533] Re: package systemd-resolved 255.4-1ubuntu8 failed to install/upgrade: installed systemd-resolved package post-installation script subprocess returned error exit status
*** This bug is a duplicate of bug 2047975 *** https://bugs.launchpad.net/bugs/2047975 For context, on the 2 boxes I have that this effected, I have disabled the systemd stub resolver in order to allow AdGuard dns server listen on all interfaces. I am assuming that is the source of the problem. -- 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/2063533 Title: package systemd-resolved 255.4-1ubuntu8 failed to install/upgrade: installed systemd-resolved package post-installation script subprocess returned error exit status 1 [cp: '/etc/resolv.conf' and '/run/systemd/resolve/stub-resolv.conf' are the same file] Status in systemd package in Ubuntu: New Bug description: Trying to update 22.04.4 to 24.04 ProblemType: Package DistroRelease: Ubuntu 24.04 Package: systemd-resolved 255.4-1ubuntu8 ProcVersionSignature: Ubuntu 6.5.0-28.29~22.04.1-generic 6.5.13 Uname: Linux 6.5.0-28-generic x86_64 ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CloudArchitecture: x86_64 CloudID: none CloudName: none CloudPlatform: none CloudSubPlatform: config Date: Thu Apr 25 23:05:36 2024 ErrorMessage: installed systemd-resolved package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2024-04-09 (16 days ago) InstallationMedia: Ubuntu-Server 22.04.4 LTS "Jammy Jellyfish" - Release amd64 (20240216.1) Python3Details: /usr/bin/python3.12, Python 3.12.3, python3-minimal, 3.12.3-0ubuntu1 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.22.6ubuntu6 apt 2.7.14build2 SourcePackage: systemd Title: package systemd-resolved 255.4-1ubuntu8 failed to install/upgrade: installed systemd-resolved package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to noble on 2024-04-26 (0 days ago) mtime.conffile..etc.init.d.apport: 2024-04-18T19:50:32 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2063533/+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 2063533] [NEW] package systemd-resolved 255.4-1ubuntu8 failed to install/upgrade: installed systemd-resolved package post-installation script subprocess returned error exit statu
Public bug reported: Trying to update 22.04.4 to 24.04 ProblemType: Package DistroRelease: Ubuntu 24.04 Package: systemd-resolved 255.4-1ubuntu8 ProcVersionSignature: Ubuntu 6.5.0-28.29~22.04.1-generic 6.5.13 Uname: Linux 6.5.0-28-generic x86_64 ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CloudArchitecture: x86_64 CloudID: none CloudName: none CloudPlatform: none CloudSubPlatform: config Date: Thu Apr 25 23:05:36 2024 ErrorMessage: installed systemd-resolved package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2024-04-09 (16 days ago) InstallationMedia: Ubuntu-Server 22.04.4 LTS "Jammy Jellyfish" - Release amd64 (20240216.1) Python3Details: /usr/bin/python3.12, Python 3.12.3, python3-minimal, 3.12.3-0ubuntu1 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.22.6ubuntu6 apt 2.7.14build2 SourcePackage: systemd Title: package systemd-resolved 255.4-1ubuntu8 failed to install/upgrade: installed systemd-resolved package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to noble on 2024-04-26 (0 days ago) mtime.conffile..etc.init.d.apport: 2024-04-18T19:50:32 ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package need-duplicate-check noble -- 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/2063533 Title: package systemd-resolved 255.4-1ubuntu8 failed to install/upgrade: installed systemd-resolved package post-installation script subprocess returned error exit status 1 Status in systemd package in Ubuntu: New Bug description: Trying to update 22.04.4 to 24.04 ProblemType: Package DistroRelease: Ubuntu 24.04 Package: systemd-resolved 255.4-1ubuntu8 ProcVersionSignature: Ubuntu 6.5.0-28.29~22.04.1-generic 6.5.13 Uname: Linux 6.5.0-28-generic x86_64 ApportVersion: 2.28.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CloudArchitecture: x86_64 CloudID: none CloudName: none CloudPlatform: none CloudSubPlatform: config Date: Thu Apr 25 23:05:36 2024 ErrorMessage: installed systemd-resolved package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2024-04-09 (16 days ago) InstallationMedia: Ubuntu-Server 22.04.4 LTS "Jammy Jellyfish" - Release amd64 (20240216.1) Python3Details: /usr/bin/python3.12, Python 3.12.3, python3-minimal, 3.12.3-0ubuntu1 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.22.6ubuntu6 apt 2.7.14build2 SourcePackage: systemd Title: package systemd-resolved 255.4-1ubuntu8 failed to install/upgrade: installed systemd-resolved package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to noble on 2024-04-26 (0 days ago) mtime.conffile..etc.init.d.apport: 2024-04-18T19:50:32 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2063533/+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 1587142] Re: Shutdown hangs in md kworker after "Reached target Shutdown."
Confirming this same issue for me on a clean install of Ubuntu 16.04.2 X64 server on a HP 8300 Elite SFF pc. Anything I can collect to troubleshoot? -- 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/1587142 Title: Shutdown hangs in md kworker after "Reached target Shutdown." Status in systemd package in Ubuntu: Confirmed Bug description: I'm booting a fully patched 16.04 from an Intel Rapid Storage Technology enterprise RAID1 volume (ThinkServer TS140 with two SATA ST1000NM0033-9ZM drives, ext4 root partition, no LVM, UEFI mode). If the RAID volume is recovering or resyncing for whatever reason, then `sudo systemctl reboot` and `sudo systemctl poweroff` work fine (I had to `sudo systemctl --now disable lvm2-lvmetad lvm2-lvmpolld lvm2-monitor` in order to consistently get that). However, once the recovery/resync is complete and clean, the reboot and poweroff commands above hang forever after "Reached target Shutdown.". Note that issuing `sudo swapoff -a` beforehand (suggested in the bug #1464917) does not help. [EDIT]Actually, the shutdown also hangs from time to time during a resync. But I've never seen it succeed once the resync is complete.[/EDIT] Then, if the server has been forcibly restarted with the power button, the Intel Matrix Storage Manager indicates a "Normal" status for the RAID1 volume, but Ubuntu then resyncs the volume anyway: [1.223649] md: bind [1.228426] md: bind [1.230030] md: bind [1.230738] md: bind [1.232985] usbcore: registered new interface driver usbhid [1.233494] usbhid: USB HID core driver [1.234022] md: raid1 personality registered for level 1 [1.234876] md/raid1:md126: not clean -- starting background reconstruction [1.234956] input: CHESEN USB Keyboard as /devices/pci:00/:00:14.0/usb3/3-10/3-10:1.0/0003:0A81:0101.0001/input/input5 [1.236273] md/raid1:md126: active with 2 out of 2 mirrors [1.236797] md126: detected capacity change from 0 to 1000202043392 [1.246271] md: md126 switched to read-write mode. [1.246834] md: resync of RAID array md126 [1.247325] md: minimum _guaranteed_ speed: 1000 KB/sec/disk. [1.247503] md126: p1 p2 p3 p4 [1.248269] md: using maximum available idle IO bandwidth (but not more than 20 KB/sec) for resync. [1.248774] md: using 128k window, over a total of 976759940k. Note that the pain of "resync upon every (re)boot" cannot even be a bit relieved thanks to bitmaps because mdadm does not support them for IMSM containers: $ sudo mdadm --grow --bitmap=internal /dev/md126 mdadm: Cannot add bitmaps to sub-arrays yet I also get this in syslog during boot when the individual drives are detected, but this seems to be harmless: May 30 17:26:07 wssrv1 systemd-udevd[608]: Process '/sbin/mdadm --incremental /dev/sdb --offroot' failed with exit code 1. May 30 17:26:07 wssrv1 systemd-udevd[608]: Process '/lib/udev/hdparm' failed with exit code 1. May 30 17:26:07 wssrv1 systemd-udevd[606]: Process '/sbin/mdadm --incremental /dev/sda --offroot' failed with exit code 1. May 30 17:26:07 wssrv1 systemd-udevd[606]: Process '/lib/udev/hdparm' failed with exit code 1. During a resync, `sudo sh -c 'echo idle > /sys/block/md126/md/sync_action'` actually stops it as expected, but it restarts immediately though nothing seems to have triggered it: May 30 18:17:02 wssrv1 kernel: [ 3106.826710] md: md126: resync interrupted. May 30 18:17:02 wssrv1 kernel: [ 3106.836320] md: checkpointing resync of md126. May 30 18:17:02 wssrv1 kernel: [ 3106.836623] md: resync of RAID array md126 May 30 18:17:02 wssrv1 kernel: [ 3106.836625] md: minimum _guaranteed_ speed: 1000 KB/sec/disk. May 30 18:17:02 wssrv1 kernel: [ 3106.836626] md: using maximum available idle IO bandwidth (but not more than 20 KB/sec) for resync. May 30 18:17:02 wssrv1 kernel: [ 3106.836627] md: using 128k window, over a total of 976759940k. May 30 18:17:02 wssrv1 kernel: [ 3106.836628] md: resuming resync of md126 from checkpoint. May 30 18:17:02 wssrv1 mdadm[982]: RebuildStarted event detected on md device /dev/md/Volume0 I attach screenshots of the hanging shutdown log after a `sudo sh -c 'echo 8 > /proc/sys/kernel/printk'`. The second screenshot shows that the kernel has deadlocked in md_write_start(). Note that `sudo systemctl start debug-shell` is unusable on this machine at this point because Ctrl+Alt+F9 brings tty9 without any keyboard. [EDIT]But I can still switch back to tty1.[/EDIT] I have also tried with much lower values for vm.dirty_background_ratio and vm.dirty_ratio, but to no avail. Linux 4.6.0-040600-generic_4.6.0-040600.201605151930_amd64 from http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.6-yakkety/ did not help either. More information below:
