Nagios Support Forum

check_procs is returning "Unable to read output" to my Nagios server. I am also getting that when I run the plugin directly from the shell. pst3 is in the libexec directory and is producing proper output.

The most puzzling thing is the other system running Solaris 11 returns the expected output for check_procs. It works exactly as intended. The binaries and permissions on the two machines for check_procs and pst3 are identical. Both of these machines are also built the same.

I have NAGIOS XI 2014R1.4 on an AWS instance running CentOS 6.5. The updates are being sent to the machine via NRDS. Here are the commands in the NRDS config and as run in the shell that produce expected output on one machine, but "Unable to read output" on the other:

• command[Procs]=/home/nagios/libexec/check_procs -w :350 -c :375
  command[Procs: CPU Hogs]=/home/nagios/libexec/check_procs -c :1 -P 50
  command[Procs: tnslsnr]=/home/nagios/libexec/check_procs -c 1: -a tnslsnr -u oracle

What happens when you run the command in verbose mode?

Box293 wrote:What happens when you run the command in verbose mode?

Code: Select all

check_procs -vvv

I see.. thank you Box293. What a headache. I have the nrds installed under the home directory, but it is looking for pst3 in /opt/.

Output:

My issue has now become reinstall NRDP or have check_procs look for the proper pst3 command?

I believe he was requesting that you run it locally from the cli on the nrdp sending server. We wanted to be sure that the plugin is actually compiled properly first.