Linux Log Rotation Explained: Manage Server Logs with logrotate Safely

Linux Log Rotation Logrotate is a practical skill for IT professionals managing Linux servers, web applications, cloud instances and internal infrastructure. This tutorial is written for readers who already know basic commands and want a more useful, real-world workflow.

Why log rotation matters

Logs are essential for troubleshooting, but they can fill disk space if not managed. A full root partition can break services, databases and package updates.

What logrotate does

logrotate rotates, compresses, removes and manages old log files based on rules. Most Linux distributions use it automatically for many system logs.

Where configuration lives

Global settings are usually in /etc/logrotate.conf, while application-specific rules are commonly stored in /etc/logrotate.d/.

Testing logrotate safely

Use debug mode before forcing rotation. This helps confirm what logrotate would do without accidentally removing important logs.

Best practices

Keep enough log history for troubleshooting, compress old logs, monitor disk usage and coordinate with compliance or security requirements before deleting logs.

Useful Linux commands

ls -lh /var/log
du -sh /var/log/*
cat /etc/logrotate.conf
ls /etc/logrotate.d/
sudo logrotate -d /etc/logrotate.conf
sudo logrotate -f /etc/logrotate.conf

Best-practice checklist

• Test changes in a lab or staging server first.
• Take backups before editing important configuration files.
• Document commands, config paths and service changes.
• Monitor logs after restarting or reloading services.
• Use least privilege and avoid unnecessary root sessions.

Final thoughts

Linux administration improves with practice and a repeatable process. Save the commands, build a small lab and test each workflow before using it on production servers.

Educational note: This tutorial is for learning purposes. Always test carefully and avoid applying changes to production systems without approval, backups and a rollback plan.