By swduncan on
My cron.php file runs just fine when I call it via www.swduncan.org/cron.php, but when I try to run the file with php in crontab I get:
Warning: main(./includes/bootstrap.inc): failed to open stream: No such file or directory in /mnt/gs01/herd02/13637/domains/swduncan.org/html/cron.php on line 9
Warning: main(): Failed opening './includes/bootstrap.inc' for inclusion (include_path='.:/usr/local/php-4.4.7-1/share/pear') in /mnt/gs01/herd02/13637/domains/swduncan.org/html/cron.php on line 9
Fatal error: Call to undefined function: drupal_bootstrap() in /mnt/gs01/herd02/13637/domains/swduncan.org/html/cron.php on line 10
Any suggestions?
Thanks!
Steve
Comments
=-=
insure your path is correct....
it would also help to know how you've set up the cronjob what command are you using. check your hosts documentation on how best to set up a cronjob on your server.
Cron path issues
I'm having the same issue.
Admin in Drupal appears to manually run cron.php fine.
I can also run it via web browser.
(At least, the Log file tells me cron was last run successfully with either process.)
The Crontab is set correctly, since I'm receiving emails when it runs.
I believe it's simply a path issue.
I've set the .htacess file to include: php_value include_path "."
I've also set some other values; none seem to help.
(Though, I think this helped with Drupal/web browser manually running, because I believe Cron never ran correctly until I added that to .htaccess)
From what I can see, maybe crontab is ignoring .htaccess ?
Similar Issue
I have been experiencing a very similar issue and my host it telling me I'll have to write my own function to get the Drupal cron to run...their normal crontab can't do it...??
This is what the told me:
"Curl module is not available currently in command line version of php that's why execution by curl function doesn't work. You need to find other function to execute."
Anyone have any input on this?
=-=
I don't believe you have to write your own function.
what command are you using? exactly?
Have you tried GET?
As it turned out, my host was
As it turned out, my host was preventing access to wget and other command line actions. They finally helped solve the problem and it's all running nicely....just took 6 days!