Debian 13 – cron jobs stop running due to anacron service disabled – Fix & Prevention

📖 ~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 tasks and reports are skipped, causing stale data and missed automations.

Environment & Reproduction

Appears after service cleanup or baseline hardening scripts disable cron-related units.

Root Cause Analysis

Cron daemon may run, but periodic catch-up behavior fails when anacron integration is missing.

Quick Triage

Confirm unit status, timers, and recent job logs in syslog or journal.

Step-by-Step Diagnosis

Validate crontab syntax, executable permissions, and system task directories.

Solution – Primary Fix

Enable and start cron/anacron services, then trigger a controlled job test.

Solution – Alternative Approaches

Migrate critical recurring jobs to systemd timers with explicit persistence semantics.

Verification & Acceptance Criteria

Test job runs and logs appear at expected schedule intervals.

Rollback Plan

Revert timer/service changes and restore previous scheduler model if conflicts emerge.

Prevention & Hardening

Include scheduler health checks in monitoring and protect units from accidental disablement.

Related Errors & Cross-Refs

Related to environment variable drift and PATH assumptions in non-interactive shells.

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

View all Debian 13 tutorials on the Tutorials Hub →

Browse all common problems & solutions on the Tutorials Hub.

References & Further Reading

Debian cron, anacron, and systemd timer best practices.