404275 - bl-bldxp01 is living a few minutes into the future

Status: RESOLVED FIXED

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

Description

[Phil Ringnalda (:philor)]

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.

Comment 1

[Dave Miller [:justdave]]

hmm.  Nope.  Just checked it, clock is accurate within a couple seconds currently, and ntpd is running.

Comment 2

[Phil Ringnalda (:philor)]

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.

Comment 3

[Nick Thomas [:nthomas] (UTC+12)]

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 ?

Comment 4

[Dave Miller [:justdave]]

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... :)

Comment 5

[Dave Miller [:justdave]]

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.