FreeBSD 14 – scheduled jobs not running because cron and periodic are misconfigured – 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

Recurring maintenance, backups, and reports fail silently, increasing operational risk.

Environment & Reproduction

Typically follows rc.conf cleanup or migration where scheduler service flags changed.

Root Cause Analysis

Cron service state, crontab syntax, or periodic configuration drift disrupts execution chain.

Quick Triage

Check scheduler service status and inspect recent log entries for skipped jobs.

Step-by-Step Diagnosis

Validate crontab ownership, PATH assumptions, and periodic daily/weekly scripts.

Solution – Primary Fix

Re-enable cron service, correct job definitions, and run controlled test execution.

Solution – Alternative Approaches

Move critical jobs to supervised task runners with explicit retry and alerting.

Verification & Acceptance Criteria

Scheduled tasks run at expected times and produce expected outputs.

Rollback Plan

Restore previous crontab and periodic configs from backup if new schedule fails.

Prevention & Hardening

Add heartbeat checks and job success telemetry for all critical schedules.

Related Errors & Cross-Refs

Related to script permission errors and missing environment variable incidents.

Related tutorial: View the step-by-step tutorial for FreeBSD 14.

View all FreeBSD 14 tutorials on the Tutorials Hub →

Browse all common problems & solutions on the Tutorials Hub.

References & Further Reading

FreeBSD cron and periodic subsystem documentation.