Closed Bug 404275 Opened 17 years ago Closed 17 years ago

bl-bldxp01 is living a few minutes into the future

Categories

(Infrastructure & Operations :: RelOps: General, task)

Product:
Infrastructure & Operations
Component:
RelOps: General
Platform:
x86
Windows XP
Type:
task
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: philor, Assigned: justdave)

References

(
URL
)

Details

The clock on bl-bldxp01 must be a few minutes fast, since it just reported finishing a test run at 12:42, when the actual time was more like 12:38.
hmm. Nope. Just checked it, clock is accurate within a couple seconds currently, and ntpd is running.
Status: NEW → RESOLVED
Closed: 17 years ago
Resolution: --- → WORKSFORME
Huh, maybe I'm in a time-warp, or tock.usno.navy.mil is off? My clock is within a tenth of a second of that, and at 13:34:28 the bl-bldxp01 run which it claimed finished at 1195421879 (Sun Nov 18 2007 13:37:59 -0800) was visible on the waterfall page.
It does appear that the clock is 3-4 minutes fast on this machine. It's trying to timesync with NIST but the firewall probably prevents a connection. Is there an NTP server in the office that could be used ?
Status: RESOLVED → REOPENED
Resolution: WORKSFORME → ---
oh, my apologies, I misread the machine name and looked at bl-bldlnx01 instead, and it's fine. :) Sorry. Heading for the correct one now... :)
Assignee: server-ops → justdave
Status: REOPENED → NEW
And yeah, we do have a time server in the office (all the linux machines are using it). Fixed to use the office time server, and it did set the clock back about 4 minutes when I did it.
Status: NEW → RESOLVED
Closed: 17 years ago → 17 years ago
Resolution: --- → FIXED
Component: Server Operations: RelEng → RelOps
Product: mozilla.org → Infrastructure & Operations
You need to log in before you can comment on or make changes to this bug.