<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:x="urn:schemas-microsoft-com:office:excel" xmlns:p="urn:schemas-microsoft-com:office:powerpoint" xmlns:a="urn:schemas-microsoft-com:office:access" xmlns:dt="uuid:C2F41010-65B3-11d1-A29F-00AA00C14882" xmlns:s="uuid:BDC6E3F0-6DA3-11d1-A2A3-00AA00C14882" xmlns:rs="urn:schemas-microsoft-com:rowset" xmlns:z="#RowsetSchema" xmlns:b="urn:schemas-microsoft-com:office:publisher" xmlns:ss="urn:schemas-microsoft-com:office:spreadsheet" xmlns:c="urn:schemas-microsoft-com:office:component:spreadsheet" xmlns:odc="urn:schemas-microsoft-com:office:odc" xmlns:oa="urn:schemas-microsoft-com:office:activation" xmlns:html="http://www.w3.org/TR/REC-html40" xmlns:q="http://schemas.xmlsoap.org/soap/envelope/" xmlns:D="DAV:" xmlns:x2="http://schemas.microsoft.com/office/excel/2003/xml" xmlns:ois="http://schemas.microsoft.com/sharepoint/soap/ois/" xmlns:dir="http://schemas.microsoft.com/sharepoint/soap/directory/" xmlns:ds="http://www.w3.org/2000/09/xmldsig#" xmlns:dsp="http://schemas.microsoft.com/sharepoint/dsp" xmlns:udc="http://schemas.microsoft.com/data/udc" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:sub="http://schemas.microsoft.com/sharepoint/soap/2002/1/alerts/" xmlns:ec="http://www.w3.org/2001/04/xmlenc#" xmlns:sp="http://schemas.microsoft.com/sharepoint/" xmlns:sps="http://schemas.microsoft.com/sharepoint/soap/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:udcxf="http://schemas.microsoft.com/data/udc/xmlfile" xmlns:wf="http://schemas.microsoft.com/sharepoint/soap/workflow/" xmlns:mver="http://schemas.openxmlformats.org/markup-compatibility/2006" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns:mrels="http://schemas.openxmlformats.org/package/2006/relationships" xmlns:ex12t="http://schemas.microsoft.com/exchange/services/2006/types" xmlns:ex12m="http://schemas.microsoft.com/exchange/services/2006/messages" xmlns:Z="urn:schemas-microsoft-com:" xmlns:st="" xmlns="http://www.w3.org/TR/REC-html40"> <head> <meta http-equiv=Content-Type content="text/html; charset=us-ascii"> <meta name=Generator content="Microsoft Word 12 (filtered medium)">  <title>New Page 1</title> <style>  </style>  </head> <body lang=EN-US link=blue vlink=purple> <div class=Section1> Well, now you’ve got me thinking…<o:p></o:p> <o:p> </o:p> I thought I couldn’t rsync the files because the running Nagios process on the failover server wouldn’t notice the changed files. However, if I can have a script run check_nagios via check_by_ssh from a cron job (I don’t know yet- I’ve never used check_by_ssh before), then Nagios doesn’t need to be running all the time on the failover server. The cron job can start the failover Nagios if the primary Nagios isn’t running, and stop the failover Nagios when the primary returns. Since the configurations on both servers would be the same, rsync could even keep Nagios itself, updated on the failover server without me having to do it manually.<o:p></o:p> <o:p> </o:p> <div> <div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'> From: Paul Weaver [mailto:paul.weaver@bbc.co.uk] Sent: Wednesday, December 03, 2008 11:09 AM To: Chris Beattie; nagios-users@lists.sourceforge.net Subject: RE: [Nagios-users] Failover monitoring and acknowlegements<o:p></o:p> </div> </div> <o:p> </o:p> For just a failover installation, are there any issues with rsyncing the files from master to slave every minute?<o:p></o:p> <o:p></o:p> <o:p></o:p> <div> --<o:p></o:p> </div> "Watch out for that tree" Paul Weaver Systems Development Engineer News Production Facilities, BBC News Work: 020 8225 8109here Mobile: 07736 481006 Room 1244, BBC Television Centre, Wood Lane, London, W12 7RJ<o:p></o:p> <div> <o:p></o:p> </div> <blockquote style='border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in 4.0pt; margin-left:3.75pt;margin-top:5.0pt;margin-right:0in;margin-bottom:5.0pt'> <o:p> </o:p> <div class=MsoNormal align=center style='text-align:center'> <hr size=2 width="100%" align=center> </div> From: Chris Beattie [mailto:cbeattie@geninfo.com] Sent: 03 December 2008 15:22 To: nagios-users@lists.sourceforge.net Subject: Re: [Nagios-users] Failover monitoring and acknowlegements<o:p></o:p> Er, both servers are Nagios 3.0.5 running on CentOS 5.2, sorry.<o:p></o:p> <o:p> </o:p> <div> <div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'> From: Chris Beattie [mailto:cbeattie@geninfo.com] Sent: Wednesday, December 03, 2008 9:53 AM To: nagios-users@lists.sourceforge.net Subject: [Nagios-users] Failover monitoring and acknowlegements<o:p></o:p> </div> </div> <o:p> </o:p> I’m setting Nagios up in a failover configuration like is described in the documentation, with the primary server feeding check results to the failover server via NSCA. That part’s working fine, but is there a good way to also keep host and service comments, acknowledgements, and scheduled downtimes up-to-date as well?<o:p></o:p> This message (including any attachments) is intended only for the use of the individual or entity to which it is addressed and may contain information that is non-public, proprietary, privileged, confidential, and exempt from disclosure under applicable law or may constitute as attorney work product. If you are not the intended recipient, you are hereby notified that any use, dissemination, distribution, or copying of this communication is strictly prohibited. If you have received this communication in error, notify us immediately by telephone and (i) destroy this message if a facsimile or (ii) delete this message immediately if this is an electronic communication.<o:p></o:p> Thank you. <o:p></o:p> This message (including any attachments) is intended only for the use of the individual or entity to which it is addressed and may contain information that is non-public, proprietary, privileged, confidential, and exempt from disclosure under applicable law or may constitute as attorney work product. If you are not the intended recipient, you are hereby notified that any use, dissemination, distribution, or copying of this communication is strictly prohibited. If you have received this communication in error, notify us immediately by telephone and (i) destroy this message if a facsimile or (ii) delete this message immediately if this is an electronic communication.<o:p></o:p> Thank you. <o:p></o:p> </blockquote> </div> <html> <head> <meta http-equiv="Content-Language" content="en-us"> <meta name="GENERATOR" content="Microsoft FrontPage 5.0"> <meta name="ProgId" content="FrontPage.Editor.Document"> <meta http-equiv="Content-Type" content="text/html; charset=windows-1252"> <title>New Page 1</title> </head> <body> This message (including any attachments) is intended only for the use of the individual or entity to which it is addressed and may contain information that is non-public, proprietary, privileged, confidential, and exempt from disclosure under applicable law or may constitute as attorney work product. If you are not the intended recipient, you are hereby notified that any use, dissemination, distribution, or copying of this communication is strictly prohibited. If you have received this communication in error, notify us immediately by telephone and (i) destroy this message if a facsimile or (ii) delete this message immediately if this is an electronic communication. Thank you. </body> </html> </body> </html>