Comments on: Wordpress wp-cron.php and Bad Behavior Apache crash

By: Asif

Asif — Thu, 06 Nov 2008 18:13:43 +0000

i m still have this issue no one originally helping.

By: Scott

Scott — Wed, 30 Jul 2008 10:12:46 +0000

Hi Tristan,

Thanks for this write up. I relize it’s a bit old but I’ve recently installed WP MU and am seeing this wp-cron.php?check=(big number) and I’ve read over your thread, checked out links like from Jonathan, etc. and can’t seem to solve this problem.

I’m not experienced enough with server stuff and all that. Is this purely an issue with Apache to you reckon?

You mentioned, “Problem solved: this seems to have been an apache2 bug under Ubuntu…”

Should I ask my host if my Apache version is at least 2.0.55-4ubuntu2?

Any other suggetions? Btw, I’m not using “Bad Behavior”, unless that’s the same thing as Akismet which I am using.

Thanks in advance

By: Jonathan

Jonathan — Thu, 03 Jan 2008 20:41:53 +0000

ganesh said: hi is it ok for now to rename the wp-cron file to different name so it doesnt get accessed , that way for now i stop this issue , my hosting people are compalining abt this frm my files.

If you are referring to this bug, then you can disable wp-cron and issue a real cron job in two steps, here, and here.

By: ganesh

ganesh — Thu, 03 Jan 2008 04:25:41 +0000

hi is it ok for now to rename the wp-cron file to different name so it doesnt get accessed , that way for now i stop this issue , my hosting people are compalining abt this frm my files.

By: Tristan

Tristan — Thu, 30 Aug 2007 08:17:48 +0000

Problem solved: this seems to have been an apache2 bug under Ubuntu… upgrading to the most recent version has stopped the problem completely (as of 8/30/2007).

High load now acts normally; processes quit after connections are dropped, even if swap space is used.

The working version is 2.0.55-4ubuntu2, previous version unknown.

This makes sense to me, as the original problem started after an ‘apt-get upgrade’ anyway, and did not exist before. Whatever it was I’m glad they finally fixed it.

By: Tristan

Tristan — Sun, 29 Apr 2007 07:05:10 +0000

Thanks, but I think this may not be as bad a problem as I originally thought, and it turns out my Apache crash is still happening. So don’t go blaming it too harshly, even though I still think this is a bug.

By: Jonathan

Jonathan — Sat, 28 Apr 2007 17:48:44 +0000

Added it to the TextDrive forum.

By: Docunext Tech Stuff Archive » Bad Behaviour

Docunext Tech Stuff Archive » Bad Behaviour — Sun, 08 Apr 2007 09:14:55 +0000

[...] This works well, but I did run into one problem wp-cron.php and bad behaviour not getting along. [...]

By: Albert

Albert — Sun, 08 Apr 2007 09:10:52 +0000

Oh wait - you can just add you ip to the whitelist.php in the bad-behavior folder. Cool.

By: Albert

Albert — Sun, 08 Apr 2007 09:05:23 +0000

Yep, I’m using bad behavior and my bad behavior table is getting filled up with entries like this:

/resources/blog/wp-cron.php?check=131accfed8363d4c…

from my own server address. Argh.