Confusion on nrpe

[Meyer, Bruce]

Hi Ed,
I don't have a problem getting it running. What I am not grasping is how to have it read the stats on the local machine and send it's data to the central monitoring server. I finally gave up trying to grasp the documentation and bought an e-book on Nagios. It was clear to me then that nrpe isn't for what I am trying to do, rather ncsa should be used in passive mode.

I appreciate your response.

Thank-you Sir,
--Bruce


From: Edwin Zoeller <Edwin.Zoeller at ama-assn.org<mailto:Edwin.Zoeller at ama-assn.org>>
Reply-To: Nagios Users List <nagios-users at lists.sourceforge.net<mailto:nagios-users at lists.sourceforge.net>>
To: "'nagios-users at lists.sourceforge.net<mailto:'nagios-users at lists.sourceforge.net>'" <nagios-users at lists.sourceforge.net<mailto:nagios-users at lists.sourceforge.net>>
Subject: Re: [Nagios-users] Confusion on nrpe

I run nrpe on both Linux and Solaris clients. Have you run the startup of nrpe on the client in debug mode? This should be straight forward, the only caverat I have run into is not having two security lib's installed.

Ed

From: Meyer, Bruce [mailto:bdmeyer at cio.sc.gov]
Sent: Monday, May 07, 2012 02:07 PM
To: Nagios Users List <nagios-users at lists.sourceforge.net<mailto:nagios-users at lists.sourceforge.net>>
Subject: Re: [Nagios-users] Confusion on nrpe

OS is CentOs on both.

From: <Meyer>, Bruce Meyer <bdmeyer at cio.sc.gov<mailto:bdmeyer at cio.sc.gov>>
Reply-To: Nagios Users List <nagios-users at lists.sourceforge.net<mailto:nagios-users at lists.sourceforge.net>>
To: Nagios Users List <nagios-users at lists.sourceforge.net<mailto:nagios-users at lists.sourceforge.net>>
Subject: [Nagios-users] Confusion on nrpe

I have been struggling with the documentation on nrpe.
It is very difficult to tell when the text is talking about configuring something on the monitoring server, and when the text is describing configuring something on the monitored device.

My goal for a group of machines behind a DMZ is to query some plugins, and send the reulsts from the Monitored servers TO the centralized Nagios server that displays the status of all ncsa, nrpe etc machines.
I thought that the purpose of NRPE was to fill this need.

Now I am starting to think that NRPE has nothing to do with this. Here is what I have tried:


I have a group of servers behind a dmz that I do not want Nagios to talk directly to.
Rather, I want these servers to send status info to the central nagios server outbound through the DMZ firewall.

I have nrpe installed on both the central nagios server, and also on the servers behind the DMZ.

I am not using xinetd, or inetd, rather a simple daemon.

To test if everything is working, from the command line on a server behind the dmz I enter:

/usr/local/nagios/libexec/check_nrpe -H (central server ip) -c check_users

And I get back the results that apply to the Central Monitoring server, not from the host..

If I swap the –H with localhost, I get back the correct info.

Is it possible to send the results from the DMZ machines to the Centralized Nagios server?

My goal is to send from servers behind dmz to the nagios server.

Thanks for any help.

--Bruce D. Meyer


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://www.monitoring-lists.org/archive/users/attachments/20120508/3b8bb2c7/attachment.html>
-------------- next part --------------
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
-------------- next part --------------
_______________________________________________
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