Issue
I have a bash script foo.sh located in the /etc/cron.daily directory, chmoded 700, owned by root, crontab list for the root user is unchanged (crontab -l) from the core Debian installation. I did run cronjob in another way than crontab -l and/or crontab -e (eg I did not restart cron daemon with /etc/init.d/cron as adviced in the specific Debian's case). Despite a test job file is running under similar conditions. The script is debugged and can be run as a standalone task without returning errors. I've also checked logs (/var/log/syslog) and nothing wrong in there.
But: this particular job is not executed at all.
Solution
Oops. Guess I found the "why" or at least, the "how" :
Only renaming the job filename without ".sh" extension solved that issue.
I thought it was a Debian's bug but it isn't, as described in the other answers below.
SOLUTION: rename your script by removing all . or + characters from its name
Answered By - hornetbzz
