Embark on a journey of knowledge! Take the quiz and earn valuable credits.
Take A QuizChallenge yourself and boost your learning! Start the quiz now to earn credits.
Take A QuizUnlock your potential! Begin the quiz, answer questions, and accumulate credits along the way.
Take A QuizGeneral Tech Bugs & Fixes 3 years ago
User submissions are the sole responsibility of contributors, with TuteeHUB disclaiming liability for accuracy, copyrights, or consequences of use; content is for informational purposes only and not professional advice.
You could try to specify the path to the php.ini file with the -c switch and also use the -f switch to indicate the file to be executed.
0 4 * * * /opt/lampstack/php/bin/php -c /etc/php.ini -f /opt/lampstack/apache2/htdocs/tests/test.php
You might also want to turn on display_errors and error_reporting
But I also agree with the other responses in that it sounds like an issue with permissions to the log file itself. If you have a global error_log parameter set you can try to echo something out with error_log() in your code.
No matter what stage you're at in your education or career, TuteeHUB will help you reach the next level that you're aiming for. Simply,Choose a subject/topic and get started in self-paced practice sessions to improve your knowledge and scores.
Ready to take your education and career to the next level? Register today and join our growing community of learners and professionals.
Your experience on this site will be improved by allowing cookies. Read Cookie Policy
Your experience on this site will be improved by allowing cookies. Read Cookie Policy
manpreet
Best Answer
3 years ago
I am utilizing crontab to execute a PHP file as follows:
I am pretty sure that the file itself is working properly because if I execute
/opt/lampstack/php/bin/php /opt/lampstack/apache2/htdocs/tests/test.phpin command line I get the expected results.In the cron log I can see that it is being called at the specified time, but the php file doesn't run (the php code is just one line that writes to a log file). I thought that maybe it has something to do with user permissions so I tried forcing it to be executed as root (by putting root between the time and /opt/lamp...) but still no luck.
Any words of wisdom?
Kate