Ok, so after a little digging around, my Proxmox Firewall service was reporting the below:
May 18 16:17:11 pve02 proxmox-firewall[5138]: error updating firewall rules: cannot execute nftables commands
May 18 16:17:16 pve02...
Seems quite long to me but it obviously depends on the slowest shutdown in the chain.
Did you already look into the shutdown time of each separate VM/LXC/host?
Hi das passiert eigentlich nur wenn man Spice aktiviert hat und keinen Viewer auf dem Client installiert.
Sonst einfach NoVNC auswählen, das kann jeder Browser.
Follow up. So I noticed an update to the kernel 7 to 7.0.2-2-pve, so I tried it on my PBS with the enterprise subscription (HP, gen 11). It's newer hardware so I figured it might be OK. And it has been fine. So I might try the newer kernel on...
From the top of my head:
you need to configure your SSH client (/root/.ssh/config) as well and set special entries for the IP and the hostname of your other nodes, e.g.
Host proxmox1 proxmox2 proxmox3
Port 2222
node1
May 18 09:28:13 nmz-cl-1 systemd[1]: Stopping pve-ha-lrm.service - PVE Local HA Resource Manager Daemon...
May 18 09:28:14 nmz-cl-1 pve-ha-lrm[754284]: received signal TERM
May 18 09:28:14 nmz-cl-1 pve-ha-lrm[754284]: got shutdown request...
It does look like a false-positive to me.
The file that gets flagged is the statically linked init executable of LXC (/usr/bin/init.lxc.static), which can probably trip up some scanners. Unfortunately, there are no details other than "something...
PVE7 is based on Debian 11/bullseye, PVE8 on 12/bookworm and PVE9 on 13/trixie.
It seems all 3 repositories you need are still available for both Proxmox and Debian:
http://download.proxmox.com/debian/pve/dists/...
Hi,
After all of the CVE's and security disclosures over the past week or two, I thought it'd be useful to upgrade my Proxmox nodes to the latest. I recently updated everything to PVE 9 & Ceph 19 and it has been working without fault for a few...
I have taken a look at the provided log, the log does not show any kernel panic, OOM, or thermal event logged.
I would suggest to double check iDRAC/IPMI logs for evidence of hardware reset or power event.
I removed the nvme device, disconnected cd drive, front usb, front card reader etc. then disabled tpm setting (I think that's what it was) in bios. Then problem solved.
So nodes upgraded and rebooted, still seems to be a problem. I've cross checked the configurations across all nodes and Host > Firewall settings are exactly the same. I've run iptables -L and they are all empty.
Um mal zum Thema zurückzukommen: ich würde als erstes ein BIOS-Update machen (gibt ein neues aus 03/2026) und danach die Defaultwerte setzen. Dann alles durchschauen, ob irgendwo eine Einstellung ist, die Probleme machen könnte.
Bitte vorher...