[Nagios-users] Failover Monitoring Acks/Comments
I'm about to design a failover solution and my client wants to ensure that the slave nagios server is up to date with state of services. Easy, just send it passive updates from the master. However, they want to make sure any service acknowledgements and comments are also sent across to the slave. Has anyone got this configured? Thanks, Glynne -- Come build with us! The BlackBerryreg; Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9#45;12, 2009. Register now#33; http://p.sf.net/sfu/devconf ___ Nagios-users mailing list Nagios-users@lists.sourceforge.net 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
Re: [Nagios-users] Failover Monitoring Acks/Comments
On Oct 2, 2009, at 8:47 AM, Glynne Jones wrote: I'm about to design a failover solution and my client wants to ensure that the slave nagios server is up to date with state of services. Easy, just send it passive updates from the master. However, they want to make sure any service acknowledgements and comments are also sent across to the slave. Has anyone got this configured? I do this for Service Acknowledgments. I've written a small perl script that runs out of cron to copy them over. It essentially starts from it's last known position in the log file, looks for ACKNOWLEDGE_SVC_PROBLEM, grabs it, ssh's over to the other host and dumps it into the external command file there. I expect the same could be done for Host Acknowledgements and comments. -- Marc -- Come build with us! The BlackBerryreg; Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9#45;12, 2009. Register now#33; http://p.sf.net/sfu/devconf ___ Nagios-users mailing list Nagios-users@lists.sourceforge.net 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
Re: [Nagios-users] Failover Monitoring.
-Original Message- From: Eddie [mailto:[EMAIL PROTECTED] To keep services status information up-to-date on the slave the master sends all service check results to the slave. I got this set up between my master and slave servers, and then noticed that comments and other stuff like that weren't being replicated. If you add hosts and services, or otherwise change your configuration, those changes won't be replicated either. If monitoring fails-over to the slave, how is the status information sent to the new slave so that it is then kept updated with new status information, or do we need to set this up manually after the failover? I wrote a script which is run every minute by a cron job on the slave server. It uses check_by_ssh to run check_nagios on the master. If Nagios is running on the master, then it checks if Nagios is running on the slave. If so, it stops the slave Nagios. If Nagios is only running on the master, it rsyncs any changed files in the whole Nagios directory (minus the checkresults directory, archives directory, lock file, and command file). If Nagios is not currently running on either server, it will start Nagios on the slave server. And, just because I could, I have it write to a log file and e-mail me if it fails over or back. It doesn't copy anything from the slave server back to the master server, because I expect the slave to run only temporarily. If the master server takes that long to fix, I can copy the status back manually. Since my master and slave servers are identically-configured, when I upgraded the master to Nagios 3.0.6, the slave got upgraded a minute later. Couldn't we nullify the need to keep two separate stores of status information data, by keeping it in one place? Is it possible to have the status information stored on a third host (say on an NFS) that both the master and slave have access to? I don't have a highly-available file share, so I keep two copies of Nagios and rsync minimizes the amount of data that has to be copied.. I plan to move the slave server to another office (it's a virtual machine). If the link between the offices went down, one Nagios or the other would lose its connection to its config files. Also, this way there is a window of time where both instances might be active and trying to write to the same files. Is it possible to have more than one slave? Yes. If you do it like the docs say, you'll need to write a script to submit check results to the slave server. It's just one more line to submit the check results to another slave server. I don't know how to write the event handler to check more than one Nagios process, though. If you do it like above, both slave servers can run the cron job, and they can check each other as well as the primary to see if they need to start their Nagios process. You might want to have one slave run the cron job on the even minutes and the other slave run the job on the odd minutes (or some other alternating pattern) so that they won't both try to start up at the same time. Are there any other resources that go into more detail on failover (and redundant monitoring)? I did a lot of Googling to get it working like in the docs, and then subscribed to this mailing list five days ago so I could ask about how to get status information to the slave server. :-) Nothing in this message is intended to make or accept and offer or to form a contract, except that an attachment that is an image of a contract bearing the signature of an officer of our company may be or become a contract. This message (including any attachments) is intended only for the use of the individual or entity to whom it is addressed. It 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, we hereby notify you that any use, dissemination, distribution, or copying of this message is strictly prohibited. If you have received this message in error, please notify us immediately by telephone and delete this message immediately. Thank you. -- SF.Net email is Sponsored by MIX09, March 18-20, 2009 in Las Vegas, Nevada. The future of the web can't happen without you. Join us at MIX09 to help pave the way to the Next Web now. Learn more and register at http://ad.doubleclick.net/clk;208669438;13503038;i?http://2009.visitmix.com/ ___ Nagios-users mailing list Nagios-users@lists.sourceforge.net 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
[Nagios-users] Failover Monitoring.
Hello all, On reading the Nagios 3 Documentation re' failover monitoring, there are some things I'd like to ask. To keep services status information up-to-date on the slave the master sends all service check results to the slave. If monitoring fails-over to the slave, how is the status information sent to the new slave so that it is then kept updated with new status information, or do we need to set this up manually after the failover? Couldn't we nullify the need to keep two separate stores of status information data, by keeping it in one place? Is it possible to have the status information stored on a third host (say on an NFS) that both the master and slave have access to? Is it possible to have more than one slave? Are there any other resources that go into more detail on failover (and redundant monitoring)? Thanks, Eddie. -- SF.Net email is Sponsored by MIX09, March 18-20, 2009 in Las Vegas, Nevada. The future of the web can't happen without you. Join us at MIX09 to help pave the way to the Next Web now. Learn more and register at http://ad.doubleclick.net/clk;208669438;13503038;i?http://2009.visitmix.com/ ___ Nagios-users mailing list Nagios-users@lists.sourceforge.net 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
Re: [Nagios-users] Failover monitoring and acknowlegements
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. That the kind of thing what I was thinking. We already use subversion to keep our libexec directories the same over (currently) 3 sites, and keep the configs Uptodate, but the var directory gets a nightly rsync to the backup server. If you want to do load balancing across nagios instances though, you should look at the full hog -- There is no time like the present for postponing what you ought to be doing. Paul Weaver Systems Development Engineer News Production Facilities, BBC News - From: Paul Weaver [mailto:[EMAIL PROTECTED] Sent: Wednesday, December 03, 2008 11:09 AM To: Chris Beattie; nagios-users@lists.sourceforge.net Subject: RE: [Nagios-users] Failover monitoring and acknowlegements For just a failover installation, are there any issues with rsyncing the files from master to slave every minute? -- 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 From: Chris Beattie [mailto:[EMAIL PROTECTED] Sent: 03 December 2008 15:22 To: nagios-users@lists.sourceforge.net Subject: Re: [Nagios-users] Failover monitoring and acknowlegements Er, both servers are Nagios 3.0.5 running on CentOS 5.2, sorry. From: Chris Beattie [mailto:[EMAIL PROTECTED] Sent: Wednesday, December 03, 2008 9:53 AM To: nagios-users@lists.sourceforge.net Subject: [Nagios-users] Failover monitoring and acknowlegements 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? 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. 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. 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
[Nagios-users] Failover monitoring and acknowlegements
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? Nothing in this message is intended to make or accept and offer or to form a contract, except that an attachment that is an image of a contract bearing the signature of an officer of our company may be or become a contract. This message (including any attachments) is intended only for the use of the individual or entity to whom it is addressed. It 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, we hereby notify you that any use, dissemination, distribution, or copying of this message is strictly prohibited. If you have received this message in error, please notify us immediately by telephone and delete this message immediately. Thank you. - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100url=/___ Nagios-users mailing list Nagios-users@lists.sourceforge.net 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
Re: [Nagios-users] Failover monitoring and acknowlegements
Er, both servers are Nagios 3.0.5 running on CentOS 5.2, sorry. From: Chris Beattie [mailto:[EMAIL PROTECTED] Sent: Wednesday, December 03, 2008 9:53 AM To: nagios-users@lists.sourceforge.net Subject: [Nagios-users] Failover monitoring and acknowlegements 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? 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. Nothing in this message is intended to make or accept and offer or to form a contract, except that an attachment that is an image of a contract bearing the signature of an officer of our company may be or become a contract. This message (including any attachments) is intended only for the use of the individual or entity to whom it is addressed. It 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, we hereby notify you that any use, dissemination, distribution, or copying of this message is strictly prohibited. If you have received this message in error, please notify us immediately by telephone and delete this message immediately. Thank you. - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100url=/___ Nagios-users mailing list Nagios-users@lists.sourceforge.net 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
Re: [Nagios-users] Failover monitoring and acknowlegements
For just a failover installation, are there any issues with rsyncing the files from master to slave every minute? -- 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 From: Chris Beattie [mailto:[EMAIL PROTECTED] Sent: 03 December 2008 15:22 To: nagios-users@lists.sourceforge.net Subject: Re: [Nagios-users] Failover monitoring and acknowlegements Er, both servers are Nagios 3.0.5 running on CentOS 5.2, sorry. From: Chris Beattie [mailto:[EMAIL PROTECTED] Sent: Wednesday, December 03, 2008 9:53 AM To: nagios-users@lists.sourceforge.net Subject: [Nagios-users] Failover monitoring and acknowlegements 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? 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. 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. - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100url=/___ Nagios-users mailing list Nagios-users@lists.sourceforge.net 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
Re: [Nagios-users] Failover monitoring and acknowlegements
Well, now you've got me thinking... 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. From: Paul Weaver [mailto:[EMAIL PROTECTED] Sent: Wednesday, December 03, 2008 11:09 AM To: Chris Beattie; nagios-users@lists.sourceforge.net Subject: RE: [Nagios-users] Failover monitoring and acknowlegements For just a failover installation, are there any issues with rsyncing the files from master to slave every minute? -- 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 From: Chris Beattie [mailto:[EMAIL PROTECTED] Sent: 03 December 2008 15:22 To: nagios-users@lists.sourceforge.net Subject: Re: [Nagios-users] Failover monitoring and acknowlegements Er, both servers are Nagios 3.0.5 running on CentOS 5.2, sorry. From: Chris Beattie [mailto:[EMAIL PROTECTED] Sent: Wednesday, December 03, 2008 9:53 AM To: nagios-users@lists.sourceforge.net Subject: [Nagios-users] Failover monitoring and acknowlegements 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? 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. 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. Nothing in this message is intended to make or accept and offer or to form a contract, except that an attachment that is an image of a contract bearing the signature of an officer of our company may be or become a contract. This message (including any attachments) is intended only for the use of the individual or entity to whom it is addressed. It 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, we hereby notify you that any use, dissemination, distribution, or copying of this message is strictly prohibited. If you have received this message in error, please notify us immediately by telephone and delete this message immediately. Thank you. - This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100url=/___ Nagios-users mailing list Nagios-users@lists.sourceforge.net https
