Closed Bug 914735 Opened 9 years ago Closed 9 years ago
Make sure we're checking DNS in SCL1
Let's audit the nagios checks we have in SCL1 for DNS. DNS runs on the admin servers in SCL1. admin1a.infra.scl1.mozilla.com admin1b.infra.scl1.mozilla.com
9 years ago
The individual admin nodes already had DNS checks in place, however the actual VIPs did not. According to DNS records RelOps only has the following nameserver VIPs in SCL1; ns-vip.build.scl1.mozilla.com (10.12.48.19) ns-vip.infra.scl1.mozilla.com (10.12.75.11) According to the DHCPD configuration all vlans are set to use one of the above VIPs for the nameservers (domain-name-servers) except vlan69. For the time being I added a PING and DNS check for (r74708.): ns-vip.build.scl1.mozilla.com ns-vip.infra.scl1.mozilla.com * All checks are green and also set to alert contact group "build". I also added a PING check for admin1.scl1.mozilla.com from Infra's scl3 nagios node. In terms of bug request, this is "Resolved/Fixed", however, will keep open as have 1-2 pending items. Those items being that we are not checking the same services that we check on infra's admin nodes; DHCP updates DHCPD Configuration Puppet catalog compilation Puppet freshness SSH Time Sync crond procs etc Will probably open new bugs for the above.
No longer blocks: re-nagios
Status: NEW → ASSIGNED
Re-adding block (seems bugzilla didn't mid-air for me...)
Following revisions submitted to fix the remaining (missing) checks and other slight modifications. 80449 80452 80457 80460 All green on nagios.
Status: ASSIGNED → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
Product: mozilla.org → mozilla.org Graveyard
You need to log in before you can comment on or make changes to this bug.