<html xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns="http://www.w3.org/TR/REC-html40"> <head> <META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1"> <meta name=ProgId content=Word.Document> <meta name=Generator content="Microsoft Word 9"> <meta name=Originator content="Microsoft Word 9"> <link rel=File-List href="cid:filelist.xml@01C2B56A.85999170">  <style>  </style> </head> <body lang=EN-US link=blue vlink=purple style='tab-interval:.5in'> <div class=Section1> The below Nagios FAQ seems to address what I’m experiencing. All but 2 of my hosts are not reachable by the central nagios server, thus when it attempts to do a host check it of course comes back as UNREACHABLE in most cases. Problem is the FAQ below doesn’t tell you what to do about it. Modify my check-host-alive command definition? To what in the case of a centralized server only accepting passive service checks? Or is it simply more appropriate to disable and ignore UNREACHABLE statuses?<o:p></o:p> <![if !supportEmptyParas]> <![endif]><o:p></o:p> My centralized server gets all checks from 2 distributed servers and cannot directly check any hosts due to firewalls. Methinks the Nagios documentation could use a bit more clarification on this type of configuration..<o:p></o:p> <![if !supportEmptyParas]> <![endif]><o:p></o:p> Appreciate any help<o:p></o:p> <![if !supportEmptyParas]> <![endif]><o:p></o:p> <![if !supportEmptyParas]> <![endif]><o:p></o:p> <![if !supportEmptyParas]> <![endif]><o:p></o:p> <![if !supportEmptyParas]> <![endif]><o:p></o:p> Title: Notifications about hosts being DOWN or UNREACHABLE when they are UP<o:p></o:p> FAQ ID: F0016<o:p></o:p> Submitted By: Ethan Galstad <o:p></o:p> Last Updated: 07/24/2002<o:p></o:p> <![if !supportEmptyParas]> <![endif]><o:p></o:p> Description:<o:p></o:p> <![if !supportEmptyParas]> <![endif]><o:p></o:p> User is receiving notifications about hosts being in certain states (i.e. DOWN or UNREACHABLE), when they are really in a different state (i.e. UP).<o:p></o:p> <![if !supportEmptyParas]> <![endif]><o:p></o:p> This seems to be one of the most common problems for new user of Nagios. Most all of the time this problem is due to an incorrect command definition for the host check command you specified in the host definition.<o:p></o:p> <o:p></o:p> <![if !supportEmptyParas]> <![endif]><o:p></o:p> Solution:<o:p></o:p> <![if !supportEmptyParas]> <![endif]><o:p></o:p> Make sure that the host check command in your host definition is configured correctly. The host check command is not a service - it is part of the host definition. Also, the host check command is not executed at regular intervals like a service is. Rather, it is executed only when Nagios finds it necessary to check the status of the host.<o:p></o:p> <![if !supportEmptyParas]> <![endif]><o:p></o:p> Important! Just because you have a service that is monitoring ping statistics for a host does not mean that the actual host status is being checked. The status of a host is only checked when a service check results in a non-OK state or if the host was previously down and a service check results in an OK state.<o:p></o:p> <![if !supportEmptyParas]> <![endif]><o:p></o:p> Some symptoms of incorrect host check commands include:<o:p></o:p> <![if !supportEmptyParas]> <![endif]><o:p></o:p> 1. Hosts incorrectly being listed as DOWN<o:p></o:p> 2. Hosts incorrectly being listed as UNREACHABLE<o:p></o:p> 3. Alternating alerts/notifications about host problems and recoveries <o:p></o:p> <![if !supportEmptyParas]> <![endif]><o:p></o:p> <o:p></o:p> <![if !supportEmptyParas]> <![endif]><o:p></o:p> Related FAQs:<o:p></o:p> F0015 Hosts are incorrectly listed as being DOWN or UNREACHABLE<o:p></o:p> Keywords: host down unreachable up incorrect wrong notification<o:p></o:p> <![if !supportEmptyParas]> <![endif]><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> </body> </html> 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.