From tilakraj.rajasekar at linkedteams.com Thu Apr 4 10:20:39 2013 From: tilakraj.rajasekar at linkedteams.com (Tilakraj Rajasekar) Date: Thu, 4 Apr 2013 13:50:39 +0530 Subject: [Nagiosplug-devel] Fwd: nagios mysql plugin issue.. In-Reply-To: References: Message-ID: Hi, I installed nagios plugin in my one of our server centos 64-bit, other nagios plugin are working fine but only that mysql plugin was not working it asking "libmysqlclient18.so" but it actually available in lib64/mysql/ folder but it's still asking. What we suspect is, that installed nagios mysql plugin it checking that mysql library in lib/ folder not in lib64/ folder. We copied that required "mysqlclient18.so" in lib64/ to lib/ folder, after we try to run the nagios mysql plugin the same error only it generates. Even we tried with the nagios-plugin 64-bit package, But sill the same error exist. We need your assistance to solve this problem. Thanks, Tilak., -- ------------------------------ ***Tilak Raj Rajasekar* (+91) 7708922548 tilakraj.rajasekar at linkedteams.com http://www.linkedteams.com** LinkedTeams India Software Pvt.Ltd. No.54, 7th Cross, Bharathi Park Road, Sai Baba Colony, Coimbatore - 641011 India (+91) 422 4347309 [image: Linkedteams] -------------- next part -------------- An HTML attachment was scrubbed... URL: From dtenney at isc.upenn.edu Thu Apr 4 14:53:32 2013 From: dtenney at isc.upenn.edu (David Tenney) Date: Thu, 4 Apr 2013 12:53:32 +0000 Subject: [Nagiosplug-devel] Nagios check_dhcp full request and release on every run Message-ID: We noticed that when using the check_dhcp plugin for Nagios, that the dhcp request process does not do a full request to release, but instead a renew. Is it possible to implement an option to force a full broadcast DISCOVER/OFFER/REQUEST/ACK cycle, followed by a RELEASE. Thanks! David Tenney Application Developer Sr. ISC / N&T Office #: 215-898-1201 Email: dtenney at isc.upenn.edu -------------- next part -------------- An HTML attachment was scrubbed... URL: From manu at netbsd.org Thu Apr 4 18:13:38 2013 From: manu at netbsd.org (Emmanuel Dreyfus) Date: Thu, 4 Apr 2013 18:13:38 +0200 Subject: [Nagiosplug-devel] A few plugins In-Reply-To: <20130326114642.GQ17856@zedat.fu-berlin.de> Message-ID: <1l0te21.y77ggd184it6oM%manu@netbsd.org> Holger Wei? wrote: > To me, this one looks neat and generally useful. I'd be interested in > including it with the standard Plugins package. An option for > specifying the PID file directory (or directories) would have to be > added, plus the usual --help/--version/--timeout boilerplate, but that's > trivial. However, this is only an option if you'd be fine with > transferring copyright to the Nagios Plugins Development Team (and with > us releasing the code under the GPLv3). Sure, feel free to include and improve. I hereby agree to the copyright be transfered to the Nagios Plugins Development Team. I'd just appreciate a comment in source file noting "This software is derived from a contribution by Emmanuel Dreyfus " -- Emmanuel Dreyfus http://hcpnet.free.fr/pubz manu at netbsd.org From holger at cis.fu-berlin.de Fri Apr 5 00:38:44 2013 From: holger at cis.fu-berlin.de (Holger =?iso-8859-1?Q?Wei=DF?=) Date: Fri, 5 Apr 2013 00:38:44 +0200 Subject: [Nagiosplug-devel] A few plugins In-Reply-To: <1l0te21.y77ggd184it6oM%manu@netbsd.org> References: <20130326114642.GQ17856@zedat.fu-berlin.de> <1l0te21.y77ggd184it6oM%manu@netbsd.org> Message-ID: <20130404223844.GD99023@zedat.fu-berlin.de> * Emmanuel Dreyfus [2013-04-04 18:13]: > Holger Wei? wrote: > > To me, this one looks neat and generally useful. I'd be interested in > > including it with the standard Plugins package. An option for > > specifying the PID file directory (or directories) would have to be > > added, plus the usual --help/--version/--timeout boilerplate, but that's > > trivial. However, this is only an option if you'd be fine with > > transferring copyright to the Nagios Plugins Development Team (and with > > us releasing the code under the GPLv3). > > Sure, feel free to include and improve. I hereby agree to the copyright > be transfered to the Nagios Plugins Development Team. Awesome, thanks. > I'd just appreciate a comment in source file noting "This software is > derived from a contribution by Emmanuel Dreyfus " Yes, I'd add such a note. Any other opinions on whether or not we should include this plugin? Holger From noreply at sourceforge.net Fri Apr 5 10:15:35 2013 From: noreply at sourceforge.net (SourceForge.net) Date: Fri, 05 Apr 2013 01:15:35 -0700 Subject: [Nagiosplug-devel] [ nagiosplug-Bugs-3600122 ] Old version of gnulib assumes gets is defined Message-ID: Bugs item #3600122, was opened at 2013-01-09 09:38 Message generated for change (Comment added) made by inakimtz You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=397597&aid=3600122&group_id=29880 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Compilation Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: racb () Assigned to: Holger Weiss (hweiss) Summary: Old version of gnulib assumes gets is defined Initial Comment: The next release of Ubuntu will use eglibc 2.16, which drops the definition of gets (following ISO C11). The embedded gnulib assumes that gets is defined, and thus causes a build failure in the current development release of Ubuntu. Upstream gnulib has followed this change in http://git.savannah.gnu.org/gitweb/?p=gnulib.git;a=commitdiff;h=66712c23388e93e5c518ebc8515140fa0c807348 Workaround is to disable the warning in gl/stdio.in.h. Please update gnulib to allow nagios-plugins to compile in environments where gets is not defined. Ubuntu bug: https://launchpad.net/bugs/1097848 Thanks! ---------------------------------------------------------------------- Comment By: inaki_mtz (inakimtz) Date: 2013-04-05 01:15 Message: Same issue on OpenSuse 12.3 clean install when compiling nagios-plugins 1.4.16 ./stdio.h:456:1: error: 'gets' undeclared here (not in a function) make[5]: *** [localcharset.o] Error 1 ---------------------------------------------------------------------- Comment By: Holger Weiss (hweiss) Date: 2013-01-09 10:57 Message: Yes, we're aware of that issue and will update Gnulib before the next release. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=397597&aid=3600122&group_id=29880 From mikelhansen2000 at gmail.com Thu Apr 11 20:35:55 2013 From: mikelhansen2000 at gmail.com (Mike Hansen) Date: Thu, 11 Apr 2013 12:35:55 -0600 Subject: [Nagiosplug-devel] Suggestion for check_ldap to work with self-signed certificates Message-ID: <003801ce36e3$67aed430$370c7c90$@gmail.com> Nagios Plugin Suggestion for check_ldap: Would it be possible to modify the check_ldap plugin to allow self-signed certificates to not return an error and to return an error when certificates are close to expiring? Our situation: 1. Our IT department uses a global LDAP server that uses self-signed certificates. 2. Our Apache web servers which we use for authentication are not picky and work. 3. When the self-signed certificate expired this morning our web applications quit working. With the plugin as currently working I would still have to check the Apache SSL error logs to find out that the LDAP server was the culprit. Suggestions: 1. Add something like "--allow_self_signed" so that check_ldap can connect and return OK for LDAP servers that use self-signed certificates. 2. Add an option such as "-C" that is similar to the check_http "-C" which checks for the number of days before a certificate is going to expire? (Adding this option is an additional check that we do for our webservers. One check_http to check if a webpage returns an error and another check_http to check for when the SSL certificate is going to expire.) Here is the command-line I'm using: ./check_ldaps -H 10.6.9.33 -b dc=students,dc=msu,dc=edu -D ldapquery at students.msu.edu -P XXXXXXX -v -p 636 -S Here is the response I get with verbose (-v) set: ldap_bind: Can't contact LDAP server (-1) additional info: TLS error -8179:Peer's Certificate issuer is not recognized. Could not bind to the LDAP server Here is the response I get with no verbose (-v) set: Could not bind to the LDAP server Our server information: CentOS 6.4 Nagios 3.2.3 check_ldap v1.4.16 (nagios-plugins 1.4.16) Thanks, Mike Hansen From noreply at sourceforge.net Mon Apr 22 22:44:31 2013 From: noreply at sourceforge.net (SourceForge.net) Date: Mon, 22 Apr 2013 13:44:31 -0700 Subject: [Nagiosplug-devel] [ nagiosplug-Bugs-3611599 ] check_load -r uses misleading value for ncpus. Message-ID: Bugs item #3611599, was opened at 2013-04-22 13:44 Message generated for change (Tracker Item Submitted) made by You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=397597&aid=3611599&group_id=29880 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: General plugin execution Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: https://www.google.com/accounts () Assigned to: Nobody/Anonymous (nobody) Summary: check_load -r uses misleading value for ncpus. Initial Comment: check_load -r uses the macro sysconf(__SC_nprocessors_conf) If you are on a system with hyper-threading disabled after boot, this value is incorrect since it counts configured rather than active CPUS. The code works correctly in this case if you change the macro to sysconf(__SC_nprocessors_ONLN) I've attached a patch to implement this change. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=397597&aid=3611599&group_id=29880 From noreply at sourceforge.net Tue Apr 23 01:19:44 2013 From: noreply at sourceforge.net (SourceForge.net) Date: Mon, 22 Apr 2013 16:19:44 -0700 Subject: [Nagiosplug-devel] [ nagiosplug-Bugs-3611614 ] check_by_ssh hostname check Message-ID: Bugs item #3611614, was opened at 2013-04-22 16:19 Message generated for change (Tracker Item Submitted) made by francyci You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=397597&aid=3611614&group_id=29880 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Christopher Francy (francyci) Assigned to: Nobody/Anonymous (nobody) Summary: check_by_ssh hostname check Initial Comment: Please add a feature in check_by_ssh to skip the host_or_die() check. I have host aliases defined in my system ssh_config (/etc/ssh/ssh_config) that are only accessible via ProxyCommand. There are no DNS records for those systems since they exist outside the local network, and are not accessible except through a Proxy. check_by_ssh.c case 'H': /* host */ host_or_die(optarg); hostname = optarg; break; If I comment out the `host_or_die()` and re-compile check_by_ssh seems to work perfectly fine to connect to the systems I have defined with aliases in my ssh_config. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=397597&aid=3611614&group_id=29880 From noreply at sourceforge.net Tue Apr 23 01:20:02 2013 From: noreply at sourceforge.net (SourceForge.net) Date: Mon, 22 Apr 2013 16:20:02 -0700 Subject: [Nagiosplug-devel] [ nagiosplug-Bugs-3611614 ] check_by_ssh skip hostname check Message-ID: Bugs item #3611614, was opened at 2013-04-22 16:19 Message generated for change (Settings changed) made by francyci You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=397597&aid=3611614&group_id=29880 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Christopher Francy (francyci) Assigned to: Nobody/Anonymous (nobody) >Summary: check_by_ssh skip hostname check Initial Comment: Please add a feature in check_by_ssh to skip the host_or_die() check. I have host aliases defined in my system ssh_config (/etc/ssh/ssh_config) that are only accessible via ProxyCommand. There are no DNS records for those systems since they exist outside the local network, and are not accessible except through a Proxy. check_by_ssh.c case 'H': /* host */ host_or_die(optarg); hostname = optarg; break; If I comment out the `host_or_die()` and re-compile check_by_ssh seems to work perfectly fine to connect to the systems I have defined with aliases in my ssh_config. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=397597&aid=3611614&group_id=29880 From noreply at sourceforge.net Fri Apr 26 00:14:02 2013 From: noreply at sourceforge.net (SourceForge.net) Date: Thu, 25 Apr 2013 15:14:02 -0700 Subject: [Nagiosplug-devel] [ nagiosplug-Bugs-3552828 ] Define source ip for check_ping. Message-ID: Bugs item #3552828, was opened at 2012-07-31 15:53 Message generated for change (Comment added) made by laurentt You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=397597&aid=3552828&group_id=29880 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: C?lestyo (calestyo) Assigned to: Nobody/Anonymous (nobody) Summary: Define source ip for check_ping. Initial Comment: Hi. This is from the old / soon to be disabled again Nagios Plugins bug tracker that used to be at Nagios itself. I've just copied this bug over. I'm not the original reporter and have no idea about the thoughts about this bug. This used to be: http://tracker.nagios.org/view.php?id=268 -------------------------------------------------------------------------------- bva: -------------------------------------------------------------------------------- There are thousand of inet aliases on same interface on Nagios host. And some of switches which I need to check, accepts ICMP only from certain internal addresses, but default route policy forward packets through wrong gateway. I couldn't change routing and settings on switches. The solution [for me] is to specify the source address for check_ping. Used nagios-plugins-1.4.15 [nagios]> ./check_ping -H 192.168.17.114 -w 3000.0,80% -c 5000.0,100% -p 1 PING CRITICAL - Packet loss = 100%|rta=5000.000000ms;3000.000000;5000.000000;0.000000 pl=100%;80;100;0 [nagios]> [nagios]> route get 192.168.17.114 route to: 192.168.17.114 destination: 192.168.17.112 mask: 255.255.255.252 gateway: cat1 interface: vlan1 flags: recvpipe sendpipe ssthresh rtt,msec rttvar hopcount mtu expire 0 0 0 0 0 0 1500 0 [nagios]> [nagios]> ./check_ping2 -S 192.168.150.3 -H 192.168.17.114 -w 3000.0,80% -c 5000.0,100% -p 1 PING OK - Packet loss = 0%, RTA = 3.67 ms|rta=3.668000ms;3000.000000;5000.000000;0.000000 pl=0%;80;100;0 ---------------------------------------------------------------------- Comment By: laurent (laurentt) Date: 2013-04-25 15:14 Message: Hi, I also think the source address option to check_ping and check_fping would make sense. btw, there is a a source selection option in fping Here my setup: I have a nagios server with several network interfaces as well. I do not run nagios as root. I want nagios to initiate checks from an interface that is not the default interface (default route doesn't go through this it) It's kind of easy, I use iptables and the owner module + policy routing based on fwmark. It works for udp and tcp. When it's about check_ping or check_fping, they both exec a setuid binary. In the end the icmp check is initiated by root and is not matched by the iptables+policy routing. The patch isn't intrusive, you might not like it as it is but it definitely adds an useful feature. nothing dubious about it imho. I'm about to implement it and deploy it anyway, Thanks C?lestyo ! ---------------------------------------------------------------------- Comment By: J. Bern (j-bern) Date: 2012-08-01 09:38 Message: This approach uses a dubitable feature of the underlying "ping" command (which is absent from, e.g., fping) to work around the lack of access to the routing config (or, for that matter, iptables SNAT) to solve the *actual* problem. As soon as the switches need to be monitored, say, via SNMP, it'll reappear with a vengeance. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=397597&aid=3552828&group_id=29880 From noreply at sourceforge.net Fri Apr 26 00:32:32 2013 From: noreply at sourceforge.net (SourceForge.net) Date: Thu, 25 Apr 2013 15:32:32 -0700 Subject: [Nagiosplug-devel] [ nagiosplug-Bugs-3552828 ] Define source ip for check_ping. Message-ID: Bugs item #3552828, was opened at 2012-07-31 15:53 Message generated for change (Comment added) made by laurentt You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=397597&aid=3552828&group_id=29880 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: C?lestyo (calestyo) Assigned to: Nobody/Anonymous (nobody) Summary: Define source ip for check_ping. Initial Comment: Hi. This is from the old / soon to be disabled again Nagios Plugins bug tracker that used to be at Nagios itself. I've just copied this bug over. I'm not the original reporter and have no idea about the thoughts about this bug. This used to be: http://tracker.nagios.org/view.php?id=268 -------------------------------------------------------------------------------- bva: -------------------------------------------------------------------------------- There are thousand of inet aliases on same interface on Nagios host. And some of switches which I need to check, accepts ICMP only from certain internal addresses, but default route policy forward packets through wrong gateway. I couldn't change routing and settings on switches. The solution [for me] is to specify the source address for check_ping. Used nagios-plugins-1.4.15 [nagios]> ./check_ping -H 192.168.17.114 -w 3000.0,80% -c 5000.0,100% -p 1 PING CRITICAL - Packet loss = 100%|rta=5000.000000ms;3000.000000;5000.000000;0.000000 pl=100%;80;100;0 [nagios]> [nagios]> route get 192.168.17.114 route to: 192.168.17.114 destination: 192.168.17.112 mask: 255.255.255.252 gateway: cat1 interface: vlan1 flags: recvpipe sendpipe ssthresh rtt,msec rttvar hopcount mtu expire 0 0 0 0 0 0 1500 0 [nagios]> [nagios]> ./check_ping2 -S 192.168.150.3 -H 192.168.17.114 -w 3000.0,80% -c 5000.0,100% -p 1 PING OK - Packet loss = 0%, RTA = 3.67 ms|rta=3.668000ms;3000.000000;5000.000000;0.000000 pl=0%;80;100;0 ---------------------------------------------------------------------- Comment By: laurent (laurentt) Date: 2013-04-25 15:32 Message: you might as well want to check ID: 3575281 ---------------------------------------------------------------------- Comment By: laurent (laurentt) Date: 2013-04-25 15:14 Message: Hi, I also think the source address option to check_ping and check_fping would make sense. btw, there is a a source selection option in fping Here my setup: I have a nagios server with several network interfaces as well. I do not run nagios as root. I want nagios to initiate checks from an interface that is not the default interface (default route doesn't go through this it) It's kind of easy, I use iptables and the owner module + policy routing based on fwmark. It works for udp and tcp. When it's about check_ping or check_fping, they both exec a setuid binary. In the end the icmp check is initiated by root and is not matched by the iptables+policy routing. The patch isn't intrusive, you might not like it as it is but it definitely adds an useful feature. nothing dubious about it imho. I'm about to implement it and deploy it anyway, Thanks C?lestyo ! ---------------------------------------------------------------------- Comment By: J. Bern (j-bern) Date: 2012-08-01 09:38 Message: This approach uses a dubitable feature of the underlying "ping" command (which is absent from, e.g., fping) to work around the lack of access to the routing config (or, for that matter, iptables SNAT) to solve the *actual* problem. As soon as the switches need to be monitored, say, via SNMP, it'll reappear with a vengeance. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=397597&aid=3552828&group_id=29880 From noreply at sourceforge.net Tue Apr 30 12:38:02 2013 From: noreply at sourceforge.net (SourceForge.net) Date: Tue, 30 Apr 2013 03:38:02 -0700 Subject: [Nagiosplug-devel] [ nagiosplug-Patches-3612263 ] Expanded SSL Version Selection; Example Use in check_http Message-ID: Patches item #3612263, was opened at 2013-04-30 03:38 Message generated for change (Tracker Item Submitted) made by j-bern You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=397599&aid=3612263&group_id=29880 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Enhancement Group: release-1.4.16 Status: Open Resolution: None Priority: 5 Private: No Submitted By: J. Bern (j-bern) Assigned to: Nobody/Anonymous (nobody) Summary: Expanded SSL Version Selection; Example Use in check_http Initial Comment: I had a problem today which seems to have been reported in more or less similar fashion in the bug tracker several times: Misunderstandings between check_http and server implementations that do not support specific SSL/TLS versions. (In my case, the server is a web app running in a CentOS 6 Tomcat 7 and refuses standard check_http requests because of SSLv2 being enabled.) I noted that the current (1.4.16) options do *not* allow to disable SSLv2 but leave *both* SSLv3 and TLSv1 enabled - so I added negative values to do just that into sslutils.c and (as an example case) check_http.c. Note that I didn't guard against old OpenSSL versions which may not have the required options ... [root at nagios nagios-plugins-1.4.16b]# plugins/check_http --ssl $PARAMS CRITICAL - Cannot make SSL connection. 23666:error:14077410:SSL routines:SSL23_GET_SERVER_HELLO:sslv3 alert handshake failure:s23_clnt.c:583: [root at nagios nagios-plugins-1.4.16b]# for SSLVER in 3 2 1 -1 -2 -3 ; do plugins/check_http --ssl=$SSLVER $PARAMS 2>&1 | sed -e "s/^/$SSLVER /" ; done 3 HTTP OK: HTTP/1.1 200 OK - 338 bytes in 0,070 second response time |time=0,069910s;;;0,000000 size=338B;;;0 2 CRITICAL - Cannot make SSL connection. 1 HTTP OK: HTTP/1.1 200 OK - 338 bytes in 0,057 second response time |time=0,056833s;;;0,000000 size=338B;;;0 -1 CRITICAL - Cannot make SSL connection. -1 19823:error:14077410:SSL routines:SSL23_GET_SERVER_HELLO:sslv3 alert handshake failure:s23_clnt.c:583: -2 HTTP OK: HTTP/1.1 200 OK - 338 bytes in 0,061 second response time |time=0,061420s;;;0,000000 size=338B;;;0 -3 CRITICAL - Cannot make SSL connection. -3 19827:error:14077410:SSL routines:SSL23_GET_SERVER_HELLO:sslv3 alert handshake failure:s23_clnt.c:583: ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=397599&aid=3612263&group_id=29880