Re: Strange date problem

Subject: Re: Strange date problem
From: Ken Schweigert (ken@byte-productions.com)
Date: Mon Jan 28 2002 - 08:26:31 MST

Zeke,

This happened to me when I initially installed YDL and forgot to set the
date and the cron.daily logrotate script ran before I remembered to set it.

To keep from having this error in my logs, I just switched user to root,
deleted the state file and re-ran the logrotate script.
  [ken@byte-8 ken]$ su -
  Password:
  [root@byte-8 /root]# rm /var/lib/logrotate.status
  rm: remove `/var/lib/logrotate.status'? y
  [root@byte-8 /root]# /etc/cron.daily/logrotate
  [root@byte-8 /root]#

logrotate creates a new statefile if one doesn't exist.

Hope this helps. 

--
-Ken Schweigert, Aspiring Network Administrator
Byte Productions, LLC
http://www.byte-productions.com

On Sat, Jan 26, 2002 at 10:53:31AM -0500, Zeke Runyon wrote:
> When I run Pine as root to check it's mail, it says on startup: "[Unable 
> to parse internal date: 27-Aug-1956 21:16:38-LCL]". When I do pine as 
> another user, this doesn't happen. I've  sync'ed my time with the 
> nist.gov server many times, with both the hardware clock and system 
> clock.
> 
> I also get this message daily in root from the cron daemon:
> 
> "/etc/cron.daily/logrotate:
> 
> error: bad year 1956 for file /var/log/messages in state file 
> /var/lib/logrotate.status"
> 
> How do I fix this? Is my hardware clock battery dead? How do I find that 
> out?
> 
> :::
> 
> # Zeke Runyon, zrunyon@mac.com
> # web: communistsquirrel.home.dhs.org (formerly zekeworld)
> # linux: gloin.dyn.dhs.org
> # Mac OS X 10.1.2 5P48 | OS 9.2.1 | Yellow Dog Linux 2.1
> # Communist squirrels shall rule the world.
> 
>

This archive was generated by hypermail 2a24 : Mon Jan 28 2002 - 08:42:11 MST