NSClient++ Help (#1) - Issue monitoring process on windows (#143) - Message List
I need a little help configuring Nagios (client?) to monitor (non) existence of a process on a windows box (explorer.exe for example). I'm using client v0.3.1 and Nagios v3.0.1 with plugins v1.4.11 on Centos 5.1 server.
My request (or wish :-)) is: OK condition: explorer.exe IS NOT running CRITICAL condition: explore.exe IS running (Note that normal condition should be NON running prosess).
I get next (good) answer: CRITICAL:CRITICAL: explorer.exe: started (critical)
Check 1 gives next entries in NSC.log: debug:.\NSClient++.cpp:516: Injecting: CheckProcState: ShowAll, explorer.exe=stopped debug:.\NSClient++.cpp:536: Injected Result: CRITICAL 'CRITICAL: explorer.exe: started (critical)'
Check 2: - which I made remotely from nagios server: I run next command: check_nt -H 192.168.5.3 -p 12489 -v PROCSTATE -l "explorer.exe=stopped" -d SHOWALL
I get next (not ok) answer: explorer.exe: Running
Check 1 gives next entries in NSC.log: debug:.\NSClient++.cpp:516: Injecting: checkProcState: ShowAll, explorer.exe=stopped, nsclient debug:.\NSClient++.cpp:536: Injected Result: OK 'explorer.exe: Running'
(Where IP addresss 192.168.5.3 is my windows box).
Using nsc log on windows box, I've found the difference between Check 1 and Check 2. It's is in injecting command. Check 2 has an additional “,nsclient” at the end of injecting line (without quotes). Unfortunately, I can'f figure why there is ",nsclient" appearing in remote command and I don't know how to fix it. Please help.
when running from check_nt it uses the "regular nrpe" commands, some of them don't conform to the syntax of check_nt so there is a "compatibility mode" so in short: the listener for the check_nt incoming call will add it to the command.
So if you want to get rid of it USE NRPE instead of check_nt (it is better any ways :)
MickeMmickem05/08/08 11:52:02 (5 years ago)