No I am not using drush. I have discovered that this only happens when I invoke cron from the Devel menu in the admin_menu bar. If I go to admin/reports/status and click the link there, it runs fine, as it also does when the normal cron run happens. So I opened an issue with Devel. Nancy Injustice anywhere is a threat to justice everywhere. -- Dr. Martin L. King, Jr.
________________________________ From: António P. P. Almeida <[email protected]> To: [email protected] Sent: Wed, September 8, 2010 12:38:40 PM Subject: Re: [development] Cron run exceeded the time limit and was aborted. On 8 Set 2010 17h26 WEST, [email protected] wrote: > [1 <text/plain; iso-8859-1 (quoted-printable)>] Nope, it's not > Update. I can run cron every minute and this happens. And I don't > think I even have Update enabled on that site. Nancy Injustice > anywhere is a threat to justice everywhere. -- Dr. Martin L. King, > Jr. I'll second Earnie's suggestion for trying Elysia Cron, you can set the cron running time for each implementation of hook_cron(). As a more hands on approach: grep the hook_cron() implementations of the installed modules and try disabling one by one until the problem disappears. Are you using drush? If so you can trace the root of the problem with relative ease. find sites/all/modules/ -type f -regex ".*\.\(module\|inc\)" -print | xargs grep "function.*_cron" Then just try drush dis -y <module> and drush cron Repeat as necessary. --- appa
