Closed Bug 380132 Opened 19 years ago Closed 19 years ago

mac tinderbox clocks are wrong

Categories

(Release Engineering :: General, defect, P2)

Product:
Release Engineering
Component:
General
Platform:
x86
macOS
Type:
defect

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: nthomas, Assigned: nthomas)

Details

It's about 15 minutes in the future at the moment, so you get warnings when pushing symbols up to the talkback server. What's our standard time-syncing solution for Macs ?
I'm guessing ntp based on bug 380235 (though that's a community machine).
Thanks Sam, but this particular machine is set up to use ntp with a box on the same part of the network. coop pointed out that Macs have this weird bug where they're set up to use ntp, but that doesn't actually work. When you open Date & Time in the System Preferences then the time then jumps back to the correct value. This looks interesting http://docs.info.apple.com/article.html?artnum=303731
unclear if this is a problem with a specific version of MacOSX... or will be fixed in new ref platform. Setting to p3 for now.
Priority: -- → P3
Assignee: build → nrthomas
Priority: P3 → P2
I have applied the Apple fix to bm-xserve04, and will check back in a few days to see how it's doing. The clock was about 3m 55s fast before this, but the drift rate is unknown. If the fix is applied to other boxes, we should just adjust /etc/ntp.conf and do step 12 (sudo SystemStarter -d restart "Network Time").
So far so good. If it continues to hold after a week or so then we'll look at rolling this out to all the Mac build machines.
Whiteboard: watching for clock drift over extended time.
Whiteboard: watching for clock drift over extended time. → fixed, watching for clock drift over extended time.
bm-xserve04's time is still good, so I'm going to apply this fix to all the build machines I can access (probably not the community ones).
I reduced the steps somewhat 1, sudo cp /etc/ntp.conf /etc/ntp.conf.bak-bug380132 2, sudo pico /etc/ntp.conf 3, remove minpoll & maxpoll & values, add "iburst" 4, sudo SystemStarter -d restart "Network Time" Fixed: bm-xserve01 - 5:15 fast bm-xserve02 - 0:29 fast bm-xserve04 - correct - modified to use setup above bm-xserve05 - recently dead bm-xserve07 - 0:20 fast bm-xserve08 - 2:54 slow bm-xserve09 - 8:23 slow bm-xserve10 - 8:45 slow bm-xserve11 - correct bm-xserve12 - 2:30 slow bm-xserve14 - 0:44 slow bm-xserve15 - correct 3 and 6 are now community boxes (says the Build:Farm wiki), 13 is now QA or community. 7 and up have NTP host set 10.2.71.5 instead of ntp1.build.mozilla.org, I've swapped them over. Could be that IT didn't know about our config when setting these boxes up. NB: Changing the ntp host in the System Preferences UI will revert the min/maxpoll ==> iburst changes. CC'ing Kairo & lilmatt in case they want to apply this fix too.
Status: NEW → RESOLVED
Closed: 19 years ago
Resolution: --- → FIXED
Summary: xserve04 clock is wrong → mac tinderbox clocks are wrong
Whiteboard: fixed, watching for clock drift over extended time.
I later had to come along and remove the iburst from /etc/ntp.conf on bm-xserve02 thru 05, because they had lost time syncing.
Product: mozilla.org → Release Engineering
You need to log in before you can comment on or make changes to this bug.