Resource Limit is Reached
When you visit your website and see the following, it signifies that CloudLinux has ceased processing it since it has reached the account limit. To prevent one hosting account from using up all of the server resources to the detriment of other accounts, we use the “CloudLinux” technology. The RAM, EP, and CPU restrictions may be found on your cPanel screen, which should provide you additional information about what is being used up.
If your site is consistently hitting its resource limit is reached, you may wish to optimize the script you’re running on your account, or consider an upgrade.
To view resource limit information for your account, follow these steps:
Firstly, log in to cPanel.
Secondly, in the METRICS section of the cPanel home screen, click CPU and Concurrent Connection Usage.
Thirdly, on the Resource Usage Overview page, cPanel displays a summary for your account. Depending on your account’s resource usage.
Next, Your site had no issues in the past 24 hours:
If you receive this message, your account did not trigger any limits within the past 24 hours.
Your site has been limited within the past 24 hours:
If you have received this notice, your account has recently exceeded at least one resource limit. Additional details about the resource (or resources) that triggered the limit are displayed by cPanel.
Your site might hit resource limits soon:
- This message is a warning that your account may trigger resource limiting in the near future. cPanel displays additional information about which resource is at risk of triggering a limit.
Click [Details] to get your account’s comprehensive resource consumption details. A utilisation table and usage graphs are displayed by cPanel:
- Resource use data for the previous 24 hours is displayed by default in cPanel. Select the desired interval in the Timeframe list box, then click Submit to adjust the time interval displayed.
Click [Snapshots] after that to see resource use snapshots. cPanel may provide a list of processes and a list of database queries depending on how many resources are being used by your account:
- Choose the date you want to view from the calendar.
- You can choose the snapshot for the precise moment you want to view it in the Choose snapshot list box:
- Click Previous snapshot to go back to the previous snapshot. Click Next snapshot to advance to the following snapshot.
Under the Process List, we see the following information:
- PID: This is the process ID.
- CMD: This is the actual command that the process ran.
- CPU: This is the CPU usage for the process. In this case, bad_script.php exceeded CPU capacity twice (102% and 101%).
- MEM: This is the amount of memory used by the process, in megabytes.
From this information, we can determine that the PHP script bad_script.php has some sort of problem that causes it to use a large amount of CPU capacity.