Internal 500 errors - 512mb not enough!!
Permalink
Hi, I'm getting constant internal 500 errors and the CSS files don't load at times so the site looks like a mess.
I've spoken to our host and they changed to CloudLinux back in February and ever since we've been having this issue, but we only discovered it 2 weeks ago.
Turns out, concrete5 is chewing up too much memory and the server is restricting the site so the CSS won't load and we get thrown internal 500 errors.
Our host has upped the memory twice now to 512mb - this hasn't helped.
We upgraded concrete5 to 5.4.2.2 (having issues upgrading 5.5.1) and that solved the problem ... Or so we thought. For about 2 weeks the site ran perfectly. The resource logs showed no faults and memory spikes - all running fine.
Then 2 weeks later out of the blue, the problem returns, worse than ever!
We haven't changed anything! The host is blaming concrete5. Just how much memory does concrete5 hog? Surely 512mb should be enough?
Please HELP.
I've spoken to our host and they changed to CloudLinux back in February and ever since we've been having this issue, but we only discovered it 2 weeks ago.
Turns out, concrete5 is chewing up too much memory and the server is restricting the site so the CSS won't load and we get thrown internal 500 errors.
Our host has upped the memory twice now to 512mb - this hasn't helped.
We upgraded concrete5 to 5.4.2.2 (having issues upgrading 5.5.1) and that solved the problem ... Or so we thought. For about 2 weeks the site ran perfectly. The resource logs showed no faults and memory spikes - all running fine.
Then 2 weeks later out of the blue, the problem returns, worse than ever!
We haven't changed anything! The host is blaming concrete5. Just how much memory does concrete5 hog? Surely 512mb should be enough?
Please HELP.
Nope, it's not budget hosting - why does everyone immediately assume it's budget hosting when theres an issue?
512mb should be plenty of memory to run C5, but it spikes and overloads. Why would C5 be chewing up so much memory? It's not right. That's got nothing to do with the host.
The strange thing is, it only occurs when a page is loaded for the first time or when a page is refreshed. Navigating to a new page fixes the issue and the CSS loads. If it were the host it would happen all the time during navigation - but that's not the case.
At first page load as well as at refresh, concrete5 must be chewing massive amounts of memory for it to overload 512mb. Something with C5 or the site is causing this - not the host.
512mb should be plenty of memory to run C5, but it spikes and overloads. Why would C5 be chewing up so much memory? It's not right. That's got nothing to do with the host.
The strange thing is, it only occurs when a page is loaded for the first time or when a page is refreshed. Navigating to a new page fixes the issue and the CSS loads. If it were the host it would happen all the time during navigation - but that's not the case.
At first page load as well as at refresh, concrete5 must be chewing massive amounts of memory for it to overload 512mb. Something with C5 or the site is causing this - not the host.
This is basically impossible to answer unless you post some of your instrumentation results, error messages, and traffic stats (specifically, number of concurrent requests).
I would experiment with turning the cache off, or adding this line to your config/site.php
Then, setting up a cronjob that periodically deletes the contents of files/cache/
The default file-based caching from Zend Cache has a garbage collection routine that can cause memory spikes and problems on larger sites.
Then, setting up a cronjob that periodically deletes the contents of files/cache/
The default file-based caching from Zend Cache has a garbage collection routine that can cause memory spikes and problems on larger sites.
If your not on a budget hosting plan than compare the prices your paying now to C5's own hosting packages, as I am sure that's a better solution than crossing your fingers, and hoping it works okay. If what your experiencing is garbage than imagine what your users on the other side of the world from the server are experiencing. If your on budget now, pay for something better, trust me you wont experience any buyers remorse.