NRPE:Unable to read output

[snapon_admin]

Same problem.

[abrist]

Is the disk full? It is really odd as it builds the check_nrpe bin just fine, and then immediately has a stat error . . .

[snapon_admin]

Nope. Plus, you should know by now, I'm famous for my "odd" issues.

Code: Select all

[root@nagiosTEST nrpe-2.15]# df -h
Filesystem            Size  Used Avail Use% Mounted on
/dev/mapper/VolGroup-lv_root
                       97G   30G   63G  32% /
tmpfs                 3.9G     0  3.9G   0% /dev/shm
/dev/sda1             485M   50M  410M  11% /boot

[lmiltchev]

Let's try to get some more info. Run the following commands:

Code: Select all

./configure --enable-command-args | tee /tmp/configure.txt
make | tee /tmp/make.txt
make install | tee /tmp/make-install.txt

then post the three files, that were generated from running the above commands in the /tmp (configure.txt, make.txt, and make-install.txt).

[snapon_admin]

Attached.

[tmcdonald]

It *looks* like it made it this time. Let's find out:

Code: Select all

ls -l /usr/local/nagios/libexec/check_nrpe

[snapon_admin]

It definitely does look like it took it that time.

Code: Select all

-rwxrwxr-x 1 nagios nagios 76769 Jul 21 16:14 /usr/local/nagios/libexec/check_nrpe

But, it's still showing the "Unable to read output" alert as warning and not unknown. Here is my modifications to nrpe.c. Note, the line that needed to be changed wasn't on line 1389, but line 1370.

Code: Select all

else if(!strcmp(buffer,"")) {
                                snprintf(buffer,sizeof(buffer)-1,"NRPE: Unable to read output\n");
                                result=STATE_UNKNOWN;
                        }

[abrist]

What version of nrpe are you running?

[snapon_admin]

The one that I just downloaded to modify is 2.15.

[abrist]

Dang, I might have been testing on a local branch of the source. I will test this change on a virgin 2.15 clone.