cPanel enables you to view detailed information about problematic processes and database queries running on your account. This information is very helpful for determining why a CloudLinux resource limit was triggered.
To view resource limit information for your account, follow these steps:
In the METRICS section of the cPanel home screen, click CPU and Concurrent Connection Usage:
On the Resource Usage Overview page, cPanel displays a summary for your account. Depending on your account's resource usage, you may see:
- 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 receive this message, your account triggered at least one resource limit within the past 24 hours. cPanel displays additional information about which resource (or resources) triggered the limit.
- 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.
To view detailed resource usage information for your account, click [Details]. cPanel displays usage graphs and a usage table:
- By default, cPanel displays resource usage information for the past 24 hours. To change the time interval displayed, in the Timeframe list box, select the interval you want, and then click .
To view resource usage snapshots, click [Snapshots]. Depending on your account's resource usage, cPanel may display a list of processes and a list of database queries:
- In the calendar, select the date you want to view.
- In the Choose snapshot list box, you can select the snapshot for the specific time you want to view:
Let's look at an actual limiting scenario and see how snapshots help troubleshoot the problem. In this example, an account has had its CPU resources limited sometime within the past 24 hours:
To view additional information about the resource limiting, as well as when it occurred, we click [Snapshots]
Under 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.