Centralizing NRPE Configuration

kyle.odonnell at gmail.com kyle.odonnell at gmail.com
Tue Nov 27 13:51:32 CET 2007


We have NRPE running over NFS.

-Kyle

On 11/26/07, Kevin Scott Sumner <ksumner at physics.unc.edu> wrote:
> Robert,
>
> I second Aaron's CFengine suggestion.
>
> Moving an infrastructure towards using something like CFengine or puppet
> will make you saner in the long run.  Much, much saner.  Setting it up to
> push a single config is a little overboard, but it makes syncing and
> sanitizing all of your machines REALLY easy.
>
> We use CFengine here, so feel free to contact me off-list for more
> specifics about it.
>
> Cheers,
> Kevin
> -----
> Kevin Sumner
> ksumner at physics.unc.edu
> (919) 962-6494
> Assistant Systems Administrator
> Physics and Astronomy Networking Infrastructure and Computing
> University of North Carolina at Chapel Hill
>
>
> On Mon, 26 Nov 2007, Aaron M. Segura wrote:
>
> > I use cfengine for that purpose.  I have it copy the config from the
> > central server then restart the nrpe daemon.  Might be a little overkill
> > for just this one thing, but it's useful for all sorts of stuff.
> >
> > http://www.cfengine.org/
> >
> > On Mon, 2007-11-26 at 17:07 -0500, Cipriani, Robert C wrote:
> >> Does anyone have any suggestions on a way to centralize NRPE configs? I
> suppose I can push (rsync, scp, whatever) my nrpe.cfg from the Nagios server
> if I need to add any commands.  Is there a better way to manage this? I'd
> like the Nagios server to be a central point of configuration. I am using
> nrpe's --enable-command-args option and passing parameters via check_nrpe,
> so once the monitored host has the nrpe.cfg, there wouldn't be much to do
> there.
> >>
> >>
> >>
> >> Robert C. Cipriani
> >> Senior Network Administrator
> >> Tampa Bay Division IT
> >> Bright House Networks
> >> W: (727) 329-2000 x74264
> >> M: (727) 365-1231
> >>
> >>
> >>
> >>
> >>
> >> CONFIDENTIALITY NOTICE: This e-mail may contain information that is
> privileged, confidential or otherwise protected from disclosure. If you are
> not the intended recipient of this e-mail, please notify the sender
> immediately by return e-mail, purge it and do not disseminate or copy it.
> >>
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2005.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> _______________________________________________
> 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
>

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
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