[development] Cron run exceeded the time limit and was aborted.

[Khalid Baheyeldin]

>From memory, having a destination makes the page do a drupal_goto(), which
does an exit() and therefore the semphore is not cleared?

On Wed, Sep 8, 2010 at 2:35 PM, nan wich <nan_wich at bellsouth.net> wrote:

> Ah, there is a slight difference: a destination is appended. It runs fine
> without the destination, but as soon as I put that on there, it bombs.
>
>
> *Nancy*
>
> Injustice anywhere is a threat to justice everywhere. -- Dr. Martin L.
> King, Jr.
>
>
>  ------------------------------
> *From:* Jamie Holly <hovercrafter at earthlink.net>
> *To:* development at drupal.org
> *Sent:* Wed, September 8, 2010 12:55:20 PM
>
> *Subject:* Re: [development] Cron run exceeded the time limit and was
> aborted.
>
> 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 Hollyhttp://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 <appa at perusio.net> <appa at perusio.net>
> *To:* development at drupal.org
> *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, nan_wich at bellsouth.net 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
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.drupal.org/pipermail/development/attachments/20100908/99c02cb3/attachment.html