508 Resource Limit Reached

The “508 Resource Limit Is Reached” error message appears when an account exceeds the resources assigned to it  – CPU usage, RAM usage or the number of concurrent processes running under the cPanel account. The error message “508 Resource Limit Is Reached” appears when your account is constantly exceeding the resources assigned to it – these can include CPU usage, RAM usage and/or the number of concurrent processes running under your cPanel account.

You can view the history of these limits being exceeded in cPanel, under Logs – Resources – Details.

There are several reasons that can be involved:

  • Normal traffic. If your site experiences high peaks in normal traffic it can exceed allocated resources. If this is a regular occurrence we would recommend considering an upgrade to a Virtual Private Server, where no such limits are in place
  • Problems in code. If there are pages on your site that have speed issues that have been introduced during development, a relatively small number of concurrent page requests can push the site over its resource limits
  • Backend operations – demanding backend operations such as imports and exports can create significant load, which in addition to normal traffic can cause resource limits to be exceeded.
  • Webcrawlers making a high number of requests per second. You can adjust the rate at which e.g. Google requests pages in Google Webmaster Tools.

We run the CloudLinux operating system on all our shared servers, and this allows us to isolate accounts in their own lightweight virtual environment with a finite amount of resources allocated to each account.

You can check the resource usage of your account by logging into your cPanel and clicking on the “Resource Usage” icon. You can also view the real time live resource usage of your account by logging into your cPanel and looking at the stats down the left hand side of the page.

A resource usage spike every now and again is nothing to worry about and will cause minimum (if any) disruption to your account, but if you are facing constant issues then you should be looking at optimizing the code on your websites, or upgrading to a VPS or Dedicated server.

If you are currently on a shared hosting account, you may find that your resource usage issue could be fixed by moving to a VPS or Dedicated server, this would mean each site would have its own cPanel, and its own set of resources. CloudLinux measures the resources on a per account basis, not per domain, so if you have a large number of domains on one account they all count towards the total resource usage.

We find that a lot of resource usage issues are due to badly coded scripts, such as 3rd party themes or plugins that are installed on a WordPress blog, if you have a WordPress blog on your account that is causing the resource usage issues, we recommend disabling all plugins, and then monitoring the resource usage with those plugins disabled, you can then reactivate the plugins 1 by 1 until your find which is causing your issue.

You can also check the document root of your websites for any error_log files, if you find an error_log file, you should take a look at the recent entries and fix any errors that are reported. Optimizing your database tables (if any of your sites are MySQL driven) via PHPMyAdmin is also a good way to keep things running smoothly.

Running error free, well coded websites will vastly reduce the resource usage on your account and lead to a much more stable hosting experience.
  • 11 Users Found This Useful
Was this answer helpful?

Related Articles

CPU Usage

Shared ServersAdriaHost allows a maximum of 25% CPU usage limit. You may exceed this limit for no...

How can I make a stronger password?

How can I make a stronger password?Password SelectionA good password is easy to remember, but...

How Can I Prevent Hacking?

The most important thing to do is keep your passwords a secret. If you must give a password to...

SQL injection, insertion

SQL injection is an attack where malicious code is passed to an SQL Server for execution. The...

How to Handle the Google Attack Page

When you see the dreaded Google Attack Site warning, you should immediately submit a ticket to...