Think this could be bad?

[root@ccam1 ~]# hwclock --show
select() to /dev/rtc to wait for clock tick timed out

[root@ccam1 ~]# hwclock --systohc
select() to /dev/rtc to wait for clock tick timed out
[root@ccam1 ~]#

 

> -----Original Message-----
> From: Perfigo SecureSmart and CleanMachines Discussion List 
> [mailto:[log in to unmask]] On Behalf Of Michael Grinnell
> Sent: Friday, August 25, 2006 11:35 PM
> To: [log in to unmask]
> Subject: Re: Time Bug
> 
> See the thread "Time configuration on 4.0.2"
> 
> > A little poking around found that the timezone was set to PDT
> > (America/Vancouver) and while our system time was correctly 
> set to EDT 
> > (via the 'date' command) the hardware time kept getting reset to 
> > several hours in the past (hwclock --show).  I'm not sure what the 
> > official Cisco fix for this is, but I ran 'timeconfig' from the 
> > command prompt and just chose the right timezone there.
> 
> Also note bug CSCse91635
> System time changes after In-Place upgrade CCA system time 
> changes after performing In Place upgrade. The In- Place 
> upgrade installer treats the BIOS time as GMT and then 
> changes the system time.
> 
> If this is your issue, then ntpdate and hwclock --systohc is 
> your friend (I think that's the syntax).
> 
> On Aug 25, 2006, at 11:02 PM, King, Michael wrote:
> 
> > Just an FYI
> >
> > I've noticed since I've upgraded to 4.0.2 that my time goes back 6 
> > hours every time I reboot my CAM.
> >
> > It might have happened in 4.0.0, but Only tonight did I 
> reboot my box 
> > enough to notice (During my upgrade to 4.0.2)
> 
> Michael Grinnell
> Network Security Administrator
> The American University
>