Closed Bug 1262820 Opened 8 years ago Closed 8 years ago

Add new nagios service for zeus-ldap-scl3

Categories

(Infrastructure & Operations :: MOC: Service Requests, task)

Product:
Infrastructure & Operations
Component:
MOC: Service Requests
Type:
task
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: jabba, Assigned: ryanc)

Details

Currently the new ldapproxy hosts in scl3 are alerting:
@nagios-scl3> jabba: ldapproxy1.dmz.scl3.mozilla.com:Zeus - Port 389 is CRITICAL - ERROR: Received noSuchName(2) error-status at error-index 1 Last Checked: 2016-04-07 06:11:52 PDT

I wasn't sure why this was happening, because the severs are definitely in zeus and taking traffic and working great. So I did a little poking and figured out what's up. We have zeus-ldap-phx1 and zeus-ldap-scl3 services in mozilla/services.pp

In phx1 both ldap slaves and ldapproxy servers used the same service, because both internal and external VIPs were on the external zeus load balancers. In scl3, however, we have ldapproxy servers on external zeus and ldap slave vip on internal zeus, so using the same check service for both no longer works.

I'm not sure the current convention on how this should be handled, but I would probably just clone the existing zeus-ldap-scl3 service and name the new one zeus-ldapproxy-scl3, and create a new hostgroup called ldapproxy-scl3 and make the ldapproxy1 and ldapproxy2.dmz.scl3 hosts be in the new host group and remove the old one. The new service would just look at external zeus instead of internal zeus.

Hope that makes sense. TL;DR. Need new ldap "Zeus - Port 389" check for ldapproxy hosts, checked on external scl3 zeus instead of internal scl3 zeus.
Hello,

Seeing the following two,

[rchilds@nagios2.private.scl3 mozilla]$ sudo ./check_zeussvc ldapmaster1.db.scl3.mozilla.com 389 zlb2.ops.scl3.mozilla.com
ldapmaster1.db.scl3.mozilla.com:389 UP(1)
> [rchilds@nagios2.private.scl3 mozilla]$ sudo ./check_zeussvc ldapproxy1.dmz.scl3.mozilla.com 389 zlb2.ops.scl3.mozilla.com
> ERROR: Received noSuchName(2) error-status at error-index 1
> [rchilds@nagios2.private.scl3 mozilla]$ sudo ./check_zeussvc ldapproxy2.dmz.scl3.mozilla.com 389 zlb2.ops.scl3.mozilla.com
> ERROR: Received noSuchName(2) error-status at error-index 1
[rchilds@nagios2.private.scl3 mozilla]$ sudo ./check_zeussvc ldap1.db.scl3.mozilla.com 389 zlb2.ops.scl3.mozilla.com
ldap1.db.scl3.mozilla.com:389 UP(1)
[rchilds@nagios2.private.scl3 mozilla]$ sudo ./check_zeussvc ldap2.db.scl3.mozilla.com 389 zlb2.ops.scl3.mozilla.com
ldap2.db.scl3.mozilla.com:389 UP(1)

Will commit a change for this momentarily.
Assignee: nobody → rchilds
Status: NEW → ASSIGNED
Committed in r116583.

15:45:42 <@nagios-scl3> ryanc: ldapproxy1.dmz.scl3.mozilla.com:Zeus External - Port 389 is OK - ldapproxy1.dmz.scl3.mozilla.com:389 UP(1) Last Checked: 2016-04-07 15:40:39 PDT

15:45:49 <@nagios-scl3> ryanc: ldapproxy2.dmz.scl3.mozilla.com:Zeus External - Port 389 is OK - ldapproxy2.dmz.scl3.mozilla.com:389 UP(1) Last Checked: 2016-04-07 15:45:40 PDT

All set.
Status: ASSIGNED → RESOLVED
Closed: 8 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.