By Lloyd on

All of a sudden Cron is not running any more. It's configured properly in Crontab. And even if I go into Drupal and run it manually I get a Cron Failed message. This has never happened before and I've been running this site on Drupal for well over a year.

⋅ Categories: Drupal 6.x

Comments

pbarnett’s picture

pbarnett commented

Have a look at http://drupal.org/node/382682

Lloyd’s picture

Lloyd commented

Awesome. Your module.inc change was perfect. I narrowed it down to the Update Status and Link Checker modules.

pbarnett’s picture

pbarnett commented

Thanks! It was just something I threw together to solve a problem I was having; it's good to know that it's helped someone else too.

Lloyd’s picture

Lloyd commented

Hmmm. So Link Checker was causing an issue. And Update Status. Now Ping is causing a problem (required for the Technorati module). I increased the max_execution_time to 240 (a recommendation in Link Checker). But still having the issue.

So now I've disabled Update Status, Link Checker, Ping and Technorati. I think there's something more going on but I"m not sure what it is. Everything has been working perfectly on this site for over a year. And all of a sudden Cron is breaking.

Any ideas what it could be?

Lloyd’s picture

Lloyd commented

I checked the log and there the error "Attempting to re-run cron while it is already running."

I deleted the cron_last and cron_semaphore variables, flushed the cache, and re-ran cron manually but still it failed to run.

I then ran via shell "drush --yes vset cron_semaphore 0". Now when I run cron manually I get a ton of MySQL messages. Repeated the process and am not getting the MySQL messages now but it still fails due to "Attempting to re-run cron while it is already running."

Lloyd’s picture

Lloyd commented

Problem was with my.cnf. I had lowered the wait_timeout to 15 which just wasn't enough for several of the modules to do their thing. Increasing it back to 120 did the trick.