I am having issues with my Cron....I know, not another cron thread.... I have searched through the Forums and tried some of the advice. In particular I have already seen and tried the advice in these threads:

http://drupal.org/node/52784
http://drupal.org/node/143519

What I have Tried:
1) Deleted cron_semaphore' from my variables table
2) After deleting semaphore in Variable table, Set XML Sitemap module chunk size to 10,000.
3) Set Search Settings to "10 per cron"
4) Removed the Updates core module
5) Ran Cron, by accessing it from the www.mysite.com/cron.php, get the white page, then check the logs and it says "Cron Run failed", looked in watchdog and see that it is because "Attempting to re-run cron while it is already running." or "Cron has been running for more than an hour"
6) I installed poormanscron and it partially runs. It is able to run these: node_cron, filter_cron, adn dblog_Cron, but it is not running the indexing etc..

I am not using a feed aggregator, or the newsletter module. If have increased the amount of time cron has to run.....not sure where to turn next.

What is the best way to figure out /track down where cron is failing....and why cron_semiphore is not getting removed...

Thanks in advance...

Comments

itowler’s picture

itowler commented

Ok, working on getting this figured out. By disabling various modules I have figured out that it is the Search Module that is causing the issues. If I disable the search module, Cron runs fine. If it is enabled cron stalls.

I have also installed Reindex, in an effort to help, and it seems to fail as well....

Not sure where to go from here.

Ian

Renee S’s picture

Renee S commented

This worked for me too, thanks. Now I just have to figure out why...

itowler’s picture

itowler commented

Found it...and now the problem is fixed.

Turns out that I had a node that was causing cron to bail out...not sure why, but by removing the node problem solved.

In an attempt to help others trouble shoot, here is what I did.

1. Disabled all modules and then added then back one by one until I found the module that caused cron to fail. For me it turned out to be the search module.

2. I reviewed my cron reports and searched for the word node, and found that a particular node kept coming up..... I deleted that node, and then everything worked fine...

Hope this helps others..

Ian

Issue resolved please close

Renee S’s picture

Renee S commented

Aaah, yes. I had a node that cleared the cache - Search was hitting it during the cron run and bailing out. Thanks for the advice, it saved me handfulls of hair :)

Renee S’s picture

Renee S commented
Status: Active » Closed (fixed)
krneely’s picture

krneely commented

I don't really understand how the search module screwed up cron so badly, but I disabled it on my site and cron began running again perfectly. Does anyone have insight? If not, I'm still happy! Thanks, y'all!