Closed
Bug 421421
Opened 17 years ago
Closed 17 years ago
Tell nagios to forget about mothballed machines
Categories
(Release Engineering :: General, defect, P1)
Release Engineering
General
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: joduinn, Assigned: joduinn)
References
Details
Attachments
(2 files)
430 bytes,
patch
|
nthomas
:
review+
|
Details | Diff | Splinter Review |
584 bytes,
patch
|
Details | Diff | Splinter Review |
The following machines are currently monitored by nagios. Can you please have nagios stop monitoring:
bl-bldlnx03
moz180-win32-tbox
tb180-win32-tbox
xserve04
...before we power-down these machines?
Updated•17 years ago
|
Assignee: server-ops → oremj
Comment 1•17 years ago
|
||
This is all in CVS, so IT doesn't have to be involved here at all, as the files are on a cronjob to update. See the files in the tools/tinderbox-configs/monitoring/ directory under /cvsroot.
Write a patch yourself to remove them? :)
Comment 2•17 years ago
|
||
(In reply to comment #1)
> This is all in CVS, so IT doesn't have to be involved here at all, as the files
> are on a cronjob to update. See the files in the
> tools/tinderbox-configs/monitoring/ directory under /cvsroot.
Umm... no. He's talking about the machine monitoring, not the tinderbox status monitoring. That's all in the actual nagios config on bm-admin01, not in the public CVS.
Comment 3•17 years ago
|
||
(In reply to comment #2)
> Umm... no. He's talking about the machine monitoring, not the tinderbox status
> monitoring. That's all in the actual nagios config on bm-admin01, not in the
> public CVS.
Ah, n/m then. My apologies.
Comment 4•17 years ago
|
||
Don't see the following in the nagios configs:
bl-bldlnx03
moz180-win32-tbox
tb180-win32-tbox
I removed:
host:bm-xserve04.build:bm-admin01:build
Status: NEW → RESOLVED
Closed: 17 years ago
Resolution: --- → FIXED
Assignee | ||
Comment 6•17 years ago
|
||
I just powered off bl-bldlnx03, and got the following nagios alert?!? Where in nagios is this coming from?
-------- Original Message --------
Subject: ** PROBLEM alert - surf/tree - Firefox is CRITICAL **
Date: Mon, 17 Mar 2008 20:48:56 -0700 (PDT)
From: nagios@dm-nagios01.mozilla.org (nagios)
To: joduinn@mozilla.com
***** Nagios *****
Notification Type: PROBLEM
Service: tree - Firefox
Host: surf
Address: 10.2.74.116
State: CRITICAL
Date/Time: 03-17-2008 20:48:56
Additional Info:
CRITICAL: missing bl-bldlnx03 - perf test
Status: VERIFIED → REOPENED
Resolution: FIXED → ---
Comment 7•17 years ago
|
||
[root@surf tinderbox-monitoring]# grep -n bl-bldlnx03 *
Tier1_Firefox.txt:2:bl-bldlnx03|perf test|fx-linux-tbox
[root@surf tinderbox-monitoring]# cvs stat Tier1_Firefox.txt
===================================================================
File: Tier1_Firefox.txt Status: Up-to-date
Working revision: 1.12
Repository revision: 1.12 /cvsroot/mozilla/tools/tinderbox-configs/monitoring/Tier1_Firefox.txt,v
That's on your end.
Assignee: oremj → nobody
Status: REOPENED → NEW
Component: Server Operations → Build & Release
QA Contact: justin → build
Assignee | ||
Comment 9•17 years ago
|
||
Remove the mothballed machines from Tier1 page, to stop nagios paging about them. This is in addition to the work already done telling Nagios to ignore these machines.
Attachment #310189 -
Flags: review?(nrthomas)
Assignee | ||
Updated•17 years ago
|
Assignee: nobody → joduinn
Priority: -- → P1
Updated•17 years ago
|
Attachment #310189 -
Flags: review?(nrthomas) → review+
Comment 10•17 years ago
|
||
I also added the windows and mac debug builds which are also tier 1 on Build:Farm.
Checking in Tier1_Firefox.txt;
/cvsroot/mozilla/tools/tinderbox-configs/monitoring/Tier1_Firefox.txt,v <-- Tier1_Firefox.txt
new revision: 1.13; previous revision: 1.12
done
Assignee | ||
Updated•17 years ago
|
Status: NEW → RESOLVED
Closed: 17 years ago → 17 years ago
Resolution: --- → FIXED
Updated•11 years ago
|
Product: mozilla.org → Release Engineering
You need to log in
before you can comment on or make changes to this bug.
Description
•