Debian 11 Cron Jobs Stop Running After Timezone Change

📖 ~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 jobs no longer execute as expected, delaying backups, reports, and routine maintenance tasks.

Environment & Reproduction

Issue appears after timezone modifications or migration from localtime assumptions in scripts.

Root Cause Analysis

Cron schedule interpretation changes while scripts still rely on old timezone or environment expectations.

Quick Triage

Check cron daemon status and review recent syslog entries for job launch attempts.

Step-by-Step Diagnosis

Run systemctl status cron, grep CRON /var/log/syslog, and inspect crontab lines for TZ handling and absolute paths.

Solution – Primary Fix

Set explicit TZ where needed, update script paths, restart cron, and run manual dry execution for key jobs.

Solution – Alternative Approaches

Move critical schedules to systemd timers for clearer timezone and dependency control.

Verification & Acceptance Criteria

Jobs execute at expected times and output artifacts appear consistently for two schedule cycles.

Rollback Plan

Revert timezone-sensitive cron edits and restore last working schedule definitions.

Prevention & Hardening

Standardize UTC scheduling and add execution heartbeat alerts for critical cron pipelines.

Related Errors & Cross-Refs

Watch for missing job logs and scripts failing due to relative path assumptions.

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

Consult cron man pages and Debian guidance on timezone management.