Please check ntp logs and configs in browserid stage

VERIFIED FIXED

Status

Cloud Services
Operations
--
major
VERIFIED FIXED
5 years ago
5 years ago

People

(Reporter: jrgm, Assigned: ckolos)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

5 years ago
With reference to https://bugzilla.mozilla.org/show_bug.cgi?id=817781#c4, I've been seeing some errors that would be explained by the server losing clock discipline. So, does `ntpq` and logs look ok on {web,sweb,sign}{1,2,3} in stage and production. e.g., are we really locked in to an ntp remote, or is that not reachable.
(Reporter)

Updated

5 years ago
Blocks: 817781
(Assignee)

Updated

5 years ago
Assignee: nobody → ckolos
(Assignee)

Comment 1

5 years ago
somewhere along the line the ntp server for adm1.stage was set to itself, so all hosts reporting to it for time were stuck in an INIT state. I changed the configuration to point to a valid ntp host and restarted NTP on all BiD stage hosts. All are showing valid status now.
Status: NEW → RESOLVED
Last Resolved: 5 years ago
Resolution: --- → FIXED
(Reporter)

Comment 2

5 years ago
Ah. Ok, thanks for figuring that out. And my errors went away shortly after that.
(Reporter)

Updated

5 years ago
Status: RESOLVED → VERIFIED
(Reporter)

Updated

5 years ago
Blocks: 818651
(Reporter)

Updated

5 years ago
Blocks: 819506
You need to log in before you can comment on or make changes to this bug.