Logrotate dies on 3-31-97

Logrotate dies on 3-31-97

Post by Scott Ellswor » Tue, 22 Apr 1997 04:00:00



Howdy all.

A rather bizzare problem showed up at the end of March.  I am using Logrotate
with my RedHat 4.1 distribution, and it seems to work quite nicely.

At the end of March, a number of files ended up with dates in the status file
of 3-31-97, which was then followed by error messages complaining about an
illegal date.  This killed logrotate cold.

It was easy to fix - I updated the dates to mid-april, and ran logortate
again.  We are now happy, and no problems have come up.  I am merely a tad
surprised that others did not have this problem, if it is an actual problem,
rather than pilot error.  I have not fiddled with the system much beyond
changing a few things to daily updates and such.

Scott


"When a great many people are unable to find work, unemployment
results" - Calvin Coolidge, (Stanley Walker, City Editor, p. 131 (1934))
"The barbarian is thwarted at the moat." - Scott Adams

 
 
 

Logrotate dies on 3-31-97

Post by Earl Fryma » Tue, 22 Apr 1997 04:00:00



> Howdy all.

> A rather bizzare problem showed up at the end of March.  I am using Logrotate
> with my RedHat 4.1 distribution, and it seems to work quite nicely.

> At the end of March, a number of files ended up with dates in the status file
> of 3-31-97, which was then followed by error messages complaining about an
> illegal date.  This killed logrotate cold.

<snip>

Go to http://www.redhat.com/support/docs/rhl/rh41-errata-general.html
and download the logrotate fix for bogus dates.

Earl Fryman

 
 
 

Logrotate dies on 3-31-97

Post by James Youngm » Wed, 23 Apr 1997 04:00:00



Quote:

>Howdy all.

>A rather bizzare problem showed up at the end of March.  I am using Logrotate
>with my RedHat 4.1 distribution, and it seems to work quite nicely.

>At the end of March, a number of files ended up with dates in the status file
>of 3-31-97, which was then followed by error messages complaining about an
>illegal date.  This killed logrotate cold.

Note that this package had been updated to logrotate-2.1-1.   A notice to this
effect appeared in the Errata and on the redhat-announce-list.

--
James Youngman       VG Gas Analysis Systems  The trouble with the rat-race
Before sending advertising material, read     is, even if you win, you're
http://www.law.cornell.edu/uscode/47/227.html         still a rat.

 
 
 

Logrotate dies on 3-31-97

Post by Scott Ellswor » Wed, 23 Apr 1997 04:00:00


[logrotate dies on 3-31-97]

Quote:>Go to http://www.redhat.com/support/docs/rhl/rh41-errata-general.html
>and download the logrotate fix for bogus dates.

I actually had done that before I posted.  I  made the mistake of reporting a
fixed bug once before, and it was a learning experience. :).

My assumption is that the bogus dates got put in there before I downloaded the
new version, and that for whatever reason, logrotate did not recover from the
problem.  The errata claims that it silently fixes the problem, but it is
quite possible I did something unusual in my setup that stymied it.

Scott


"When a great many people are unable to find work, unemployment
results" - Calvin Coolidge, (Stanley Walker, City Editor, p. 131 (1934))
"The barbarian is thwarted at the moat." - Scott Adams

 
 
 

1. Logrotate: "error: bad day 31" (RH4.1)

  Tom> Using Redhat 4.1, I get the following error email to root daily:

  Tom> error: bad day 31 for file /var/log/httpd/access_log in state file
  Tom> /var/lib/logrotate.status"

There is an update for this on ftp.redhat.com.

  Tom> I have searched DejaNews and found several references to installing
  Tom> logrotate-2.1-1.i386.rpm available at
  Tom> http://www.redhat.com/support/docs/rhl/rh41-errata-general.html#logro...

That's it.

  Tom> I have tried this a couple times including using rpm with --force to
  Tom> ensure reload.

Why?  Didn't it work?   If not, you should post the exact error
message.  I suspect initially you just tried to install the update.
You should be *upgrading* your logrotate package -- use the "-U" flag,
not the "-i" flag.

2. GDM errors

3. Apache dies on logrotate

4. I need a beefy stats program

5. kernel 2.0.31, Redhat 4.2; Dies starting XFree86

6. point a newbie in the right direction?

7. PC-NFS, printing, bannerpage. die.die.die

8. Los Angeles Web Spinners Meeting This Sat. - Topic: DNS

9. Zombie die die die

10. /ethan die,die,die

11. Patches against 2.0.31 (Re: List of bugs in 2.0.31)

12. 2.1.97 kernel wants 2.1.85 modutils which want 2.1.97....

13. Freeware (was Re: Die Netscape Die)