Apache error

Our shared servers constantly monitor the integrity of the shared resources. These monitors are the guarantors of the quality of service provided because they prevent most abuses by ensuring that a site cannot use too many resources to the detriment of other hosted sites.

Several parameters are monitored by these monitors and can cause your script to stop PHP :

• Too long a turnaround time : if your script PHP takes more than 30 seconds, then it runs the risk of being killed by the system. If you get a 500 error after a long page load time you are probably in this situation

• Too much memory consumed : as soon as your script PHP consumes more than 128 MB of RAM, it may be stopped by the system. This usually results in an immediate 500 error, with no prior loading time.

• Too much CPU consumed If your script uses the CPU too intensively, it may be killed by the system. If the 500 errors occur rather randomly, you may be in this situation.

• Too many processes PHP simultaneous In shared hosting, we are obliged to limit the number of processes PHP launched simultaneously by a site; indeed, without this limitation, resources could quickly become saturated and all hosted sites impacted. A frequent case is the display of images through PHP (of the type image.php?crc=/images/monimg.jpg ): when the page is displayed, there are as many processes PHP launched than images. This is a bad way of programming and in any case incompatible with shared hosting.

• A file .htaccess malformed: Check that yourURL Rewriting are correct, that you do not use a php_valueand that you have not inserted any unwanted characters using an unsuitable text editor (e.g. WordPad).

Of course, each case is unique and requires its own investigation. Below we give you some tips for verification:

• If the error occurs after a long loading timeIf your script establishes connections to another web site, and that site is down, then your site may be down. For example, if your script establishes connections with another website, and that website is unavailable, then your website itself may be unavailable. So check for any external element: inclusion of a remote page/image, flows RSS, meters and guestbooks, etc.; identify the problematic resource and remove it from your page, or modify your programming to take into account the possibility of the resource being unavailable. A common case is also the call for API like Google or Yahoo. Don't forget that in shared hosting the IPs are shared, if other customers abuse these APIThe IP may be temporarily blocked and your site may be impacted.

• Identify a possible programming problem. Check that you have not made an infinite loop, or code that could generate a programming problem. Go through your code line by line, commenting step by step on the programming blocks in order to identify the line(s) that cause problems. Check in particular that you do not no remote include HTTP and you only work with local disk paths.

• Check your databases : Log in to your PhpMyAdmin and make sure that the size of your tables, the session table, statistics table, log table, etc., has not reached disproportionate proportions. Empty the affected tables and see this article to maintain your MySQL databases.

• Check the features of your scripts PHP Does your site make image processingdoes it manage visit statisticsa Live ChatDoes it send large numbers of e-mails, does it offer large files for download, and more generally, is it likely to generate actions that may consume many (too many) resources? In general, you should systematically disable any logging/stats/tracking system incompatible with a shared environment.

If despite everything, your site is too greedy and continues to generate errors, the most reasonable solution is to consider migrating the site to a private server or a dedicated server