Article ID: 926, created on Oct 6, 2008, last review on May 10, 2014

  • Applies to:
  • Plesk for Linux/Unix


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/
# mv /var/lib/ /var/lib/logrotate.status

29d1e90fd304f01e6420fbe60f66f838 a914db3fdc7a53ddcfd1b2db8f5a1b9c 56797cefb1efc9130f7c48a7d1db0f0c

Email subscription for changes to this article
Save as PDF