Cron Jobs: The Ultimate Guide to Task Automation on Ubuntu

Step 1: Check System Updates (Best Practice)

Always ensure your system is up-to-date before configuring new services or tools.

Step 2: Understanding Crontab Files

Cron jobs are stored in `crontab` files. There are two main types:

• User-specific Crontabs: Each user on the system can have their own `crontab`. These are managed using the `crontab` command. This is the most common method for automating tasks related to a specific user's applications or files.
• System-wide Crontabs:
  • `/etc/crontab`: The main system-wide crontab.
  • `/etc/cron.d/`: A directory for individual cron files, often installed by packages.
  • `/etc/cron.hourly`, `/etc/cron.daily`, `/etc/cron.weekly`, `/etc/cron.monthly`: Directories where scripts are placed to run at predefined intervals by the system.

Step 3: Editing Your User Crontab

To add or modify cron jobs for your user, you use the `crontab` command.

Open your crontab for editing:

Add your cron job entries to this file. Each entry follows a specific format (explained next). Save and exit the editor (`Ctrl+O`, `Enter`, then `Ctrl+X` for `nano`).

Step 4: Understanding Cron Syntax (The Positional Values)

A cron job entry consists of five time fields, followed by the command or script to execute. The format is: minute hour day_of_month month day_of_week command

Special Characters:

• `*` (Asterisk): Matches every possible value for that field. E.g., `*` in the "minute" field means "every minute".
• `,` (Comma): Specifies a list of values. E.g., `1,15` in the "day of month" field means "on the 1st and 15th of the month".
• `-` (Hyphen): Specifies a range of values. E.g., `9-17` in the "hour" field means "every hour from 9 AM to 5 PM (inclusive)".
• `/` (Slash): Specifies step values. E.g., `*/5` in the "minute" field means "every 5 minutes". `*/2` in the "hour" field means "every other hour".

Special Strings (Shortcuts):

For convenience, you can use these instead of the five time fields:

• `@reboot`: Run once after system reboot.
• `@yearly` or `@annually`: Run once a year (`0 0 1 1 *`).
• `@monthly`: Run once a month (`0 0 1 * *`).
• `@weekly`: Run once a week (`0 0 * * 0`).
• `@daily` or `@midnight`: Run once a day (`0 0 * * *`).
• `@hourly`: Run once an hour (`0 * * * *`).

Step 5: Environment Variables in Cron

As mentioned in the warnings, cron jobs run with a very minimal environment. This is often the cause of scripts failing when run via cron but working perfectly manually.

You can define environment variables at the top of your `crontab` file, before any job definitions.

Common variables to set:

• `PATH`: Crucial! Specifies directories where executable programs are located. Your interactive shell has a long `PATH`, but cron's is much shorter.
• `SHELL`: The shell to use for executing commands (e.g., `/bin/bash` or `/bin/sh`).
• `MAILTO`: If set, cron will email output to this address. If empty (`MAILTO=""`), no email is sent.

How to get your current `PATH`:

Example of setting variables in `crontab`:

SHELL=/bin/bash
PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin
MAILTO=""

# Your cron jobs start here...

Step 6: Output Redirection & Logging

By default, cron emails any output from your commands to the user's local mail spool. To prevent this (and potential disk-filling), you should redirect output.

• Discarding all output: `> /dev/null 2>&1` (most common for silent tasks).
• Logging output to a file: `>> /path/to/logfile.log 2>&1` (appends both stdout and stderr).
• Logging errors only: `> /dev/null 2>> /path/to/error.log` (stdout discarded, stderr appended to error log).

Step 7: Practical Examples for Different Task Types

Here are common cron job scenarios. Remember to use absolute paths for everything!

A. Running a Bash Script

First, create your Bash script (e.g., `/home/ubuntu/scripts/daily_backup.sh`):

#!/bin/bash
# Script to perform a daily backup
BACKUP_DIR="/home/ubuntu/backups"
DATE=$(date +"%Y%m%d_%H%M%S")
mkdir -p $BACKUP_DIR

echo "Starting daily backup at $DATE..." >> $BACKUP_DIR/backup.log
tar -czvf $BACKUP_DIR/my_project_$(date +"%Y%m%d").tar.gz /var/www/my_project/ >> $BACKUP_DIR/backup.log 2>&1
echo "Backup finished." >> $BACKUP_DIR/backup.log

# Optional: Clean up old backups (e.g., older than 7 days)
find $BACKUP_DIR -name "*.tar.gz" -type f -mtime +7 -delete

echo "Old backups cleaned." >> $BACKUP_DIR/backup.log

Make the script executable:

Add to crontab (`crontab -e`): Run daily at 2:30 AM.

B. Running a PHP Script

Create your PHP script (e.g., `/var/www/html/my_app/process_queue.php`):

#!/usr/bin/php
<?php
    // Script to process a background queue
    $logFile = '/var/log/my_php_cron.log';
    file_put_contents($logFile, date('[Y-m-d H:i:s]') . " PHP queue processing started.\n", FILE_APPEND);

    // Simulate some work
    sleep(5);

    // Add your PHP application logic here
    // e.g., require_once __DIR__ . '/bootstrap.php';
    // (new App\QueueProcessor())->process();

    file_put_contents($logFile, date('[Y-m-d H:i:s]') . " PHP queue processing finished.\n", FILE_APPEND);
?>

Make the script executable:

Add to crontab (`crontab -e`): Run every 10 minutes.

C. Running a Java Program (JAR file)

Assume you have a compiled Java application in a JAR file (e.g., `/home/ubuntu/java_apps/my_java_processor.jar`).

Add to crontab (`crontab -e`): Run every hour at 15 minutes past the hour.

D. Fetching a URL (Website Request)

This is useful for triggering webhooks, internal APIs, or "pinging" your application's internal cron scheduler.

Add to crontab (`crontab -e`): Fetch a URL every 5 minutes.

E. Running a Python Script

Create your Python script (e.g., `/home/ubuntu/scripts/data_cleaner.py`):

#!/usr/bin/python3
import datetime
import sys

log_file = '/var/log/my_python_cron.log'

def log_message(message):
    with open(log_file, 'a') as f:
        f.write(f"[{datetime.datetime.now()}] {message}\n")

log_message("Python data cleaner started.")

# Simulate some data cleaning
# Example: delete old records from a database or clean temporary files
log_message("Simulating data cleaning for 10 seconds...")
import time
time.sleep(10)

log_message("Python data cleaner finished.")
sys.exit(0) # Exit successfully

Make the script executable:

Add to crontab (`crontab -e`): Run daily at 1:00 AM.

F. More Common Time-Based Examples

Directly in `crontab -e`:

# Every minute
* * * * * /usr/bin/command_every_minute

# Every 15 minutes
*/15 * * * * /usr/bin/command_every_15_minutes

# Every hour (at minute 0)
0 * * * * /usr/bin/command_every_hour

# Daily at 3:00 AM
0 3 * * * /usr/bin/command_daily_at_3am

# Weekly on Monday at 00:00 (midnight)
0 0 * * 1 /usr/bin/command_weekly_monday

# Monthly on the 1st day at 04:00 AM
0 4 1 * * /usr/bin/command_monthly_first_day

# Run at 8:00 AM and 5:00 PM every weekday (Monday-Friday)
0 8,17 * * 1-5 /usr/bin/command_weekday_morning_evening

# Using special strings (example for a daily task)
@daily /usr/bin/command_at_midnight_daily

Step 8: "Cron Job Creator" - Building Your Cron String

Manually constructing cron strings can be tricky. Use this helper to understand each field and build your command. For complex schedules, online cron expression generators are invaluable.

Step 9: Viewing and Deleting Cron Jobs

Manage your crontab entries once they are set.

View your current cron jobs:

Delete all your cron jobs: