By amccann on

I am getting "last CRON run did not complete" on 4.7 RC2 after moving to Textdrive.

I have tried turning off the aggregator and ping modules to no avail.

Does anyone have any suggestions as to what I should look at.

Thanks

⋅ Categories: Drupal 4.7.x

Comments

markus_petrux’s picture

markus_petrux commented

In your .htaccess file, try adding (or tweaking, if exists):

php_value max_execution_time  120

...or higher?

Doubt is the beginning, not the end of wisdom.

amccann’s picture

amccann commented

Thanks...I'll try it now.

amccann’s picture

amccann commented

Didn't work...I set to 240 (verified through phpinfo() and it has had several cyles to to attempt to complete.

Any other thoughts?

Thanks

markus_petrux’s picture

markus_petrux commented

It is strange cron.php taking so much time. Have you tried disabling all suspicious modules (you could search the source for implementations of modulename_cron) to see where is the bottleneck.

There is something "new" comming that you might want to look at:
http://drupal.org/node/59863

Close to that "trick", I have a site running that's using the default site/settings.php, hence I can run cron.php from the command line, as described in the above issue.

But maybe there is an endless loop here, somewhere, so it would be nice to try to identify where is the problem by enabling modules one by one.

Doubt is the beginning, not the end of wisdom.

amccann’s picture

amccann commented

Thanks. I will try turning off all the modules tonight.

Interesting question - is there a reason why the .php files don't have a ?> at the end

Heine’s picture

Heine commented

See Coding standards and links therein in the handbook.
--
Tips for posting to the forums.
When your problem is solved, please post a follow-up to the thread you started.

BigMoneyJim@mylectern.com’s picture

BigMoneyJim@mylectern.com commented

I've had cron jobs fail due to running out of memory, but I think it was a forked process that failed. Still, you might check php's memory_limit setting and see if bumping it up helps. I've definitely had admin actions fail due to a low memory_limit setting.

amccann’s picture

amccann commented

Thanks to a great tech support guy at TextDrive, the problem is fixed.

I moving hosting providers, I had updated to RC2 (just a few hours before RC3 was announced - humph!) and went from a PHP4 platform to PHP5.

One of my modules was out of date (Amazon tools) and was failing - I thought I had updated them all in the changeover.

So, testing cron while enabling modules incrementally would have found this but the tech at TextDrive went above the call of duty and helped identify the issue based on what he could see at his end.

Thanks for all your help!