Cron has been running for more than an hour and is most likely stuck
drupallogic - March 25, 2009 - 01:45
Hello
I don't know if this is the right place. Please move it if not as I hate the organization of Drupal.org forums. Anyway....
"Cron has been running for more than an hour and is most likely stuck"
I'm getting news around 100 RSS feeds and this is the error I continuosly get. I searched it and saw that it has an error coming from 5.x series. It's surprising that someone didn't fix it in core aggregator module. The error is most probably being caused a feed temporarly but it's stupid that Aggregator module is stuck and doesn't move on and cron.php works more than an hour!
so any solution ? may be a fix on Drupal 6.11 ?
thanks!!!
Try disabling the Update
Try disabling the Update module, if its enabled.
Eric
__________
Eric Aitala - f1m@f1m.com
The Formula 1 Modeling Website
www.f1m.com
I did. but still get this
I did. but still get this error. thanks though.
so any help on this ? I will
so any help on this ? I will appreciate any help.
Same Issue Here
Encountering the same issue.
Same here...just started
Same here...just started recently, and disabling update doesn't work for me either
I am getting the same thing.
I am getting the same thing. I have 60-80 aggregator items from a variety of sources. I am running Drupal 5.
I started using poormanscron
I started using poormanscron hoping to benefit from its built-in logging and the problem hasn't recurred for me yet.
Same Problem
I have the same issue that started a couple weeks ago. Disabling Update didn't work either. Consequently, cron hasn't run for a couple weeks and I can't get it to run by manually inputting the address either. I'm using Drupal version 6.11 on a shared host.
Same here
same same....
This is a very normal problem
It seems that most shared hosting has been timing out on drupals cron. For what ever reason Drupal has to check the database to see if the cron is running before it runs again. Thats problem 1
The second problem seems to be related to how long it takes the cron to run. In the end I am in the same boat as you all are. Make sure your not backing up your drupal site with Backup and Migrate.
I think shared hosting companies have changed something in how they do things. They probably saw our cron jobs running high amounts of resources and thus have made it near impossible to run them. The only perminant solution to this that I know of is poormanscron.
Unfortunately it seems to have come down to this *cry*
allourquilts.com
.
please don't cry.. it's not the Drupal way. lol
I had this happen after an upgrade to D6.12 on a vps. I never did find the trouble, ended up reverting to a previous sql backup. That fixed it.
It still bugs me what was up.. don know. I have 2 Drupal sites on a shared host and they haven't had that issue. All my Drupal sites run poormanscron and backup_migrate.
You can go in PHPMyAdmin to the variable table and delete the cron run instance and try again. Delete the following rows from the variable table
cron_last
cron_semaphore
WORKS!
This worked for me, Thanks dbeall!!
-Jordan Willis
www.jwillis.ca
www.opticvi.org
Backup and Migrate seems to be the issue
Deleting cron_last and cron_semaphore didn't work for me, but a fresh install of Drupal seems to get cron going again. That is, until a scheduled backup runs by the Backup and Migrate module. Then, this error comes up again and I can't get cron going again. Right now, everything seems to be working when I re-installed the Drupal codebase and remove all scheduled backups. I can run the backup manually from Backup and Migrate and cron continues to work fine.
Also, http://mysite.com/cron.php results in a blank page, but shows that it runs in the db log. Using http://mysite.com/admin/reports/status/run-cron it runs fine.
I'm on a shared host--hostmonster. Cron ran fine under older versions of Drupal. It seems to quit working after the upgrade to 6.11 and 6.12.
I fixed it just unistalling devel module and removing the folder
Hello,
Yesterday, I had the same issue.
I have:
Drupal 6.12
CCK 6.x-2.4
Fieldfield 6.x-3.1
google_analytics 6.x-2.2
i18n 6.x-1.1
imageapi 6.x-1.6
imagecache 6.x-2.0-beta9
imagefield 6.x-3.1
l10n_client 6.x-1.7
languageicons 6.x-1.1
lightbox2 6.x-1.9
tagadelic 6.x-1.2
taxonomy_breadcrumb 6.x-1.0
taxonomy_redirect 6.x-1.3
token 6.x-1.12
transliteration 6.x-2.1
views 6.x-2.6
views_tagadelic
I also have devel module not activated, but I uninstalled it and removed it from the server (the entire folder). I run update.php (just in case) and then executed the cron. It worked!
Visit my drupal site at: www.viajesdesorganizados.com (Disorganized Trips!)