Bug 1320096

Summary:	psacct will start after logrotate, even though it is disabled by chkconfig
Product:	Red Hat Enterprise Linux 6	Reporter:	masanari iida <masanari.iida>
Component:	psacct	Assignee:	Jan Rybar <jrybar>
Status:	CLOSED ERRATA	QA Contact:	Branislav Náter <bnater>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	6.8	CC:	bnater
Target Milestone:	rc	Keywords:	EasyFix
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:	psacct-6.3.2-69.el6	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-03-21 11:41:09 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description masanari iida 2016-03-22 10:05:27 UTC

Description of problem:
psacct will start the accounting everytime after the logroate,
even though it is disabled by chkconfig.

This bug was reported on RHEL5 (BZ#447028),  
but the fix was not forward ported on RHEL6.

Version-Release number of selected component (if applicable):
psacct-6.3.2-63.el6_3.3.x86_64 from RHEL6.8 Beta iso.

Additional informatoin.
On RHEL5,  /etc/logroate.d/psacct

postrotate
  if [ -f /var/lock/subsys/psacct ]; then
  /usr/sbin/accton /var/account/pacct
  fi
endscript
}

On RHEL6,  /etc/logroate.d/psacct

postrotate
  /usr/sbin/accton /var/account/pacct
endscript
}

Comment 1 Ondrej Vasik 2016-03-22 10:13:30 UTC

Thanks for report, confirmed, however as RHEL 6 is entering production phase 2 with RHEL 6.9 update, I can't guarantee this will get prioritized for fix. In RHEL 7, psacct logrotate file is much better, rewritten, so issue doesn't occur there.

Comment 8 errata-xmlrpc 2017-03-21 11:41:09 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHBA-2017-0770.html