cron 240 seconds exceeded : fatal error : cron make me crazy! [#430690]

the first time i run cron.php today :
error :Fatal error: Maximum execution time of 240 seconds exceeded in C:\root\feed\modules\update\update.fetch.inc on line 185
so , i run again the crom.php
but more error showup:

Fatal error: Maximum execution time of 240 seconds exceeded in C:\root\feed\includes\common.inc on line 501

Fatal error: Maximum execution time of 240 seconds exceeded in C:\root\feed\includes\session.inc on line 56

Fatal error: Maximum execution time of 240 seconds exceeded in C:\root\feed\sites\all\modules\memcache\memcache_admin\memcache_admin.module on line 224

Fatal error: Maximum execution time of 240 seconds exceeded in C:\root\feed\includes\session.inc on line 14

the third time i run cron "failed"
.
.
.
failed and failed again and again

i think cron.php is a week point of my site , so , asked for your help

Comments

Comment #1

cesar.brod@gmail.com commented 25 April 2009 at 18:11

I just noticed my cron didn't run drupal's cron for the last five days for the same reason. Tweaking php.ini max_execution_time didn't help at all. Drupal always reported the 240 seconds. Tried to low to 50 the number of indexed itens in: admin/settings/search. Also lowered to 10. Still not working. Anyone? Any hint?

Thanks!

Comment #2

haojiang commented 26 April 2009 at 04:40

i delete all of my feed , then the cron.php goes all right , but the point is that ::::: i have to delete all!
do you use the module "feedapi" too?

Comment #3

haojiang commented 26 April 2009 at 11:52


Fatal error: Maximum execution time of 240 seconds exceeded in C:\root\feed\includes\common.inc on line 501

Fatal error: Maximum execution time of 240 seconds exceeded in C:\root\feed\includes\session.inc on line 56

Fatal error: Maximum execution time of 240 seconds exceeded in C:\root\feed\sites\all\modules\memcache\memcache_admin\memcache_admin.module on line 224

Fatal error: Maximum execution time of 240 seconds exceeded in C:\root\feed\includes\session.inc on line 14

Comment #4

cesar.brod@gmail.com commented 28 April 2009 at 18:53

Nopes, I don't use the feedapi and it seems my problem is only with the search.module. I still haven't figured out how to solve this.

Thanks!

Comment #5

cesar.brod@gmail.com commented 28 April 2009 at 19:10

Well, I just tried to run it again and it seems this problem is not actually tied to a specific module:

Fatal error: Maximum execution time of 240 seconds exceeded in /var/casacinepoa/includes/unicode.inc(345) : regexp code on line 1

Question is: how to make this Maximum execution time bigger, so at least we can debug this a little further?

Comment #6

mikeryan

he/him

English

Pittsfield, MA, USA

commented 17 May 2009 at 23:12

Status:

Active

» Closed (duplicate)

The cron limitation of 240 seconds is a long-standing problem, this is the currently active issue for that: #375578: Cron: guarantee each cron implementation the same share of execution time.

In terms of figuring out what module is taking so much cron time, one thing to do is to instrument module_invoke_all() - something like

    $function = $module .'_'. $hook;
    if ($hook == 'cron') {
      $start = time();
      print $function . ': ';
    }
    $result = call_user_func_array($function, $args);
    if ($hook == 'cron') {
      print time() - $start . ' sec<br />;
    }