[SOLVED] Sparkly new install, packages report as "not correctly installed"

[HiltonT]

G'day All,

I performed a fresh install of Proxmox 6.2-4 yesterday and when clicking on the node, then Summary, then "Package versions" I see a lot of the following errors:

<package_name>: not correctly installed

I performed an update, now at 6.2-9, and these incorrectly installed package reports still persist.

Any idea why on a fresh install we have so many packages being reported as not correctly installed?

proxmox-ve: 6.2-1 (running kernel: 5.4.34-1-pve)
pve-manager: not correctly installed (running version: 6.2-9/4d363c5b)
pve-kernel-5.4.34-1-pve: 5.4.34-2
ceph-fuse: 12.2.11+dfsg1-2.1+b1
corosync: not correctly installed
criu: 3.11-3
glusterfs-client: 5.5-3
ifupdown: 0.8.35+pve1
ksm-control-daemon: 1.3-1
libjs-extjs: 6.0.1-10
libknet1: not correctly installed
libproxmox-acme-perl: not correctly installed
libpve-access-control: not correctly installed
libpve-apiclient-perl: 3.0-3
libpve-common-perl: not correctly installed
libpve-guest-common-perl: not correctly installed
libpve-http-server-perl: not correctly installed
libpve-storage-perl: not correctly installed
libqb0: 1.0.5-1
libspice-server1: 0.14.2-4~pve6+1
lvm2: 2.03.02-pve4 lxc-pve: 4.0.2-
lxcfs: not correctly installed
novnc-pve: 1.1.0-1
proxmox-mini-journalreader: 1.1-1
proxmox-widget-toolkit: not correctly installed
pve-cluster: 6.1-8
pve-container: not correctly installed
pve-docs: 6.2-4
pve-edk2-firmware: not correctly installed
pve-firewall: 4.1-2
pve-firmware: 3.1-1
pve-ha-manager: not correctly installed
pve-i18n: not correctly installed
pve-qemu-kvm: not correctly installed
pve-xtermjs: 4.3.0-1
qemu-server: not correctly installed
smartmontools: 7.1-pve2
spiceterm: 3.1-1
vncterm: 1.6-1
zfsutils-linux: not correctly installed

 

[tom]

I performed a fresh install of Proxmox 6.2-4 yesterday

How, via ISO install?

Please post the full output of:

> apt update
> apt install proxmox-ve

 

[HiltonT]

Install via the ISO from the Proxmox download page, then an update yesterday morning using the web interface.

Now I see the following errors on the console of the Dell R510 I have this installed on, and can no longer log in through the web interface. I get the login prompt, but it doesn't progress to the 2FA request and errors out, reporting that the PVE services aren't running...

[timestamp] INFO task vgs:20945 blocked for more than 120 seconds.
[timestamp] Tainted: P IOE 5.4.34-1-pve #1
"echo 0 > /proc sys/kernel/hung_task_timeout_secs" disables this message.
...
[timestamp] INFO task vgs:20945 blocked for more than 1208 seconds.
[timestamp] Tainted: P IOE 5.4.34-1-pve #1
"echo 0 > /proc sys/kernel/hung_task_timeout_secs" disables this message.

When trying to reboot this (C-A-D issued over iDRAC) it starts to reboot, then I get:
(1 of 2) A stop job is running for PVE API Daemon (time counter increasing past 6 minutes)
(1 of 2) A stop job is running for PVE Status Daemon (time counter increasing past 6 minutes)
...
A stop job is running for Monitoring of LVM2 mirrors, snapshots etc. using dmeventd or progress polling (over 13 minutes - I gave up at this point and warm booted the machine through iDRAC)

Right now I have nothing running on it aside from a test Win 10 VM, so I can completely blow it away again and reinstall if needed - especially if an updated ISO can be built - the system has been successfully running Windows Server 2019 and Hyper-V with a few guests on it for many years (prior to that Server 2016, prior to that Server 2008 R2) and iDRAC shows no system hardware faults at all. I have a USB HDD attached that is reporting a SMART predicted failure, but that shouldn't be causing any of these issues I'm seeing in Proxmox.

root@pve:~# apt-get update
Hit:1 http://security.debian.org buster/updates InRelease
Hit:2 http://ftp.au.debian.org/debian buster InRelease
Hit:3 http://ftp.au.debian.org/debian buster-updates InRelease
Err:4 https://enterprise.proxmox.com/debian/pve buster InRelease
401 Unauthorized [IP: 51.91.38.34 443]
Reading package lists... Done
E: Failed to fetch https://enterprise.proxmox.com/debian/pve/dists/buster/InRelease 401 Unauthorized [IP: 51.91.38.34 443]
E: The repository 'https://enterprise.proxmox.com/debian/pve buster InRelease' is not signed.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.
N: See apt-secure(8) manpage for repository creation and user configuration details.

root@pve:~# apt install proxmox-ve
E: dpkg was interrupted, you must manually run 'dpkg --configure -a' to correct the problem.

root@pve:~# dpkg --configure -a
Setting up libvotequorum8:amd64 (3.0.4-pve1) ...
Setting up libcpg4:amd64 (3.0.4-pve1) ...
Setting up libcmap4:amd64 (3.0.4-pve1) ...
Setting up libquorum5:amd64 (3.0.4-pve1) ...
Setting up pve-kernel-5.4.44-2-pve (5.4.44-2) ...
Examining /etc/kernel/postinst.d.
run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 5.4.44-2-pve /boot/vmlinuz-5.4.44-2-pve
run-parts: executing /etc/kernel/postinst.d/initramfs-tools 5.4.44-2-pve /boot/vmlinuz-5.4.44-2-pve
update-initramfs: Generating /boot/initrd.img-5.4.44-2-pve
run-parts: executing /etc/kernel/postinst.d/pve-auto-removal 5.4.44-2-pve /boot/vmlinuz-5.4.44-2-pve
run-parts: executing /etc/kernel/postinst.d/zz-pve-efiboot 5.4.44-2-pve /boot/vmlinuz-5.4.44-2-pve
Re-executing '/etc/kernel/postinst.d/zz-pve-efiboot' in new private mount namespace..
No /etc/kernel/pve-efiboot-uuids found, skipping ESP sync.
run-parts: executing /etc/kernel/postinst.d/zz-update-grub 5.4.44-2-pve /boot/vmlinuz-5.4.44-2-pve
Generating grub configuration file ...
/dev/sdf: open failed: No medium found
Found linux image: /boot/vmlinuz-5.4.44-2-pve
Found initrd image: /boot/initrd.img-5.4.44-2-pve
/dev/sdf: open failed: No medium found
Found linux image: /boot/vmlinuz-5.4.34-1-pve
Found initrd image: /boot/initrd.img-5.4.34-1-pve
/dev/sdf: open failed: No medium found
Found memtest86+ image: /boot/memtest86+.bin
Found memtest86+ multiboot image: /boot/memtest86+_multiboot.bin
done
Setting up pve-i18n (2.1-3) ...
Setting up libcfg7:amd64 (3.0.4-pve1) ...
Setting up libnvpair1linux (0.8.4-pve1) ...
Setting up pve-edk2-firmware (2.20200531-1) ...
Setting up pve-kernel-5.4 (6.2-4) ...
Setting up libproxmox-backup-qemu0 (0.6.1-1) ...
Setting up corosync (3.0.4-pve1) ...
Setting up libzfs2linux (0.8.4-pve1) ...
Setting up pve-qemu-kvm (5.0.0-9) ...
Setting up libzpool2linux (0.8.4-pve1) ...
Setting up zfsutils-linux (0.8.4-pve1) ...
Installing new version of config file /etc/zfs/zfs-functions ...
zfs-import-scan.service is a disabled or a static unit not running, not starting it.
Setting up zfs-initramfs (0.8.4-pve1) ...
Setting up zfs-zed (0.8.4-pve1) ...
Setting up libproxmox-acme-perl (1.0.4) ...
Setting up libpve-common-perl (6.1-5) ...
Setting up libpve-storage-perl (6.2-3) ...
Setting up libpve-access-control (6.1-2) ...
Setting up libpve-http-server-perl (3.0-6) ...
Setting up libpve-guest-common-perl (3.0-11) ...
Setting up pve-container (3.1-10) ...
system-pve\x2dcontainer.slice is a disabled or a static unit, not starting it.
Setting up qemu-server (6.2-8) ...
Setting up pve-manager (6.2-9) ...
Processing triggers for systemd (241-7~deb10u4) ...
Processing triggers for man-db (2.8.5-2) ...
Processing triggers for pve-ha-manager (3.0-9) ...
Processing triggers for mime-support (3.62) ...
Processing triggers for initramfs-tools (0.133+deb10u1) ...
update-initramfs: Generating /boot/initrd.img-5.4.44-2-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) ...

root@pve:~# apt install proxmox-ve
Reading package lists... Done
Building dependency tree
Reading state information... Done
proxmox-ve is already the newest version (6.2-1).
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

(Reboot, check again...)

Not getting the long hang times as reported above...

...and that cleaned up the errors I initially reported. Looks like at some point during the initial update it crashed and didn't complete.

I have a feeling this was related to the other reported bug in 6.2-4 that I was seeing where the web interface was logging people out all over the shop (which is now fixed in 6.2-9).

Thanks for the pointer - it is something I will keep an eye on in the future...

 

[Stoiko Ivanov]

Err:4 https://enterprise.proxmox.com/debian/pve buster InRelease
401 Unauthorized [IP: 51.91.38.34 443]
Reading package lists... Done
E: Failed to fetch https://enterprise.proxmox.com/debian/pve/dists/buster/InRelease 401 Unauthorized [IP: 51.91.38.34 443]

It seems your repository configuration is not quite right:
* either purchase a subscription to access the enterprise repository
* or configure the no-subscription repository - see:
https://pve.proxmox.com/pve-docs/pve-admin-guide.html#sysadmin_package_repositories

I hope this helps!

 

[HiltonT]

Aahhh, I've just done a reinstall and will be reconfiguring (at least for now) with the no-subscription repository. Re-running through the setup as I'm not a fan of a fresh install that I borked somehow, then fixed, then put into production.

 

[Stoiko Ivanov]

Glad that worked - thanks for marking the thread as 'SOLVED'

 

[HiltonT]

(Found another issue - after the rebuild - so will start another issue as it may not be related...)