Support forum for Nagios Core, Nagios Plugins, NCPA, NRPE, NSCA, NDOUtils and more. Engage with the community of users including those using the open source solutions.
However, Nagios seems like it is unable to find the process at all. Any ideas?
What error is being returned to nagios?
Former Nagios employee
"It is turtles. All. The. Way. Down. . . .and maybe an elephant or two."
VI VI VI - The editor of the Beast!
Come to the Dark Side.
I heard the issue was related to an older version of NSClient so I upgraded the latest version. However, when I try to run a checkCPU command I am getting the following error on the Nagios GUI:
Check CPU
UNKNOWN 04-17-2013 21:57:56 0d 0h 7m 14s 4/10 CHECK_NRPE: No output returned from daemon.
What is listed in the configuration tab for this: check_nrpe_checkcpu!80%!90%!
but... when I run the command via CLI to test...
[root@nagios libexec]# ./check_nrpe -H 1.1.1.1 -c checkcpu -a warn=80
OK CPU Load ok.
Can you post your command definition for " check_nrpe_checkcpu"?
Former Nagios employee
"It is turtles. All. The. Way. Down. . . .and maybe an elephant or two."
VI VI VI - The editor of the Beast!
Come to the Dark Side.
It shows critical for some reason but I at least know that it is working now. However, when I run the command via CLI:
./check_nrpe -H x.x.x.x -c CheckProcState -a MinCritCount=0 ShowAll match=regexp cmdLine .*java.*fiseco.*=started
output:
OK: "java" -cp (+ the whole command line location)
Thanks for your help.
Last edited by and1100 on Thu Apr 18, 2013 6:29 pm, edited 1 time in total.
which I just use to check for the running Java processes shows up as critical on the GUI For 0.4.1 when the same exact syntax had previously worked in 0.3.9.
and1100 wrote:which I just use to check for the running Java processes shows up as critical on the GUI For 0.4.1 when the same exact syntax had previously worked in 0.3.9.
This sounds like a bug, I would recommend reporting your findings on the NSClient site as it is not managed by us.