By drupallogic on

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!!!

⋅ Categories: Drupal 6.x

Comments

aitala’s picture

aitala commented

Try disabling the Update module, if its enabled.

Eric

__________
Eric Aitala - ema13@psu.edu
Penn State

224b8605113373e086cb27708ff301ba18ce394db1996e7e22928e4555e0d20b1b6cecc7f67c9bd9e536cb915779c485

drupallogic’s picture

drupallogic commented

I did. but still get this error. thanks though.

drupallogic’s picture

drupallogic commented

so any help on this ? I will appreciate any help.

someone_cooler’s picture

someone_cooler commented

Encountering the same issue.

michaeldhart’s picture

michaeldhart commented

Same here...just started recently, and disabling update doesn't work for me either

lhtown’s picture

lhtown commented

I am getting the same thing. I have 60-80 aggregator items from a variety of sources. I am running Drupal 5.

lhtown’s picture

lhtown commented

I started using poormanscron hoping to benefit from its built-in logging and the problem hasn't recurred for me yet.

brisath’s picture

brisath commented

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.

Starminder’s picture

Starminder commented

same same....

MGParisi’s picture

MGParisi commented

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*

dbeall’s picture

dbeall commented

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

willisjt’s picture

willisjt commented

This worked for me, Thanks dbeall!!

brisath’s picture

brisath commented

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.

tuwebo’s picture

tuwebo commented

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!

robbertnl’s picture

robbertnl commented

Great idea! Deleting the devel module also fixed my cron.