Now that the try server queue has been shortened these machines need to go back to their regular home. This isn't a rush request, but it would be great if you could get to it this week.
I will be at the data center tomorrow to take care of this.
Assignee: server-ops → phong
moz2-darwin9-slave03 10.2.71.141 moz2-darwin9-slave04 10.2.71.142 moz2-darwin9-slave08 10.2.71.163 bm-xserve12 10.2.71.12 I just need the following ports moved to vlan 71 and a quick reboot. asx103-07b:0/38 asx103-07b:0/01 asx103-07b:0/48 core1:4/15
Derek: pass this back to me when you're done.
Assignee: phong → dmoore
The four ports listed above have been moved to the build network (vlan 71)
Assignee: dmoore → phong
[phong@boris ~]$ ping bm-xserve12.build PING bm-xserve12.build.mozilla.org (10.2.71.12) 56(84) bytes of data. 64 bytes from bm-xserve12.build.mozilla.org (10.2.71.12): icmp_seq=1 ttl=64 time=1.28 ms [phong@boris ~]$ ping moz2-darwin9-slave04.build PING moz2-darwin9-slave04.build.mozilla.org (10.2.71.142) 56(84) bytes of data. 64 bytes from moz2-darwin9-slave04.build.mozilla.org (10.2.71.142): icmp_seq=1 ttl=64 time=1.18 ms [phong@boris ~]$ ping moz2-darwin9-slave03.build PING moz2-darwin9-slave03.build.mozilla.org (10.2.71.141) 56(84) bytes of data. 64 bytes from moz2-darwin9-slave03.build.mozilla.org (10.2.71.141): icmp_seq=1 ttl=64 time=1.29 ms [phong@boris ~]$ ping moz2-darwin9-slave08.build PING moz2-darwin9-slave08.build.mozilla.org (10.2.71.163) 56(84) bytes of data. 64 bytes from moz2-darwin9-slave08.build.mozilla.org (10.2.71.163): icmp_seq=1 ttl=64 time=14.7 ms
Status: NEW → RESOLVED
Last Resolved: 10 years ago
Resolution: --- → FIXED
REOPENing - the nagios tests for moz2-darwin9-slave03/04/08 haven't gone green since these machines moved back to the build LAN. The PING tests report moz2-darwin9-slave03: CRITICAL - Host Unreachable (10.2.71.200) moz2-darwin9-slave04: CRITICAL - Host Unreachable (10.2.71.201) moz2-darwin9-slave08: CRITICAL - Host Unreachable (10.2.71.219) The other tests return "Connection refused or timed out". Those IPs don't match comment #2 (which is also what I get back from the DNS server 10.2.74.125) so the nagios server needs some help.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
update nagios and it should be looking for the hosts on the new IPs now.
Status: REOPENED → RESOLVED
Last Resolved: 10 years ago → 10 years ago
Resolution: --- → FIXED
Thanks Phong, working now. Nagios notifications re-enabled for those three machines.
Status: RESOLVED → VERIFIED
Product: mozilla.org → mozilla.org Graveyard
You need to log in before you can comment on or make changes to this bug.