Comments on: Drupal Cron Troubleshooting

By: Ankleface Wroughtlandmire

Ankleface Wroughtlandmire — Thu, 07 Jul 2011 18:13:39 +0000

Ok, thanks again for the help! I really appreciate it.

By: greggo

greggo — Thu, 07 Jul 2011 15:38:07 +0000

Two reasons to not leave the code in all the time. I don't think it'll break anything, but there are no real benefits either:

1. It's adding extra db queries and cruft to the watchdog logs that you don't need, except to troubleshoot this particular problem.

2. When you update Drupal core, the hack will get overwritten.

By: Ankleface Wroughtlandmire

Ankleface Wroughtlandmire — Thu, 07 Jul 2011 15:06:31 +0000

Thanks very much for this debugging tip. I was pulling out my hair. Finally found the problem. Any reason I shouldn't just leave this “Hit” code in there all the time?

By: Gawrion

Gawrion — Thu, 23 Sep 2010 19:58:51 +0000

One more thing.. I tohought that maybe if you could check out our drupal site at http://niepoprawni.pl, you could find whats is possible to optimize etc. Obviously that would be some kind of deal ;) If you want to talk - plzz contact us at niepoprawni.pl/contact form.

By: Gawrion

Gawrion — Thu, 23 Sep 2010 19:55:08 +0000

Hey – that was my third attempt to solve my problem with crone. Googled “drupal cron mysql” i i easily find your very pragmatic way to solve cron-problem!!

Your article is very helpful.. Most of us dont know architecture of drupal soft. Your debugging hint solves all problems..

ThankS!! :)