π ~1 min read
Table of contents
Symptom & Impact
Large app logs consume disk and can crash services that cannot write new log data.
Environment & Reproduction
Application writes to /var/log/myapp/*.log but no logrotate rule exists.
ls -lh /var/log/myapp
Root Cause Analysis
logrotate does not include custom path or postrotate reload hook is missing.
Quick Triage
Check cron or systemd timer execution and logrotate status file.
systemctl status logrotate.timer
cat /var/lib/logrotate/logrotate.status | tail -n 20
Step-by-Step Diagnosis
Run logrotate in debug mode to inspect rule matching.
logrotate -d /etc/logrotate.conf
grep -R myapp /etc/logrotate.d

Solution – Primary Fix
Create a dedicated logrotate policy and test forced rotation.
Still having issues? Our IT Solutions & Services team can diagnose and resolve this for you. Get in touch for a free consultation.
sudo tee /etc/logrotate.d/myapp >/dev/null <<'EOF'
/var/log/myapp/*.log {
daily
rotate 14
compress
missingok
notifempty
copytruncate
}
EOF
sudo logrotate -f /etc/logrotate.conf

Solution – Alternative Approaches
Shift logs to journald and control retention centrally.
Verification & Acceptance Criteria
Rotated files appear with compression and current log is truncated.
ls -lh /var/log/myapp
logrotate -d /etc/logrotate.conf
Rollback Plan
Remove custom rule if it conflicts with application logging behavior.
Prevention & Hardening
Require logrotate policy as part of every service deployment checklist.
Related Errors & Cross-Refs
Related to journald growth and permissions preventing compression.
Related tutorial: View the step-by-step tutorial for oracle-linux-10.
View all oracle-linux-10 tutorials on the Tutorials Hub β
Browse all common problems & solutions on the Tutorials Hub.
References & Further Reading
RHEL logrotate and service logging best practices.
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.