>       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 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=100&url=/
_______________________________________________
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

Reply via email to