Linux Archive

Linux Archive (http://www.linux-archive.org/)
-   CentOS (http://www.linux-archive.org/centos/)
-   -   Strange issue with system time being off (http://www.linux-archive.org/centos/692372-strange-issue-system-time-being-off.html)

Russell Jones 08-09-2012 07:33 PM

Strange issue with system time being off
 
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!
_______________________________________________
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

08-09-2012 07:43 PM

Strange issue with system time being off
 
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.
>
So, it's obviously setting it to GMT.

> 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!

Wonder if there's some permission or ownership problem.... You might also
check in the BIOS, if some protection is turned on.

mark

_______________________________________________
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Russell Jones 08-09-2012 07:51 PM

Strange issue with system time being off
 
Thanks for the reply.

The hwclock can be set properly from the OS. No BIOS permissions to
even set for the clock, it's just a standard old 24 hour clock.


On Thu, Aug 9, 2012 at 2:43 PM, <m.roth@5-cent.us> wrote:
> 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.
>>
> So, it's obviously setting it to GMT.
>
>> 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!
>
> Wonder if there's some permission or ownership problem.... You might also
> check in the BIOS, if some protection is turned on.
>
> mark
>
> _______________________________________________
> CentOS mailing list
> CentOS@centos.org
> http://lists.centos.org/mailman/listinfo/centos
_______________________________________________
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Craig White 08-09-2012 07:56 PM

Strange issue with system time being off
 
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@centos.org
http://lists.centos.org/mailman/listinfo/centos

Russell Jones 08-09-2012 08:08 PM

Strange issue with system time being off
 
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@ttiltd.com> 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@centos.org
> http://lists.centos.org/mailman/listinfo/centos
_______________________________________________
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Craig White 08-09-2012 08:22 PM

Strange issue with system time being off
 
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@ttiltd.com> 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@centos.org
>> http://lists.centos.org/mailman/listinfo/centos
> _______________________________________________
> CentOS mailing list
> CentOS@centos.org
> http://lists.centos.org/mailman/listinfo/centos

--
Craig White ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ craig.white@ttiltd.com
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@centos.org
http://lists.centos.org/mailman/listinfo/centos

Russell Jones 08-09-2012 08:30 PM

Strange issue with system time being off
 
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@ttiltd.com> 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@ttiltd.com> 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@centos.org
>>> http://lists.centos.org/mailman/listinfo/centos
>> _______________________________________________
>> CentOS mailing list
>> CentOS@centos.org
>> http://lists.centos.org/mailman/listinfo/centos
>
> --
> Craig White ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ craig.white@ttiltd.com
> 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@centos.org
> http://lists.centos.org/mailman/listinfo/centos
_______________________________________________
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Russell Jones 08-09-2012 08:41 PM

Strange issue with system time being off
 
Also in case it wasn't clear, I have ran "hwclock --systohc" after
"date" shows the correct time.



On Thu, Aug 9, 2012 at 3:30 PM, Russell Jones <arjones85@gmail.com> wrote:
> 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@ttiltd.com> 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@ttiltd.com> 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@centos.org
>>>> http://lists.centos.org/mailman/listinfo/centos
>>> _______________________________________________
>>> CentOS mailing list
>>> CentOS@centos.org
>>> http://lists.centos.org/mailman/listinfo/centos
>>
>> --
>> Craig White ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ craig.white@ttiltd.com
>> 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@centos.org
>> http://lists.centos.org/mailman/listinfo/centos
_______________________________________________
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

08-09-2012 09:03 PM

Strange issue with system time being off
 
Russell Jones wrote:
> Also in case it wasn't clear, I have ran "hwclock --systohc" after
> "date" shows the correct time.
>
Please don't top post.

Here's a question: run hwclock, then, when you reboot, go into the BIOS,
and see what the time is.

mark
>
>
> On Thu, Aug 9, 2012 at 3:30 PM, Russell Jones <arjones85@gmail.com> wrote:
>> 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@ttiltd.com>
>> 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@ttiltd.com>
>>>> 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@centos.org
>>>>> http://lists.centos.org/mailman/listinfo/centos
>>>> _______________________________________________
>>>> CentOS mailing list
>>>> CentOS@centos.org
>>>> http://lists.centos.org/mailman/listinfo/centos
>>>
>>> --
>>> Craig White ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>>> craig.white@ttiltd.com
>>> 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@centos.org
>>> http://lists.centos.org/mailman/listinfo/centos
> _______________________________________________
> CentOS mailing list
> CentOS@centos.org
> http://lists.centos.org/mailman/listinfo/centos
>


_______________________________________________
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos

Russell Jones 08-09-2012 09:26 PM

Strange issue with system time being off
 
>
> Here's a question: run hwclock, then, when you reboot, go into the BIOS,
> and see what the time is.
>
> mark



Thanks Mark. "hwclock" showed the right time before reboot. After
reboot, entering BIOS it still showed the correct local time. After
the server came up, "date" is slow by 5 hours.


[root@nod705 ~]# date
Thu Aug 9 11:26:12 CDT 2012

[root@nod705 ~]# hwclock
Thu 09 Aug 2012 04:26:15 PM CDT -0.002574 seconds
_______________________________________________
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos


All times are GMT. The time now is 04:51 PM.

VBulletin, Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO ©2007, Crawlability, Inc.