Recent content by Darkk

I went ahead and rebooted the nodes which seems to fix the issue. From the looks of it you're right that it was running the old packages which I wasn't able to pkill it. Reboot took care of that.

Looks like the pveproxy worker (three daemons) are running at 100% of CPU all the time. I don't think this is normal?

Hello, After fixing the broken WebGUI this morning via new updated packages. Now I've noticed on all of my PVE nodes that the CPU usage have increased a great deal. Each node's CPU are bit different which consists of Intel Xeon, Intel i7 and AMD Ryzen 9 5950X. My wife noticed the CPU fans...

Yep, it died again. I too am using HAProxy to reach the WebGUI servers. Guess I will remote into it via SSH and do the updates and fixes. EDIT: The updated packages fixed the issue.

Yep, it broke the WebGUI on my three nodes this morning after the update. I had to reboot them and it came back up ok.

After a botched ZFS rpool mirror-1 replacement it somehow converted itself to a full ZFS raid-0 on that same pool. I've tried different ways in fixing it but at the end it now makes sense just move the VMs and replication off of that node and rebuild it using new node name and IPs. I've read...

Might be an issue with the target storage path. Try manually change the storage location for restore and see what happens.

I wonder if ProxMox Datacenter Management can do this for you as it doesn't need to be in a cluster?

What version of PBS are you running? I am using PBS version 3.3.2 and all of my PVE7 nodes are running 7.4-19. So far the backups and restores are still working. I just did a test restore this morning and it's working fine. I have plans to upgrade my PVE7 nodes to PVE8 soon.

Yes, that's another way of doing it. I'd probably would use a VM or LXC Debian container with acme.sh script and add it to push the new ssl cert to the PVE hosts. I try not to add anything extra to the PVE hosts as it could break something during upgrades / updates.

Seems this wildcard SSL for ACME still not available. The biggest reason for this is to hide my internal infrastructure from the internet. Granted my hosts aren't exposed to the internet but every time you generate a new Let's Encrypt Certificate it gets published for everyone to see. This...

Might be something to do with the MTU on Wireguard. Wireguard generally don't have any restrictions on bandwidth. Wireguard will use much bandwidth as you give it. Sometimes ISPs mangle the MTUs on their network which result in poor performance. Some protocols are sensitive to that.

What does SMART values on the drive say?

The riscv64 emulation in ProxMox would be flippin cool as Risc-V is gaining steam in development. It won't take over ARM or x86 anytime soon but over time it might.

I too been stung by this. From what I understand Debian won't do this again for a long time. To me it's better to let the changes happen and then fix the interfaces so they start working again using the new naming scheme. Lucky for me at work I use iDrac9 so it's easy to go in and fix the...