[SOLVED] pve-manager 7.4-15 hangs on post install steps

[jbloomer]

My Primary host was running impossibly slow and I was troubleshooting. In my efforts I ran updates (apt dist-upgrade) and it is trying to install pve-manager 7.4-15 but I noticed when it executes

/bin/sh /var/lib/dpkg/info/pve-manager.postinst configure 7.1-8

it just hangs and never completes regardless of how long I let it run. I am unable to remove it and reinstall it as well. Just wondering if anyone has seen this before and has any insight as to things to do?

 

[Linky]

Edit TLDR: I had the same issue, resolved it by rolling back to kernel 5.13.19-6-pve and re-running pve-manager package apt install --reinstall pve-manager. I was running kernel 5.18 when having the error.

Hi I'm in the same boat and have not yet been able to resolve it resolved it by rolling back to an older kernel.

Google searches turned up both a blog and a Reddit post that stated the service needs to be able to resolve the hostname for the install to complete. I have tried that and it did not resolve it, but maybe it will work for you.

When trying to reinstall:

hostname# apt install --reinstall pve-manager
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
0 upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 0 not upgraded.
2 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
E: Internal Error, No file name for pve-manager:amd64

When trying to reconfigure the package it hangs forever:

hostname# dpkg --configure pve-manager          
Setting up pve-manager (7.4-15) ...

Here is my system status:

hostname# pveversion -v
proxmox-ve: not correctly installed (running kernel: 5.15.108-1-pve)
pve-manager: not correctly installed (running version: 7.4-15/a5d2a31e)
pve-kernel-5.15: 7.4-4
pve-kernel-5.13: 7.1-9
pve-kernel-5.15.108-1-pve: 5.15.108-1
pve-kernel-5.15.104-1-pve: 5.15.104-2
pve-kernel-5.13.19-6-pve: 5.13.19-15
pve-kernel-5.13.19-1-pve: 5.13.19-3
pve-kernel-4.15: 5.4-6
pve-kernel-4.15.18-18-pve: 4.15.18-44
pve-kernel-4.15.18-9-pve: 4.15.18-30
ceph-fuse: 14.2.21-1
corosync: 3.1.7-pve1
criu: 3.15-1+pve-1
glusterfs-client: 9.2-1
ifupdown: residual config
ifupdown2: 3.1.0-1+pmx4
ksm-control-daemon: 1.4-1
libjs-extjs: 7.0.0-1
libknet1: 1.24-pve2
libproxmox-acme-perl: 1.4.4
libproxmox-backup-qemu0: 1.3.1-1
libproxmox-rs-perl: 0.2.1
libpve-access-control: 7.4.1
libpve-apiclient-perl: 3.2-1
libpve-common-perl: 7.4-2
libpve-guest-common-perl: 4.2-4
libpve-http-server-perl: 4.2-3
libpve-rs-perl: 0.7.7
libpve-storage-perl: 7.4-3
libqb0: 1.0.5-1
libspice-server1: 0.14.3-2.1
lvm2: 2.03.11-2.1
lxc-pve: 5.0.2-2
lxcfs: 5.0.3-pve1
novnc-pve: 1.4.0-1
proxmox-backup-client: 2.4.2-1
proxmox-backup-file-restore: 2.4.2-1
proxmox-kernel-helper: 7.4-1
proxmox-mail-forward: 0.1.1-1
proxmox-mini-journalreader: 1.3-1
proxmox-offline-mirror-helper: 0.5.2
proxmox-widget-toolkit: 3.7.3
pve-cluster: 7.3-3
pve-container: 4.4-6
pve-docs: 7.4-2
pve-edk2-firmware: 3.20230228-4~bpo11+1
pve-firewall: 4.3-4
pve-firmware: 3.6-5
pve-ha-manager: 3.6.1
pve-i18n: 2.12-1
pve-qemu-kvm: 7.2.0-8
pve-xtermjs: 4.16.0-2
qemu-server: 7.4-4
smartmontools: 7.2-pve3
spiceterm: 3.2-2
swtpm: 0.8.0~bpo11+3
vncterm: 1.7-1
zfsutils-linux: 2.1.11-pve1

 

[jbloomer]

Interesting find. I will give that a go and report back my findings. I think I am running 5.15 as my kernel

 

[jbloomer]

Great find. I booted using the 5.13.9-6-pve kernel just as you did and I was able to get the configure to work

root@proxmox01:~# dpkg --configure -a
Setting up pve-manager (7.4-15) ...
Setting up proxmox-ve (7.4-1) ...

I then checked versions and it looks good to me

root@proxmox01:~# pveversion -v
proxmox-ve: 7.4-1 (running kernel: 5.13.19-6-pve)
pve-manager: 7.4-15 (running version: 7.4-15/a5d2a31e)
pve-kernel-5.15: 7.4-4
pve-kernel-5.13: 7.1-9
pve-kernel-5.15.108-1-pve: 5.15.108-1
pve-kernel-5.13.19-6-pve: 5.13.19-15
pve-kernel-5.13.19-2-pve: 5.13.19-4
ceph-fuse: 16.2.13-pve1
corosync: 3.1.7-pve1
criu: 3.15-1+pve-1
glusterfs-client: 9.2-1
ifupdown2: 3.1.0-1+pmx4
ksm-control-daemon: 1.4-1
libjs-extjs: 7.0.0-1
libknet1: 1.24-pve2
libproxmox-acme-perl: 1.4.4
libproxmox-backup-qemu0: 1.3.1-1
libproxmox-rs-perl: 0.2.1
libpve-access-control: 7.4.1
libpve-apiclient-perl: 3.2-1
libpve-common-perl: 7.4-2
libpve-guest-common-perl: 4.2-4
libpve-http-server-perl: 4.2-3
libpve-rs-perl: 0.7.7
libpve-storage-perl: 7.4-3
libspice-server1: 0.14.3-2.1
lvm2: 2.03.11-2.1
lxc-pve: 5.0.2-2
lxcfs: 5.0.3-pve1
novnc-pve: 1.4.0-1
proxmox-backup-client: 2.4.2-1
proxmox-backup-file-restore: 2.4.2-1
proxmox-kernel-helper: 7.4-1
proxmox-mail-forward: 0.1.1-1
proxmox-mini-journalreader: 1.3-1
proxmox-offline-mirror-helper: 0.5.2
proxmox-widget-toolkit: 3.7.3
pve-cluster: 7.3-3
pve-container: 4.4-6
pve-docs: 7.4-2
pve-edk2-firmware: 3.20230228-4~bpo11+1
pve-firewall: 4.3-4
pve-firmware: 3.6-5
pve-ha-manager: 3.6.1
pve-i18n: 2.12-1
pve-qemu-kvm: 7.2.0-8
pve-xtermjs: 4.16.0-2
qemu-server: 7.4-4
smartmontools: 7.2-pve3
spiceterm: 3.2-2
swtpm: 0.8.0~bpo11+3
vncterm: 1.7-1
zfsutils-linux: 2.1.11-pve1

I then rebooted my machine and let it boot to the latest kernel again and It seems to be functional now. Guess I should mark this thread as Solved now. Thanks for sharing the fix.

 

[Linky]

Very happy this was helpful to you. Thank you for confirming the solution worked!

 

[Respy]

Fix didn't work for me. Went back to 5.15.74-1-pre and still hangs on dpkg --configure -a
Trying with 5.11.7-1... When installing the new (old) kernel it get stuck on "Setting up pve-manager (7.4-15)".
Booted into 5.11.7-1 and still hangs when "Setting up..." :/

 

[pagalba-com]

Had exactly same problem on test cluster, which was partially shrunk, and two nodes left. One of nodes was upgraded to 7.4 and first node left at 7.3. Not sure if reboot of second node was the cause, but it disconnected from cluster, and first node was silently stuck in non quorum mode.

The syslog guided me to this direction:
pveproxy[3550]: Cluster not quorate - extending auth key lifetime!

So setting

pvecm expected 1
pvecm status
...
Votequorum information
----------------------
Expected votes:   1
Highest expected: 1
Total votes:      1
Quorum:           1  
Flags:            Quorate

then retrying apt upgrade worked like a charm, after which I manually upgraded

apt upgrade proxmox-ve

and went to version 7.4