<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
<title></title>
</head>
<body text="#000000" bgcolor="#ffffff">
On 1/3/11 11:53 AM, James Moseley wrote:
<blockquote
cite="mid:AANLkTimGeB6rgV-nK0xBGRcoeposHtxufK-1VTAzLmOD@mail.gmail.com"
type="cite"><br>
<div class="gmail_quote">
<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt
0.8ex; border-left: 1px solid rgb(204, 204, 204);
padding-left: 1ex;">
I was directed in the irc forum to look at<br>
<a moz-do-not-send="true"
href="http://nagios.sourceforge.net/docs/3_0/statetypes.html"
target="_blank">http://nagios.sourceforge.net/docs/3_0/statetypes.html</a>
and I learned<br>
that services or hosts need to have a hard state failure, in
order for<br>
notifications to go out. I've been trying to reboot my servers
in order<br>
to get my notifications to go out. I'd like to check that I'll
actually<br>
get notifications as soon as there is a problem, for example,
a host<br>
goes offline, I'd like to know after about 2 minutes if
possible!<br>
<br>
</blockquote>
<div><br>
Then just turn a server off and wait a bit... ;-) You could
also create a fake host, one with an unpingable IP address.<br>
</div>
</div>
</blockquote>
My favorite trick, that doesn't require adding fake config or
rebooting a server, is updating /etc/hosts on the monitoring host to
point a real host at a known bad ip address. Requires root, and
that you use dns for your hostaddress entries, however.<br>
<br>
<pre class="moz-signature" cols="72">--
Mike Lindsey</pre>
</body>
</html>