Actually I do watchdog("my function', myfunction(10)) so the output goes to dblog when it works. I never use exit() in Drupal. Nancy Injustice anywhere is a threat to justice everywhere. -- Dr. Martin L. King, Jr. ________________________________ From: Ted <ted-drupalists@webfirst.com> To: development@drupal.org Sent: Wed, September 8, 2010 12:24:14 PM Subject: Re: [development] Cron run exceeded the time limit and was aborted. Have you tried suppressing the output of your function? Also, make sure you're not calling drupal_goto--or anything else that calls exit(). Ted On 9/8/2010 12:17 PM, nan wich wrote: If I comment that line out, the problem goes away, so yes, I am reasonably convinced it is my function.
I can clearly see it returning in far less than even 30 seconds, so there is no way it's taking 240. Nancy Injustice anywhere is a threat to justice everywhere. -- Dr. Martin L. King,
Jr.
________________________________ From: Earnie Boyd <earnie@users.sourceforge.net>
To: development@drupal.org Sent: Wed, September 8, 2010 12:08:25 PM Subject: Re: [development] Cron run exceeded the time limit and was aborted.
nan wich wrote:
I have a function that runs a few updates and displays a list of what it did. In
order to get caught up from a long period of neglect, I decided to add it into
the hook_cron. Every time I invoke cron, I get "Cron run exceeded the time limit
and was aborted" yet it completes in far less than 30 seconds. Any ideas how my
code could be inadvertantly triggering this? Nancy Injustice anywhere is a threat to justice everywhere. -- Dr. Martin L. King, Jr.
Are you sure it is your code? Try using Elysia Cron to schedule the hook_cron of different modules. The cron API gives 240 seconds for all hook_cron to execute, if all the modules exceed the 240 seconds then you'll see the exceeded time limit message.
-- Earnie -- http://progw.com -- http://www.for-my-kids.com