Overview
CloudLinux improves shared hosting stability by limiting each account's CPU, memory, entry processes, IO, and other resources. CloudLinux Manager lets server owners view usage and tune limits.
Key terms
- LVE: the isolated resource environment for each account.
- CPU limit: maximum CPU share.
- Memory limit: amount of physical memory the account can use.
- Entry processes: concurrent web request slots.
- IO and IOPS: disk throughput and disk operation limits.
- Faults: events where an account hits a resource limit.
Customer impact
When a site hits limits, it may feel slow or return temporary errors. Check traffic, plugins, cron jobs, PHP errors, database queries, and attacks before upgrading limits.
Detailed setup notes
CloudLinux Manager helps providers see account resource usage and tune shared hosting limits. The goal is not only to restrict customers; it is to keep one busy or broken account from slowing the entire server.
What staff should review
- Accounts with repeated CPU, memory, IO, IOPS, or entry process faults.
- Top resource users during peak hours.
- Whether limits match the hosting plans sold in WHMCS.
- Whether account faults line up with attacks, cron jobs, backups, or normal traffic.
Customer explanation
Tell customers which limit they hit, when it happened, and what process or URL appears responsible if logs show it. Offer optimization first when practical, then suggest a plan upgrade when usage is legitimate.
Reference links
- CloudLinux Manager: https://docs.cloudlinux.com/cloudlinuxos/cloudlinux_os_components/#cloudlinux-manager
Shared hosting impact
CloudLinux and CageFS protect the whole server by isolating users and limiting runaway accounts. When a site hits limits, the fix may be optimization, malware cleanup, bot blocking, plan upgrade, or moving to VPS/dedicated hosting.
Quick support handoff
If this article does not solve the issue, open a support ticket with the domain, service name, exact error, time the problem started, and what changed recently.
