I have just moved my site over to VPS hosting. I am using WHM and Cpanel to manage my site.
Since the transfer I have been receiving many, many emails stating that the processing time for PHP has been exceeded. Up to 100 emails a day.
This is the exact email details
Time: Thu Jan 19 11:41:11 2012 +1100
Resource: Process Time
Exceeded: 2091 > 1800 (seconds)
Command Line: /usr/bin/php
Could someone please help to as why I keep receiving these emails and should I act upon them.
I.E Do I set a setting in WHM to increase the PHP timeout limit and if so where would I do this?
Or should I simply ignore these emails and is there a setting in WHM to turn them off, if so where would I find this?
This is an old post and I know this won't help Jason, but I'm hoping it will help someone else.
I'm going to guess that you're using FastCGI (FCGI) as your PHP handler. If so, that's what's causing this.
The Apache website says, "[FastCGI] starts a sufficient number instances of the CGI program to handle concurrent requests, and these programs remain running to handle further incoming requests."
So there's really nothing wrong with your system and, even though you may not like having your PHP scripts unmonitored, the best way to stop the alerts is to set add PHP to the ignore list.
Since you are using WHM Cpanel, go to the CSF control area, scroll down to the "Edit lfd ignore file" section, select "csf.pignore - Process Tracking" and add exe:/usr/bin/php to the list.
The resource notification is sent by the firewall in the vps. so, ask your provider to increase the process execution time in firewall config file or ask to ignore the php in the firewall. This is only way to avoid the notification from the server side . Otherwise you have to optimize your php code.
You can configure the time for this directly in CSF, and it is pretty straightforward - they explain all of the parameters right inside the configuration file. However, this is telling you that some piece of code is keeping these php processes alive and thus may be indicating an issue that needs attention. There could also be times where this could occur due to exploit - so you really have to take a look at the pattern for those alerts and make an informed decision from the details you see there.