Differences

This shows you the differences between two versions of the page.

--- computing:proxmox [2023/12/26 03:00] – oemb1905
+++ computing:proxmox [2024/01/07 00:09] (current) – oemb1905
@@ Line 156: / Line 156: @@
 2 * * 1 /usr/bin/certbot renew >> /var/log/le-renew.log
+On one of my VMs, which is running apache and behind the nginx reverse proxy, I got a client sync error for the nextcloud service running on it. It was complaining about the file size. Note: the GNU/Linux clients had no such error. Anyway, the following was needed on PVE / reverse proxy configs to resolve this error:
-Now the reverse proxy / PVE instance has matching certs to the clients its serving. This project achieves VMs that are publicly accessible, internally accessible, TLS-secured, and separate VMs (database/stack reasons), and using only one external IP.
+  sudo nano /etc/nginx.proxy_params
+  <post_max_size 10G;>
+  <upload_max_filesize 10G;>
+  sudo nano /etc/nginx/nginx.conf
+  <client_max_body_size 10G;>
+  <client_body_buffer_size 400M;>
+Now the reverse proxy / PVE instance has matching certs to the clients its serving. This project achieves VMs that are publicly accessible, internally accessible, TLS-secured, and separate VMs (database/stack reasons), and using only one external IP. Now, for managing how you much your instance can handle, here's some tips:
- --- //[[jonathan@haacksnetworking.org|oemb1905]] 2023/12/25 04:27//
+  * Physical Cores * Threads * Physical CPUs = Assignable Virtual Cores
+  * If using zfs for the storage, estimate 50% of RAM used by it
+If ram is an issue, make sure to throttle arc. In my case, I let zfs run free and tightly provision the VMs. Each rig and use case will be different; adjust accordingly. Above, I already shared the command to determine your physical CPUs / sockets. Here's how to determine all three:
+  lscpu | grep "thread"
+  lscpu | grep "per socket"
+  lscpu | grep "Socket(s)"
+  Thread(s) per core: 2
+  Core(s) per socket: 12
+  Socket(s): 2
+To determine vCPUs, you do threads*cores*physical-sockets, or (12*2)*(12)*(2) = 576 for a Supermicro with 2x Xeon e5-2650 v4 chips. As for RAM, I have 64GB total, so subtracting 4Gb for the OS, I have 32GB left for the VMs with roughly 32GB being allocated for zfs. PVE is very strict in interpreting allocated RAM and will OOM kill VMs if it senses it is short. This is in contrast, for example, with virsh which will allow sysadmins to run how they see fit even at risk of virsh crashing. For this reason, either expand your rig, adjust arc, or tightly provision your VMs, or all three. I personally just tightly provisioned my VMs as I want zfs to use as much RAM as it needs. If you prefer to throttle arc, here's how:
+  sudo nano /etc/modprobe.d/zfs.conf
+  options zfs zfs_arc_max=1073741824 [1 gigabyte example]
+  update-initramfs -u -k all
+  reboot
+Adjust arc throttle to fit your system. If you need to stop a system at the CLI because you can't reboot/shutdown at the GUI-level, then do something like:
+  /var/lock/qemu-server/lock-101.conf
+Next entry ...
+ --- //[[jonathan@haacksnetworking.org|oemb1905]] 2023/12/28 05:26//

Haack's Wiki

User Tools

Site Tools

Differences

Page Tools