In this case, I can count to 5 and it's back, so it is clearly not taking long enough to time out. Nancy Injustice anywhere is a threat to justice everywhere. -- Dr. Martin L. King, Jr.
________________________________ From: Khalid Baheyeldin <[email protected]> To: [email protected] Sent: Wed, September 8, 2010 1:17:28 PM Subject: Re: [development] Cron run exceeded the time limit and was aborted. A better approach for timing cron stuff here http://drupal.org/node/131536#comment-1117255 There is a variable to turn this on or off on demand. On Wed, Sep 8, 2010 at 12:55 PM, Jamie Holly <[email protected]> wrote: The link in devel is just a link to the same URL as clicking it in the status report (/admin/reports/status/run-cron). > >Here's a good hacky trick I have used before to diagnose cron problems. Go >into >module.inc and edit the module_invoke_all function so it looks like this: > > foreach (module_implements($hook) as $module) { > $function = $module .'_'. $hook; > if ($hook=='cron'){ > echo "$module <br />"; > } > >That will give you an idea of exactly which cron implementation it's hanging >up >at, then you can just revert the changes in module.inc when you are done >troubleshooting. > >Jamie Holly http://www.intoxination.net http://www.hollyit.net > >On 9/8/2010 12:46 PM, nan wich wrote: >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 >> >> -- Khalid M. Baheyeldin 2bits.com, Inc. http://2bits.com Drupal optimization, development, customization and consulting. Simplicity is prerequisite for reliability. -- Edsger W.Dijkstra Simplicity is the ultimate sophistication. -- Leonardo da Vinci
