Debian 12 Cron Jobs Not Executing on Schedule

📖 ~1 min read

Table of contents

1. Symptom & Impact
2. Environment & Reproduction
3. Root Cause Analysis
4. Quick Triage
5. Step-by-Step Diagnosis
6. Solution – Primary Fix
7. Solution – Alternative Approaches
8. Verification & Acceptance Criteria
9. Rollback Plan
10. Prevention & Hardening
11. Related Errors & Cross-Refs
12. References & Further Reading

Symptom & Impact

Scheduled maintenance and automation scripts do not run, causing backlog and stale data.

Environment & Reproduction

Typical when scripts depend on interactive shell profiles or changed executable paths.

Root Cause Analysis

Cron uses limited environment and may reject malformed crontab syntax or missing permissions.

Quick Triage

Confirm cron service state and execute target script manually under same user.

Step-by-Step Diagnosis

Inspect syslog cron entries, crontab formatting, shebang lines, and PATH usage.

Solution – Primary Fix

Correct crontab syntax, use absolute paths, set explicit environment variables, and fix script perms.

Solution – Alternative Approaches

Use systemd timers for better dependency control and structured logging.

Verification & Acceptance Criteria

Job executes at expected interval and logs successful completion status consistently.

Rollback Plan

Restore previous crontab from backup and disable failing entries until corrected.

Prevention & Hardening

Standardize job wrappers, centralized logging, and periodic schedule validation tests.

Related Errors & Cross-Refs

CRON bad minute; command not found; permission denied executing script.

Related tutorial: View the step-by-step tutorial for debian-12.

View all debian-12 tutorials on the Tutorials Hub →

Browse all common problems & solutions on the Tutorials Hub.

References & Further Reading

crontab manual, Debian cron package docs, and systemd timer migration guides.