AnsweredAssumed Answered

multiple cron runs hogging the system

Question asked by Francesca Shiekh on May 13, 2015
Latest reply on May 15, 2015 by Francesca Shiekh
I find that I have multiple cron runs which are hogging the system.
An example from this morning:

               

apache     903  0.0  0.0 106096  1136 ?        Ss   08:00   0:00 /bin/sh -c cd /var/www/html/sugarcrm; php -f cron.php > /dev/null 2>&1

 

apache     905 19.0  1.4 542372 147468 ?       R    08:00  19:16 php -f cron.php

 

apache    5148  0.0  0.0 106096  1132 ?        Ss   08:34   0:00 /bin/sh -c cd /var/www/html/sugarcrm; php -f cron.php > /dev/null 2>&1

 

apache    5149 19.9  5.3 938748 545416 ?       R    08:34  13:28 php -f cron.php

 

apache   12408  0.0  0.0 106096  1136 ?        Ss   09:30   0:00 /bin/sh -c cd /var/www/html/sugarcrm; php -f cron.php > /dev/null 2>&1

 

apache   12410 17.0  3.7 777012 383216 ?       R    09:30   1:57 php -f cron.php

 

apache   29416  0.0  0.0 106096  1132 ?        Ss   May08   0:00 /bin/sh -c cd /var/www/html/sugarcrm; php -f cron.php > /dev/null 2>&1

 

apache   29417 77.5  8.6 1267216 873004 ?      R    May08 5647:11 php -f cron.php


Clearly some of these (see May 8) are just hanging there...
Could this be due to jobs not completing?

I have had problems with Checking Inbound Email since going live with v7 on April 24th. It often ends in "'Forced failure on timeout" and I've not been able to determine why yet.

We had the same problem in v6 and I had to do a lot of work to make sure the Check Inbound Email didn't coincide with other jobs, the more jobs executing at once the greater the chance that Check Inbound Email would end up timing out.... 

I thought I had that resolved this, but now the problem is back

Any suggestions for debugging/optimizing cron jobs?
thanks,
Francesca

Outcomes