By andrewl-1 on
Hi,
My cron job is now giving errors for the last couple of days when it runs (every hour).
I have not changed anything though I suspect my host has but they are clueless.
This is the error...any ideas?
406 Not Acceptable
An appropriate representation of the requested resource /cron.php could not be found on this server.
Apache/2.2.8 (Unix) mod_ssl/2.2.8 OpenSSL/0.9.7a mod_auth_passthrough/2.1 mod_bwlimited/1.4 FrontPage/5.0.2.2635 Server at xxxxxxx.org.uk Port 80
Comments
RE: Cron errors just started
@andrewl: I'm assuming the file cron.php still exists?
I wasted several hours dealing with cron with my hosting company. I've been with them a long time and overall they're great, but getting the cron job to run caused all kinds of errors. Finally I gave up and am using poormanscron, which works fine.
==
Tom Kephart
Editor, New Tech Heroes
Owner/Creative Director, Kephart & Associates
Marine City, Michigan, USA
Cron file exists
Sure, the cron file exists, though I don't rule out the possibility that they have corrupted it!
Thanks for the tip on poormanscron.
I have exactly the same
I have exactly the same issue - which host are you with?
I have been hosting with
I have been hosting with Site5 and they just changed the mod_security rules. Now cron is not functional. I spent many hours with their tech support (clueless bunch) trying to find the problem. They couldn't figure it out. I did. I have not found a workaround yet, so am using poormanscron. But that does not solve the problem of non-drupal cron jobs. I probably will change web host.
I received the following
I received the following from my host support team:
Most servers use a security program called mod_security. It appears that this has upgraded to version 2 and you are violating one of the restrictions setup by it;
Access denied with code 406 (phase 2). Match of "rx ^apache.*perl" against "REQUEST_HEADERS:User-Agent" required. [id "990011"] [msg "Request Indicates an automated program explored the site"] [severity "NOTICE"]
Something that your cron is doing is not liked by the system as it see's it as a security risk. I would recommend contacting the script designer/developer to inquire about a workaround for this.