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!
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
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
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
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
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,
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
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
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
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
Russell Jones wrote:
Here's a question: run hwclock, then, when you reboot, go into the BIOS, and see what the time is.
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.
Hmmm... and the BIOS doesn't have something that says use GMT? If not, sounds like there's a configuration file *somewhere* that's saying use GMT.
I'm out of here for the day. See if something comes to mind tonight....
mark
[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
On Thu, Aug 9, 2012 at 4:30 PM, m.roth@5-cent.us wrote:
Russell Jones wrote:
Here's a question: run hwclock, then, when you reboot, go into the BIOS, and see what the time is.
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.
Hmmm... and the BIOS doesn't have something that says use GMT? If not, sounds like there's a configuration file *somewhere* that's saying use GMT.
I'm out of here for the day. See if something comes to mind tonight....
mark
Nope, no timezone configuration options at all. Like I said, very strange. Usually time just "works" on a box.
Thanks for the help
On Aug 9, 2012, at 2:26 PM, Russell Jones wrote:
Here's a question: run hwclock, then, when you reboot, go into the BIOS, and see what the time is.
markThanks 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
---- something is changing your software clock.
You might want to reconfigure time...
yum install system-config-date system-config-date
you might want to check for funny entries in /etc/ntp.conf (is it running?) chkconfig --list ntpd ps aux|grep ntp
cat /etc/ntp/steptickers cat /etc/ntp.conf
Craig
On Thu, Aug 09, 2012 at 04:40:19PM -0700, Craig White wrote:
On Aug 9, 2012, at 2:26 PM, Russell Jones wrote:
Here's a question: run hwclock, then, when you reboot, go into the BIOS, and see what the time is.
markThanks 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.
Let's back up a bit. I bet Mr Jones, the OP, is in the US central time zone, which right now is 5 hours earlier than UTC. I'm betting the hardware clock is set to UTC, but that Centos believes that the hw clock is set to local time, i.e. CST6CDT. (That is how it would be set for Windoze.) There is some pitiful setting to correct the Windoze problem, and it is being applied. It shouldn't be.
Reboot, set bios clock to UTC. Then track down wherever Centos gets the idea that you have a dual boot windows machine whose clock is set to local time, and whack that.
I'm reasonably confident that this is the problem. The "exactly five hours off" is what clued me.
I think some others up-thread have been hinting about this, at least indirectly.
Dave
On Thu, Aug 9, 2012 at 6:59 PM, Woodchuck marmot@pennswoods.net wrote:
On Thu, Aug 09, 2012 at 04:40:19PM -0700, Craig White wrote:
On Aug 9, 2012, at 2:26 PM, Russell Jones wrote:
Here's a question: run hwclock, then, when you reboot, go into the BIOS, and see what the time is.
markThanks 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.
Let's back up a bit. I bet Mr Jones, the OP, is in the US central time zone, which right now is 5 hours earlier than UTC. I'm betting the hardware clock is set to UTC, but that Centos believes that the hw clock is set to local time, i.e. CST6CDT. (That is how it would be set for Windoze.) There is some pitiful setting to correct the Windoze problem, and it is being applied. It shouldn't be.
Reboot, set bios clock to UTC. Then track down wherever Centos gets the idea that you have a dual boot windows machine whose clock is set to local time, and whack that.
I'm reasonably confident that this is the problem. The "exactly five hours off" is what clued me.
I think some others up-thread have been hinting about this, at least indirectly.
Dave
The principles of accounting are not arbitrary. They are natural law. -- Mencius Moldbug
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Hi Dave, Robert,
Thanks for the help!
Dave: There are no options for time zones in the BIOS clock. The time is just "there" to be set. It is currently set to 7:08 PM, which is the current Central Time.
Robert: Great idea! I am fairly certain that is a good direction to go in. I will check this on Tuesday (next time I am in the office).
On Thu, Aug 09, 2012 at 07:11:02PM -0500, Russell Jones wrote:
On Thu, Aug 9, 2012 at 6:59 PM, Woodchuck marmot@pennswoods.net wrote:
Thanks for the help!
Dave: There are no options for time zones in the BIOS clock. The time is just "there" to be set. It is currently set to 7:08 PM, which is the current Central Time.
Set it to UTC, see what happens. Unix likes UTC.
Dave
Hello Mark,
On Thu, 2012-08-09 at 17:03 -0400, m.roth@5-cent.us wrote:
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.
I do agree. However Mark, perhaps *you* could trim your post too.
Regards, Leonard.
On 9 Aug 2012, at 22:03, "m.roth@5-cent.us" m.roth@5-cent.us wrote:
Please don't top post.
Please trim your replies.
Ben
Benjamin Donnachie wrote:
On 9 Aug 2012, at 22:03, "m.roth@5-cent.us" m.roth@5-cent.us wrote:
Please don't top post.
Please trim your replies.
I'm sorry, I thought I had. I usually manage that....
mark
on 8/9/2012 12:33 PM Russell Jones spake the following:
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!
Since you say "servers" do you have one that you can bring more current then 5.3 to see if there was a kernel patch or something that fixed this? Between 5.3 and Current (5.8) anything could have happened.
On Thu, 2012-08-09 at 15:35 -0700, Scott Silva wrote:
on 8/9/2012 12:33 PM Russell Jones spake the following:
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!
Since you say "servers" do you have one that you can bring more current then 5.3 to see if there was a kernel patch or something that fixed this? Between 5.3 and Current (5.8) anything could have happened.
What is in /etc/sysconfig/clock ?
cat /etc/sysconfig/clock ZONE="America/New_York" UTC=false ARC=false
On 08/09/2012 02: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.
Apparently something is amiss in the initramfs preventing access to the rtc, and once the real root filesystem is mounted, rtc access works. I'm not sure where to look or how an error might have crept in, but when I unpack my initramfs on a couple of systems (it's a compressed cpio archive) and grep for "rtc", I find:
./etc/modprobe.d/dist.conf:alias char-major-10-135 rtc ./etc/udev/rules.d/50-udev-default.rules:SUBSYSTEM=="rtc", DRIVERS=="rtc_cmos", SYMLINK+="rtc"
Hello Russell,
On Thu, 2012-08-09 at 14:33 -0500, Russell Jones wrote:
After the system is up. "hwclock" works fine. hwclock --debug does not show any error at all.
Have you tried adding --debug to CLOCKFLAGS in rc.sysinit to see if it reports anything for the first invocation?
Regards, Leonard.
On 08/09/2012 12:33 PM, Russell Jones wrote:
The hardware clock is configured in local time. /etc/sysconfig/clock is set to UTC=false and ZONE="America/Chicago".
What other settings are in that file?
The system is treating your hardware clock as if it were UTC. Actually setting it to UTC is probably the easiest fix (and possibly the best one).
Hi all,
After poking around a bit I ended up just going the /etc/ntp/step-tickers route to resolve the issue and have the time in-sync as soon as the OS comes up.
Thanks for all the help!
On Sat, Aug 11, 2012 at 7:15 PM, Gordon Messmer yinyang@eburg.com wrote:
On 08/09/2012 12:33 PM, Russell Jones wrote:
The hardware clock is configured in local time. /etc/sysconfig/clock is set to UTC=false and ZONE="America/Chicago".
What other settings are in that file?
The system is treating your hardware clock as if it were UTC. Actually setting it to UTC is probably the easiest fix (and possibly the best one).
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
-
Benjamin Donnachie -
Craig White -
Gordon Messmer -
Leonard den Ottolander -
m.roth＠5-cent.us -
Robert Nichols -
Ron Loftin -
Russell Jones -
Scott Silva -
Woodchuck