no longer seeing service

[JohnFLi]

Code: Select all

Installed Version:	2024R1.4.1

i have a service that Nagios has been seeing for awhile (few months)...over the weekend it no longer sees it as existing.

Code: Select all

 /usr/local/nagios/libexec/check_ncpa.py -H <hostname> -t 'token' -P 5693 -M 'services' -q 'service=dfs,status=running'
UNKNOWN: No services found for service names: dfs

I have tried dfssvc.exe, same result.
all other services it sees are just fine

dfs.jpg

[DoubleDoubleA]

Hi John,

Thanks for that note. What XI version are you on?

Aaron

[JohnFLi]

Code: Select all

Latest Available Version:	2024R1.4.1
Installed Version:	2024R1.4.1
Last Update Check:	03/10/2025 13:08:53

[DoubleDoubleA]

Hi John,

Try this: re-run the NCPA Wizard against that machine and see what services come up in the XI interface for the Wizard, and if you see NFS in any way, go ahead and configure monitoring for it, and see what the actual command comes out as.

Did that machine update? Did MS change the name and nobody saw the announcement?

We're also taking a look at making sure we know how NCPA is string matching there. I see you are on 2024R1.4.1 so clearly you have updated recently but nothing in that update should have affected checks or NCPA.

Aaron

[bbahn]

Hello @JohnFLi,

It seems you're having a matching issue. By default, NCPA only matches services with an exact match with the service name. To troubleshoot this, you can go into the NCPA web interface (https://my_ncpa_ip:my_port_usually_5693) and go to API and then select services from the dropdown and use the Service Filter(s) section to test out different matches.
Under filter settings, you can also modify whether you want exact match (default), search match (partial matches allowed), or regex matching.

If you're wondering how to construct a Nagios check with this information, get your filters to filter as you desire and then select the "Run as a Nagios check" button. This will show a View in alternate format button on the bottom from which you can select As active check using check_ncpa.py. This will show how to construct a check_ncpa.py CLI query to get the desired result from your NCPA API.

------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

Since you aren't passing any match= options into your check, it's looking for a strict match, so if the name of the service changes (it looks to me like that may have been what happened here. Also, it IS case sensitive when using strict matching (default)), it will no longer find it.

[JohnFLi]

Hi John,

Try this: re-run the NCPA Wizard against that machine and see what services come up in the XI interface for the Wizard, and if you see NFS in any way, go ahead and configure monitoring for it, and see what the actual command comes out as.

Did that machine update? Did MS change the name and nobody saw the announcement?

We're also taking a look at making sure we know how NCPA is string matching there. I see you are on 2024R1.4.1 so clearly you have updated recently but nothing in that update should have affected checks or NCPA.

Aaron

I did try that....it does not see it doing that either

[JohnFLi]

Hello @JohnFLi,

It seems you're having a matching issue. By default, NCPA only matches services with an exact match with the service name. To troubleshoot this, you can go into the NCPA web interface (https://my_ncpa_ip:my_port_usually_5693) and go to API and then select services from the dropdown and use the Service Filter(s) section to test out different matches.
Under filter settings, you can also modify whether you want exact match (default), search match (partial matches allowed), or regex matching.

If you're wondering how to construct a Nagios check with this information, get your filters to filter as you desire and then select the "Run as a Nagios check" button. This will show a View in alternate format button on the bottom from which you can select As active check using check_ncpa.py. This will show how to construct a check_ncpa.py CLI query to get the desired result from your NCPA API.

------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

Since you aren't passing any match= options into your check, it's looking for a strict match, so if the name of the service changes (it looks to me like that may have been what happened here. Also, it IS case sensitive when using strict matching (default)), it will no longer find it.

Case sensitve was teh issue.

Code: Select all

-q 'service=Dfs,status=running'
OK: Dfs is running

This issue may now be closed

[DoubleDoubleA]

Glad it is sorted, thanks for letting us know.