Nagios Support Forum

Good morning,

I was attempting to fix an issue I was having with some Service Cluster checks we built yesterday and I think I may have hosed something up.

Here's the command: check_service_cluster!"ADMIN-AD ADCluster"!1!2!$SERVICESTATEID:gc1.admin-ad:NTDS$,$SERVICESTATEID:gc2.admin-ad:NTDS$!!!!

Attached is what it looks like in CCM. When I Run Check Command from that screen it shows: [nagios@nagiosxi ~]$ /usr/local/nagios/libexec/check_cluster --service -l "ADMIN-AD ADCluster" -w 1 -c 2 -d $SERVICESTATEID:gc1.admin-ad:NTDS$,$SERVICESTATEID:gc2.admin-ad:NTDS$ CLUSTER OK: ADMIN-AD ADCluster: 2 ok, 0 warning, 0 unknown, 0 critical

For some reason though, all 16 of the service clusters we built are showing '2 unknown' and are in a Warning status even though they show OK when we run the check command.

Please PM me a copy of your profile (you can download the zip file from Admin > System Profile > Download Profile) so that I can validate all of the info.

This is because the NTDS service description was changed from NTDS (more than likely) to Active Directory Domain Services OR the NTDS service was deleted OR you didn't use the nagios service description and instead used the actual service name of the service.

Either way, please edit your service and change all occurrences of NTDS with Active Directory Domain Services for it to work.

Save, Apply Config, Test.

That should do it.

Yes, I did check the check from Active Directory Domain Services to NTDS.

The reason I did that is because it didn't seem like the check was reporting correctly with Active Directory Domain Services as the name of the service.

As you can see, it only returns 1 ok. Shouldn't it be 2 ok since we're checking the service on two different servers?

[nagios@nagiosxi ~]$ /usr/local/nagios/libexec/check_cluster --service -l "ADMIN-AD ADCluster" -w 1 -c 2 -d $SERVICESTATEID:gc1.admin-ad:Active Directory Domain Services$,$SERVICESTATEID:gc2.admin-ad:Active Directory Domain Services$ CLUSTER OK: ADMIN-AD ADCluster: 1 ok, 0 warning, 0 unknown, 0 critical

I believe having the check configured this way, the warning and critical thresholds will not work properly. We want it to warn when one service goes down and go critical when both go down.

Please PM a fresh copy of your profile, it looks proper from my end.

Ok, the Host you're looking for is named ADMIN-AD_AD. It's only reporting 1 ok.

So, if one of the services goes does the check goes critical. We don't want that.

I just PM'd you the updated profile.

It certainly looks proper to me still, matches the format exactly and the service exists with that name... hmm.

For testing, try changing these values on the service to:
- Make sure to change all 3, they are all different
Then apply config and see if it's working, if it's still not working, please create a ticket for this and include a link back to this forum thread so we can get a remote session setup:

https://support.nagios.com/tickets/

Still coming back as only 1 ok:

[nagios@nagiosxi ~]$ /usr/local/nagios/libexec/check_cluster --service -l ADMIN-AD_ADCluster -w 3 -c 1 -d $SERVICESTATEID:gc1.admin-ad:Active Directory Domain Services$,$SERVICESTATEID:gc2.admin-ad:Active Directory Domain Services$ CLUSTER OK: ADMIN-AD_ADCluster: 1 ok, 0 warning, 0 unknown, 0 critical

I really don't think that's going to report properly when there's an issue.

Oh, wait, you cannot run this from the command line to check it or by using the Test Check Command button.

You need to apply configuration and force a check, that's likely why.

Ok yeah, it's showing correctly on the Service Status Detail screen.

That's weird, why does it behave that way? Showing 1 ok when you run the check command, but 2 ok on the Service Status Detail page.