"Cron run failed"
NancyDru - May 24, 2007 - 15:37
| Project: | Drupal |
| Version: | 7.x-dev |
| Component: | base system |
| Category: | bug report |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | active |
Jump to:
Description
The message that Cron run failed should, IMHO, be at least a warning level message not just a notice level.
The real problem is Attempting to re-run cron while it is already running. But it is not running, and has not run in over 3 days.
If it matters: Drupal 5.1 running on Windows XP (SP2), Apache/2.2.3 (Win32) mod_ssl/2.2.3 OpenSSL/0.9.8d PHP/5.2.0 mod_perl/2.0.3-dev Perl/v5.8.8, MySQL database/5.0.27
#1
There's currently no way to fix this without doing:
DELETE FROM `variable` WHERE name = 'cron_semaphore';DELETE FROM `variable` WHERE name = 'cron_last';
It'd be good to have a "restart cron" button which does this somewhere - maybe in /admin/logs/status next to "run cron manually".
#2
Yes, I did this. The "problem" is Update_Status and the length of time it takes it get data from DO.
BTW, I also added a check for this condition in my Site Documentation module.
#3
/wonders if drupal.org slowness has anything to do with update status. Haven't checked out your site documentation module yet, but it looks interesting.
#4
This feature has not been committed yet.
#5
The problem has not recurred since the big update and table moves. And I know how to fix it easily, so I'm closing this.
#6
#7
even after deleting the values from variables table, Cron failed to run for my site.
DELETE FROM `variable` WHERE name = 'cron_semaphore';
DELETE FROM `variable` WHERE name = 'cron_last';
#8
try clearing the cache
#9
it worked for me after trying for many times.
running the command.
restarting apache
and clearing cache
#10
I was getting this error for over an hour (thought waiting for the process to finish might help, but didn't seem to). So, I searched and found this issue and this article: http://www.mojahmedia.net/drupal-cron-run-failed-cron-busy-probably-stuc..., which has more details, that I haven't tried yet.
The first thing that is mentioned here and there:
DELETE FROM `variable` WHERE name = 'cron_semaphore';
DELETE FROM `variable` WHERE name = 'cron_last';
seemed to fix everything.
Thanks
#11
Bumping this thread because I ran over the same problem with D6. This needs something like in #1 (or a *real* fix). This is especially confusing for novice users.
Setting version status to 7.x-dev for discussing about this functionality to getting included, and for drawing attention to the subject which is not so trivial as one may think (broken cron is serious). Cheers.
#12
Same symptoms as everyone else.
Fixed by disabling the Search module.
As a suggestion, instead of printing only "Cron run failed", some sort of error information would be helpful as it seems cron can break in a few different ways.