Bug 726980

Summary:	Logrotate complains that it can not set ACL:s
Product:	[Fedora] Fedora	Reporter:	Göran Uddeborg <goeran>
Component:	logrotate	Assignee:	Jan Kaluža <jkaluza>
Status:	CLOSED ERRATA	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	15	CC:	jkaluza, tsmetana
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Linux
Whiteboard:
Fixed In Version:	logrotate-3.7.9-14.fc15	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2011-08-09 01:31:45 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Göran Uddeborg 2011-07-31 17:48:42 UTC

Description of problem:
I've started to get complaints from logrotate that it can not set the ACL:s of log files. Like these:

/etc/cron.daily/logrotate:

error: setting ACL for /var/log/messages: Operation not supported

Yesterday it happened to /var/log/mythtv/mythbackend.log and today to /var/log/messages.

A side effect appears to be that the postrotate script isn't run. At least, yesterday mythbackend was still writing to mythbackend.log-20110730, and today rsyslogd was still writing to /var/log/messages-20110731. After manually executing the postrotate scripts in the corresponding files in logrotate.d, the daemons switched and started writing to the new file.

Version-Release number of selected component (if applicable):
logrotate-3.7.9-13.fc15.x86_64

How reproducible:
It has happened twice so far. I guess it happens every time there is a log to rotate, but I don't know for sure.

Steps to Reproduce:
1. Just let logrotate do its job.

Actual results:
Error messages as per above.

Expected results:
Properly rotated logs.

Additional info:
This happens on a diskless client, with the root file system, including /var/log, over NFS.

The command getfacl on some file on this filesystem returns something which looks sensible, but trying to use setfacl fails with an "Operation not supported".

I upgraded to the current version of logrotate last Thursday, so it seems likely the problem was introduced at that point.

When I run getfacl on /var/log/messages or /var/log/mythtv/mythbackend.log it only returns the regular permission bits, no additional ACL:s. So I don't see any obvious reason for logrotate to try to SET any ACL:s in the first place.

Comment 1 Jan Kaluža 2011-08-01 06:42:07 UTC

Thanks for report. I think the problem was there, but logrotate suppressed error messages when executed by cron. This changed in that update.


I've fixed it upstream and I will create packages soon.

Comment 2 Fedora Update System 2011-08-01 10:46:22 UTC

logrotate-3.7.9-14.fc15 has been submitted as an update for Fedora 15.
https://admin.fedoraproject.org/updates/logrotate-3.7.9-14.fc15

Comment 3 Fedora Update System 2011-08-02 02:02:59 UTC

Package logrotate-3.7.9-14.fc15:
* should fix your issue,
* was pushed to the Fedora 15 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing logrotate-3.7.9-14.fc15'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/logrotate-3.7.9-14.fc15
then log in and leave karma (feedback).

Comment 4 Göran Uddeborg 2011-08-07 13:34:01 UTC

Last night was the first night there was anything to rotate after the fix was released.  And it worked as it should.  The logs were rotated, no mails with any error messages, and e.g. rsyslogd has the new files open.

Everything seems fine! :-)

Comment 5 Fedora Update System 2011-08-09 01:31:41 UTC

logrotate-3.7.9-14.fc15 has been pushed to the Fedora 15 stable repository.  If problems still persist, please make note of it in this bug report.