Closed Bug 608334 Opened 14 years ago Closed 14 years ago

ntp1.build.mozilla.org no longer works

Categories

(mozilla.org Graveyard :: Server Operations, task)

Product:
mozilla.org Graveyard
Component:
Server Operations
Platform:
ARM
Maemo
Type:
task
Priority:
Not set
Severity:
critical

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: jhford, Assigned: ravi)

References

Details

This server is part of the mobile testing infrastructure and needs to be up. It doesn't matter which ntp server is there, but all n900-XXX hostnames on the build network need to be able to reach it with the name 'ntp1.build.mozilla.org'. Changing the name of this server would require generating a new filesystem image for the n900 (1-2 hours), validating it (1day) and flashing it to 90 devices (2-3 days). This blocks the deployment of 40 new slaves which are needed to enable try builds for maemo.
Assignee: server-ops → ravi
Status: NEW → ASSIGNED
border1 isn't currently answer ntp. Not a firewall or dns issue.
We disabled (filtered) NTP on this host months ago. ravi and I discussed this, and we're going to go ahead and spin up NTP on the build DNS servers internally.
I configured ns[12].infra.scl1 to be a time source and reconfigured ntp[12].build.mozilla.org to point to them respectively. I also configured ntp.build.mozilla.org to resolve to both IPs which may be a better hostname to use in the future. I tested synchronization successfully when I connected to build VPN.
Status: ASSIGNED → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
Product: mozilla.org → mozilla.org Graveyard
You need to log in before you can comment on or make changes to this bug.