Re: Unable to get check_nrpe to find process on Linux server
Posted: Fri Apr 24, 2015 10:18 am
Steve,
If you modify the nrpe.cfg file on your remote client like so:
Then run the following from the Nagios Server CLI:
Do you get proper output?
I want to clarify a little bit about what we're trying to do here.
When we set the 'command' variable in nrpe.cfg, the command (check_for_route_debug) is tied to the arguments that follow (/usr/local/nagios/libexec/check_procs -a 'Route /opt/nyfix/abim/current/config/appia FMPQA2-10011 DEBUG').
What this means is that from NRPE, we simply call the command:
And the NRPE client then runs the arguments that follow that command, and returns the output to Nagios.
This way, we don't pass any arguments through NRPE - it's handled on the client, which simplifies configuration and provides an additional layer of security.
Does that make sense? Let me know if you have any questions.
If you modify the nrpe.cfg file on your remote client like so:
Code: Select all
command[check_for_route_debug]=/usr/local/nagios/libexec/check_procs -a 'Route /opt/nyfix/abim/current/config/appia FMPQA2-10011 DEBUG'Code: Select all
./check_nrpe -H 10.10.205.69 -c check_for_route_debugI want to clarify a little bit about what we're trying to do here.
When we set the 'command' variable in nrpe.cfg, the command (check_for_route_debug) is tied to the arguments that follow (/usr/local/nagios/libexec/check_procs -a 'Route /opt/nyfix/abim/current/config/appia FMPQA2-10011 DEBUG').
What this means is that from NRPE, we simply call the command:
Code: Select all
./check_nrpe -H 192.168.1.1 -c check_for_route_debugThis way, we don't pass any arguments through NRPE - it's handled on the client, which simplifies configuration and provides an additional layer of security.
Does that make sense? Let me know if you have any questions.