One of my unreleased websites hasn't been touched in about six months. I've come back to it recently to find a lot of HTTP 500 errors - not on the HTML / PHP pages themselves but on scripts that are subsequently called. The error is:
The HTML / PHP script calls other resources such as images, CSS, Javascript etc. as you'd expect. However, some of those supposedly static resources are actually PHP scripts because they need to be built and delivered in a dynamic manner, like this:
I am now finding that while page.php and logo.jpeg work fine, qr.png, css.css and javascript.js intermittently fail with the above error. I understand that each PHP call will attempt to create a new process (four near-simultaneous processes in the example above) but until a few months ago this was not a problem.
My question is simply: has the available memory for PHP been reduced in the last six months on shared hosting, particularly on euk5.
I might be able to work around some of the issues here, and I'm not averse to paying more for 'proper' hosting once this website is ready for release, but at the moment I need to understand what has changed, because it isn't the code base.
Thank you
Code:
(12)Cannot allocate memory: [client <IP address>:39555] couldn't create child process: /opt/suphp/sbin/suphp for /home/<php script>, referer: http://<URL>
Code:
page.php |-- logo.jpeg [normal static image] |-- qr.png [PHP for a dynamic QR code image] |-- css.css [PHP for dynamic CSS] |-- javascript.js [PHP for dynamic JS]
My question is simply: has the available memory for PHP been reduced in the last six months on shared hosting, particularly on euk5.
I might be able to work around some of the issues here, and I'm not averse to paying more for 'proper' hosting once this website is ready for release, but at the moment I need to understand what has changed, because it isn't the code base.
Thank you
Comment