nrpe installation on clients

Andreas Ericsson ae at op5.se
Thu Jun 10 12:23:12 CEST 2004


Kerry Cox wrote:
> On Wed, 2004-06-09 at 15:07, Marc Powell wrote:
> 
>>Only the NRPE client, it's config file and the specific plugins you
>>intend to use. NRPE really isn't that difficult to get going.
> 
> 
> Right, which is what I did. However, the docs with NRPE did not specify
> that the check_* scripts needed to be on the remote host as well. I had
> to figure that out.

nrpe --help, as well as the message at the end of compilation tells you 
exactly that. Also, it might not be too far fetched to say that it 
actually should be pretty obvious when you configure it (and yes, it's 
mentioned in the config file as well).

> The Nagios FAQ page is good for most debugging but I
> think it ignores this fact.

Nagios and NRPE are two different projects. Ethan has left NRPE to me so 
he can focus on Nagios. I've added a README to NRPE which explains how 
things are and how they should be configured.
When I find the time, I'll make a man-page out of it as well.

> And yes, it is an easy matter to simply tar all the scripts up and place
> them on whatever box you want. I am simply partial to the bblient script
> included with Big Brother. It's fairly automated.
> 

This might be included with NRPE v2.2

> 
>>>regarding setting up the client. Again, I had to have the check_*
>>>scripts on the remote client for the Nagios host to see anything.    
>>
>>Nagios has to be able to run the plugin on the remote machine so you
>>must put plugins there that are specific to the OS and architecture. It
>>can't just push the plugin and have it execute on the remote machine
>>because a) that's very very insecure and b) it could be a completely
>>foreign architecture (try running an ELF compiled program on WinXP).
>>Once you've defined the basics of what you want to monitor on each
>>machine and how you want to monitor it, it's a trivial task to create a
>>tarball to put all the necessary files in the correct places, presuming
>>the architecure and OS are the same across the board.
> 
> 
> Right. Again, it sounded like the entire Nagios program had to be
> installed, but if you only need the plugins, then couldn't you just
> simply create a /usr/local/nagios/libexec directory and run them there?

You can put it anywhere you want, so long as you configure nrpe properly.

> Otherwise, I like Nagios and am working to migrate all the monitoring to
> it specifically. I would just like to reduce the amount of time involved
> in getting the clients set up.

You can make a script to propagate it you know. It's really not that 
hard. If I get around to writing one, I'll include it with the next version.

> Thanks.
> KJ
> 

-- 
Andreas Ericsson
OP5 AB
+46 (0)733 709032
andreas.ericsson at op5.se


-------------------------------------------------------
This SF.Net email is sponsored by: GNOME Foundation
Hackers Unite!  GUADEC: The world's #1 Open Source Desktop Event.
GNOME Users and Developers European Conference, 28-30th June in Norway
http://2004/guadec.org
_______________________________________________
Nagios-users mailing list
Nagios-users at lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nagios-users
::: Please include Nagios version, plugin version (-v) and OS when reporting any issue. 
::: Messages without supporting info will risk being sent to /dev/null





More information about the Users mailing list