KB Parallels: Sometimes a logrotate process might take a lot of CPU resources. What could be wrong?

Resolution

It might happen because Logrotate saves information about all the files ever processed in /var/lib/logrotate.status. If this file is too big, then, Logrotate spends a lot of time for reading and checking each entry. In this case you can clean up logrotate.status with the following command lines:

# grep -v '"/usr/local/expand/var/log/action/act_' /var/lib/logrotate.status > /var/lib/logrotate.status.new
# mv /var/lib/logrotate.status.new /var/lib/logrotate.status

Parallels

Sometimes a logrotate process might take a lot of CPU resources. What could be wrong?

Resolution

Please provide feedback on this article