πΈ Rybbit - open-source and privacy-friendly alternative to Google Analytics that is 10x more intuitive.
Add troubleshooting section for ClickHouse on Proxmox VMs
Bill Yang35f6e768d70f
diff --git a/docs/content/docs/troubleshooting.mdx b/docs/content/docs/troubleshooting.mdxindex 62abaf7d3..2dd5bc5db 100644--- a/docs/content/docs/troubleshooting.mdx+++ b/docs/content/docs/troubleshooting.mdx@@ -92,6 +92,33 @@ cp .env.example .envdocker-compose up -d```+## ClickHouse keeps crashing on a Proxmox VM++ClickHouse requires the SSE 4.2 instruction set. Proxmox VMs default to a generic CPU type (like `kvm64` or `x86-64-v2-AES`) that doesn't expose all of the host CPU's instruction sets to the VM, which causes ClickHouse to fail with `Illegal instruction` errors or get stuck in a restart loop.++To fix this, set the VM's CPU type to `host` so it passes through the physical CPU directly:++<Steps>+<Step>+### Open the VM's hardware settings+In the Proxmox web UI, select your VM, then go to **Hardware** β **Processors** β **Edit**.+</Step>++<Step>+### Set the CPU type to `host`+Change the **Type** dropdown to `host` and click **OK**.+</Step>++<Step>+### Fully stop and start the VM+A reboot from inside the guest is not enough β do a full **Stop** and then **Start** from Proxmox for the CPU change to take effect.+</Step>+</Steps>++<Callout type="info">+The `host` CPU type can prevent live migration between Proxmox nodes with different CPU models. If you need migration, any CPU type that includes SSE 4.2 (e.g. `x86-64-v2-AES` on a host that supports it, or newer) may also work β but `host` is the most reliable option.+</Callout>+## I ran out of disk spaceRegular web analytics events take up almost no space in Clickhouse, so it is very unlikely that you ran out of disk space from from this. There are two main reasons why you might have run out of disk space: