Update issues on V8

ropeguru

Member
Nov 18, 2019
37
2
13
65
So I am trying to update my nodes and every single one is stuck at, "Processing triggers for pve-manager (8.0.4) ..."

Looking at top there is nothing unusual going on and all the VM's are running with no issues. Anyone else seeing issues in the latest round of upgrades?

Code:
Setting up libpve-cluster-perl (8.0.4) ...
Setting up libuutil3linux (2.1.13-pve1) ...
Setting up libnozzle1:amd64 (1.26-pve1) ...
Setting up libpve-cluster-api-perl (8.0.4) ...
Setting up libzfs4linux (2.1.13-pve1) ...
Setting up proxmox-kernel-6.2 (6.2.16-15) ...
Setting up libpve-guest-common-perl (5.0.5) ...
Setting up libzpool5linux (2.1.13-pve1) ...
Setting up zfsutils-linux (2.1.13-pve1) ...
Setting up zfs-initramfs (2.1.13-pve1) ...
Setting up zfs-zed (2.1.13-pve1) ...
Installing new version of config file /etc/zfs/zed.d/zed.rc ...
Processing triggers for initramfs-tools (0.142) ...
update-initramfs: Generating /boot/initrd.img-6.2.16-15-pve
Running hook script 'zz-proxmox-boot'..
Re-executing '/etc/kernel/postinst.d/zz-proxmox-boot' in new private mount namespace..
No /etc/kernel/proxmox-boot-uuids found, skipping ESP sync.
Processing triggers for libc-bin (2.36-9+deb12u3) ...
Processing triggers for pve-manager (8.0.4) ...


Last few lines from dpkg.log

Code:
2023-10-05 08:56:21 configure zfs-initramfs:all 2.1.13-pve1 <none>
2023-10-05 08:56:21 status unpacked zfs-initramfs:all 2.1.13-pve1
2023-10-05 08:56:21 status half-configured zfs-initramfs:all 2.1.13-pve1
2023-10-05 08:56:21 status installed zfs-initramfs:all 2.1.13-pve1
2023-10-05 08:56:21 configure zfs-zed:amd64 2.1.13-pve1 <none>
2023-10-05 08:56:21 status unpacked zfs-zed:amd64 2.1.13-pve1
2023-10-05 08:56:21 status half-configured zfs-zed:amd64 2.1.13-pve1
2023-10-05 08:56:22 status installed zfs-zed:amd64 2.1.13-pve1
2023-10-05 08:56:22 trigproc initramfs-tools:all 0.142 <none>
2023-10-05 08:56:22 status half-configured initramfs-tools:all 0.142
2023-10-05 08:56:38 status installed initramfs-tools:all 0.142
2023-10-05 08:56:38 trigproc libc-bin:amd64 2.36-9+deb12u3 <none>
2023-10-05 08:56:38 status half-configured libc-bin:amd64 2.36-9+deb12u3
2023-10-05 08:56:38 status installed libc-bin:amd64 2.36-9+deb12u3
2023-10-05 08:56:38 trigproc pve-manager:amd64 8.0.4 <none>
2023-10-05 08:56:38 status half-configured pve-manager:amd64 8.0.4
 
Last edited:
Hi,
you can check the output of ps faxl, i.e. the tree below the apt process, which might give a hint as to where the command is stuck. From which version did you upgrade? Anything in the system logs/journal?