> -----Original Message----- > From: [EMAIL PROTECTED] [mailto:nagios-users- > [EMAIL PROTECTED] On Behalf Of Robert Snyder > Sent: Wednesday, June 14, 2006 1:10 PM > To: Nagios Users > Subject: [Nagios-users] Re(2): Supressing notifications of services when > host isdown... > > > >Use a host check_command that returns a CRITICAL state when the host is > >down. > > > >http://nagios.sourceforge.net/docs/1_0/networkreachability.html > > Marc, > > What do you do if you are monitoring a service on a host that does not > return a ping? I have am running a check_http on a box that does not > return pings. So I am constantly getting notices that the host is down, > even though the service is up. Here are my settings:
The simple answer is to change the host check_command to be something that _does_ indicate when the host is really down, either directly or by proxy. If possible pick something unrelated the service checks for the host check_command (listening on port 22 for linux or 139 for windows for example). Iff the only thing you can check on that host remotely is whether your web server is answering then make check_http your host check command as well. The unfortunate side effect in that case is that you can't really tell between a web server crash or if the host is really down. [config chopped] > > The PSUWebNoPing hostgroup is not a listed on the check_ping service. > > But I still get host down notifications every two hours. > Your host definition does have checks (active and on-demand) disabled via 'checks_enabled 0' but you're still receiving host notifications. That indicates to me that either nagios wasn't restarted after making the config change (1.x) or that you may have multiple nagios daemons running at the same time (1.x and 2.x). -- Marc _______________________________________________ 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
