Craig,
Let me clarify. I correct the time, and both "date" and "hwclock" both
show the correct time. I reboot the server and "date" is again 5 hours
slow.
On Thu, Aug 9, 2012 at 3:22 PM, Craig White <craig.white@xxxxxxxxxx> wrote:
> until you set your clock so that 'date' gives the right time, don't bother doing anything else. Once you get it set, then execute the hwclock --systohc
>
> Craig
>
> On Aug 9, 2012, at 1:08 PM, Russell Jones wrote:
>
>> Thanks, I tried again, rebooted, still 5 hours off slow. The second I
>> do "hwclock --hctosys" the time is fine. That's silly to have to do
>> that though, I feel like I am missing a configuration parameter
>> somewhere.
>>
>>
>>
>> [root@nod705 ~]# date
>> Thu Aug 9 10:06:36 CDT 2012
>>
>> [root@nod705 ~]# hwclock
>> Thu 09 Aug 2012 03:06:39 PM CDT -0.437183 seconds
>>
>>
>> [root@nod705 ~]# cat /etc/sysconfig/clock
>> # The ZONE parameter is only evaluated by system-config-date.
>> # The timezone of the system is defined by the contents of /etc/localtime.
>> ZONE="America/Chicago"
>> UTC=false
>> ARC=false
>>
>>
>>
>> [root@nod705 ~]# cat /etc/adjtime
>> 0.0 0 0.0
>> 0
>> LOCAL
>>
>>
>>
>>
>>
>> On Thu, Aug 9, 2012 at 2:56 PM, Craig White <craig.white@xxxxxxxxxx> wrote:
>>>
>>> On Aug 9, 2012, at 12:33 PM, Russell Jones wrote:
>>>
>>>> Hi all,
>>>>
>>>> I am having an issue with some older CentOS 5.3 servers. Every time
>>>> the server boots, it gives the error "Cannot access the hardware clock
>>>> by any known method", and then promptly sets the time 5 hours behind
>>>> the hardware clock, down to the second.
>>>>
>>>> After the system is up. "hwclock" works fine. hwclock --debug does not
>>>> show any error at all.
>>>>
>>>> The hardware clock is configured in local time. /etc/sysconfig/clock
>>>> is set to UTC=false and ZONE="America/Chicago". /etc/localtime is a
>>>> copy of Chicago's zone file. /etc/adjtime is configured with "LOCAL"
>>>> as the third row. I am at a loss as to what is causing this.
>>>>
>>>> Any assistance is appreciated! Thanks!
>>> ----
>>> Chicago is GMT +5 if I recall correctly so it would seem that perhaps a previous install used UTC=true to set the hwclock
>>>
>>> after you get the time set (date -s "08/09/2012 14:54:00" or whatever) then set the hwclock to system time
>>>
>>> hwclock --systohc
>>>
>>> Craig
>>>
>>> _______________________________________________
>>> CentOS mailing list
>>> CentOS@xxxxxxxxxx
>>> http://lists.centos.org/mailman/listinfo/centos
>> _______________________________________________
>> CentOS mailing list
>> CentOS@xxxxxxxxxx
>> http://lists.centos.org/mailman/listinfo/centos
>
> --
> Craig White ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ craig.white@xxxxxxxxxx
> 1.800.869.6908 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ www.ttiassessments.com
>
> Need help communicating between generations at work to achieve your desired success? Let us help!
>
> _______________________________________________
> CentOS mailing list
> CentOS@xxxxxxxxxx
> http://lists.centos.org/mailman/listinfo/centos
_______________________________________________
CentOS mailing list
CentOS@xxxxxxxxxx
http://lists.centos.org/mailman/listinfo/centos
