[SOLVED] New install errors 10 to 15 minutes after boot

truwrecks

New Member
Jan 22, 2024
3
0
1
I think something is seriously wrong with my PROXMOX install.
It will work fine for 10 to 15 minutes after I boot the system up. After about 15 minutes I start getting "Parameter verification failed. (400) poolid: property is not defined in schema and the schema does not allow additional properties" errors when I try to configure almost anything. I see that when editing users, LCX resources on LCX hosts that are off, storage pool resources, groups, and more. I have to reboot the entire server to get it working correctly again.

This is a pretty vanilla PVE 8.1 install. Running on an HPE DL325 with a 16 core EPYC and 336 GB DDR4 ECC. It has plenty of resources to run PVE.

Please help. I can't find any solutions anywhere online for these issues. There has to be something causing it that I am overlooking.

Code:
root@pve:~# pveversion --verbose
proxmox-ve: 8.1.0 (running kernel: 6.5.11-4-pve)
pve-manager: 8.1.4 (running version: 8.1.4/ec5affc9e41f1d79)
proxmox-kernel-helper: 8.1.0
proxmox-kernel-6.5: 6.5.11-7
proxmox-kernel-6.5.11-7-pve-signed: 6.5.11-7
proxmox-kernel-6.5.11-4-pve-signed: 6.5.11-4
ceph-fuse: 17.2.7-pve1
corosync: 3.1.7-pve3
criu: 3.17.1-2
glusterfs-client: 10.3-5
ifupdown2: 3.2.0-1+pmx8
ksm-control-daemon: 1.4-1
libjs-extjs: 7.0.0-4
libknet1: 1.28-pve1
libproxmox-acme-perl: 1.5.0
libproxmox-backup-qemu0: 1.4.1
libproxmox-rs-perl: 0.3.3
libpve-access-control: 8.0.7
libpve-apiclient-perl: 3.3.1
libpve-common-perl: 8.1.0
libpve-guest-common-perl: 5.0.6
libpve-http-server-perl: 5.0.5
libpve-network-perl: 0.9.5
libpve-rs-perl: 0.8.8
libpve-storage-perl: 8.0.5
libspice-server1: 0.15.1-1
lvm2: 2.03.16-2
lxc-pve: 5.0.2-4
lxcfs: 5.0.3-pve4
novnc-pve: 1.4.0-3
proxmox-backup-client: 3.1.2-1
proxmox-backup-file-restore: 3.1.2-1
proxmox-kernel-helper: 8.1.0
proxmox-mail-forward: 0.2.3
proxmox-mini-journalreader: 1.4.0
proxmox-offline-mirror-helper: 0.6.4
proxmox-widget-toolkit: 4.1.3
pve-cluster: 8.0.5
pve-container: 5.0.8
pve-docs: 8.1.3
pve-edk2-firmware: 4.2023.08-3
pve-firewall: 5.0.3
pve-firmware: 3.9-1
pve-ha-manager: 4.0.3
pve-i18n: 3.2.0
pve-qemu-kvm: 8.1.2-6
pve-xtermjs: 5.3.0-3
qemu-server: 8.0.10
smartmontools: 7.3-pve1
spiceterm: 3.3.0
swtpm: 0.8.0+pve1
vncterm: 1.8.0
zfsutils-linux: 2.2.2-pve1

Disks:
root@pve:~# lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
loop0 7:0 0 20G 0 loop
sda 8:0 0 5.5T 0 disk
└─sda1 8:1 0 5.5T 0 part /mnt/TNT
sdb 8:16 0 232.9G 0 disk
├─sdb1 8:17 0 1007K 0 part
├─sdb2 8:18 0 1G 0 part /boot/efi
└─sdb3 8:19 0 231.9G 0 part
├─pve-swap 252:0 0 8G 0 lvm [SWAP]
├─pve-root 252:1 0 68G 0 lvm /
├─pve-data_tmeta 252:2 0 1.4G 0 lvm
│ └─pve-data 252:4 0 137.1G 0 lvm
└─pve-data_tdata 252:3 0 137.1G 0 lvm
└─pve-data 252:4 0 137.1G 0 lvm
nvme0n1 259:0 0 232.9G 0 disk

The path /mnt/TNT at /dev/sda1 is a SSD RAID array that is holding the VMs and Containers for this system. It is owned by this host. It was imported from different Debian 12 server. This should not be an issue since I get the errors with and without this disk mounted.

Thank you.
 
Hi,
you can verify the integrity of the installed packages with apt install debsums && debsums -s. Might take a while and no output means "all good".

You can also try to look for files where the poolid property is mentioned, e.g. find /etc/pve -type f -exec grep poolid {} \;.

I'd do both commands before and after the issue starts happening.
 
Running the first command did result in a few packages being installed.

Code:
root@pve:~# apt install debsums && debsums -s
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following additional packages will be installed:
  libdpkg-perl libfile-fcntllock-perl libfile-fnmatch-perl
Suggested packages:
  debian-keyring gcc | c-compiler patch git bzr
The following NEW packages will be installed:
  debsums libdpkg-perl libfile-fcntllock-perl libfile-fnmatch-perl
0 upgraded, 4 newly installed, 0 to remove and 0 not upgraded.
Need to get 684 kB of archives.
After this operation, 2,311 kB of additional disk space will be used.
Do you want to continue? [Y/n] y
Get:1 http://ftp.us.debian.org/debian bookworm/main amd64 libdpkg-perl all 1.21.22 [603 kB]
Get:2 http://ftp.us.debian.org/debian bookworm/main amd64 libfile-fnmatch-perl amd64 0.02-3+b1 [10.2 kB]
Get:3 http://ftp.us.debian.org/debian bookworm/main amd64 debsums all 3.0.2.1 [35.5 kB]
Get:4 http://ftp.us.debian.org/debian bookworm/main amd64 libfile-fcntllock-perl amd64 0.22-4+b1 [34.8 kB]
Fetched 684 kB in 1s (578 kB/s)                   
Selecting previously unselected package libdpkg-perl.
(Reading database ... 53022 files and directories currently installed.)
Preparing to unpack .../libdpkg-perl_1.21.22_all.deb ...
Unpacking libdpkg-perl (1.21.22) ...
Selecting previously unselected package libfile-fnmatch-perl.
Preparing to unpack .../libfile-fnmatch-perl_0.02-3+b1_amd64.deb ...
Unpacking libfile-fnmatch-perl (0.02-3+b1) ...
Selecting previously unselected package debsums.
Preparing to unpack .../debsums_3.0.2.1_all.deb ...
Unpacking debsums (3.0.2.1) ...
Selecting previously unselected package libfile-fcntllock-perl.
Preparing to unpack .../libfile-fcntllock-perl_0.22-4+b1_amd64.deb ...
Unpacking libfile-fcntllock-perl (0.22-4+b1) ...
Setting up libfile-fcntllock-perl (0.22-4+b1) ...
Setting up libdpkg-perl (1.21.22) ...
Setting up libfile-fnmatch-perl (0.02-3+b1) ...
Setting up debsums (3.0.2.1) ...
Processing triggers for man-db (2.11.2-2) ...
root@pve:~#

I am going to try everything that was causing errors before to see if there is any difference.

Thank you very much. This has been a very frustrating issue.

-Tru
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!