Cron Jobs on Ubuntu: Schedule Any Task Like a Pro

Clean up temporary files that file conversion tools create:

# Every hour, delete temp files older than 1 hour
0 * * * * find /tmp/reformat -type f -mmin +60 -delete 2>/dev/null

# Every day at 4am, delete old log files
0 4 * * * find /var/log/myapp -name "*.log" -mtime +30 -delete

# Every 15 minutes, check disk space and alert
*/15 * * * * /usr/local/bin/disk-check.sh

Monitor your application and restart it if it goes down:

sudo nano /usr/local/bin/health-check.sh

#!/bin/bash
SERVICE="myapi"
URL="http://127.0.0.1:8000/health"

HTTP_CODE=$(curl -s -o /dev/null -w "%{http_code}" --max-time 10 $URL)

if [ "$HTTP_CODE" != "200" ]; then
    echo "$(date): $SERVICE is down (HTTP $HTTP_CODE). Restarting..." >> /var/log/health-check.log
    systemctl restart $SERVICE
fi

chmod +x /usr/local/bin/health-check.sh
crontab -e
# Check every 2 minutes
*/2 * * * * /usr/local/bin/health-check.sh

This is a simple but effective uptime monitor. For production systems, pair this with an external monitoring service like UptimeRobot or Betterstack.

Cron jobs fail silently by default. Here's how to debug:

1. Always redirect output to a log file:

* * * * * /path/to/script.sh >> /var/log/myjob.log 2>&1

2. Check cron daemon logs:

grep CRON /var/log/syslog | tail -20

3. Common problems:

• PATH is different — cron runs with minimal PATH. Use full paths:

  # Bad

  python script.py
  # Good
  /usr/bin/python3 /home/deploy/script.py
  

• Environment variables missing — cron doesn't load your .bashrc. Source them:

  * * * * * source /home/deploy/.env && /path/to/script.sh

  

• Permission denied — make sure the script is executable:

  chmod +x /path/to/script.sh

  

4. Test by running the exact cron command manually:

/bin/bash -c '/path/to/your/cron/command'