Recent content by jamesharr

A couple updates... - I can confirm what @tkell said, CertiNext seems to be working now. I tested on Proxmox-VE 9.2.3 and 8.4.19 - I contacted support a while ago and they have a patch in the works that will (eventually) make its way into the build: https://lore.proxmox.com/pve-devel/?q=5978

We're running into this issue when using CertiNext. @Foorack's patch did the trick, but I know this will be overwritten as soon as we run through an upgrade. LetsEncrypt seems to return a cert chain formatted with a double-new-line (0x0a) between certificates and no new-line at the end of the...

@shanreich , I'm curious if you've had a chance to try NFTables in newer kernels and/or in PVE 9.x. I'm specifically wondering if the IPSet merge feature in NFTables isn't as broken as when you first worked on it. Reference bug: https://bugzilla.proxmox.com/show_bug.cgi?id=6517

I've been chatting with support to bug hunt a little bit; the default is "no rate limit" fwiw

Just out of curiosity, do you know what the default "put-rate-limit" is? I couldn't find it in the docs yet.

I'm not sure this is possible. If I'm not mistaken when a backup is pruned, not only is the name/timestamp/etc lost, but also the map of which chunks go where on disk. Garbage collection just takes chunks that are unreferenced by a backup and removes them. You really need that "backup" So in...

For those curious, I had overlapping IP addressing in one of my cluster IPSets. I would have had no idea what to look at, but shanreich found the issue. If anyone else runs into this same issue, I suggest running through your IPSets looking for overlaps

So for whatever reason, the forums are telling me I'm not allowed to send DMs to you. Am I doing something wrong? shanreich got in touch via DM and I got the log file to them

Hello, I'm working on trying out the new nftables proxmox-firewall on a couple nodes of our dev cluster to see how it works and I hit something I can't quite work past. Our rules are kind of a mess on our dev cluster, so it's probably going to be a good test of how the new code works. Issues...

@fiona , can you confirm if this package is now in the subscription repo? I'm looking and I see 6.8.8-2 on both a production (support) servers and one of our lab servers (community) when I run `apt changelog proxmox-kernel-6.8`, and I see 6.8.8-2 available. So I think it's available now, but I...

Rebooting the nodes got the new microcode into the Kernel. Or at least it seems to have... Unfortunately it's looking like hot-patching CPUs isn't supported in Proxmox-VE. The Proxmox-VE kernel is compiled without CONFIG_MICROCODE_LATE_LOADING. The short version is that microcode can be...

See also this proxmox wiki page: https://pve.proxmox.com/wiki/Storage:_LVM_Thin

What "pvdisplay" shows is a physical volumes and doesn't show whether or not you're using volume thin provisioning. What does "lvdisplay" show? This will show if you're using lvm thin provisioning or not

I haven't, I got busy with other tasks and I also figured "time may fix it". We have a shiny new proxmox cluster I might be able to try things out on (that will have support on it). I'll report what happens, though it may be a few weeks in the future.

I determined that it wasn't necessary to set this value. Most people use LVM thin provisioning. To quote @fabian, If you do use LVM thin provisioning, you can always edit /etc/lvm/lvm.conf to insert this line: issue_discards = 1