Closed
Bug 1006349
Opened 12 years ago
Closed 12 years ago
wrong cmos time for b-2008-sm-0002
Categories
(Infrastructure & Operations :: RelOps: General, task)
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: massimo, Assigned: afernandez)
References
Details
b-2008-sm-0002 has a wrong clock setting.
coop: "Every time it reboots, its clock gets set back to UTC. Not sure if it's relevant, but running |w32tm /query /source| tells me the time is coming from the CMOS clock." (https://bugzilla.mozilla.org/show_bug.cgi?id=1005427#c2)
| Reporter | ||
Updated•12 years ago
|
Blocks: b-2008-sm-0002
Comment 1•12 years ago
|
||
We need the clocks to be set to PDT. I've give this to aj in hopes that he's seen this issue before on other seamicros and knows a fix.
Assignee: relops → afernandez
Comment 2•12 years ago
|
||
I logged in to the chassis to take a look at the clock, and it's reporting the correct time AND using ntp:
seamicro-c1# show clock
Wed May 7 05:00:30 PDT 2014
seamicro-c1# show ntp
remote refid st t when poll reach delay offset jitter
==============================================================================
*10.22.0.6 64.246.132.14 2 u 923 1024 377 0.312 -0.421 0.057
+10.22.0.7 72.20.40.62 3 u 626 1024 377 0.999 -0.048 0.266
I don't see anything about separately setting the time on the blades, though there is a note:
"Note: On internal servers, you cannot execute the OS command “hwclock --systohc” to set the current system time to the hardware real time clock (RTC). This is because there is only one physical RTC in the chassis, which resides on the SM card."
| Assignee | ||
Comment 3•12 years ago
|
||
As per Amy's troubleshooting, things are correctly configured on the chassis side.
Seems there's a Windows setting that needs to be set/check to make sure that it DOESN'T use the CMOS clock for timing.
If there's a Windows node I could check to troubleshoot (ie reboot when needed etc), please let me know and point me to login (gpg).
| Assignee | ||
Comment 4•12 years ago
|
||
After further discussion in irc, I am troubleshooting the issue with node 0 in the chassis.
| Assignee | ||
Comment 5•12 years ago
|
||
Test(s) results:
node 0 already has CentOS6.x installed, booting into single user mode and correct time was obtained:
[root@seamicro-test1 /]# date
Mon May 12 09:42:13 PDT 2014
# hwclock
Mon 12 May 2014 09:43:06 AM PDT -0.770300 seconds
Having some issues with kickstarting in specific vlans (in order to test a fresh "live" system). Will update again with results.
Comment 6•12 years ago
|
||
Going to wontfix this because we're working around it at the OS level.
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•