[SOLVED] Error during update: "pve-manager"

[AngryAdm]

Hi there,

Whenever I do a clean install of proxmox 6.2-1 from the downloadable ISO and subsequently run apt-get update/apt-get upgrade I get the following error and was wondering if that is a problem or not. I usually run apt-get dist-upgrade to get to 6.2-11 afterwards

Setting up pve-manager (6.2-11) ...
Job for pvedaemon.service failed.
See "systemctl status pvedaemon.service" and "journalctl -xe" for details.
dpkg: error processing package pve-manager (--configure):
 installed pve-manager package post-installation script subprocess returned error exit status 1

And abit later:

Updating certificates in /etc/ssl/certs...
0 added, 0 removed; done.
Running hooks in /etc/ca-certificates/update.d...
done.
Processing triggers for pve-ha-manager (3.1-1) ...
Errors were encountered while processing:
 pve-manager
E: Sub-process /usr/bin/dpkg returned an error code (1)

 

[oguz]

hi,

See "systemctl status pvedaemon.service" and "journalctl -xe" for details.

what does journalctl -xe say? obviously something is going wrong during the installation of the package

 

[AngryAdm]

....
Setting up pve-ha-manager (3.1-1) ...
Job for pve-ha-lrm.service failed because the control process exited with error code.
See "systemctl status pve-ha-lrm.service" and "journalctl -xe" for details.
Job for pve-ha-crm.service failed because the control process exited with error code.
See "systemctl status pve-ha-crm.service" and "journalctl -xe" for details.
Setting up pve-container (3.2-1) ...
system-pve\x2dcontainer.slice is a disabled or a static unit, not starting it.
Setting up pve-manager (6.2-11) ...
Job for pvedaemon.service failed.
See "systemctl status pvedaemon.service" and "journalctl -xe" for details.
dpkg: error processing package pve-manager (--configure):
installed pve-manager package post-installation script subprocess returned error exit status 1
Processing triggers for systemd (241-7~deb10u4) ...
Processing triggers for man-db (2.8.5-2) ...
Processing triggers for mime-support (3.62) ...
Processing triggers for initramfs-tools (0.133+deb10u1) ...
update-initramfs: Generating /boot/initrd.img-5.4.34-1-pve
Running hook script 'zz-pve-efiboot'..
Re-executing '/etc/kernel/postinst.d/zz-pve-efiboot' in new private mount namespace..
No /etc/kernel/pve-efiboot-uuids found, skipping ESP sync.
Processing triggers for libc-bin (2.28-10) ...
Processing triggers for rsyslog (8.1901.0-1) ...
Processing triggers for ca-certificates (20200601~deb10u1) ...
Updating certificates in /etc/ssl/certs...
0 added, 0 removed; done.
Running hooks in /etc/ca-certificates/update.d...
done.
Processing triggers for pve-ha-manager (3.1-1) ...
Errors were encountered while processing:
pve-manager
E: Sub-process /usr/bin/dpkg returned an error code (1)[/CODE]

 

[AngryAdm]

I forgot to note that I had joined the node to a cluster immediately after installation and before the update/upgrade command was issued

 

[oguz]

you haven't posted the journalctl output.


on a hunch i would check the /etc/hosts file to see if it contains an entry with 127.0.1.1 and if yes remove that line

 

[AngryAdm]

I rebooted the system already, I am not sure it is still in the output :/ However, I attached what is presently output by journalctl -xe

 

[oguz]

thanks, i couldn't see anything interesting in the output - maybe you can re-run the update and send it again?

also see if this applies to your case:

on a hunch i would check the /etc/hosts file to see if it contains an entry with 127.0.1.1 and if yes remove that line

when you run hostname --ip-address you should see the public IP of the PVE host (or the internal IP, however you access it)

 

[AngryAdm]

I will create a virtual server and install proxmox from iso again. It will cause the same error message. It has done so on every host I have installed so far. I suspect it is because I have joined the server to a cluster prior to the update.

I will try not to join the server to a cluster and see what I get. Give me 30 minuttes as I am doing a few other tasks.

 

[AngryAdm]

In Denmark 30 minuttes are fast

reproduction steps:
Download ISO
Install Proxmox 6.2-1
Add proxmox non-sub apt source
apt-get update
apt-get upgrade

 

[oguz]

firstly please remove the enterprise repository since it seems you're using no-subscription repository

Install Proxmox 6.2-1

could you explain the options you're choosing during the install? is it all default?

apt-get upgrade

try apt dist-upgrade instead

and please check /etc/hosts file, see my previous posts

 

[AngryAdm]

firstly please remove the enterprise repository since it seems you're using no-subscription repository



could you explain the options you're choosing during the install? is it all default?


try apt dist-upgrade instead

and please check /etc/hosts file, see my previous posts

They are all default options indeed apart from hostname, email etc.

127.0.0.1 localhost.localdomain localhost
10.0.0.223 pvetest.winwinsol.local pvetest

# The following lines are desirable for IPv6 capable hosts

::1     ip6-localhost ip6-loopback
fe00::0 ip6-localnet
ff00::0 ip6-mcastprefix
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters
ff02::3 ip6-allhosts

dist-upgrade yields no errors. pve-manager installs correctly.

 

[oguz]

dist-upgrade yields no errors. pve-manager installs correctly.

so it worked? can you check pveversion -v to make sure?

 

[AngryAdm]

Yes, it worked with dist-upgrade

 

[oguz]

great. please mark the thread as [SOLVED] so others know what to expect

 

[wawa_marek]

could you explain the options you're choosing during the install? is it all default?


try apt dist-upgrade instead

and please check /etc/hosts file, see my previous posts

I had the same issue, just after upgrading new, fresh node. I spent whole day to find a solution, finally it was simple. Thank you.

 

[cyberspace-cat]

Just an FYI for anyone reading this via google, I had the same issue, and as oguz said apt-get dist-upgrade did the trick.

More details on my issue and steps:

• apt-get update then apt-get upgrade, failed at pve-manager like OP.
• NoVNC was failing
• Multiple reboots
• apt-get upgrade again without pve-manager error
• Still failed NoVNC
• Saw various pve services were failing
• Added internal IP to /etc/hosts and ran apt-get dist-upgrade
• Rebooted and works

 

[tom]

apt-get update then apt-get upgrade

Never do this, it will always break Proxmox VE - please read the upgrade docs and/or just use the GUI updater.

=> https://pve.proxmox.com/pve-docs/pve-admin-guide.html#_system_software_updates

 

[1nspy]

I was stuck with this.

apt dist-upgrade

did the trick.

Thank you guys