Derek, do you have more logs for April 24? It would be very valuable to know what started the apt/dpkg processes. These files would be useful (most are rotated: most likely data for April 24 is in a foo.*.gz file):
apt/dpkg/unattended-upgrades logs: - /var/log/apt/history.log* - /var/log/apt/term.log* - /var/log/dpkg.log* -/var/log/unattended-upgrades/* system logs (in order to find out connection/disconnection times and possible other errors) - /var/log/syslog* - /var/log/auth.log* System logs likely contain private information, especially syslog and auth.log. All logs fairly explicit when it comes to dates and it should be easy to narrow logs down to the appropriate time range and remove whatever needs to be removed. Thanks a lot. That would be tremendously helpful since, as you can see, the actual error happens weeks before the report and it has been difficult to collect useful logs. Seth, I don't think needrestart spawns debconf (but launchpad/HTML doesn't display consecutive spaces as several ones). My understanding is as follows: dpkg (1224019) sources/runs /etc/dpkg/dpkg.cfg.d/needrestart as PID 1224020 sh (1224020) spawns a subshell as PID 1224021 sh (1224021) spawns /sh /usr/lib/needrestart/dpkg-status as PID 1224022 dpkg-status (1224022) reads dpkg's output, probably until dpkg exits dpkg (1224019) runs the grub postinst script, probably as PID 1224023 (not listed) grub's postinst (1224023?) sources debconf's script which notices debconf is not running and therefore execs debconf which then spawns the grub postinst again as PID 1224024; AFAIU that's the intended behavior grub's postinst (1224023) sits there waiting, possibly for results from debconf Since the grub postinst never finishes, dpkg itself never finishes and needrestart doesn't finish either. Btw, I'm getting more motivated to get rid of the current postinst in openssl because it's responsible for a large number of bug reports (both because the behaviour is suboptimal and because it uses debconf and gathers such bug reports [ I would also like this to be fixed debconf side obviously ]). -- 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/2008846 Title: package libssl3:amd64 3.0.2-0ubuntu1.8 failed to install/upgrade: installed libssl3:amd64 package post-installation script subprocess returned error exit status 1 Status in needrestart package in Ubuntu: New Status in openssl package in Ubuntu: Incomplete Bug description: encounter error when attempting to do sudo update, upgrade, and full- upgrade ProblemType: Package DistroRelease: Ubuntu 22.04 Package: libssl3:amd64 3.0.2-0ubuntu1.8 ProcVersionSignature: Ubuntu 5.15.0-58.64-generic 5.15.74 Uname: Linux 5.15.0-58-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.3 Architecture: amd64 CasperMD5CheckResult: pass Date: Wed Mar 1 10:28:26 2023 ErrorMessage: installed libssl3:amd64 package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2022-10-01 (150 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) Python3Details: /usr/bin/python3.10, Python 3.10.6, python3-minimal, 3.10.6-1~22.04 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.21.1ubuntu2.1 apt 2.4.8 SourcePackage: openssl Title: package libssl3:amd64 3.0.2-0ubuntu1.8 failed to install/upgrade: installed libssl3:amd64 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/needrestart/+bug/2008846/+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
