Bug 1213143

Summary: log files compressed with xz but end in .gz
Product: Red Hat Enterprise Linux 7 Reporter: Peter Portante <pportant>
Component: logrotateAssignee: Jan Kaluža <jkaluza>
Status: CLOSED DUPLICATE QA Contact: qe-baseos-daemons
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 7.1   
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-04-24 11:27:08 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:
Embargoed:
Attachments:
Description Flags
/etc/logrotate.conf
none
/etc/logrotate.d/syslog
none
/etc/logrotate.d none

Description Peter Portante 2015-04-19 11:57:52 UTC 
# file /var/log/messages*.gz
/var/log/messages-20150315.gz: XZ compressed data
/var/log/messages-20150323.gz: XZ compressed data
/var/log/messages-20150329.gz: XZ compressed data
/var/log/messages-20150406.gz: XZ compressed data
/var/log/messages-20150412.gz: XZ compressed data
#
#
# # Shouldn't those files end in .xz?
Comment 2 Jan Kaluža 2015-04-20 06:50:39 UTC 
What's in your /etc/logrotate.conf and /etc/logrotate.d/syslog config files, please?
Comment 3 Peter Portante 2015-04-20 11:04:04 UTC 
Created attachment 1016322 [details]
/etc/logrotate.conf
Comment 4 Peter Portante 2015-04-20 11:05:03 UTC 
Created attachment 1016323 [details]
/etc/logrotate.d/syslog
Comment 5 Jan Kaluža 2015-04-24 06:34:41 UTC 
Could you create tarball containing all files in /etc/logrotate.d/* and attach it here? The problem is probably in some config file in /etc/logrotate.d/ directory which sets "compress" globally.
Comment 6 Peter Portante 2015-04-24 11:20:36 UTC 
Created attachment 1018416 [details]
/etc/logrotate.d

Created via:

# cd /etc
# tar cf /tmp/logrotate.d.tar logrotate.d
Comment 7 Peter Portante 2015-04-24 11:23:45 UTC 
Yes, it is glusterfs* files that seem to be causing this.
Comment 8 Jan Kaluža 2015-04-24 11:27:08 UTC 
There's already bugreport against glusterfs. I will close this bug as duplicate of glusterfs Bug 1172542.

*** This bug has been marked as a duplicate of bug 1172542 ***