Page 1 of 1

check_nt not monitoring a process

Posted: Mon Jun 24, 2019 9:03 am
by deek
Hi

We are trying to monitor a specific process on a given server. All other processes we are able to monitor but this process is running and we are not able to monitor with check_nt. Attached the snapshot for reference. Could you help us

Re: check_nt not monitoring a process

Posted: Mon Jun 24, 2019 9:25 am
by deek
checked with check_nrpe and still showing the process is stopped while it is actually running.

Re: check_nt not monitoring a process

Posted: Mon Jun 24, 2019 9:59 am
by lmiltchev
I was going to ask you to try check_nrpe instead of check_nt, but you already did that... :D

It is possible that NSClient++ doesn't have access/permissions to the "finsrv.exe" process. Is there any restrictions about the "tmmgr" user this process is running under?

Note: NSClient++ is not developed or maintained by us (Nagios). Since this is a very specific issue to NSClient++, I would recommend that you also ask your question on the NSClient++ support forum. You may resolve the issue faster this way.

You could also try our own agent - NCPA to see if it would detect the state of the process correctly.

For example, you could try:

Code: Select all

/usr/local/nagios/libexec/check_ncpa.py -H <client ip> -t 'mytoken' -P 5693 -M 'processes' -q 'name=finsrv.exe,match=search,check=true'

Re: check_nt not monitoring a process

Posted: Fri Jun 28, 2019 3:11 am
by deek
@ lmiltchev Thanks for the support. check_ncpa also didn't work. Let me get in touch with NSClient++ support forum

Re: check_nt not monitoring a process

Posted: Fri Jun 28, 2019 9:20 am
by lmiltchev
Sounds good.

By the way, do you see the "finsrv.exe" process in the output if you open a CMD prompt, and run the following command?

Code: Select all

tasklist

Re: check_nt not monitoring a process

Posted: Fri Jun 28, 2019 9:47 am
by deek
Yes it is there in the tasklist.

Re: check_nt not monitoring a process

Posted: Fri Jun 28, 2019 9:54 am
by lmiltchev
It's shown as "finsrv.exe", not some other name, right? If both agents, NSClient++ and NCPA don't see the process, it must be a permissions issue. Is there any restrictions about the "tmmgr" user this process is running under?