Closed
Bug 748369
Opened 12 years ago
Closed 12 years ago
Pull old preproduction machines
Categories
(Infrastructure & Operations :: RelOps: General, task)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: rail, Assigned: arich)
References
Details
preproduction-stage.build.sjc1.mozilla.com. preproduction-master.build.sjc1.mozilla.com. These VMs can be shut down and removed from monitoring. Thanks in advance.
Assignee | ||
Comment 1•12 years ago
|
||
The replacements aren't responding correctly to nagios checks yet. Have they been finished?
Assignee: server-ops-releng → arich
Assignee | ||
Comment 2•12 years ago
|
||
I've shut down the old vms. Nagios is still not functioning for the new ones, nor was there a request to move the dns CNAME for the bmo subdomain, so I haven't done that, either.
Reporter | ||
Comment 3•12 years ago
|
||
(In reply to Amy Rich [:arich] [:arr] from comment #2) > I've shut down the old vms. Nagios is still not functioning for the new > ones, nor was there a request to move the dns CNAME for the bmo subdomain, > so I haven't done that, either. Now I can see nrpe daemons running on both machines. Is there something else needed to be done to enable nagios checks?
Assignee | ||
Comment 4•12 years ago
|
||
The master is still failing several of its checks for various reasons: https://nagios.mozilla.org/nagios/cgi-bin/status.cgi?host=preproduction-master.srv.releng.scl3 The NRPE timeout for mysql is probably a misconfiguration for mysql or a missing flow. Not sure what the errors are with the queue checks (ask catlee?), and there are too many buildbot processes running. And the storage vm is missing a number of check definitions: https://nagios.mozilla.org/nagios/cgi-bin/status.cgi?host=preproduction-stage.srv.releng.scl3 Those should be in puppet if they're not.
Assignee | ||
Updated•12 years ago
|
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → FIXED
Updated•11 years ago
|
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.
Description
•