Linux Server / Filesystems, LVM & Recovery
Preview Linux log rotation without changing files
Rapid log growth can stem from a failed rotation policy or an application that never reopens its log. Inspect rotation decisions first.
Environment and inputs: Linux server baseline · Ubuntu 24.04 LTS / RHEL 9-style systems. Use the specified distribution, init system and installed tool; service names, privileges and supported options can differ.
Start with this check
Confirm the host, shell and access role. Replace sample names, paths, domains and interfaces with approved targets. These are diagnostic commands; assess policy and workload impact before making changes.
logrotate --debug /etc/logrotate.confRead the result
Debug mode prints evaluation information without rotating logs or updating the state file. It still needs access to the relevant configuration and paths.
Resolve and verify
Compare the affected log policy, last rotation and application reopen behavior. Correct the narrow configuration and test the supported rotation path in an approved window.
Before changing production
Do not force rotation or delete active logs blindly; the application may retain open handles or require a specific post-rotation action.