Can't Upgrade? 'dpkg --configure -a'

[abcrate]

Trying to go from 0.1.8 to 0.1.10, haven't checked PDM in about a week or so.

When trying to upgrade via GUI or apt full-upgrade I get this error - E: dpkg was interrupted, you must manually run 'dpkg --configure -a' to correct the problem.
On running dpkg --configure -a the shell will close itself with this message - proxmox-datacenter-manager-daily-update.service is a disabled or a static unit not running, not starting it.

Anyone else experience this issue? Maybe a PDM issue or just a basic Linux thing that has a common workaround?

Many thanks


SOLVED: run dpkg --configure -a via direct access to the VM/host.

 

[dixie2000]

I have the same issue, have not found a solution as yet.

 

[tom]

Please do update via the integrated console, use ssh (or the host directly).

The issue should be fixed with one of the next update round.

 

[dixie2000]

Tried doing the upgrade using the console as well as ssh'ing into the VM, same error.

 

[abcrate]

Same here, I get the same error regardless of shell access method and it closes the session on me

 

[_--James--_]

We have to console to the PDM VM/server and run dpkg --configure -a and then apt upgrade for the upgrade from 0.1.8 to 0.1.10 to work. If we SSH/WebConsole or use the WebUpgrade option the --configure fails because the console PID is dropped during man-db and libc-bin processing, failing the pre-reqs for apt upgrade to work.

Here is what the successful process from the PDM console looks like - Highlighted where SSH/WebShell/WebUpgrades are failing.

 

[abcrate]

This worked, thank you! I thought I had tried this already but I guess I must not have.
It's almost too obvious.. haha

 

[_--James--_]

This worked, thank you! I thought I had tried this already but I guess I must not have.
It's almost too obvious.. haha

Oh no worries, I was hitting my head against this one for a few days (0.1.9 failed too, same error) then I found this thread with the maintainer saying to use console and i was like 'I wonder...' Boom upgraded!

Funny enough 0.1.7 to 0.1.8 worked normally no issue, so something broke with dpkg on 1.0.8.