Portal Home > Knowledgebase > Articles Database > Server Load


Server Load




Posted by jarchee, 01-20-2010, 01:16 PM
Hi, This might sound pretty odd! I have a website on a dedicated server in a test environment. the platform that I used for the website has a caching capability that I use it very often. The server is running Centos (latest) with Cpanel/WHM. now that the size of DB is growing to over 400MB, the cache takes a life to complete. everytime that I run the cache and check the server status in cpanel I see the cpu load not going over 2(even less) and ram not going over 20%. how can I increase these limits in cpanel or centos itself so the server will not kill the process before it is done? Thank you.

Posted by DigitalLinx, 01-20-2010, 01:38 PM
I assume the caching is done by the website by creating static pages so it wont query the database and load the php processor. But the problem is the caching program takes a long time to finish. If so you would need to increase max_execution_time in php.ini or use set_time_limit() in the caching php file to override the php.ini setting for max_execution_time.

Posted by jarchee, 01-20-2010, 01:59 PM
I modified my php.ini and even in php setting in whm. it does not go over the limits that I mentioned. What should I do?

Posted by DigitalLinx, 01-20-2010, 02:04 PM
Any error messages in the website's error_log or /var/log/messages ?

Posted by jarchee, 01-20-2010, 02:15 PM
Nothing at all.

Posted by DigitalLinx, 01-20-2010, 02:23 PM
Then my best bet is the script is dying on it's own. Try to add some debug information and extra error handling at crucial places, perhaps the script is exceeding php's memory_limit, but that should be logged in the website's error_log. Are you sure you have a Error_log directive in httpd.conf for that website? We need errors in order to troubleshoot, otherwise we can just assume what's causing this.

Posted by CrazyTech, 01-20-2010, 03:54 PM
I have to say that if you're not getting anything in the error_log or the Apache log then it's probably time to debug the script. If it's hitting limits, there really should be an error message somewhere.



Was this answer helpful?

Add to Favourites Add to Favourites    Print this Article Print this Article

Also Read