Updates failing after 8.3 Upgrade

B

banjocookies

New Member
Nov 23, 2024
1
0
1
Upgraded to 8.3 the other day and now when I go to update via GUI or shell I am getting the following error output.
starting apt-get update
Reading package lists...
E: Method http has died unexpectedly!
E: Sub-process http received signal 7.
E: Method /usr/lib/apt/methods/http did not start correctly
E: Method http has died unexpectedly!
E: Sub-process http received signal 7.
E: Method /usr/lib/apt/methods/http did not start correctly
E: Method http has died unexpectedly!
E: Sub-process http received signal 7.
E: Method /usr/lib/apt/methods/http did not start correctly
E: Method http has died unexpectedly!
E: Sub-process http received signal 7.
E: Method /usr/lib/apt/methods/http did not start correctly
E: Failed to fetch http://deb.debian.org/debian/dists/bookworm/InRelease
E: Failed to fetch http://deb.debian.org/debian/dists/bookworm-updates/InRelease
E: Failed to fetch http://security.debian.org/debian-security/dists/bookworm-security/InRelease
E: Failed to fetch http://download.proxmox.com/debian/pve/dists/bookworm/InRelease
E: Some index files failed to download. They have been ignored, or old ones used instead.
TASK ERROR: command 'apt-get update' failed: exit code 100
Click to expand...
I have tried rebooting, I've checked the source list to make sure they are all referencing Bookworm, ran the Post Install Helper Script to make sure I'm on the no subscription repo. Nothing seems to resolve the error. Any ideas?
 
Hi,
signal 7 is SIGBUS on Linux, which often points to certain kinds of memory access issues. Does booting into an older kernel make the issue go away? If not, I'd run memtest86+ (from the installer ISO) to check the RAM. Please check the system logs/journal to see if there is more information about the error.
 
Here is the log when apt upgrade failed on a fresh 8.3 install

```
Proxmox update upgrade error leaves proxmox in a state where the VM can't boot.
```

Code: 
```
root@msi:~# sudo apt update
107 packages can be upgraded. Run 'apt list --upgradable' to see them.

root@msi:~# sudo apt upgrade -y
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Calculating upgrade... Done
Fetched 402 MB in 11s (35.9 MB/s)                                                                                                                                                                                               
apt-listchanges: Reading changelogs...
Extracting templates from packages: 100%
Preconfiguring packages ...
Generation complete.
Setting up systemd-boot (252.36-1~deb12u1) ...
Setting up tzdata (2025b-0+deb12u1) ...

Current default time zone: 'America/Los_Angeles'
Local time is now:      Thu Apr  3 10:22:10 PDT 2025.
Universal Time is now:  Thu Apr  3 17:22:10 UTC 2025.
Run 'dpkg-reconfigure tzdata' if you wish to change it.

Setting up novnc-pve (1.6.0-2) ...
Setting up proxmox-backup-client (3.3.4-1) ...
Setting up libfreetype6:amd64 (2.12.1+dfsg-5+deb12u4) ...
Setting up libgnutlsxx30:amd64 (3.7.9-2+deb12u4) ...
Setting up proxmox-kernel-6.8.12-9-pve-signed (6.8.12-9) ...
Examining /etc/kernel/postinst.d.
run-parts: executing /etc/kernel/postinst.d/initramfs-tools 6.8.12-9-pve /boot/vmlinuz-6.8.12-9-pve
update-initramfs: Generating /boot/initrd.img-6.8.12-9-pve
Running hook script 'zz-proxmox-boot'..
Re-executing '/etc/kernel/postinst.d/zz-proxmox-boot' in new private mount namespace..
Copying and configuring kernels on /dev/disk/by-uuid/B820-0CDB
    Copying kernel 6.8.12-4-pve
    Copying kernel 6.8.12-9-pve
Generating grub configuration file ...
Found linux image: /boot/vmlinuz-6.8.12-9-pve
Found initrd image: /boot/initrd.img-6.8.12-9-pve
Found linux image: /boot/vmlinuz-6.8.12-4-pve
Found initrd image: /boot/initrd.img-6.8.12-4-pve
Adding boot menu entry for UEFI Firmware Settings ...
done
run-parts: executing /etc/kernel/postinst.d/proxmox-auto-removal 6.8.12-9-pve /boot/vmlinuz-6.8.12-9-pve
run-parts: executing /etc/kernel/postinst.d/zz-proxmox-boot 6.8.12-9-pve /boot/vmlinuz-6.8.12-9-pve
Re-executing '/etc/kernel/postinst.d/zz-proxmox-boot' in new private mount namespace..
Copying and configuring kernels on /dev/disk/by-uuid/B820-0CDB
    Copying kernel 6.8.12-4-pve
    Copying kernel 6.8.12-9-pve
Generating grub configuration file ...
Found linux image: /boot/vmlinuz-6.8.12-9-pve
Found initrd image: /boot/initrd.img-6.8.12-9-pve
Found linux image: /boot/vmlinuz-6.8.12-4-pve
Found initrd image: /boot/initrd.img-6.8.12-4-pve
Adding boot menu entry for UEFI Firmware Settings ...
done
run-parts: executing /etc/kernel/postinst.d/zz-update-grub 6.8.12-9-pve /boot/vmlinuz-6.8.12-9-pve
Generating grub configuration file ...
Found linux image: /boot/vmlinuz-6.8.12-9-pve
Found initrd image: /boot/initrd.img-6.8.12-9-pve
/usr/sbin/grub-probe: error: unknown filesystem.
Found linux image: /boot/vmlinuz-6.8.12-4-pve
Found initrd image: /boot/initrd.img-6.8.12-4-pve
/usr/sbin/grub-probe: error: unknown filesystem.
Adding boot menu entry for UEFI Firmware Settings ...
done
Setting up libavahi-common-data:amd64 (0.8-10+deb12u1) ...
Setting up spl (2.2.7-pve2) ...
Setting up python3-ceph-common (18.2.4-pve3) ...
Setting up udev (252.36-1~deb12u1) ...
Job for systemd-udevd.service failed because the control process exited with error code.
See "systemctl status systemd-udevd.service" and "journalctl -xeu systemd-udevd.service" for details.
invoke-rc.d: initscript udev, action "restart" failed.
● systemd-udevd.service - Rule-based Manager for Device Events and Files
     Loaded: loaded (/lib/systemd/system/systemd-udevd.service; static)
     Active: activating (auto-restart) (Result: exit-code) since Thu 2025-04-03 10:23:05 PDT; 1ms ago
TriggeredBy: ● systemd-udevd-control.socket
             ● systemd-udevd-kernel.socket
       Docs: man:systemd-udevd.service(8)
             man:udev(7)
    Process: 200459 ExecStart=/lib/systemd/systemd-udevd (code=exited, status=226/NAMESPACE)
   Main PID: 200459 (code=exited, status=226/NAMESPACE)
        CPU: 754us

Apr 03 10:23:05 msi systemd[1]: systemd-udevd.service: Scheduled restart job, restart counter is at 3.
Apr 03 10:23:05 msi systemd[1]: Stopped systemd-udevd.service - Rule-based Manager for Device Events and Files.
Apr 03 10:23:05 msi systemd[1]: Starting systemd-udevd.service - Rule-based Manager for Device Events and Files...
Apr 03 10:23:05 msi (md-udevd)[200460]: systemd-udevd.service: Failed to set up mount namespacing: /run/systemd/unit-root/proc/sys/kernel/domainname: No such file or directory
Apr 03 10:23:05 msi (md-udevd)[200460]: systemd-udevd.service: Failed at step NAMESPACE spawning /lib/systemd/systemd-udevd: No such file or directory
Apr 03 10:23:05 msi systemd[1]: systemd-udevd.service: Main process exited, code=exited, status=226/NAMESPACE
Apr 03 10:23:05 msi systemd[1]: systemd-udevd.service: Failed with result 'exit-code'.
Apr 03 10:23:05 msi systemd[1]: Failed to start systemd-udevd.service - Rule-based Manager for Device Events and Files.
dpkg: error processing package udev (--configure):
 installed udev package post-installation script subprocess returned error exit status 1
Setting up pve-i18n (3.4.1) ...
Setting up ucf (3.0043+nmu1+deb12u1) ...
Setting up libpve-network-api-perl (0.10.1) ...
Setting up libdpkg-perl (1.21.22) ...
dpkg: dependency problems prevent configuration of libpve-storage-perl:
 libpve-storage-perl depends on udev; however:
  Package udev is not configured yet.

dpkg: error processing package libpve-storage-perl (--configure):
 dependency problems - leaving unconfigured
Setting up python3-urllib3 (1.26.12-1+deb12u1) ...
Setting up pve-edk2-firmware-legacy (4.2025.02-2) ...
Setting up criu (3.17.1-2+deb12u1) ...
Setting up libxslt1.1:amd64 (1.1.35-1+deb12u1) ...
Setting up libpam-systemd:amd64 (252.36-1~deb12u1) ...
Setting up libcurl4:amd64 (7.88.1-10+deb12u12) ...
Setting up libpython3.11-minimal:amd64 (3.11.2-6+deb12u5) ...
Setting up curl (7.88.1-10+deb12u12) ...
Setting up libuutil3linux (2.2.7-pve2) ...
Setting up libpve-http-server-perl (5.2.0) ...
Setting up bind9-host (1:9.18.33-1~deb12u2) ...
Setting up pve-edk2-firmware (4.2025.02-2) ...
Setting up proxmox-kernel-6.8 (6.8.12-9) ...
Setting up libproxmox-backup-qemu0 (1.5.1) ...
Setting up libgstreamer1.0-0:amd64 (1.22.0-2+deb12u1) ...
Setcap worked! gst-ptp-helper is not suid!
Setting up rsync (3.2.7-1+deb12u2) ...
rsync.service is a disabled or a static unit not running, not starting it.
Setting up libzpool5linux (2.2.7-pve2) ...
Setting up gnutls-bin (3.7.9-2+deb12u4) ...
Setting up python3.11-minimal (3.11.2-6+deb12u5) ...
Setting up openssh-sftp-server (1:9.2p1-2+deb12u5) ...
Setting up librados2 (18.2.4-pve3) ...
dpkg: dependency problems prevent configuration of pve-container:
 pve-container depends on libpve-storage-perl (>= 7.2-10); however:
  Package libpve-storage-perl is not configured yet.

dpkg: error processing package pve-container (--configure):
 dependency problems - leaving unconfigured
Setting up librgw2 (18.2.4-pve3) ...
Setting up openssh-server (1:9.2p1-2+deb12u5) ...
rescue-ssh.target is a disabled or a static unit not running, not starting it.
ssh.socket is a disabled or a static unit not running, not starting it.
Setting up pve-nvidia-vgpu-helper (0.2.0) ...
Setting up libpython3.11-stdlib:amd64 (3.11.2-6+deb12u5) ...
Setting up xsltproc (1.1.35-1+deb12u1) ...
Setting up libavahi-common3:amd64 (0.8-10+deb12u1) ...
Setting up libgstreamer-plugins-base1.0-0:amd64 (1.22.0-3+deb12u4) ...
dpkg: dependency problems prevent configuration of pve-manager:
 pve-manager depends on libpve-storage-perl (>= 8.2.8); however:
  Package libpve-storage-perl is not configured yet.
 pve-manager depends on pve-container (>= 5.1.11); however:
  Package pve-container is not configured yet.

dpkg: error processing package pve-manager (--configure):
 dependency problems - leaving unconfigured
Setting up libzfs4linux (2.2.7-pve2) ...
dpkg: dependency problems prevent configuration of qemu-server:
 qemu-server depends on libpve-storage-perl (>= 8.2.10); however:
  Package libpve-storage-perl is not configured yet.

dpkg: error processing package qemu-server (--configure):
 dependency problems - leaving unconfigured
Setting up libcephfs2 (18.2.4-pve3) ...
Setting up nfs-common (1:2.6.2-4+deb12u1) ...
auth-rpcgss-module.service is a disabled or a static unit not running, not starting it.
nfs-idmapd.service is a disabled or a static unit not running, not starting it.
nfs-utils.service is a disabled or a static unit not running, not starting it.
proc-fs-nfsd.mount is a disabled or a static unit not running, not starting it.
rpc-gssd.service is a disabled or a static unit not running, not starting it.
rpc-statd.service is a disabled or a static unit not running, not starting it.
rpc-svcgssd.service is a disabled or a static unit not running, not starting it.
var-lib-nfs-rpc_pipefs.mount is a disabled or a static unit not running, not starting it.
dpkg: dependency problems prevent configuration of proxmox-kernel-helper:
 proxmox-kernel-helper depends on udev; however:
  Package udev is not configured yet.

dpkg: error processing package proxmox-kernel-helper (--configure):
 dependency problems - leaving unconfigured
Setting up grub-common (2.06-13+pmx6) ...
Setting up zfsutils-linux (2.2.7-pve2) ...
Setting up libradosstriper1 (18.2.4-pve3) ...
Setting up zfs-initramfs (2.2.7-pve2) ...
Setting up libproxmox-acme-plugins (1.6.0) ...
Setting up librbd1 (18.2.4-pve3) ...
Setting up bind9-dnsutils (1:9.18.33-1~deb12u2) ...
Setting up grub-efi-amd64-bin (2.06-13+pmx6) ...
Setting up ceph-fuse (18.2.4-pve3) ...
Setting up libavahi-client3:amd64 (0.8-10+deb12u1) ...
Setting up python3.11 (3.11.2-6+deb12u5) ...
Setting up python3-rados (18.2.4-pve3) ...
Setting up grub-efi-amd64-signed (1+2.06+13+pmx6) ...
Setting up ssh (1:9.2p1-2+deb12u5) ...
Setting up grub2-common (2.06-13+pmx6) ...
Setting up python3-rbd (18.2.4-pve3) ...
Setting up grub-pc-bin (2.06-13+pmx6) ...
Setting up zfs-zed (2.2.7-pve2) ...
Installing new version of config file /etc/zfs/zed.d/zed.rc ...
Setting up grub-efi-amd64 (2.06-13+pmx6) ...
Generating grub configuration file ...
Found linux image: /boot/vmlinuz-6.8.12-9-pve
Found initrd image: /boot/initrd.img-6.8.12-9-pve
/usr/sbin/grub-probe: error: unknown filesystem.
Found linux image: /boot/vmlinuz-6.8.12-4-pve
Found initrd image: /boot/initrd.img-6.8.12-4-pve
/usr/sbin/grub-probe: error: unknown filesystem.
Adding boot menu entry for UEFI Firmware Settings ...
done
Setting up python3-rgw (18.2.4-pve3) ...
Setting up python3-cephfs (18.2.4-pve3) ...
Setting up proxmox-grub (2.06-13+pmx6) ...
Setting up ceph-common (18.2.4-pve3) ...
Setting system user ceph properties..usermod: no changes
usermod: unlocking the user's password would result in a passwordless account.
You should set a password with usermod -p to unlock this user's password.
..done
chown: cannot access '/var/log/ceph/*.log*': No such file or directory
Fixing /var/run/ceph ownership....done
Setting up proxmox-secure-boot-support (1.0.12) ...
Setting up pve-qemu-kvm (9.2.0-3) ...
Setting up libpve-rs-perl (0.9.2) ...
Setting up libproxmox-rs-perl (0.3.5) ...
Processing triggers for mailcap (3.70+nmu1) ...
dpkg: dependency problems prevent processing triggers for pve-ha-manager:
 pve-ha-manager depends on pve-container (>= 5.0.1); however:
  Package pve-container is not configured yet.
 pve-ha-manager depends on qemu-server (>= 8.0.2); however:
  Package qemu-server is not configured yet.

dpkg: error processing package pve-ha-manager (--configure):
 dependency problems - leaving triggers unprocessed
Processing triggers for initramfs-tools (0.142+deb12u1) ...
update-initramfs: Generating /boot/initrd.img-6.8.12-9-pve
Running hook script 'zz-proxmox-boot'..
Re-executing '/etc/kernel/postinst.d/zz-proxmox-boot' in new private mount namespace..
Copying and configuring kernels on /dev/disk/by-uuid/B820-0CDB
    Copying kernel 6.8.12-4-pve
    Copying kernel 6.8.12-9-pve
Generating grub configuration file ...
Found linux image: /boot/vmlinuz-6.8.12-9-pve
Found initrd image: /boot/initrd.img-6.8.12-9-pve
Found linux image: /boot/vmlinuz-6.8.12-4-pve
Found initrd image: /boot/initrd.img-6.8.12-4-pve
Adding boot menu entry for UEFI Firmware Settings ...
done
Processing triggers for libc-bin (2.36-9+deb12u10) ...
Processing triggers for systemd (252.36-1~deb12u1) ...
Processing triggers for man-db (2.11.2-2) ...
Processing triggers for dbus (1.14.10-1~deb12u1) ...
Processing triggers for shim-signed:amd64 (1.44+pmx1+15.8-1+pmx1) ...
Errors were encountered while processing:
 udev
 libpve-storage-perl
 pve-container
 pve-manager
 qemu-server
 proxmox-kernel-helper
 pve-ha-manager
E: Sub-process /usr/bin/dpkg returned an error code (1)
root@msi:~#
```
 
I reinstalled proxmox 8.3 and this time I made sure to NOT add the CEPH repo


Code: 
# - name: Add No Subscription ceph repository
    #   apt_repository:
    #     repo: deb http://download.proxmox.com/debian/ceph-reef {{ ansible_distribution_release }} no-subscription
    #     filename: ceph-no-subscription
    #     update_cache: false
    #     state: present

and then the upgrade went through just fine after a fresh install
 
Thanks Fiona.

If `apt upgrade` is incorrect, I expect proxmox VE system to refuse to run that incorrect command, and instead, guide the user to run the correct command.
 
You must log in or register to reply here.
Top Bottom