A service that happens to be a check_ping is not the same thing as the host check command.
The host check command should be a plugin that determines whether or not the host is alive - usually a ping, but can be something else. See http://nagios.sourceforge.net/docs/3_0/hostchecks.html for more info on this, but as Marc explained, if you set up your host definition with a correct check_command, what will happen when a host goes down is this (without setting up regularly scheduled host checks): 1. A service check fails on the host 2. Nagios immediately schedules a host check for the host 3. If the host check_command fails, notifications for all services on the host are suppressed until the host check_command clears which is what you want in this case. Regards Martin Melin On Mon, Dec 28, 2009 at 8:26 PM, Brandino Andreas <[email protected]> wrote: > Are you sure that it works that way?? > I disabled notifications for "ping" service, but still I receive > notifications from other services although the host is down.... > > Do I have to enable any other option? > > Thank you > Regards > > > > Friday, December 25, 2009, 4:19:08 PM, you wrote: > >> On Dec 25, 2009, at 5:28 AM, Brandino Andreas wrote: > >>> Hi all and happy holidays! >>> >>> Lets assume that a host has three service checks (ping, uptime and cpu). If >>> for some reason >>> connection fails, a mail for each service is being sent (with random >>> order). >>> Is any way when "uptime" or "cpu" check fails (not when is critical), to >>> force a "ping service" check and finally send a notification only for that >>> service?? >>> >>> This behavior can be achieved somehow? With services dependencies can >>> I force a check to be performed at specific points? > >> No service dependencies needed. Get rid of the ping service check >> and make it the host check. If a service on a host fails, the host >> is checked. If the host check returns non-OK, notifications for >> services are suppressed and only the host down notification is sent. > >> -- >> Marc > > >> ------------------------------------------------------------------------------ >> This SF.Net email is sponsored by the Verizon Developer Community >> Take advantage of Verizon's best-in-class app development support >> A streamlined, 14 day to market process makes app distribution fast and easy >> Join now and get one step closer to millions of Verizon customers >> http://p.sf.net/sfu/verizon-dev2dev >> _______________________________________________ >> Nagios-users mailing list >> [email protected] >> 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 > > <> --- - - - --- <> > Brandino Andreas > [email protected] > <> --- - - - --- <> > > > ------------------------------------------------------------------------------ > This SF.Net email is sponsored by the Verizon Developer Community > Take advantage of Verizon's best-in-class app development support > A streamlined, 14 day to market process makes app distribution fast and easy > Join now and get one step closer to millions of Verizon customers > http://p.sf.net/sfu/verizon-dev2dev > _______________________________________________ > Nagios-users mailing list > [email protected] > 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 the Verizon Developer Community Take advantage of Verizon's best-in-class app development support A streamlined, 14 day to market process makes app distribution fast and easy Join now and get one step closer to millions of Verizon customers http://p.sf.net/sfu/verizon-dev2dev _______________________________________________ Nagios-users mailing list [email protected] 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
