Recent content by CZappe

I have a couple of aging QNAP QTS servers that I've been using as shared NFS file storage for several standalone Proxmox nodes. I'm looking into replacing these QNAPs with newer models running the ZFS-based QuTS Hero operating system. I know this will entail some changes to our current Proxmox...

I am also experiencing the "Error 2" issue you're describing here. I recently upgraded a node to PVE 7.4-17 and am on kernel 5.15.126-1-pve. I followed the steps I previously used to download and update my ixgbe drivers based on this Proxmox forum post: PVE 6.0-7 + ixgbe firmware errors. Post...

Yep, that was it. I had mapped the wrong mount point, "Public" :rolleyes: nfs: qnap1v1 export /Public path /mnt/pve/qnap1v1 server 192.168.XX.XX content backup,images options vers=3 prune-backups keep-daily=3,keep-monthly=1,keep-weekly=2 I...

I just configured a new PVE node (v 7.4-17) in our existing environment and have added several NFS shares to Datacenter>Storage that we use to host production disk images and VZDump files. The NFS shares populate under the new node, as expected and show the correct storage usage that our other...

That was it! :D I was writing a reply here and lost my draft, but removing the comments in tfa.cfg got the same secret key working for both WebGUI and SSH connections. I'm settling with the fact that the recovery codes are going to be different between the two interfaces since they normally...

Agreed. Password + 2FA is the first step in our process while we secure public keys for our administrators. The goal is to move to passwordless authentication with 2FA.

Thanks for the initial pointers here! I went ahead and installed libpam-google-authenticator and initialized it as I've done on our other Debian-based servers. This generated a configuration file, /root/.google_authenticator with permissions '0400' I then copied in the secret from...

I'm configuring TOTP multifactor authentication for our Linux servers, including Proxmox nodes, and have a question about whether the codes Proxmox uses in the Web GUI could be configured for use for SSH connections as well. Ideally, I'd like to have one method of generating TOTP codes work for...

I'm adding a quick reply to this thread, as the original poster, to provide a one-line, node-to-node method for moving config files over a network connection via rsync, without the need for time intesive copying and renaming of files along the way. You may need to install rsync via apt to use...

Awesome! I found the rrd database for my vm under /var/lib/rrdcached/db/pve2-vm/[VMID] I copied the file to the same relative directory on the new node, appended with ".new", and ran the following one-liner. This allowed me to swap in the historical rrd data while the VM was running on the...

I recently migrated the config file for a long-running VM in our environment to a new, unclustered node. The virtual disk is hosted on an NFS server, so the VM boots and is running just fine on the new node. However, the summary data for the VM has started again from scratch, as all of the...

In terms of memory allocation on this node, the total memory size allotted to the active VMs is greater than the available RAM on the node. However, the host memory usage is still below 50%, so it doesn't seem like reducing VM memory allocation would really have an impact here

I think you're probably right that what I'm seeing here is a slow-creep of file-based as opposed to anonymous page swapping. If the Proxmox kernel does indeed use the Control Group swappiness value rather than the global swappiness value, this would seem to make sense: root@node:~# cat...

I suppose if I were to boil this down to a concrete problem it would be this: The constant utilization of ~100% of any server resource indicates to me a need to either upgrade or reconfigure the server. In this case, my concern is that keeping the swap usage pegged will lead to perpetual IO...

I have a Proxmox node currently configured with 126 GB RAM, actively running 10 Linux and Windows VMs. Our users were reporting issues with some of these VMs which seemed to coincide with high SWAP usage on the node, even though total RAM usage was below 50%. To ease the SWAP load, I made two...