π ~1 min read
Table of contents
Symptom & Impact
Rapid log growth fills /var, causing service failures and write errors.
Environment & Reproduction
Seen during noisy daemon failures or debug-level logging left enabled.
df -h /var
ls -lah /var/log | sort -k5 -h
Root Cause Analysis
Unbounded log verbosity and insufficient rotation thresholds trigger disk exhaustion.
Quick Triage
Identify top log producers and stop the most disruptive source first.
du -sh /var/log/* | sort -h | tail -n 10
Step-by-Step Diagnosis
Review syslog.conf, newsyslog config, and repeating error signatures.
grep -n '^[^#]' /etc/syslog.conf
grep -n '^[^#]' /etc/newsyslog.conf

Solution – Primary Fix
Reduce verbosity, trigger rotation, and restart logging safely.
Still having issues? Our IT Solutions & Services team can diagnose and resolve this for you. Get in touch for a free consultation.
service syslogd restart
newsyslog -F
truncate -s 0 /var/log/

Solution – Alternative Approaches
Forward logs to centralized collector and keep local retention short.
Verification & Acceptance Criteria
Disk utilization stabilizes and key services recover without write failures.
df -h /var
tail -n 50 /var/log/messages
Rollback Plan
Re-enable previous logging levels temporarily if troubleshooting data is needed.
Prevention & Hardening
Set strict newsyslog policies and alert on rapid /var consumption trends.
Related Errors & Cross-Refs
No space left on device, write failed in /var/log, syslogd dropped messages.
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 syslogd/newsyslog manuals and logging architecture guidance.
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.