<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> <HTML xmlns="http://www.w3.org/TR/REC-html40" xmlns:o = "urn:schemas-microsoft-com:office:office" xmlns:w = "urn:schemas-microsoft-com:office:word"><HEAD> <META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1"> <META content=Word.Document name=ProgId> <META content="MSHTML 5.50.4611.1300" name=GENERATOR> <META content="Microsoft Word 9" name=Originator><LINK href="cid:filelist.xml@01C2B572.A8271CF0" rel=File-List> <STYLE>@page Section1 {size: 8.5in 11.0in; margin: 1.0in 1.25in 1.0in 1.25in; mso-header-margin: .5in; mso-footer-margin: .5in; mso-paper-source: 0; } P.MsoNormal { FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"; mso-style-parent: ""; mso-pagination: widow-orphan; mso-fareast-font-family: "Times New Roman" } LI.MsoNormal { FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"; mso-style-parent: ""; mso-pagination: widow-orphan; mso-fareast-font-family: "Times New Roman" } DIV.MsoNormal { FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"; mso-style-parent: ""; mso-pagination: widow-orphan; mso-fareast-font-family: "Times New Roman" } P.MsoAutoSig { FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"; mso-pagination: widow-orphan; mso-fareast-font-family: "Times New Roman" } LI.MsoAutoSig { FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"; mso-pagination: widow-orphan; mso-fareast-font-family: "Times New Roman" } DIV.MsoAutoSig { FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"; mso-pagination: widow-orphan; mso-fareast-font-family: "Times New Roman" } SPAN.EmailStyle15 { COLOR: black; mso-style-type: personal-compose; mso-ansi-font-size: 10.0pt; mso-ascii-font-family: Arial; mso-hansi-font-family: Arial; mso-bidi-font-family: Arial } DIV.Section1 { page: Section1 } </STYLE> </HEAD> <BODY lang=EN-US style="tab-interval: .5in"> <DIV>You may find one particular problem with this approach.</DIV> <DIV> </DIV> <DIV>If the service check fails, Nagios will attempt to do the host check. Once the host check recovers, Nagios resumes the service checks. However, you've removed that host checking ability, so you may find that the service check stays critical, despite the fact that a manual check reveals otherwise.</DIV> <DIV> </DIV> <DIV>You might want to define a special case host check, call it something like check-host-dummy and define the appropriate command in checkcommands.cfg to use the check_dummy plugin.</DIV> <DIV> </DIV> <DIV>Just to reiterate, for any given host, you can only have one host check, but you can have any number of service checks. A host check can be completely arbitrary, but by default is configured to use check-host-alive, which in checkcommands.cfg relates to the check_ping plugin. This is something that confused me a bit at first, so you're not alone. :)</DIV> <DIV> </DIV> <DIV>Food for thought.</DIV> <DIV> </DIV> <DIV>jc</DIV> <BLOCKQUOTE dir=ltr style="PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #000080 2px solid; MARGIN-RIGHT: 0px"> <DIV class=OutlookMessageHeader dir=ltr align=left>-----Original Message----- From: Gerald Wichmann [mailto:gwichman@zantaz.com] Sent: Monday, January 06, 2003 12:59 PM To: Nagios (E-mail) Subject: [Nagios-users] Notifications about hosts being DOWN or UNREACHABL E when they are UP </DIV> <DIV class=Section1> Ok I think after some reading the trick is to remove the check_command statement in hosts.cfg for those servers that cannot be directly checked by the centralized server. I thought all checks were done/defined by the services.cfg file but apparently not. Common newbie misunderstanding I guess. Helps to read deeper into how nagios actually works. Seems to be working well now though I’ll have to make sure when a service check goes red, so does that particular respective host.<o:p></o:p> <![if !supportEmptyParas]><![endif]> <o:p></o:p> Gerald Wichmann<o:p></o:p> Senior Systems Development Engineer<o:p></o:p> Zantaz, Inc.<o:p></o:p> 925.598.3099 (w)<o:p></o:p> <![if !supportEmptyParas]><![endif]> <o:p></o:p></DIV> This e-mail has been captured and archived by the ZANTAZ Digital Safe(tm) service. For more information, visit us at www.zantaz.com. IMPORTANT: This electronic mail message is intended only for the use of the individual or entity to which it is addressed and may contain information that is privileged, confidential or exempt from disclosure under applicable law. If the reader of this message is not the intended recipient, or the employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify the sender immediately by telephone or directly reply to the original message(s) sent. Thank you.</BLOCKQUOTE></BODY></HTML>