Closed Bug 629763 Opened 13 years ago Closed 13 years ago

decommission DNR hosts

Categories

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

Product:
Infrastructure & Operations
Component:
RelOps: General
Type:
task
Priority:
Not set
Severity:
minor

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: dustin, Assigned: mlarrain)

References

(
URL
)

Details

This system seems to be having disk problems?  It took forever to start up, refusing NRPE and SSH connections, and once it did start accepting those, it did so very slowly.  The first time running 'uptime' took a good 5-10 seconds.

This will need some investigation from server ops, I think.
moz2-darwin9-slave05 seems to have similar problems.
Summary: moz2-darwin9-slave40 *very* slow → moz2-darwin9-slave40, moz2-darwin9-slave05 *very* slow
Machines are now DNR'd
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → WONTFIX
So what does DNR mean from the point of view nagios/dns/etc ? I ask because moz2-darwin9-slave40 is still chirruping away in #build:
[77] moz2-darwin9-slave40.build.sjc1:PING is CRITICAL: PING CRITICAL - Packet loss = 100%
Hm, imho, DNR means we should decommission them and pull them from service.  I'll remove them from nagios.

These should be pulled from the racks.
Assignee: server-ops-releng → mlarrain
Status: RESOLVED → REOPENED
colo-trip: --- → sjc1
Resolution: WONTFIX → ---
Summary: moz2-darwin9-slave40, moz2-darwin9-slave05 *very* slow → decommission moz2-darwin9-slave40 and moz2-darwin9-slave05
The following are marked as DNR and should be decommissioned:

moz2-darwin9-slave05
moz2-darwin9-slave20
moz2-darwin9-slave40
moz2-darwin9-slave59
Summary: decommission moz2-darwin9-slave40 and moz2-darwin9-slave05 → decommission DNR hosts
try-mac-slave11
p3-linux01 (old dell or hp workstation likely in the mtv third floor server room)
bm-l10n-pmac-01 (see bug 625512) 
try-pmac-unit-01 (see bug 625512)
cm-bbot-leopard-003 is sick (see bug 631966)
I will go and pull all these machines today/tomorrow and build a fort around my desk with them till I can wipe there drives and pass them off.
    try-mac-slave11
    cm-bbot-leopard-003 

Unable to find the above machines. Will work with netops to switch hunt them down.
bug 631966 covers cm-bbot-leopard-003.  it got put on zandr's desk sometime back.
bug 655126 covers try-mac-slave11.  it was also on zandr's desk.
moz2-darwin9-slave10
all these machines have been pulled and are at my desk. I will figure out if we are going to wipe or drill these drives.
Severity: normal → minor
Closing because these machines are now tracked at 
https://docs.google.com/spreadsheet/ccc?key=0AnwZMiMU7toNdE5VQ2swUDJmLUhRR1gwb1pmd0FtMWc&hl=en_US#gid=0
URL: https://docs.google.com/spreadsheet/c...
Status: REOPENED → RESOLVED
Closed: 13 years ago → 13 years ago
Resolution: --- → FIXED
Being removed from slave-alloc in bug 700705.
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.