Identify and resolve CPU/RAM spikes.
- First, check the Overview tab on your service page in the Client Portal. It shows live CPU, RAM, and disk usage gauges, a real-time performance graph (toggle between CPU, Network, and Disk I/O views), and your current transfer usage. Use this to confirm whether high usage is actually occurring before SSHing in.
- If the portal confirms elevated usage, SSH into your server and install
htopif not already present:apt install htop - Run
htopand sort by CPU or RAM (press F6 to change sort column) to identify the process responsible. - Kill a rogue process:
kill -9 PID - Check system logs for errors or crash loops that may be causing the spike:
journalctl -xeordmesg - If load is sustained and legitimate, consider upgrading your plan via the portal.