Search results

We run the same hardware, Proxmox 6.x, today we had also a crash. Hetzner did offer to update the BIOS. Its not the first crash tho, will see how it goes.

Sorry for the late reply. The Ubuntu USN's are exactly my problem. The changelog will only appear 3-5 days later when Proxmox already has patched the kernel. Is there any way you could inform us prior, that a security update for the kernel is on the way?

Hey, Current method is, to watch the ubuntu update/security notifications and take actions when a security update which is relevant has been dropped. But the current method sucks balls. The current issue is, the latest Proxmox Kernel is from 15th February, while Ubuntu dropped notifications 3...

Well, everything worked fine, until I restarted to many nodes at the same time. Why should that be tinc's fault? Everything worked before. I reboot a node, it fails back into not enough quonum state until i manually fix it by restarting the services. Well, these are based in 3 different data...

Hey, It seems like it was a bad timing, I always made sure I just reboot one node and wait until its back. Running these commands seems to fixed the issue: service pve-cluster restart systemctl restart corosync However, when I reboot a single node, the node runs into the same issue again...

Hey, I did configured a 3 Node cluster over tinc, about 10ms between the nodes. So after I rebooted the nodes to apply changes, the cluster broke up, into 3 nodes in Standalone mode. I attached screenshots, so you can take a look. Afterwards, I tried to check the status with: pvecm status It...

The Webinterface runs local as it should be, since I use a reverse proxy.

Any Update?

Here you go: I also tried to disable the spiceproxy since I dont need it but your guide to remove it from the autostart did not work anymore. Yeah and I took a look at the manuals but it does not really help.

No idea?

I missed to mention that I mean the current stable release.

Hey, Since some updates it seems like pveproxy seems to ignore the localhost setting. I could reproduce that on 3 nodes running the newest Proxmox version. It does only accept Localhost connections but it does listen on all devices, which was not the case before. Before It did only accept...