Mastering crontab: Common Pitfalls, Debugging Tips, and Practical Examples

What is crontab?

crond is the Linux daemon that executes scheduled tasks, similar to Windows Task Scheduler. After installation it runs automatically and checks every minute for jobs to run.

Types of task scheduling

System tasks: periodic jobs such as cache flushing or log cleanup.

User tasks: jobs defined by individual users, stored in /var/spool/cron with filenames matching the usernames.

Common uses include data backup, system health checks, data collection, configuration updates, and report generation.

crontab command syntax

crontab [-u user] [file]
crontab [-u user] [-e|-l|-r|-i]

Options: -u user: operate on another user's crontab (requires root). file: read a file containing cron entries. -e: edit the current user's crontab. -l: list the current user's crontab. -r: remove the current user's crontab. -i: ask for confirmation before removal.

crontab entry format

minute hour day month week command

Fields:

minute : 0‑59 hour : 0‑23 day : 1‑31 month : 1‑12 week : 0‑7 (0 or 7 = Sunday) command : any shell command or script.

Special characters:

* – all possible values. , – list of values. - – range of values. / – step values (e.g., 0-23/2 every two hours).

Practical examples

0 */3 * * * /usr/local/apache2/apachectl restart

Restart Apache every three hours. 30 3 * * 6 /webdata/bin/backup.sh Run backup script at 03:30 every Saturday. 0 0 1,20 * * fsck /dev/sdb8 Check the disk on the 1st and 20th of each month.

10 5 */5 * * echo "" > /usr/local/apache2/log/access_log

Clean Apache access logs on the 5th, 10th, 15th, 20th, 25th, and 30th of each month at 05:10.

System‑wide crontab (/etc/crontab)

SHELL=/bin/bash
PATH=/sbin:/bin:/usr/sbin:/usr/bin
MAILTO=root
HOME=/
01 * * * * root run-parts /etc/cron.hourly
02 4 * * * root run-parts /etc/cron.daily
22 4 * * 0 root run-parts /etc/cron.weekly
42 4 1 * * root run-parts /etc/cron.monthly

The first four lines set environment variables; the remaining lines define scheduled tasks.

Online crontab parser

Tool for testing cron expressions and viewing next execution times: https://crontab.guru

Typical pitfalls and solutions

Environment variables : crontab runs with a minimal PATH ( /usr/bin:/bin). Use absolute paths or source the user profile, e.g., * * * * * source $HOME/.bash_profile && command.

Time field mistakes : * 2 * * * runs every minute during the 2 am hour. The correct expression for a single run at 02:00 is 0 2 * * *.

Special character % : The first % starts stdin; subsequent % are newlines. Escape with \% when needed.

Output redirection : Without redirection, cron output is mailed to the user. Suppress mail by setting MAILTO="" or redirect both stdout and stderr to /dev/null, e.g.,

0 * * * * /usr/local/apache2/apachectl restart >/dev/null 2>&1

.

Debugging workflow

Check /var/log/cron or journalctl -u crond to see if the job was triggered.

If not executed, verify the cron expression, environment variables, permissions, and special characters.

Confirm the crond service is running: systemctl status crond.service (systemd) or service crond status (SysVinit).

Redirect command output to a log file to capture errors, e.g.,

* * * * * python /path/script.py >> /tmp/script.log 2>&1

. Review the log for missing commands or other errors.