Bug 593160

Summary: logrotate uses wrong file name format, logs are lost
Product: [Fedora] Fedora Reporter: William Estrada <mrumunhum>
Component: httpdAssignee: Joe Orton <jorton>
Status: CLOSED NOTABUG QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 12CC: dnovotny, jorton, pahan, tsmetana
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-05-18 12:22:47 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:
Attachments:
Description Flags
output of logrotate none

Description William Estrada 2010-05-18 02:16:20 UTC 
Created attachment 414706 [details]
output of logrotate

Description of problem:
Logrotate uses wrong logname format

Version-Release number of selected component (if applicable):


How reproducible:
use logrotate

Steps to Reproduce:
1.logrotate /etc/logrotate.d/httpd
2.
3.
  
Actual results:
He tries to rotate log.0,log.1,log.2,etc.

Old logs are lost


Expected results:
SHoud use log-yyyymmdd format


Additional info:
Comment 1 Daniel Novotny 2010-05-18 12:04:38 UTC 
$ rpm -qf /etc/logrotate.d/httpd 
httpd-2.2.14-1.fc12.i686

=> reassigning to httpd
Comment 2 Tomas Smetana 2010-05-18 12:18:40 UTC 
The "dateext" (yyyymmdd) suffix format is configured in the /etc/logrotate.conf file before the application specific configurations in /etc/logrotate.d directory are being processed.  Therefore if the user runs 'logrotate -f /etc/logrotate.d/httpd' the system-wide settings are not read and the old log format is being used because it's the hard-coded default.

I wouldn't consider this to be a bug at all.
Comment 3 Joe Orton 2010-05-18 12:22:47 UTC 
I agree with Tomas.