[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
[Nagios-users] Custom Variable not working.
Hi all, I'd like to have a custom variable in my contact definitions for the contacts timezone. Nagios docs say that it must begin with an underscore, so I've named it... _timezone According to the docs I should now be able to reference it when calling my email script using... $_CONTACTTIMEZONE$ but this just gives me a dollar ($) character. I've also tried these... $CONTACTTIMEZONE$ $_CONTACT_TIMEZONE$ $NAGIOS__CONTACTTIMEZONE$ but they all gave me that same result. What could I be doing wring? Thanks, Eddie. - 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] Custom Variable not working.
Looks like it just took some time to take effect... It seems to be working fine now. On Fri, Jul 18, 2008 at 7:18 PM, Eddie [EMAIL PROTECTED] wrote: Hi all, I'd like to have a custom variable in my contact definitions for the contacts timezone. Nagios docs say that it must begin with an underscore, so I've named it... _timezone According to the docs I should now be able to reference it when calling my email script using... $_CONTACTTIMEZONE$ but this just gives me a dollar ($) character. I've also tried these... $CONTACTTIMEZONE$ $_CONTACT_TIMEZONE$ $NAGIOS__CONTACTTIMEZONE$ but they all gave me that same result. What could I be doing wring? Thanks, Eddie. - 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] How do we report a possible bug (in check_ping)?
System ping work fine... # /bin/ping -n -U -w 10 -c 5 nagios.org PING nagios.org (66.118.156.22) 56(84) bytes of data. 64 bytes from 66.118.156.22: icmp_seq=1 ttl=45 time=431 ms 64 bytes from 66.118.156.22: icmp_seq=2 ttl=45 time=461 ms 64 bytes from 66.118.156.22: icmp_seq=3 ttl=45 time=451 ms 64 bytes from 66.118.156.22: icmp_seq=4 ttl=45 time=441 ms 64 bytes from 66.118.156.22: icmp_seq=5 ttl=45 time=452 ms --- nagios.org ping statistics --- 5 packets transmitted, 5 received, 0% packet loss, time 3999ms rtt min/avg/max/mdev = 431.271/447.571/461.284/10.243 ms On Fri, Jun 20, 2008 at 4:20 PM, Mathieu Gagné [EMAIL PROTECTED] wrote: Eddie F wrote: See the two examples below, running check_ping on our system. Firstly using the domain name, then using IP address... # /usr/local/nagios/libexec/check_ping -H nagios.org -w 300,10% -c 1000,50% -p 5 CRITICAL - Plugin timed out after 10 seconds # /usr/local/nagios/libexec/check_ping -H 66.118.156.22 -w 300,10% -c 1000,50% -p 5 PING WARNING - Packet loss = 0%, RTA = 709.87 ms|rta=709.869019ms;300.00;1000.00;0.00 pl=0%;10;50;0 If you execute ping manually, what's the result? /bin/ping -n -U -w 10 -c 5 nagios.org -- Mathieu - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php ___ 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] How do we report a possible bug (in check_ping)?
Hi all, How/where do I report bugs for Nagios? And just as importantly, how/where do I check to see if it is something that has already been reported? I think I might have found a bug in check_ping when a a domain name is entered for host_address rather than the IP address. I've found that using the domain name seems to work fine with some other check commands (FTP, HTTP and SSH). See the two examples below, running check_ping on our system. Firstly using the domain name, then using IP address... # /usr/local/nagios/libexec/check_ping -H nagios.org -w 300,10% -c 1000,50% -p 5 CRITICAL - Plugin timed out after 10 seconds # /usr/local/nagios/libexec/check_ping -H 66.118.156.22 -w 300,10% -c 1000,50% -p 5 PING WARNING - Packet loss = 0%, RTA = 709.87 ms|rta=709.869019ms;300.00;1000.00;0.00 pl=0%;10;50;0 I've tried this with many hosts (one on the same sub-net), and the result have always been the same Thanks, Eddie. - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php ___ 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] How do we report a possible bug (in check_ping)?
Yes, DNS was the first thing I thought of, but that is definitely fine. As I mentioned FTP, HTTP and SSH are working fine using the same domain name. On Fri, Jun 20, 2008 at 2:14 PM, Andrew D (Webzone) [EMAIL PROTECTED] wrote: Eddie F wrote: Hi all, How/where do I report bugs for Nagios? And just as importantly, how/where do I check to see if it is something that has already been reported? I think I might have found a bug in check_ping when a a domain name is entered for host_address rather than the IP address. I've found that using the domain name seems to work fine with some other check commands (FTP, HTTP and SSH). I can think of a reason for this, using a hostname is really testing 2 things, your DNS resolution and the 'reachablity' of the said host. If your DNS goes down then the ping test fails even though it might be fine. See the two examples below, running check_ping on our system. Firstly using the domain name, then using IP address... # /usr/local/nagios/libexec/check_ping -H nagios.org -w 300,10% -c 1000,50% -p 5 CRITICAL - Plugin timed out after 10 seconds # /usr/local/nagios/libexec/check_ping -H 66.118.156.22 -w 300,10% -c 1000,50% -p 5 PING WARNING - Packet loss = 0%, RTA = 709.87 ms|rta=709.869019ms;300.00;1000.00;0.00 pl=0%;10;50;0 I've tried this with many hosts (one on the same sub-net), and the result have always been the same Thanks, Eddie. - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php ___ 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 -- Network Administrator / Manager Webzone Internet 1st Floor (Oakley Street Entrance) 167 Grote Street Adelaide SA, 5000 Phone 1300 303 932 Fax 08 8221 6204 Email [EMAIL PROTECTED] [EMAIL PROTECTED] - Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php ___ 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
