π ~1 min read
Table of contents
Symptom & Impact
Application daemon does not start at boot, leaving dependent workloads unavailable.
Environment & Reproduction
Common with custom rc.d scripts missing proper REQUIRE/BEFORE metadata.
service -e
ls /usr/local/etc/rc.d
Root Cause Analysis
Incorrect rcorder dependency tags start service before prerequisites are ready.
Quick Triage
Run rcorder over scripts and inspect startup logs for dependency timing.
rcorder /etc/rc.d/* /usr/local/etc/rc.d/* | grep
Step-by-Step Diagnosis
Check rc script headers and required services for proper ordering semantics.
head -n 40 /usr/local/etc/rc.d/
grep -n '_enable' /etc/rc.conf

Solution – Primary Fix
Correct rc.d metadata and ensure required dependencies are enabled.
Still having issues? Our Server Management team can diagnose and resolve this for you. Get in touch for a free consultation.
vi /usr/local/etc/rc.d/
sysrc _enable=YES
service start

Solution – Alternative Approaches
Replace fragile rc scripts with supervised service wrappers where appropriate.
Verification & Acceptance Criteria
Service starts automatically after reboot and remains healthy.
reboot
service status
Rollback Plan
Revert rc.d script changes and start service manually while investigating.
Prevention & Hardening
Version-control rc scripts and run dependency validation before deployment.
Related Errors & Cross-Refs
service not found in rcorder, dependency failed, rc script exited with status 1.
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 rc scripting and rcorder dependency documentation.
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.