I had issues with cron. The jobs were not running, so it seemed. It turned out that they were in fact running. The jobs were firing off based on schedule. The problem was, cron didn’t have the correct path to the commands. I realized this when I looked at a couple of log files, in /var/mail and /var/log/syslog to look for clues. The fix was to include the path in cron.
Edit cron.
crontab -e |
Add the shell and path at the top of the file.
SHELL=/bin/sh PATH=/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin |
ben says
April 16, 2018 at 7:18 amWow, thanks for following up with this…. Oddly, I was burnt at the start of my Linux life with absolute paths (not including them) in cron. Ever since then I have been hyper diligent to always include them…. that said, I have never seen the method you mention, so thanks for the tip Ul.
Ulysses says
April 16, 2018 at 7:35 pmHey, anytime! It took me a couple months, and several failed jobs to realize they weren’t completing the job. It’s amazing what you can find with Google Search. You often wonder how sysadmins did their jobs in the old days.