Cron – Troubleshooting Shell Scripts Not Working with Crontab

Cron jobs can be run as root or another specified user. If that user does not have the permission to write to the .sql file the job will fail.

If the file exist and it has write permission for the user running the job the file will be written.

if the file does not exist and the user does not have permission to create files in target directory, the job will fail.

I can typically say

sudo touch /var/log/foo.log
sudo chown my_username /var/log/foo.log

now I can say:

echo bar > /var/log/foo.log

but if the file does not exist it will fail, as I have no permission to create files in /var/log/.

So question becomes if the user running the job have the right to create files where ever the output from mysqldump is written.

Now if I set up a cron job to run a script with this:

date > /var/log/foo.log

every minute, I can add:

*  *    * * *   my-user-name  /path/to/script

to /etc/crontab. As I have no permission to create files in /var/log/ the cron daemon will send me an email when the job fails.

After 1 minute there are no file. I go to a terminal and type mail:

$ mail
>N  1 Cron Daemon        Sat Jan 31 05:15   19/731   Cron <user@host>    /path/to/script
? type
...

/path/to/script: line 3: /var/log/foo.log: Permission denied

OK. My bad. I create the file and chown it to me. Now all is OK.

Have a look at these as well:

• Where are cron errors logged?
• What are the runtime permissions of a cron job?

$SOMEPATH isn't defined within cron, so your crontab line that tries to source /$SOMEPATH/some.env will fail. (Unless //some.env exists, that is.)

For debugging cron related issues, be aware that it writes stderr messages - including its own - to the local user's mailbox. If you don't have a mail client installed (mail or mailx) you could use something like this to read these messages:

less /var/mail/$USER

Or if you want to be really generic

"${PAGER:-less}" "${MAIL:-/var/mail/${USER:-${LOGIN:-$(whoami)}}}"