From mox87 at mail.ru Thu Feb 4 11:43:58 2010 From: mox87 at mail.ru (=?koi8-r?Q?=F0=C1=D7=C5=CC_=F4=C9=CD=CF=C6=C5=C5=D7?=) Date: Thu, 04 Feb 2010 13:43:58 +0300 Subject: [Nagiosplug-devel] =?koi8-r?b?Y2hlY2tfcGluZyBlcnJvciBpbiBGcmVl?= =?koi8-r?b?QlNE?= Message-ID: Hello folks! I wrote about this problem earlier (http://article.gmane.org/gmane.network.nagios.plugins.devel/6176) Now it still is present. Please, use this patch --- check_ping.c Thu Feb 4 13:32:11 2010 +++ /usr/home/ptimofeev/check_ping_my.c Thu Feb 4 13:31:23 2010 @@ -537,6 +537,8 @@ die (STATE_CRITICAL, _("CRITICAL - Host not found (%s)"), addr); else if (strstr (buf, "Time to live exceeded")) die (STATE_CRITICAL, _("CRITICAL - Time to live exceeded (%s)"), addr); + else if (strstr (buf, "Host is down")) + die (STATE_CRITICAL, _("CRITICAL - Host is down (%s)"), addr); if (strstr (buf, "(DUP!)") || strstr (buf, "DUPLICATES FOUND")) { if (warn_text == NULL) This is FreeBSD specified problem. From waja at cyconet.org Thu Feb 4 14:54:05 2010 From: waja at cyconet.org (Jan Wagner) Date: Thu, 4 Feb 2010 14:54:05 +0100 Subject: [Nagiosplug-devel] Error in check_ping In-Reply-To: References: Message-ID: <201002041454.08720.waja@cyconet.org> Hi Pavel, On Wednesday 05 November 2008 12:48:12 ????? ???????? wrote: > If you use standart ping util to pinging this hosts you get this: could it be, that you are using inetutils-ping? Or is this anything else? With kind regards, Jan. -- Never write mail to , you have been warned! -----BEGIN GEEK CODE BLOCK----- Version: 3.12 GIT d-- s+: a C+++ UL++++ P+ L+++ E--- W+++ N+++ o++ K++ w--- O M V- PS PE Y++ PGP++ t-- 5 X R tv- b+ DI D+ G++ e++ h---- r+++ y++++ ------END GEEK CODE BLOCK------ -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part. URL: From noreply at sourceforge.net Fri Feb 5 14:59:49 2010 From: noreply at sourceforge.net (SourceForge.net) Date: Fri, 05 Feb 2010 13:59:49 +0000 Subject: [Nagiosplug-devel] [ nagiosplug-Bugs-2946553 ] check_dns returns incorrect state when specifying server Message-ID: Bugs item #2946553, was opened at 2010-02-05 13:59 Message generated for change (Tracker Item Submitted) made by dicko82 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=397597&aid=2946553&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: dicko (dicko82) Assigned to: Nobody/Anonymous (nobody) Summary: check_dns returns incorrect state when specifying server Initial Comment: Plugin Version (-V output): check_dns v1992 (nagios-plugins 1.4.13) Plugin Name: check_dns Plugin Commandline showing issues: /usr/lib/nagios/plugins/check_dns -H www.test.com -s 1.1.1.1 Operating System: Red Hat Enterprise Linux Server release 5.4 (Tikanga) An incorrect state is returned when checking that the dns server ( 1.1.1.1 ) can resolve the host www.test.com when the dns server is down. The following command is used /usr/lib/nagios/plugins/check_dns -H www.test.com -s 1.1.1.1 If the DNS server is unavailable the check still returns OK. This worked correctly on RHEL 5.3 but not in Rhel 5.4 It appears that the behaviour of nslookup has changed between bind-utils-9.3.4-10.P1.el5 and bind-utils-9.3.6-4.P1.el5 On RHEL 5.3 bind-utils-9.3.4-10.P1.el5, nslookup timed out when querying against a server that was not working. [root at nagios nagios]# nslookup www.rm.com 194.238.49.43 ;; connection timed out; no servers could be reached On RHEL 5.4 bind-utils-9.3.6-4.P1.el5, the same query against a non existent dns server returns an ip address. [root at nagios ~]# nslookup www.rm.com 1.1.1.1 Server: 10.34.1.11 Address: 10.34.1.11#53 Non-authoritative answer: Name: www.rm.com Address: 2.2.2.2 It appears that nslookup now makes best efforts to resolve the query even if it cant resolve it against the server specified. This results in an incorrect state being returned when using check dns to ensure that a specific mail server is working correctly. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=397597&aid=2946553&group_id=29880 From davidb at srihosting.com Sat Feb 13 00:47:35 2010 From: davidb at srihosting.com (David Beuving) Date: Fri, 12 Feb 2010 15:47:35 -0800 Subject: [Nagiosplug-devel] check_http bug? Message-ID: <4B75E897.8050106@srihosting.com> Hello, I have found a certain behavior in the check_http plugin that seems like a bug to me. When using the plugin in verbose mode, it responds showing this as part of the report: http://ipaddress:port/path This leads me to believe that it is sending the ipaddress as the host header rather than the hostname, but after looking at the code it is clear the check works by sending the hostname it simply shows ipaddress in the verbose response. I have replaced line 912 in check_http.c: use_ssl ? "https" : "http", server_address, with use_ssl ? "https" : "http", host_name ? host_name : server_address, Please let me know if this is a bug and something you will update in the next release or if it is meant to work this way. Thanks, David From noreply at sourceforge.net Sun Feb 14 16:56:10 2010 From: noreply at sourceforge.net (SourceForge.net) Date: Sun, 14 Feb 2010 15:56:10 +0000 Subject: [Nagiosplug-devel] [ nagiosplug-Feature Requests-2951604 ] check_snmp - add unit in performance data Message-ID: Feature Requests item #2951604, was opened at 2010-02-14 16:56 Message generated for change (Tracker Item Submitted) made by bartoszbiegun You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=397600&aid=2951604&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 Priority: 5 Private: No Submitted By: bartosz.biegun (bartoszbiegun) Assigned to: Nobody/Anonymous (nobody) Summary: check_snmp - add unit in performance data Initial Comment: Add unit in performance data, pleese. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=397600&aid=2951604&group_id=29880 From noreply at sourceforge.net Tue Feb 16 16:41:55 2010 From: noreply at sourceforge.net (SourceForge.net) Date: Tue, 16 Feb 2010 15:41:55 +0000 Subject: [Nagiosplug-devel] [ nagiosplug-Bugs-2952850 ] Unspecified performance data format for threshold ranges Message-ID: Bugs item #2952850, was opened at 2010-02-16 16:41 Message generated for change (Tracker Item Submitted) made by patricia_jung You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=397597&aid=2952850&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: Interface (example) Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Patricia Jung (patricia_jung) Assigned to: Nobody/Anonymous (nobody) Summary: Unspecified performance data format for threshold ranges Initial Comment: Hello there, for thresholds given as ranges it still seems that performance data can't be implemented properly as the developer guidelines do not specify an appropriate format. I am aware of that this is a known issue (see e.g. http://nagiosplugins.org/rfc/new_threshold_syntax), but I would like to know whether there has been some progress recently. If so please change the developer guidelines accordingly, if not please provide a specification. Thanks Patricia ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=397597&aid=2952850&group_id=29880 From noreply at sourceforge.net Wed Feb 17 09:41:46 2010 From: noreply at sourceforge.net (SourceForge.net) Date: Wed, 17 Feb 2010 08:41:46 +0000 Subject: [Nagiosplug-devel] [ nagiosplug-Bugs-2953364 ] Unspecified performance data format for threshold ranges Message-ID: Bugs item #2953364, was opened at 2010-02-17 09:41 Message generated for change (Tracker Item Submitted) made by patricia_jung You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=397597&aid=2953364&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: Interface (example) Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Patricia Jung (patricia_jung) Assigned to: Nobody/Anonymous (nobody) Summary: Unspecified performance data format for threshold ranges Initial Comment: Hello there, for thresholds given as ranges it still seems that performance data can't be implemented properly as the developer guidelines do not specify an appropriate format. I am aware of that this is a known issue (see e.g. http://nagiosplugins.org/rfc/new_threshold_syntax), but I would like to know whether there has been some progress recently. If so please change the developer guidelines accordingly, if not please provide a specification. Thanks Patricia ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=397597&aid=2953364&group_id=29880 From noreply at sourceforge.net Wed Feb 17 09:59:29 2010 From: noreply at sourceforge.net (SourceForge.net) Date: Wed, 17 Feb 2010 08:59:29 +0000 Subject: [Nagiosplug-devel] [ nagiosplug-Bugs-2953364 ] Unspecified performance data format for threshold ranges Message-ID: Bugs item #2953364, was opened at 2010-02-17 09:41 Message generated for change (Comment added) made by patricia_jung You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=397597&aid=2953364&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: Interface (example) Group: None >Status: Deleted Resolution: None >Priority: 1 Private: No Submitted By: Patricia Jung (patricia_jung) Assigned to: Nobody/Anonymous (nobody) Summary: Unspecified performance data format for threshold ranges Initial Comment: Hello there, for thresholds given as ranges it still seems that performance data can't be implemented properly as the developer guidelines do not specify an appropriate format. I am aware of that this is a known issue (see e.g. http://nagiosplugins.org/rfc/new_threshold_syntax), but I would like to know whether there has been some progress recently. If so please change the developer guidelines accordingly, if not please provide a specification. Thanks Patricia ---------------------------------------------------------------------- >Comment By: Patricia Jung (patricia_jung) Date: 2010-02-17 09:59 Message: This is a duplicate of 2952850, and I have no idea why it was created. Please delete. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=397597&aid=2953364&group_id=29880 From noreply at sourceforge.net Tue Feb 23 22:22:30 2010 From: noreply at sourceforge.net (SourceForge.net) Date: Tue, 23 Feb 2010 21:22:30 +0000 Subject: [Nagiosplug-devel] [ nagiosplug-Patches-2957455 ] check_http leaks memory for pages larger than buffer Message-ID: Patches item #2957455, was opened at 2010-02-23 22:22 Message generated for change (Tracker Item Submitted) made by jimmybergman You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=397599&aid=2957455&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: Bugfix Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Jimmy Bergman (jimmybergman) Assigned to: Nobody/Anonymous (nobody) Summary: check_http leaks memory for pages larger than buffer Initial Comment: Since asprintf allocates a new buffer and is used in the main check_http receive loop like: asprintf (&full_page, "%s%s", full_page, buffer); full_page is overwritten every iteration of the loop, thereby leaking lots of memory. This makes check_http use 460 MB resident memory when downloading a 16 MB file completely reproduceable. The attached patch fixes this bug by making asprintf store the reference to the new string in a separate pointer and freeing the old one on each iteration instead, thus only keeping one version of the page in memory. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=397599&aid=2957455&group_id=29880 From benjamin.stier at ub.uni-tuebingen.de Fri Feb 26 10:12:37 2010 From: benjamin.stier at ub.uni-tuebingen.de (Benjamin Stier) Date: Fri, 26 Feb 2010 10:12:37 +0100 Subject: [Nagiosplug-devel] Patch for check_log: ignore patterns Message-ID: <20100226091237.GA8505@hapi.ub.uni-tuebingen.de> Hi list, I wrote a small patch for the check_log plugin. This patch allows to specify a regexp via --ignore which you don't want to be checked. My intention for this was, that I only check for crashing processes with "exited with signal". But some programs crash everytime, especially when building ports (conftest, apr and stuff). I would like to know if this patch can be put upstream, so I wouldn't have to patch it for myself on every update. Here's the patch: ============================================================================== --- /usr/local/libexec/nagios/check_log 2009-07-03 20:13:05.000000000 +0200 +++ check_log 2010-02-26 00:18:40.000000000 +0100 @@ -76,7 +76,7 @@ . $PROGPATH/utils.sh print_usage() { - echo "Usage: $PROGNAME -F logfile -O oldlog -q query" + echo "Usage: $PROGNAME -F logfile -O oldlog -q query [-i ignoreregexp]" echo "Usage: $PROGNAME --help" echo "Usage: $PROGNAME --version" } @@ -139,6 +139,14 @@ oldlog=$2 shift ;; + -i) + nomatch=$2 + shift + ;; + --ignore) + nomatch=$2 + shift + ;; --query) query=$2 shift @@ -174,6 +182,14 @@ exit $STATE_UNKNOWN fi +# Maybe we want to ignore something +# It's a simple egrep to discard this regexp +if [ ! -z $nomatch ]; then + nomatch="|($nomatch)" +else + nomatch='' +fi + # If the old log file doesn't exist, this must be the first time # we're running this test, so copy the original log file over to # the old diff file and exit @@ -197,7 +213,7 @@ $CHMOD 600 $tempdiff fi -$DIFF $logfile $oldlog | $GREP -v "^>" > $tempdiff +$DIFF $logfile $oldlog | $GREP -v "^>$nomatch" > $tempdiff # Count the number of matching log entries we have count=`$GREP -c "$query" $tempdiff` ============================================================================== Kind regards, Benjamin From noreply at sourceforge.net Fri Feb 26 17:22:05 2010 From: noreply at sourceforge.net (SourceForge.net) Date: Fri, 26 Feb 2010 16:22:05 +0000 Subject: [Nagiosplug-devel] [ nagiosplug-Patches-2957455 ] check_http leaks memory for pages larger than buffer Message-ID: Patches item #2957455, was opened at 2010-02-23 21:22 Message generated for change (Comment added) made by tonvoon You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=397599&aid=2957455&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: Bugfix Group: None >Status: Closed >Resolution: Fixed Priority: 5 Private: No Submitted By: Jimmy Bergman (jimmybergman) >Assigned to: Ton Voon (tonvoon) Summary: check_http leaks memory for pages larger than buffer Initial Comment: Since asprintf allocates a new buffer and is used in the main check_http receive loop like: asprintf (&full_page, "%s%s", full_page, buffer); full_page is overwritten every iteration of the loop, thereby leaking lots of memory. This makes check_http use 460 MB resident memory when downloading a 16 MB file completely reproduceable. The attached patch fixes this bug by making asprintf store the reference to the new string in a separate pointer and freeing the old one on each iteration instead, thus only keeping one version of the page in memory. ---------------------------------------------------------------------- >Comment By: Ton Voon (tonvoon) Date: 2010-02-26 16:22 Message: Jimmy, Thanks for the patch. All tests passed in tests/check_http.t with the change. Have applied to git, so should be in the next snapshot. Ton ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=397599&aid=2957455&group_id=29880