I have no idea why it comes up so far off, but do you have setupntp in your postscripts. At least that should help realign it over time. It does assume you have setup the MN as a ntp server.
Lissa K. Valletta 2-3/T12 Poughkeepsie, NY 12601 (tie 293) 433-3102 From: Russell Jones <[email protected]> To: <[email protected]> Date: 08/09/2012 05:59 PM Subject: Re: [xcat-user] Time issues with some stateless IBM nodes On 09.08.2012 16:51, Russell Jones wrote: Hi all, I am having an issue with time on some CentOS 5.2 dx360 M2 nodes. Whenever the node boots up, it's system time is consistently 5 hours, to the second, behind the hardware clock. In addition, it states at the top during bootup "Could not access the hardware clock via any known methods", and then right after that sets the system time to be exactly 5 hours behind the hardware clock. Details: * BIOS clock is set to local time properly, and maintains its time between reboots / power cycles. * /etc/localtime is set to Chicago properly * /etc/sysconfig/clock contains the following: TIMEZONE="America/Chicago" UTC=false ARC=false * /etc/adjtime contains the following: 0.0 0 0 0 LOCAL I've ran out of ideas on what is getting left behind that could be confusing the system clock. The site table's timezone is set to "America/Chicago" as well. I am unsure if this is a CentOS or xCAT configuration issue. Any brainstorming ideas on what I could try would be greatly appreciated. Thanks! Thought I would add in what the output looks like when this issue occurs: At boot: SELinux: Disabled at runtime. type=1404 audit(1344531308.511:2): selinux=0 auid=4294967295 ses=4294967295 INIT: version 2.86 booting Welcome to CentOS release 5.3 (Final) Press 'I' to enter interactive startup. Cannot access the Hardware Clock via any known method. Use the --debug option to see the details of our search for an access method. Setting clock : Thu Aug 9 11:55:08 CDT 2012 [ OK ] In the OS: [root@system ~]# date Thu Aug 9 11:56:05 CDT 2012 root@system ~]# hwclock Thu 09 Aug 2012 04:56:08 PM CDT -0.333130 seconds [root@system ~]# hwclock --debug hwclock from util-linux-2.13-pre7 Using /dev/rtc interface to clock. Last drift adjustment done at 0 seconds after 1969 Last calibration done at 0 seconds after 1969 Hardware clock is on unknown time Assuming hardware clock is kept in local time. Waiting for clock tick... /dev/rtc does not have interrupt functions. Waiting in loop for time from /dev/rtc to change ...got clock tick Time read from Hardware Clock: 2012/08/09 16:56:14 Hw clock time : 2012/08/09 16:56:14 = 1344549374 seconds since 1969 Thu 09 Aug 2012 04:56:14 PM CDT -0.756991 seconds ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ xCAT-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/xcat-user
<<inline: graycol.gif>>
------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________ xCAT-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/xcat-user
