Recent content by rdfeij

I got the same problem on my 1 node cluster. (It was 2 node when migrating to new hardware. I got it fixed, it seems that the problem is that there was no quorum for HA. After a reboot, local login again and start dpkg --configure -a it got stuck again. Via shell i ran pvecm expect 1 and the...

Just to add some information, just encountered the same. Solved by removing the extra empty line. It seems to have started from last run update to version pve-manager/8.4.10. The file was never knowlingly changed since a few years. I do notice some files in /etc/network were changed during the...

ethtool still solves it with kernel 6.8.12-9 (with me) but sometimes i have to change to rx-usecs 1 in stead of 0 to get it fixed. Then it stays fixed (can change it to 0 and 1) till next reboot filtering on the messages still fills up the /var/log/kern.log rapidly filling valuable SSD space...

https://bugzilla.proxmox.com/show_bug.cgi?id=5610

I'm sorry, dug into the issue deeper since it was some time ago, users are still in the groups but do not exist as user anymore. So problem is still there. I will report a bug

There is a sync job active running every 2 hours, shouldn't that have done the same?

Fixed by enabling 'Remove vanished properties from synced users'. It was disabled. I expected that Entry: Remove vanished users and group entries would be enough. Is this stil a bug then or did i misinterpret these functions?

Anyone?

Within our proxmox cluster we have an Active directory sync only used for login of our users (no OU assignments to automate grouprights). One of our users has been remove from the OU allowing him to login to Proxmox so the sync removed his username. However the user is still in the usergroup he...

Hi Fiona, You are correct, if i map the TPM disk first by shell the VM starts normally. Shutting it down again (it unmaps automatically) and start it again fails it again. But only on this node it works on 4 other nodes.

This was during a fresh start. VM shutdown, moved to faulty node and started again. Right after start it failed, HA tried again (same error) and then HA migrated/moved it (offline) to a non-faulty node where it started normally. The requested output bothers me, i get errors while running the...

task started by HA resource agent /dev/rbd0 TPM2_EvictControl failed: 0x14c create_ek failed: 0x1 An error occurred. Authoring the TPM state failed. swtpm_setup: Starting vTPM manufacturing as root:root @ Thu 15 Feb 2024 04:09:38 PM CET swtpm_setup: TPM is listening on Unix socket. swtpm_setup...

Not working host: proxmox-ve: 8.1.0 (running kernel: 6.5.11-8-pve) pve-manager: 8.1.4 (running version: 8.1.4/ec5affc9e41f1d79) proxmox-kernel-helper: 8.1.0 pve-kernel-5.15: 7.4-9 proxmox-kernel-6.5: 6.5.11-8 proxmox-kernel-6.5.11-8-pve-signed: 6.5.11-8 proxmox-kernel-6.5.11-7-pve-signed...

Same problem running TPM from Ceph after cloning(full) from template. moved TPM to nfs share and VM starts normally. Moved back to ceph, again failure. Moved VM to another host and now it is working with TPM on ceph.. could there be any underlying hardware issue?

@VictorSTS This issue has to be brought back to a misconfigurement within FRR, although we tested and checked many times after rebuilding the FRR config it is now working. Thank you for your help.