Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 85969 - logrotate enters inconsistent state if /var is full prior to run
logrotate enters inconsistent state if /var is full prior to run
Product: Red Hat Linux
Classification: Retired
Component: logrotate (Show other bugs)
i686 Linux
medium Severity high
: ---
: ---
Assigned To: Elliot Lee
Jay Turner
Depends On:
  Show dependency treegraph
Reported: 2003-03-11 12:46 EST by Jeff Lawson
Modified: 2015-01-07 19:04 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2003-03-25 13:36:20 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Jeff Lawson 2003-03-11 12:46:49 EST
Description of problem:
The lograte utility enters inconsistent state if /var is full prior to run. It 
creates a 0 byte file at "/var/lib/logrotate.status". On subsequent runs (even 
once there is space available on /var) it aborts with the error "error: error 
reading top line of /var/lib/logrotate.status"

This causes any new logs to not be archived and potentially be lost entirely.

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

# /usr/sbin/logrotate -v
logrotate 3.5.9 - Copyright (C) 1995-2001 Red Hat, Inc.

# rpm -qa | grep logr

How reproducible:

Steps to Reproduce:
1. fill /var
2. run logrotate


1. rm /var/lib/logrotate.status
2. touch /var/lib/logrotate.status
3. /usr/sbin/logrotate /etc/logrotate.conf

Actual Results:  logrotate aborts with error

Expected Results:  logrotate rotates logs
Comment 1 Jeff Lawson 2003-03-25 12:46:16 EST
This appears to have been fixed in 3.6.1 of logrotate, meaning that RedHat 7.3 
includes this updated version.  We're running RedHat 7.2, for which the latest 
version is logrotate-3.5.9-1

Note You need to log in before you can comment on or make changes to this bug.