Debian 11 – cron jobs stop running due to anacron or timer overlap

📖 ~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 execute as expected.

Environment & Reproduction

Frequent on systems mixing cron jobs with systemd timers and anacron.

Root Cause Analysis

Environment differences, overlap suppression, or failed cron daemon state blocks execution.

Quick Triage

Check service state and recent cron logs for execution evidence.

Step-by-Step Diagnosis

Validate job syntax, PATH assumptions, and file permissions.

Solution – Primary Fix

Correct cron environment declarations, ensure executable scripts, and restart scheduler services.

Solution – Alternative Approaches

Migrate critical jobs to systemd timers for stronger observability and dependency control.

Verification & Acceptance Criteria

Jobs execute on schedule and produce expected output/artifacts.

Rollback Plan

Restore previous crontab from backup if new schedule behavior is incorrect.

Prevention & Hardening

Use absolute paths and centralized monitoring for job runtime and failures.

Related Errors & Cross-Refs

Related symptoms include missed backups and stale report generation pipelines.

Related tutorial: View the step-by-step tutorial for Debian 11.

View all Debian 11 tutorials on the Tutorials Hub →

Browse all common problems & solutions on the Tutorials Hub.

References & Further Reading

Debian cron, anacron, and systemd timer documentation.