📖 ~1 min read
Table of contents
Symptom & Impact
Security and maintenance tasks rely on periodic and cron, and missed runs increase operational risk.
Environment & Reproduction
No daily security emails appear, logs stop rotating, and housekeeping tasks are outdated.
Root Cause Analysis
cron disabled, broken crontab syntax, mail delivery issues, or incorrect periodic variables are typical.
Quick Triage
Run service cron onestatus, inspect /var/log/cron, and execute periodic daily manually to test pipeline.
Step-by-Step Diagnosis
Confirm daemon state and recent run timestamps in logs. image_ref=0

Solution – Primary Fix
Enable cron with sysrc cron_enable=”YES”, fix crontab syntax, and retest using periodic daily output checks. image_ref=1
Still having issues? Our IT Solutions & Services team can diagnose and resolve this for you. Get in touch for a free consultation.

Solution – Alternative Approaches
Control scheduler with service cron start|restart and verify rc.conf persistence after reboot.
Verification & Acceptance Criteria
Tune /etc/periodic.conf variables for security checks and ensure root mail alias is valid.
Rollback Plan
Permit outbound SMTP relay if periodic output depends on external mail forwarding.
Prevention & Hardening
Run periodic daily and check successful completion plus expected report delivery path.
Related Errors & Cross-Refs
Track cron heartbeat jobs and alert when periodic reports are missing for a defined window.
Related tutorial: View the step-by-step tutorial for freebsd-13.
View all freebsd-13 tutorials on the Tutorials Hub →
Browse all common problems & solutions on the Tutorials Hub.
References & Further Reading
Consult man periodic, man cron, man crontab, and FreeBSD administration guides.
Need Expert Help?
If you cannot resolve this yourself, our team offers hands-on Server Management, Managed IT Services, and flexible Support Plans. Contact us today — we respond within one business day.