I have a cronjob in /etc/cron.d/mycron
that looks like this:
0 3 * * * apache php /path/to/my/script.php
In the same file there are other cronjobs begin run as root and other users (which work), but for some reason this job running as apache isn't running and isn't reporting anything in /var/log/messages
or sending anything to the MAILTO
address in the cron file. When I su apache
and run the cronjob's command, it works fine, but cron doesn't like it.
This is a long running problem for me and so far I have gathered the following possibilities:
- The apache user doesn't have a home directory (the other cron users do), and crond doesn't like this.
- There's some PAM or
/etc/security/access.conf
setting blocking apache using crond, although/etc/security/access.conf
is completely commented out. - SELinux - this is usually the culprit when a problem seems really weird.
Any ideas or experience with this problem and what the solution might be?
Thanks
A home directory must be set for the user. If the user doesn't have one, you can specify it directly in the cron.d-file.
You probably need to provide PATH=/usr/bin/ too, or specify full path for the command.
/usr/bin/php
grep apache /etc/passwd
As far as I know, user should always have home directory. It may reside not in /home.cron
by default runs with a very limitedPATH
; do you need to put in the full path to thephp
binary?