attempt recovery on service CRITICAL with nrpe

[Russell Adams]

Checkout MONIT. I've considered daemontools, but MONIT seems to fit
the bill better. I'm about to roll it out to several of my machines
with an older unstable UCD-SNMP daemon on them... 

http://www.tildeslash.com/monit/

Russell

On Fri, Jan 31, 2003 at 01:27:31PM -0600, Carroll, Jim P [Contractor] wrote:
> If you're running the nrpe daemon on your client host as the unprivileged
> user nagios, you might discover some privilege problems, especially trying
> to start network daemons which listen on ports below 1024.  If you're
> running the nrpe daemon on your client host as root, ... ah, but there's no
> point discussing that insecure option, because you wouldn't be doing that.
> Would you?  ;)
> 
> There might be better options to consider.  The one which springs to mind is
> daemontools (http://cr.yp.to/)  This is certainly how tinydns and dnscache
> run.  If (for some unknown reason) the daemon exits, daemontools will simply
> start it up again.  If you direct daemontools to shut down the daemon, then
> it will.  If you direct daemontools to restart the daemon, then it will.
> 
> Daemontools may not work for all daemons available.  Having said that, there
> may be other solutions out there.
> 
> I'm more in favour of letting Nagios do the centralized monitoring, and
> letting systems keep themselves running.  If you push the responsibility of
> restarting daemons to Nagios, you now have a single point of failure (not to
> mention the latency between checks in larger environments which could delay
> the recovery of a downed daemon).
> 
> Something else to consider is this:  If a daemon dies for no good reason,
> why not get to the bottom of it and get it fixed?  Especially if it's a
> mission critical process?
> 
> Just my $0.02.
> 
> jc
> 
> > -----Original Message-----
> > From: Shayne Lebrun [mailto:slebrun at muskoka.com]
> > Sent: Friday, January 31, 2003 12:34 PM
> > To: nagios-users at lists.sourceforge.net
> > Subject: RE: [Nagios-users] attempt recovery on service CRITICAL with
> > nrpe
> > 
> > 
> > If only NRPE could pass arguments, I could do something like:
> > 
> > event_handler    check_nrpe!restart-sillydaemon
> > 
> > Then in your command:
> > command
> > command_line      /path/check_nrpe -H $HOSTADDRESS$ -c
> > restart-sillydaemon -ArgChain 
> > $SERVICESTATUS$!$STATETYPE$!$SERVICEATTEMPT$
> > 
> > Then in the nrpe.cfg on the remote host:
> > command[restart-sillydaemon]=/path/restart-sillydaemon $ARG1$ 
> > $ARG2$ $ARG3$
> > 
> > i.e. I just want the ArgChain, !-delimited, separated into 
> > ARGn variables,
> > which nrpe could then send along said arguments to the commands.
> > 
> > Ah well.  If wishes were horses, then beggers would ride.
> > 
> > Consider it a feature request. :-)
> > 
> > Muskoka.com
> > 115 Manitoba Street
> > Bracebridge, Ontario
> > P1L 2B6
> > (705)645-6097
> > 
> > Muskoka.com is pleased to announce
> > New High Speed  Services
> > please visit
> > http://www.muskoka.com/services.htm
> > for more information
> > 
> > 
> > 
> > 
> > -------------------------------------------------------
> > This SF.NET email is sponsored by:
> > SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
> > http://www.vasoftware.com
> > _______________________________________________
> > Nagios-users mailing list
> > Nagios-users at lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/nagios-users
> > 
> 
> 
> -------------------------------------------------------
> This SF.NET email is sponsored by:
> SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
> http://www.vasoftware.com
> _______________________________________________
> Nagios-users mailing list
> Nagios-users at lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/nagios-users


-------------------------------------------------------
This SF.NET email is sponsored by:
SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
http://www.vasoftware.com