Re: [Nagios-users] Hey I was wondering about the check_ping from the newest stable plugins.
* Eliezer Croitoru elie...@ngtech.co.il [2013-08-09 16:46]: I have compiled all nagios plugins many times but on the last time this what happens: nagios-plugins-1.4.16.tar.gz I compile with no errors and then when nagios do a check it states: CRITICAL - Network Unreachable (repo.ngtech.co.il) My guess would be that your IPv6 connectivity is broken. In that case, using check_ping's -4 flag should do the trick. If that _doesn't_ help, could you please paste the output of check_ping -vvv [...]? Can anyone test it please and make sure that my assumptions are right? For me, both of the following commands return OK: $ check_ping -4 -H repo.ngtech.co.il -w '500.0,10%' -c '1000.0,50%' $ check_ping -6 -H repo.ngtech.co.il -w '500.0,10%' -c '1000.0,50%' Holger -- Get 100% visibility into Java/.NET code with AppDynamics Lite! It's a free troubleshooting tool designed for production. Get down to code-level detail for bottlenecks, with 2% overhead. Download for free and get started troubleshooting in minutes. http://pubads.g.doubleclick.net/gampad/clk?id=48897031iu=/4140/ostg.clktrk ___ 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] Hey I was wondering about the check_ping from the newest stable plugins.
JFTR (we clarified this on IRC): * Eliezer Croitoru elie...@ngtech.co.il [2013-08-09 17:23]: which is a bit weird why is it using ping6 for a simple ping by default? Hos is the check_ping recognises that there is a need for ping6 ?? the host dosn't even has ipv6 connectivity.. There's no sensible way to detect the availability of IPv6. The plugin could auto-fallback to IPv4 if IPv6 fails, but so far users are expected to simply add the -4 flag in IPv4-only environments (or to use check_icmp). Holger -- Get 100% visibility into Java/.NET code with AppDynamics Lite! It's a free troubleshooting tool designed for production. Get down to code-level detail for bottlenecks, with 2% overhead. Download for free and get started troubleshooting in minutes. http://pubads.g.doubleclick.net/gampad/clk?id=48897031iu=/4140/ostg.clktrk ___ 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] Monitor radius status.
* Luis H. Forchesatto luisforchesa...@gmail.com [2013-07-19 13:46]: I've tried to use check_radius to monitor radius server but it requires a configuration file to be passed via parameter -f. Which configuration file it refers to? It says The format of the configuration file is described in the radiusclient library sources. but I don't know where to check. Here's an example of that file: ftp://ftp.in-berlin.de/pub/users/weiss/nagios/radius/radiusclient.conf It refers to a servers file, which looks like this: ftp://ftp.in-berlin.de/pub/users/weiss/nagios/radius/servers Holger -- See everything from the browser to the database with AppDynamics Get end-to-end visibility with application monitoring from AppDynamics Isolate bottlenecks and diagnose root cause in seconds. Start your free trial of AppDynamics Pro today! http://pubads.g.doubleclick.net/gampad/clk?id=48808831iu=/4140/ostg.clktrk ___ 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] check_ntp_peer parsing error
JFTR: * Marc Haber mh+nagios-us...@zugschlus.de [2013-06-26 21:22]: I have a system running Debian oldstable with Nagios-Plugins 1.4.15. A few weeks ago, my check_ntp_peer checks have started acting up: $ /usr/lib/nagios/plugins/check_ntp_peer --hostname=2001:1b18:f:4::2 --warning 3 --critical 5 --jwarn 10 --jcrit 20 --twarn 2: --tcrit 3: --swarn 2 --scrit 2 -v 3 candidate peers available synchronization source found Getting offset, jitter and stratum for peer e20a parsing offset from peer e20a: error: unable to read server offset response. parsing jitter from peer e20a: error: unable to read server jitter/dispersion response. parsing stratum from peer e20a: error: unable to read server stratum response. NTP CRITICAL: Offset unknown, jitter=-1,00, stratum=-1, truechimers=6| jitter=-1,00;10,00;20,00;0,00 stratum=-1;2;2;0;16 truechimers=6;0;0;0 This is probably caused by a bug in Force10 switches mentioned here: http://news.ntppool.org/2013/06/ipv6-monitoring-problems-for-g.html Due to that bug, the check_ntp_peer requests got duplicated on their way to the server, and the server therefore sent multiple responses per request. check_ntp_peer then stumbled over those duplicated responses. That's a bug, I'll fix it later today. Thanks to Marc for providing tcpdump output and for his help with tracking the issue down. Holger -- This SF.net email is sponsored by Windows: Build for Windows Store. http://p.sf.net/sfu/windows-dev2dev ___ 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] check_ntp_time offset unknown
* Bennett, Jan jbenn...@ntta.org [2013-06-14 14:10]: # ./check_ntp_time -H localhost NTP CRITICAL: Offset unknown| Could you please run ntpq -c rv when this happens and post the output? It has been suggested that the stratum=0 may be the culprit, but I'm not sure of my options here. Yes, stratum=0 is the culprit. An NTP server wouldn't usually report such a stratum value. Holger -- Holger Weiß | Freie Universität Berlin hol...@zedat.fu-berlin.de | Zentraleinrichtung für Datenverarbeitung (ZEDAT) Telefon: +49 30 838-55949 | Fabeckstraße 32, 14195 Berlin (Germany) Telefax: +49 30 838455949 | https://www.zedat.fu-berlin.de/ -- This SF.net email is sponsored by Windows: Build for Windows Store. http://p.sf.net/sfu/windows-dev2dev ___ 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] ANNOUNCE: NSCA-ng 1.1
Today, I released NSCA-ng 1.1. Debian packages and the source tarball can be downloaded from: https://www.nsca-ng.org/ NSCA-ng is a drop-in replacement for NSCA that allows for submitting passive check results, downtimes, and many other commands to Nagios. It uses TLS encryption and shared-secret authentication with per-client passwords, as well as fine-grained authorization control. Version 1.1 is a minor release that adds some improvements and fixes, including the following: - Add chroot(2) support to the server. - Let the server accept `hosts' patterns in `authorize' sections. They're syntactic sugar for allowing host checks to be submitted (analogous to the `services' patterns for service check submissions). - Let the client ignore empty input lines. This fixes some corner cases where NSCA-ng's client didn't accept the same input as the client provided with the original NSCA package. - Add the `-e' client option, which allows for specifying a delimiter to use instead of the ASCII ETB character for separating check results. - Let the `invoke_check' script (provided in the `contrib' directory of the source tarball) survive plugin return codes other than zero. This should make the script slightly more useful :-) Thanks go to Stuart Henderson for adding the chroot(2) support, to Mirko Tasler for spotting the bug in the `invoke_check' script, and to everyone else who provided feedback. Have a nice weekend! Holger -- Precog is a next-generation analytics platform capable of advanced analytics on semi-structured data. The platform includes APIs for building apps and a phenomenal toolset for data science. Developers can use our toolset for easy data analysis visualization. Get a free account! http://www2.precog.com/precogplatform/slashdotnewsletter ___ 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] ANNOUNCE: NSCA-ng 1.0
* Tech Support supp...@voipbusiness.us [2013-03-18 10:43]:
I took one of my perl plugins and simply redefined the send_nsca binary
and config file, while keeping everything else the same.
my $ETB = \027;
# If we want to use nsca-ng instead of nsca.
$nscaprog = '/usr/local/sbin/send_nsca';
$nscacfg = '/usr/local/etc/send_nsca.cfg';
...
...
foreach my $param ( @params ) {
my $service = Sys Info - $param;
my $code= $ERRORS{ OK } if $stats-{ $param } ne $NULL;
$code = $ERRORS{ UNKNOWN } if $stats-{ $param } eq $NULL;
my $message = $param = $stats-{ $param };
$nsca_cmd .= $nscahost\t$service\t$code\t$message\n$ETB;
};
# Now send all of the results to the Nagios host.
my $retval = `$system /bin/echo -e $nsca_cmd | $nscaprog -H $nagioshost -c
$nscacfg`;
But I'm getting the error:
send_nsca: [FATAL] Input format incorrect, see the send_nsca(8) man page
This probably happens because echo adds a trailing newline character and
NSCA-ng's send_nsca interprets that as another check result (because
it's seperated from the previous result with an ETB character). The
following commit lets send_nsca ignore such trailing newlines:
https://www.nsca-ng.org/cgi-bin/repository/nsca-ng/commit/?id=521c7d15
However, using echo -n -e [...] should do the trick.
Holger
--
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdyn_d2d_mar
___
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] ANNOUNCE: NSCA-ng 1.0
Today, I released NSCA-ng 1.0. Debian packages and the source tarball can be downloaded from: https://www.nsca-ng.org/ As far as I can tell, it works very well, and it has all the features I wanted the 1.0 release to have. The client features include: * Accepts all input, command line arguments, and configuration files accepted by the send_nsca binary provided with the original NSCA package. * Supports submission of arbitrary Nagios commands (not just check results) of arbitrary size. That is, NSCA-ng could be used to submit downtimes or acknowledgements, for example. * Optional random delay before the client connects to the server. * Messages can optionally be sent to syslog(3). * Should run on any non-ancient Unix-like system. The server features include: * TLS encryption and shared-secret authentication with client-specific passwords. * Fine-grained authorization control. * Very good performance and scalability. The next step will be to tackle some of my wish list items: https://www.nsca-ng.org/documentation/todo.html If you happen to be interested in any of those (or other features), I'd be happy about any feedback you may have. Holger -- Symantec Endpoint Protection 12 positioned as A LEADER in The Forrester Wave(TM): Endpoint Security, Q1 2013 and remains a good choice in the endpoint security space. For insight on selecting the right partner to tackle endpoint security challenges, access the full report. http://p.sf.net/sfu/symantec-dev2dev ___ 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] Problem sending passive results using NSCA with multi-line output
* diego.roc...@gmail.com [2013-02-22 09:31]: You can't [transmit multiline plugin output] with nsca. You can, see my earlier responses in this thread: http://article.gmane.org/gmane.network.nagios.user/74959 Holger -- Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_d2d_feb ___ 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] Problem sending passive results using NSCA with multi-line output
* Esteban Monge este...@nuevaeralatam.com [2013-02-16 15:00]: This looks like you're using a send_nsca version 2.9, where multiple check results were seperated using newlines. In that case, you'll have to replace each newline character within multi-line output with the literal string '\n'. With NSCA = 2.9, multiple check results are seperated using ASCII ETB characters (octal value: 27) instead of newlines, and multi-line output can be piped into send_nsca as-is. (Actually, converting the newline characters into '\n' will no longer work with NSCA = 2.9.) I have one situation with both versions: NSCA 2.9 in clients and NSCA 2.9 in server. Can send passive checks with \n for newline? Yes, replacing newline characters with the literal string '\n' should do the trick in your case. Holger -- The Go Parallel Website, sponsored by Intel - in partnership with Geeknet, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials, tech docs, whitepapers, evaluation guides, and opinion stories. Check out the most recent posts - join the conversation now. http://goparallel.sourceforge.net/ ___ 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] Problem sending passive results using NSCA with multi-line output
* Tech Support supp...@voipbusiness.us [2013-02-13 11:58]:
foreach my $service ( @services ) {
Blah, Blah, Blah, do some stuff
$nsca_cmd .= $nscahost\t$service\t$code\t$output;
};
my $retval = `$system /bin/echo -e $nsca_cmd | $nscaprog -H $nagioshost -c
$nscacfg`;
Like I said, Nagios is choking when the output contains multi-line output.
This looks like you're using a send_nsca version 2.9, where multiple
check results were seperated using newlines. In that case, you'll have
to replace each newline character within multi-line output with the
literal string '\n'.
With NSCA = 2.9, multiple check results are seperated using ASCII ETB
characters (octal value: 27) instead of newlines, and multi-line output
can be piped into send_nsca as-is. (Actually, converting the newline
characters into '\n' will no longer work with NSCA = 2.9.)
Holger
--
Free Next-Gen Firewall Hardware Offer
Buy your Sophos next-gen firewall before the end March 2013
and get the hardware for free! Learn more.
http://p.sf.net/sfu/sophos-d2d-feb
___
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] A plugin to run the existing plugins for NSCA
* PRA nagios...@gmail.com [2012-09-05 09:00]: I was configuring nagios and NSCA and found that we need to run the plugins in cron and send the output to NAGIOS. So below is what I plan.So I plan to develop another plugin with runs the other plugins 1) Another plugin that takes service_description (the description that is sent to nagios) , plugin with parameters as command line arguments. 2) Runs the send_nsca command with provided inputs. 3) A conf file which has the details(send_nsca path,pluginspath,nsca server,nsca port). Here's a trivial shell script which you could take as a starting point, if you like: ftp://ftp.in-berlin.de/pub/users/weiss/nagios/tools/send_nagios The output can be piped to send_nsca. Holger -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ 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] Trouble with check_radius.
* Luis H. Forchesatto luisforchesa...@gmail.com [2012-08-01 14:53]: Figuring out how to configure the check_radius plugin to check a remote server that run radius I'v look at the configuration file it request and mine config file are default, it was never used but is needed to make check_radius work. Which parameter should I look to adjust it as needed to make de plugin work? My configuration looks like this: authserverradius.example.com acctserverradius.example.com login_tries 3 login_timeout 30 radius_timeout10 radius_retries3 dictionary/etc/radiusclient/dictionary mapfile /etc/radiusclient/port-id-map servers /server/nagios/etc/radius/servers seqfile /server/nagios/var/run/radius/seq nologin /etc/nologin The servers file referenced in the above radiusclient.conf file holds the shared secret(s): radius.example.com sh4red-s3cr3t Holger -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ 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] check_ntp_peer reports stratum off-by-one?
* Marc Haber mh+nagios-us...@zugschlus.de [2012-07-14 21:02]:
$ ntpq -c pe torres.zugschlus.de
remote refid st t when poll reach delay offset jitter
==
*ptbtime1.ptb.de .PTB.1 u 1044 1024 377 18.521 -1.513 0.258
+ptbtime2.ptb.de .PTB.1 u 903 1024 377 18.132 -1.277 0.373
-node01.mserverz 85.10.240.2533 u 651 1024 377 18.721 -7.067 6.829
zefiris.semidef 192.53.103.108 2 u 490 1024 377 16.4964.906 0.680
-evie.fra1.as411 78.47.148.1743 u 974 1024 377 18.8794.630 0.616
+geiger-online.c 81.94.123.17 2 u 556 1024 377 18.2004.669 0.694
$ /usr/lib/nagios/plugins/check_ntp_peer -H torres.zugschlus.de --warning=3
--critical=5 --jwarn=1 --jcrit=2 --twarn=5 --tcrit=5 --swarn=2 --scrit=2
NTP OK: Offset -0,001 secs, jitter=0,00, stratum=1,
truechimers=5|offset=-0,001000s;3,00;5,00;
jitter=0,00;1,00;2,00;0,00 stratum=1;2;2;0;16
truechimers=5;5;5;0
$
Does this mean that the --swarn und --twarn options actually check the
stratum of the best peer of the queried server, not the queried
server itself?
The --swarn and --scrit options (not --twarn), yes.¹
And, while we're at it, why is this:
$ /usr/lib/nagios/plugins/check_ntp_peer -H torres.zugschlus.de --twarn=5
--tcrit=4 -v
3 candidate peers available
synchronization source found
Getting offset, jitter and stratum for peer 20cf
parsing offset from peer 20cf: -0,001
NTP CRITICAL: Offset -0,001 secs,
truechimers=5|offset=-0,001000s;60,00;120,00; truechimers=5;5;4;0
$
critical?
--tcrit=4 is equivalent to --tcrit=0:4 and tells the plugin to raise a
critical alert if the number of truechimers is outside the range {0..4}.
The (arguably somewhat confusing²) syntax for specifying thresholds is
documented here:
http://nagiosplug.sf.net/developer-guidelines.html#THRESHOLDFORMAT
So, you want to specify --twarn=6: --tcrit=5: or --twarn=@5 --tcrit=@4.
Holger
¹ http://permalink.gmane.org/gmane.network.nagios.plugins/4333
² In his talks, Ton used to quiz the audience about the results of
various threshold specifications in order to demonstrate the need for
a new threshold syntax, as proposed here:
http://nagiosplugins.org/rfc/new_threshold_syntax
--
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
___
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] check_ping strange behavior with google
* Travis Runyard travisruny...@gmail.com [2012-06-07 08:39]: The check_ping Nagios plugin does not ping hostnames, only IP addresses. The check_ping plugin supports hostnames just fine. On Wed, Jun 6, 2012 at 11:54 PM, Cosmin Neagu cosmin.ne...@omnilogic.rowrote: Starting from yesterday, check_ping is behaving strange for a single host. When giving -H parameter as www.google.ro it gives CRITICAL - Network Unreachable But when giving -H parameter as IP address it is working. I have checked and there are no DNS issues The hostname www.google.ro now¹ also resolves to an IPv6 address, and check_ping has issues with IPv6 dependending on the ping6(1) implementation used. These issues will hopefully be fixed in the next release of the Nagios Plugins; until then, check_ping -4 [...] should do the trick. Holger ¹ http://en.wikipedia.org/wiki/World_IPv6_Day_and_World_IPv6_Launch_Day -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ 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] check_ping strange behavior with google
* Travis Runyard travisruny...@gmail.com [2012-06-07 09:56]: http://nagiosplugins.org/man/check_ping host_address = IP address. NOT hostname. Indeed, host_address seems to suggest an IP address. Then again, the long option is called --hostname :-) Anyway, you can specify either an IP address or a hostname. Why don't you simply try it out? $HOSTADDRESS$ - Address of the host. This value is taken from the *address* directive in the host definition You neither have to hand over the $HOSTADDRESS$ to check_ping (you could use the $HOSTALIAS$ or whatever you like instead), nor do you have to specify an IP address as the address of a host.¹ We use only hostnames in our Nagios configuration. Holger ¹ Normally, this is an IP address, although it could really be anything you want -- http://nagios.sf.net/docs/3_0/objectdefinitions.html#host -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ 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] check_ping strange behavior with google
* Travis Runyard travisruny...@gmail.com [2012-06-07 12:47]: Long option and short option achieve the same thing, which requires an IP address. I have tried it out, on two separate nagios boxes, one running Debian, the other, Redhat. Why don't you copy and paste the results from shell to prove me wrong? $ check_ping -H nagios-plugins.org -w 500,10% -c 750,50% PING OK - Packet loss = 0%, RTA = 123.06 ms|rta=123.056999ms;500.00;750.00;0.00 pl=0%;10;50;0 Holger -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ 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] check_ping strange behavior with google
* Travis Runyard travisruny...@gmail.com [2012-06-07 13:18]: It does work but I was using google.com which doesn't. Strange because it is pingable but returns network unreachable with check_ping. See my initial reply in this thread: | The hostname www.google.ro now¹ also resolves to an IPv6 address, and | check_ping has issues with IPv6 dependending on the ping6(1) | implementation used. These issues will hopefully be fixed in the next | release of the Nagios Plugins; until then, check_ping -4 [...] should | do the trick. [ http://article.gmane.org/gmane.network.nagios.user/73851 ] Holger -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ 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] Configuration Management for Nagios services/hosts/commands definitions
* Jake Xu j...@demonware.net [2012-02-01 17:53]: I'd like to know some best practices for managing all those Nagios configuration files. FWIW, Bcfg2 has a plugin for managing Nagios object configuration files: http://docs.bcfg2.org/server/plugins/generators/nagiosgen.html Holger -- Try before you buy = See our experts in action! The most comprehensive online learning library for Microsoft developers is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3, Metro Style Apps, more. Free future releases when you subscribe now! http://p.sf.net/sfu/learndevnow-dev2 ___ 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] check_http results - interpreting error messages.
* Giles Coochey gi...@coochey.net [2011-11-02 09:09]: I am monitoring a website, and I sometimes get two types of error: One is: CRITICAL - Socket timeout after 10 seconds and the other is: HTTP CRITICAL - No data received from host What is the difference between the two errors? Is it the case that the HTTP CRITICAL error connected to the server via TCP, but didn't get a page and that the Socket timeout error didn't even establish the TCP connection? Yes, that's the difference. Holger -- RSA#174; Conference 2012 Save $700 by Nov 18 Register now#33; http://p.sf.net/sfu/rsa-sfdev2dev1 ___ 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 to find active check status for a service?
* Paul M. Dubuc w...@paul.dubuc.org [2010-07-15 17:08]: Is there some programmatic way to find out whether or not active checks are enabled or disabled for a service in Nagios. We have a requirement for an audit to provide notifications for certain critical services that may have their active checks disabled so they aren't left that way any longer than necessary. You could parse the status file, see ftp://ftp.in-berlin.de/pub/users/weiss/nagios/tools/disabled-notifications for an example. Holger -- This SF.net email is sponsored by Sprint What will you do first with EVO, the first 4G phone? Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first ___ 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] Checking DHCP
* Cosmin Neagu cosmin.ne...@omnilogic.ro [2010-07-08 10:12]: So from what i see on the server: DHCPD: DHCPDISCOVER received from client 0050.56a1.4fbf through relay 192.168.53.250 DHCPD: Seeing if there is an internally specified pool class DHCPD: there is no address pool for 192.168.53.250 Why can't you simply add an entry for 192.168.53.250 to the DHCP server configuration? I thing that nagios sets the relay agent ip address in dhcp header to be the ip address of the interface from where the dhcpdiscover is sent. Is there any posibilities to control this, i mean to put in that header whatever ip address i want for dhcp relay agent? No, because the server uses that IP address for the reply. That is, if you fake the field in question (giaddr), you won't get a response. Otherwise, i thing nagios cand only monitor dhcp servers on the same lan/subnet. check_dhcp's -u option works just fine if the server is configured appropriately. (And of course, you could use a real DHCP relay agent instead of check_dhcp's -u option.) Holger -- This SF.net email is sponsored by Sprint What will you do first with EVO, the first 4G phone? Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first ___ 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
