Home / server / Questions / 767034
Accepted
thepocketwade
Asked: 2016-03-31 05:05:45 +0800 CST

NRPE: Command line success vs Web error

  • 772

I've got about 10 machines configured with nrpe and Dell's OMSA to report to nagios. For each of those machines, output on the command line from the nagios server a la

./check_nrpe -H $HOSTNAME -c check_om_tag

matches the output I see in the web interface.

I've got one machine, though, that returns successful output from the command line on the nagios server, but on the web interface reports

NRPE: Unable to read output.

Every discussion I can find of the "unable to read output" error assumes that the command always fails, whether command line or web and suggests permissions or SELinux fixes. But the command line success should mean I don't have permissions or SELinux issues. Does anyone have experience with this kind of mismatch?

EDIT:

Success on command line on Nagios server

Error for client in Web interface

nagios

1 Answers

  1. Best Answer

    Well, this turns out to be much ado about nothing. After combing the logs, I found Nagios sending requests to an IP that doesn't belong to any of the configured servers. Double checked the configuration for this particular client, and it was wrong. Fixing that, of course, fixed the weird error mismatching.

    • 0