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