[SOLVED] Upgrade hangs with "Setting up pve-manager (9.0.17) ..."

[Zoker]

Hi there,

Today I ran a update, which does not seem to be sucessfully. Everytime I try to upgrade, the process hangs at the

root@jupiter:~# dpkg --configure -a
Setting up pve-manager (9.0.17) ...

I tried to wait for an hour, but nothing happens. I rebooted and tried to update/upgrade, but it tells me that there is a upgrade running:

root@jupiter:~# apt update
Hit:1 http://download.proxmox.com/debian/pve trixie InRelease
Hit:2 http://security.debian.org trixie-security InRelease
Hit:3 http://ftp.de.debian.org/debian trixie InRelease
Hit:4 http://ftp.de.debian.org/debian trixie-updates InRelease
All packages are up to date.
root@jupiter:~# apt upgrade
Error: dpkg was interrupted, you must manually run 'dpkg --configure -a' to correct the problem.

Here is the full output of ps faxl:
https://gist.github.com/TheZoker/9d6f534b02f69ee920b63e44cf10d4ff

When I access the UI, it tells me that it is already using 9.0.17:


Now my question is how can I solve this?
Is there any way to run the upgrade again?

I run the same upgrade on a second device before and it worked without issues....

Thanks!

 

[Zoker]

Ok after some more investigation I was able to fix it by running these commands:

kill -9 13337
kill -9 11328
rm /var/lib/dpkg/lock-frontend
rm /var/lib/dpkg/lock
dpkg --configure -a

After that the updates went through

 

[Onslow]

Hi, @Zoker!
Would you mind writing what, exactly, were these 13337 and 11328 processes?
It can be helpful for other users in future.

 

[Zoker]

Hi @Onslow

Yes sure, so here is a list of the relevant processes on my system:

root@jupiter:~# ps auxf | grep -A 5 dpkg
root       11328  0.0  0.0  11988  6264 pts/0    T    15:05   0:00              \_ dpkg --configure -a
root       11375  0.0  0.0   2688  1912 pts/0    T    15:05   0:00              |   \_ /bin/sh /var/lib/dpkg/info/pve-manager.postinst configure 9.0.15
root       13337  0.0  0.0  21368  8160 pts/0    T    15:05   0:00              |       \_ systemctl reload-or-restart pvescheduler.service
root       13339  0.0  0.0  17856  6708 pts/0    T    15:05   0:00              |           \_ /usr/bin/systemd-tty-ask-password-agent --watch
root       71531  0.0  0.0  11016  5844 pts/0    R+   15:16   0:00              \_ ps auxf
root       71532  0.0  0.0   6536  2392 pts/0    S+   15:16   0:00              \_ grep -A 5 dpkg
root        1127  0.0  0.0  43992  4764 ?        Ss   15:04   0:00 /usr/lib/postfix/sbin/master -w
postfix     1128  0.0  0.0  44500  7516 ?        S    15:04   0:00  \_ pickup -l -t unix -u -c
postfix     1129  0.0  0.0  44520  7692 ?        S    15:04   0:00  \_ qmgr -l -t unix -u
root        1136  1.2  0.5 572132 179652 ?       SLsl 15:04   0:09 /usr/sbin/corosync -f
root        1137  0.0  0.0  13808  6480 ?        Ss   15:04   0:00 /usr/libexec/proxmox/proxmox-firewall start
root@jupiter:~#

So the relevant processes are

root       11328  0.0  0.0  11988  6264 pts/0    T    15:05   0:00              \_ dpkg --configure -a
root       13337  0.0  0.0  21368  8160 pts/0    T    15:05   0:00              |       \_ systemctl reload-or-restart pvescheduler.service

After killing them, the upgrade was successful[/code]