Why is my cron.daily script not running?
Over the years when setting up servers I have run into the various ways that your cron.daily or cron.hourly scripts manage to fail to run. Today I ran into a new reason which I don't recall running into before, maybe something has changed or maybe I just never ran into it.
I ran into the problem on a Ubuntu 16.04 LTS server - I placed a script in
/etc/cron.daily/my_script.sh but it was not running.
I checked all the usual suspects, the reasons I was aware of that cause a cron script to be ignored:
- The script must have the
- The script did not depend on certain environment variables being set (for example if you rely on
$HOMEto be set, you may need to define it yourself). Cron scripts do not have all the same environment variables that you have when you are logged in to a shell, so the script can work when you run it but fail when cron runs it.
- The script did not rely on a customized
PATHto execute commands. The
PATHthat cron gives your script will be minimal, and if you have made customizations to it they may not show up. The best way around this is to use the full path to your commands (use the
whichcommand to help figure this out).
But my problem was not any of the above. I found that you can execute the
run-parts command in a test mode to see which scripts it would call in a directory. You can run it like this (it will not execute any of the scripts, it just outputs which ones it would execute):
run-parts --test /etc/cron.daily
My script was not listed in the output! Well, that was comforting at least but why was it not listed? It turns out you cannot have a file extension on the script, so by renaming the script from
my_script it works!
Like this? Follow me ↯Tweet Follow @pfreitag
Why is my cron.daily script not running? was first published on January 10, 2018.
If you like reading about cron, linux, unix, or shell then you might also like:
- The 15 Essential UNIX commands
- Bash Loop To Wait for Server to Start
- Recursively Counting files by Extension on Mac or Linux
- Howto Backup your Mac incrementally over SSH
- Unix Job processing
- Top 20 Internet Security Vulnerabilities of 2005
Want Security Advisories via Email?
Advisory Week is a new weekly email containing security advisories published by major software vendors (Adobe, Apple, Microsoft, etc).
The run-parts and extension tips did the trick. One thing., my scheduled backup command starts with '$(which duplicity)'
Is there a way that I can verify it will work when cron runs it?
I've got a lot of experience work with RH/CentOS, and only have a couple of servers with Debian. Little differences like this one can drive you nuts (sames script on the other servers works fine with the extension).
The post is spot on !