Red Hat Bugzilla – Bug 78151
Logrotate sucks cpu when logrotate.status grows too large
Last modified: 2015-01-07 19:01:45 EST
From Bugzilla Helper: User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.1) Gecko/20020826 Description of problem: I had a previous problem with logrotate creating large numbers of files in /var/log/mailman. I deleted all of the log files, and everything was fine for a while. But now, logrotate just runs and sucks up cpu for no apparent reason. The /var/lib/logrotate.status file was about 18 MB long, so I deleted it. Now logrotate runs correctly. I haven't yet verified this fix on other machines. But I do have other users complaining about running logrotate processes again. Version-Release number of selected component (if applicable): How reproducible: Didn't try Additional info:
Not a high enough priority to investigate at this point, but patches welcome.
My logrotate on two RH Linux 7.3 boxes was 17MB and I found the logrotate deaemon taking up 99-100% USER on CPU0 (while CPU1 was idle) and TIME was 192.00 per TOP. I am deleting the /var/lib/logrotate.status file to see if helps. (What kind of silly place is /var/lib for this file !!!
Hi, I also went through the logrotate-cpu-mailman-okforawhile-logrotate.status-oknow cycle. I can just add that as logrotate.status grows large, logrotate sucks cpu EVEN IF you outcomment all lines in /etc/logrotate.conf Bye, Olivier
Anyone seen this problem lately (with FC2 or RHEL3, say)?