From noreply at sourceforge.net Fri Jul 3 02:25:41 2009 From: noreply at sourceforge.net (SourceForge.net) Date: Fri, 03 Jul 2009 00:25:41 +0000 Subject: [Nagiosplug-devel] [ nagiosplug-Patches-2816049 ] Solaris pst3 string functions undeclared Message-ID: Patches item #2816049, was opened at 2009-07-03 10:25 Message generated for change (Tracker Item Submitted) made by dejavu4u2 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=397599&aid=2816049&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: Grant Byers (dejavu4u2) Assigned to: Nobody/Anonymous (nobody) Summary: Solaris pst3 string functions undeclared Initial Comment: pst3.c doesn't include string.h (or unistd.h) root# ./pst3 S UID PID PPID VSZ RSS %CPU COMMAND ARGS Segmentation Fault (core dumped) This is due to string functions such as strdup, strchr & strrchr not being declared, thus returning int. Simply including the necessary headers SunOS unix 5.10 Generic_138888-01 sun4u sparc SUNW,Sun-Fire-V890 Sun Studio Compiler 12 root# /opt/SUNWspro/bin/cc -V cc: Sun C 5.9 SunOS_sparc Patch 124867-01 2007/07/12 /opt/SUNWspro/bin/cc -o pst3 -m64 pst3.c --- pst3.c Fri Jul 3 10:16:28 2009 +++ pst3.c.gbst Fri Jul 3 10:16:39 2009 @@ -43,6 +43,8 @@ #include #include +#include +#include #include #include #include ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=397599&aid=2816049&group_id=29880 From perldork at webwizarddesign.com Wed Jul 8 18:53:55 2009 From: perldork at webwizarddesign.com (Max) Date: Wed, 8 Jul 2009 12:53:55 -0400 Subject: [Nagiosplug-devel] Suggested code addition to perl Nagios::Plugin module - instance methods for starting and resetting a global alarm() Message-ID: Hi, We use this extensively in our scripts, simple addition, but keeps code nice and clean. I realize this is simplistic and will break if the user uses a module that sets alarm() after the plugin alarm is set, we mostly use this in my subclass of Nagios::Plugin, Nagios::Plugin::SNMP, but use it for some non-SNMP plugins as well. - Max Example use: my $plugin = Nagios::Plugin->new(...); # Starts a timer only if the user provided a positive integer to --timeout; # If timeout is reached, will exit with UNKNOWN and error message. $plugin->start_timer(); ... code ... code # All done, reset so alarm is not triggered. $plugin->reset_timer(); - Max Code: # ------------------------------------------------------------------------- # NP - time out helpers # Start a global timer for the plugin sub start_timer { my $self = shift; my $timeout = $self->opts->get('timeout'); return if ((! defined $timeout) || ($timeout < 1)); $SIG{'ALRM'} = sub { $self->nagios_exit(UNKNOWN, "Plugin timeout (${timeout}s) exceeded!"); }; alarm($timeout); } # Reset the global counter sub reset_timer { my $self = shift; alarm(0); } From william at leibzon.org Wed Jul 8 21:03:42 2009 From: william at leibzon.org (William Leibzon) Date: Wed, 8 Jul 2009 12:03:42 -0700 Subject: [Nagiosplug-devel] Suggested code addition to perl Nagios::Plugin module - instance methods for starting and resetting a global alarm() In-Reply-To: References: Message-ID: I don't use Nagios::Plugin library but I have this type of code in half of my plugins. I suggest not only adding to the library but actually making a default or at least recommended in the docs. It comes real handy when your plugin has to call external commands that may hang - you don't want any extra zombie processes, etc. On Wed, Jul 8, 2009 at 9:53 AM, Max wrote: > Hi, > > We use this extensively in our scripts, simple addition, but keeps > code nice and clean. I realize this is simplistic and will break if > the user uses a module that sets alarm() after the plugin alarm is > set, we mostly use this in my subclass of Nagios::Plugin, > Nagios::Plugin::SNMP, but use it for some non-SNMP plugins as well. > > - Max > > Example use: > > my $plugin = Nagios::Plugin->new(...); > > # Starts a timer only if the user provided a positive integer to > --timeout; > # If timeout is reached, will exit with UNKNOWN and error message. > > $plugin->start_timer(); > > ... code > ... code > > # All done, reset so alarm is not triggered. > $plugin->reset_timer(); > > - Max > > Code: > > # ------------------------------------------------------------------------- > # NP - time out helpers > > # Start a global timer for the plugin > sub start_timer { > > my $self = shift; > my $timeout = $self->opts->get('timeout'); > > return if ((! defined $timeout) || ($timeout < 1)); > > $SIG{'ALRM'} = sub { > $self->nagios_exit(UNKNOWN, "Plugin timeout (${timeout}s) > exceeded!"); > }; > > alarm($timeout); > > } > > # Reset the global counter > sub reset_timer { > my $self = shift; > alarm(0); > } > > > ------------------------------------------------------------------------------ > Enter the BlackBerry Developer Challenge > This is your chance to win up to $100,000 in prizes! For a limited time, > vendors submitting new applications to BlackBerry App World(TM) will have > the opportunity to enter the BlackBerry Developer Challenge. See full prize > details at: http://p.sf.net/sfu/Challenge > _______________________________________________________ > Nagios Plugin Development Mailing List > Nagiosplug-devel at lists.sourceforge.net > Unsubscribe at > https://lists.sourceforge.net/lists/listinfo/nagiosplug-devel > ::: Please include plugins version (-v) and OS when reporting any issue. > ::: Messages without supporting info will risk being sent to /dev/null -------------- next part -------------- An HTML attachment was scrubbed... URL: From dhorn2000 at gmail.com Wed Jul 8 23:25:14 2009 From: dhorn2000 at gmail.com (David Horn) Date: Wed, 8 Jul 2009 17:25:14 -0400 Subject: [Nagiosplug-devel] check_dns.c patch review request Message-ID: <25ff90d60907081425v338f9fbak4d3a8ba2775c3cbd@mail.gmail.com> This is just a request to please review and/or commit the changes to check_dns to support IPv6 AAAA record types (and others). Let me know if there are any test cases you want me to write, or any additional information or changes needed to accept this patch. Patch is attached to this tracker entry: https://sourceforge.net/tracker/?func=detail&aid=2741269&group_id=29880&atid=397599 --Thanks in advance. -_Dave From shadhin71 at gmail.com Wed Jul 8 23:27:01 2009 From: shadhin71 at gmail.com (shadih rahman) Date: Wed, 8 Jul 2009 17:27:01 -0400 Subject: [Nagiosplug-devel] multiple options with same argument. Message-ID: <6db4a4200907081427k6ed707e0k1480bc1bd6a07c12@mail.gmail.com> All, how do you parse multiple of same argument in Nagios::Plungin. I am calling my check as this perl check_htturl -H wind.columbia.edu -u username -p pass -P /login -q me -q you when I print -q it should print me&you but its not doing that. This is my code. Please advise on this. Thanks #!/usr/bin/perl -w =head1 NAME check_httpurl - Check httpurl with sequential query. =head1 AUTHOR Shadhin Rahman =head1 SYNOPSYS This particular plugin can do sequential query upon first query, ideal for CAS type authentication check =head1 REQUIRES Perl5.004, strict, URI, Nagios::Plugin, HTTP::Request::Common, LWP::UserAgent =head1 EXPORTS Nothing =head1 DESCRIPTION OK if response code is 200 and regex checks succeed, or if response code is 200 and no regex checks were specified UNKNOWN if HTTP response status code class is not recognized WARNING if HTTP response status code is class 1xx or 3xx CRITICAL if HTTP response status code is class 4xx or 5xx, or if class is 200 and $matchregex not found or if class is 200 and $errorregex is found =cut use warnings; use strict; no warnings qw( redefine prototype ); BEGIN { use Nagios::Plugin; use URI; use HTTP::Request::Common; use LWP::UserAgent; } # END BEGIN my( $usagemsg ) = < [-w ] [-c ][-v|d] [-h] USAGE my( $blurb ) = <new( usage => "Usage: %s [ -v|--verbose ] [-H ] " . "[ -c|--critical= ] [ -w|--warning= ]", ); my( $plugin ) = Nagios::Plugin->new( shortname => 'check_httpurl', usage => $usagemsg, version => '0.2', blurb => $blurb, license => $license, ); =head2 Plugin Metadata Metadata is documented in L and L. Other available options of interest include C, C, and C. =cut $plugin->add_arg( spec => 'hostname|H=s', help => [ "Hostname to query", "IP address to query", ], label => [ 'HOSTNAME', 'IP' ], required => 1, ); $plugin->add_arg( spec => 'ssl|S=s', help => [ "confifrms ssl transmission", ], label => [ 'SSL' ], required => 0, ); $plugin->add_arg( spec => 'username|u=s', help => "username for authentication", label => [ 'username' ], required => 1, ); $plugin->add_arg( spec => 'password|p=s', help => "password for authentication", label => [ 'password' ], required => 1, ); $plugin->add_arg( spec => 'url|P=s', help => "path of the url", label => [ 'path' ], required => 1, ); $plugin->add_arg( spec => 'query|q=s', help => "additional query to inject", label => [ 'query' ], required => 0, ); $plugin->add_arg( spec => 'regex|r=s', help => "regex to match", label => [ 'regex' ], required => 0, ); $plugin->getopts; my ( $opts ) =$plugin->opts; my ( $server, $username, $password, $path, $query, $regex ); $server=$opts->get('hostname'); $username = $opts->get('username'); $password=$opts->get('password'); $path=$opts->get('url'); if ( $query = $opts->get( 'query' ) ) { $query=join ( '&', $opts->get('query') ); } $regex=$opts->get('regex'); print $query ."\n"; -- Cordially, Shadhin Rahman -------------- next part -------------- An HTML attachment was scrubbed... URL: From dermoth at aei.ca Thu Jul 9 01:02:24 2009 From: dermoth at aei.ca (Thomas Guyot-Sionnest) Date: Wed, 08 Jul 2009 19:02:24 -0400 Subject: [Nagiosplug-devel] Suggested code addition to perl Nagios::Plugin module - instance methods for starting and resetting a global alarm() In-Reply-To: References: Message-ID: <4A552580.1060305@aei.ca> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 08/07/09 12:53 PM, Max wrote: > Hi, > > We use this extensively in our scripts, simple addition, but keeps > code nice and clean. I realize this is simplistic and will break if > the user uses a module that sets alarm() after the plugin alarm is > set, we mostly use this in my subclass of Nagios::Plugin, > Nagios::Plugin::SNMP, but use it for some non-SNMP plugins as well. > > - Max > > Example use: > > my $plugin = Nagios::Plugin->new(...); > > # Starts a timer only if the user provided a positive integer to --timeout; > # If timeout is reached, will exit with UNKNOWN and error message. > > $plugin->start_timer(); > > ... code > ... code > > # All done, reset so alarm is not triggered. > $plugin->reset_timer(); What you want is already implemented trough Nagios::Plugin::Getopt, which (among others) automatically parses the -t (or -0-timeout) argument. For example if you copy-paste this you'll trigger a timeout ("$" is your prompt): $ perl -MNagios::Plugin -e '$0="check_stuff"; '\ ' $n = Nagios::Plugin->new(usage=>"", timeout=>1); $n->getopts(); '\ ' alarm($n->opts->timeout); select(undef, undef, undef, 1.5); '\ ' $n->nagios_exit(OK, "All good");' Which return: CHECK_STUFF UNKNOWN - plugin timed out (timeout 1s) Here's like-by-line what it does: > $ perl -MNagios::Plugin -e '$0="check_stuff"; '\ Execute perl from command-line, load Nagios::Plugin and trick is into thinking the base command name is "check_stuff" > ' $n = Nagios::Plugin->new(usage=>"", timeout=>1); $n->getopts(); '\ Instantiate a new plugin, set a blank usage (normally you'd want to at least specify the -t option) and give it the default timeout. > ' alarm($n->opts->timeout); select(undef, undef, undef, 1.5); '\ Set alarm to the timeout passed to the plugin (default timeout of one) and then use select() to sleep 1.5 second) > ' $n->nagios_exit(OK, "All good");' This is the normal way to end the plugin but it gets never executed because the timeout kicks in There's likely place for enhancements (like defining the result code to send or passing our own SIGALRM sub), but whatever you do should be based on what I just shown. - -- Thomas -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFKVSWA6dZ+Kt5BchYRAodbAJ9zz8089H/k6BzTB5PKX6MSKYsjLwCfQ9Sh nfFznNzW1ovwkf9m0kqTX1g= =Wszy -----END PGP SIGNATURE----- From perldork at webwizarddesign.com Thu Jul 9 02:14:44 2009 From: perldork at webwizarddesign.com (Max) Date: Wed, 8 Jul 2009 20:14:44 -0400 Subject: [Nagiosplug-devel] Suggested code addition to perl Nagios::Plugin module - instance methods for starting and resetting a global alarm() In-Reply-To: <4A552580.1060305@aei.ca> References: <4A552580.1060305@aei.ca> Message-ID: Why make the user suddenly go out of an OO paradign and into a procedural one when n::p already has the timeout option implemented? I don't see the value of forcing the user to call alarm() instead of just putting a convenience method in n::p ... It is not like there are multiple alarm()-like calls to choose from in perl. There is only one, so why not wrap it in the instance and use the state (value for timeout) that the n::p instance already knows? On 7/8/09, Thomas Guyot-Sionnest wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > On 08/07/09 12:53 PM, Max wrote: >> Hi, >> >> We use this extensively in our scripts, simple addition, but keeps >> code nice and clean. I realize this is simplistic and will break if >> the user uses a module that sets alarm() after the plugin alarm is >> set, we mostly use this in my subclass of Nagios::Plugin, >> Nagios::Plugin::SNMP, but use it for some non-SNMP plugins as well. >> >> - Max >> >> Example use: >> >> my $plugin = Nagios::Plugin->new(...); >> >> # Starts a timer only if the user provided a positive integer to >> --timeout; >> # If timeout is reached, will exit with UNKNOWN and error message. >> >> $plugin->start_timer(); >> >> ... code >> ... code >> >> # All done, reset so alarm is not triggered. >> $plugin->reset_timer(); > > What you want is already implemented trough Nagios::Plugin::Getopt, > which (among others) automatically parses the -t (or -0-timeout) argument. > > For example if you copy-paste this you'll trigger a timeout ("$" is your > prompt): > $ perl -MNagios::Plugin -e '$0="check_stuff"; '\ > ' $n = Nagios::Plugin->new(usage=>"", timeout=>1); $n->getopts(); '\ > ' alarm($n->opts->timeout); select(undef, undef, undef, 1.5); '\ > ' $n->nagios_exit(OK, "All good");' > > Which return: > CHECK_STUFF UNKNOWN - plugin timed out (timeout 1s) > > > Here's like-by-line what it does: > >> $ perl -MNagios::Plugin -e '$0="check_stuff"; '\ > Execute perl from command-line, load Nagios::Plugin and trick is into > thinking the base command name is "check_stuff" > >> ' $n = Nagios::Plugin->new(usage=>"", timeout=>1); $n->getopts(); '\ > Instantiate a new plugin, set a blank usage (normally you'd want to at > least specify the -t option) and give it the default timeout. > >> ' alarm($n->opts->timeout); select(undef, undef, undef, 1.5); '\ > Set alarm to the timeout passed to the plugin (default timeout of one) > and then use select() to sleep 1.5 second) > >> ' $n->nagios_exit(OK, "All good");' > This is the normal way to end the plugin but it gets never executed > because the timeout kicks in > > > There's likely place for enhancements (like defining the result code to > send or passing our own SIGALRM sub), but whatever you do should be > based on what I just shown. > > - -- > Thomas > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.6 (GNU/Linux) > Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org > > iD8DBQFKVSWA6dZ+Kt5BchYRAodbAJ9zz8089H/k6BzTB5PKX6MSKYsjLwCfQ9Sh > nfFznNzW1ovwkf9m0kqTX1g= > =Wszy > -----END PGP SIGNATURE----- > > ------------------------------------------------------------------------------ > Enter the BlackBerry Developer Challenge > This is your chance to win up to $100,000 in prizes! For a limited time, > vendors submitting new applications to BlackBerry App World(TM) will have > the opportunity to enter the BlackBerry Developer Challenge. See full prize > details at: http://p.sf.net/sfu/Challenge > _______________________________________________________ > Nagios Plugin Development Mailing List > Nagiosplug-devel at lists.sourceforge.net > Unsubscribe at https://lists.sourceforge.net/lists/listinfo/nagiosplug-devel > ::: Please include plugins version (-v) and OS when reporting any issue. > ::: Messages without supporting info will risk being sent to /dev/null > From perldork at webwizarddesign.com Thu Jul 9 05:16:39 2009 From: perldork at webwizarddesign.com (Max) Date: Wed, 8 Jul 2009 23:16:39 -0400 Subject: [Nagiosplug-devel] Suggested code addition to perl Nagios::Plugin module - instance methods for starting and resetting a global alarm() In-Reply-To: <4A552580.1060305@aei.ca> References: <4A552580.1060305@aei.ca> Message-ID: On Wed, Jul 8, 2009 at 7:02 PM, Thomas Guyot-Sionnest wrote: > What you want is already implemented trough Nagios::Plugin::Getopt, > which (among others) automatically parses the -t (or -0-timeout) argument. I did say we subclass Nagios::Plugin, so the code you see in my code that calls ->opts->get('timeout') is calling your methods as I extend your module. I am not reimplimenting nor repeating code you have done. If you look at my module Nagios::Plugin::SNMP on CPAN you will see I don't reinvent any wheels you have already made :). > ' ?alarm($n->opts->timeout); This still doesn't make sense to me over having a simple wrapper around timeout in Nagios::Plugin so the user doesn't have to call alarm($n->opts->timeout) in their code every time they want to do a timeout instead of doing $plugin->start_timer(); which would also then make it easy to let the user override a default $SIG{'ALRM'} handler by passing a reference to a function in to either new() or to the wrapper function, e.g. $plugin->start_timer( sub { my $secs = $plugin->opts->get('timeout'); $plugin->exit(CRITICAL, "Timeout of ${secs} seconds breached!"); } ); From dermoth at aei.ca Fri Jul 10 04:34:06 2009 From: dermoth at aei.ca (Thomas Guyot-Sionnest) Date: Thu, 09 Jul 2009 22:34:06 -0400 Subject: [Nagiosplug-devel] Suggested code addition to perl Nagios::Plugin module - instance methods for starting and resetting a global alarm() In-Reply-To: References: <4A552580.1060305@aei.ca> Message-ID: <4A56A89E.9040007@aei.ca> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 08/07/09 11:16 PM, Max wrote: > On Wed, Jul 8, 2009 at 7:02 PM, Thomas Guyot-Sionnest wrote: >> What you want is already implemented trough Nagios::Plugin::Getopt, >> which (among others) automatically parses the -t (or -0-timeout) argument. > > I did say we subclass Nagios::Plugin, so the code you see in my code > that calls ->opts->get('timeout') is calling your methods as I extend > your module. I am not reimplimenting nor repeating code you have > done. If you look at my module Nagios::Plugin::SNMP on CPAN you will > see I don't reinvent any wheels you have already made :). > >> ' alarm($n->opts->timeout); > > This still doesn't make sense to me over having a simple wrapper > around timeout in Nagios::Plugin so the user doesn't have to call > alarm($n->opts->timeout) in their code every time they want to do a > timeout instead of doing > > $plugin->start_timer(); Sure, but I don't get why making such an issue about it... There would be nothing else in this function than a call to alarm($self->opts->timeout). > which would also then make it easy to let the user override a default > $SIG{'ALRM'} handler by passing a reference to a function in to either > new() or to the wrapper function, e.g. This is already possible to implement in the current way of doing it. > $plugin->start_timer( > sub { my $secs = $plugin->opts->get('timeout'); > $plugin->exit(CRITICAL, "Timeout of ${secs} seconds breached!"); } > ); I'm not a perl OO guru, but you'll probably need to pass $plugin (or any variable you need to access) to the sub somehow. Making is global will likely break ePN... - -- Thomas -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFKVqid6dZ+Kt5BchYRAh9dAJ9JEGhygOFlIn3UJBLM7LA5kBsX8gCeOALA lh7ocG7Pn/vuZz/IN+uzaZs= =OKxV -----END PGP SIGNATURE----- From dermoth at aei.ca Fri Jul 10 04:39:27 2009 From: dermoth at aei.ca (Thomas Guyot-Sionnest) Date: Thu, 09 Jul 2009 22:39:27 -0400 Subject: [Nagiosplug-devel] multiple options with same argument. In-Reply-To: <6db4a4200907081427k6ed707e0k1480bc1bd6a07c12@mail.gmail.com> References: <6db4a4200907081427k6ed707e0k1480bc1bd6a07c12@mail.gmail.com> Message-ID: <4A56A9DF.8010401@aei.ca> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 08/07/09 05:27 PM, shadih rahman wrote: > All, > how do you parse multiple of same argument in Nagios::Plungin. I am > calling my check as this > > perl check_htturl -H wind.columbia.edu -u > username -p pass -P /login -q me -q you > > when I print -q it should print me&you but its not doing that. This is > my code. Please advise on this. Thanks > Nagios::Pluin uses Getopt::Long to parse arguments, so its parameters are pretty much the same. While I doubt you can force N::P to return an array you can have Getopt::Long return a array reference. > $plugin->add_arg( > spec => 'query|q=s', > help => "additional query to inject", > label => [ 'query' ], > required => 0, > ); try with: spec => 'query|q=s@' Since it'll be a ref don't forget to deference it when you get it from $plugin->opts->query - -- Thomas -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFKVqnf6dZ+Kt5BchYRAqyxAJ0YH3qpu5FZxWDzp+mXu2SAc0oyMgCfYwzy nD7sZohL3qGiv8XnWkPcJjg= =E5N0 -----END PGP SIGNATURE----- From dermoth at aei.ca Fri Jul 10 05:07:32 2009 From: dermoth at aei.ca (Thomas Guyot-Sionnest) Date: Thu, 09 Jul 2009 23:07:32 -0400 Subject: [Nagiosplug-devel] check_dns.c patch review request In-Reply-To: <25ff90d60907081425v338f9fbak4d3a8ba2775c3cbd@mail.gmail.com> References: <25ff90d60907081425v338f9fbak4d3a8ba2775c3cbd@mail.gmail.com> Message-ID: <4A56B074.1080001@aei.ca> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 08/07/09 05:25 PM, David Horn wrote: > This is just a request to please review and/or commit the changes to > check_dns to support IPv6 AAAA record types (and others). > > Let me know if there are any test cases you want me to write, or any > additional information or changes needed to accept this patch. > > Patch is attached to this tracker entry: > https://sourceforge.net/tracker/?func=detail&aid=2741269&group_id=29880&atid=397599 It looks good. I just have one question - on what basis did you increase the ADDRESS_LENGTH macro? It would be helpful to know on what it's based or how it was calculated. Also, for inclusion we'll need to add tests too (plugins/t/check_dns.t). If you can write them that would be awesome, otherwise it would really help if you could at least give us a list of commands and what to expect from them (return code and/or text match). Thanks - -- Thomas -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFKVrB06dZ+Kt5BchYRAjUkAKDRw7nHLrL/JDRkcxZAZmVm5+C8vgCeJqW4 /um/wrIiMznzBqBhv6R6B6A= =Ovbo -----END PGP SIGNATURE----- From noreply at sourceforge.net Fri Jul 10 05:09:03 2009 From: noreply at sourceforge.net (SourceForge.net) Date: Fri, 10 Jul 2009 03:09:03 +0000 Subject: [Nagiosplug-devel] [ nagiosplug-Patches-2741269 ] check_dns: add AAAA, MX, TXT, SRV, CNAME Message-ID: Patches item #2741269, was opened at 2009-04-07 13:21 Message generated for change (Settings changed) made by dermoth You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=397599&aid=2741269&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: None Status: Open >Resolution: Accepted Priority: 5 Private: No Submitted By: David Horn (dhorn2000) >Assigned to: Thomas Guyot-Sionnest (dermoth) Summary: check_dns: add AAAA,MX,TXT,SRV,CNAME Initial Comment: Added optional support for the major DNS record types (AAAA, MX, TXT, SRV, CNAME, A, ANY). Specifically, allow for a new optional --querytype parameter, and a new optional --accept-cname parameter. Help text has been updated to reflect the changes as well. Patch is against SVN trunk of check_dns.c from April 7,2009. This change should be completely backwards compatible with existing check_dns usage and syntax. New features are off by default. ---------------------------------------------------------------------- >Comment By: Thomas Guyot-Sionnest (dermoth) Date: 2009-07-09 23:09 Message: Patch looks good. I'll get it in as soon as I receive the tests for it or find time to write them myself. ---------------------------------------------------------------------- Comment By: David Horn (dhorn2000) Date: 2009-04-07 15:26 Message: Added git version of patch. (Thanks Babar for the pointer to the repo) ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=397599&aid=2741269&group_id=29880 From perldork at webwizarddesign.com Fri Jul 10 05:33:18 2009 From: perldork at webwizarddesign.com (Max) Date: Thu, 9 Jul 2009 23:33:18 -0400 Subject: [Nagiosplug-devel] Suggested code addition to perl Nagios::Plugin module - instance methods for starting and resetting a global alarm() In-Reply-To: <4A56A89E.9040007@aei.ca> References: <4A552580.1060305@aei.ca> <4A56A89E.9040007@aei.ca> Message-ID: On Thu, Jul 9, 2009 at 10:34 PM, Thomas Guyot-Sionnest wrote: > $plugin->start_timer(); Sure, but I don't get why making such an issue about it... There would be nothing else in this function than a call to alarm($self->opts->timeout). Well, there is the wrapper to ensure that it is only called if timeout is defined and is greater than 0 as well if ((defined $self->opts->get('timeout') && ($self->opts->get('timeout') > 0) { ... } So that if timeout is for some reason not-defined the script will not throw an undefined value warning and cause ePN to kill the script. >> $plugin->start_timer( >> ? ? sub { my $secs = $plugin->opts->get('timeout'); >> ? ? ? ? ? ? ?$plugin->exit(CRITICAL, "Timeout of ${secs} seconds breached!"); ?} >> ); > > I'm not a perl OO guru, but you'll probably need to pass $plugin (or any > variable you need to access) to the sub somehow. Making is global will > likely break ePN... I am not a guru either. I have been doing OO perl since 2000 or thereabouts. If you define the subroutine within the scope of the method, $plugin is passed in within the scope it is defined, so it is not global, it is lexical to the plugin script file and will be marked for freeing when the $plugin instance is destroyed as it would only be referenced within the plugin itself, not stored in any module-level structure that would persist after the plugin instance is gone. Every perl plugin I write is meant to run clean under ePN, this code as well :). - Max From dermoth at aei.ca Fri Jul 10 05:55:34 2009 From: dermoth at aei.ca (Thomas Guyot-Sionnest) Date: Thu, 09 Jul 2009 23:55:34 -0400 Subject: [Nagiosplug-devel] check_dns.c patch review request In-Reply-To: <4A56B074.1080001@aei.ca> References: <25ff90d60907081425v338f9fbak4d3a8ba2775c3cbd@mail.gmail.com> <4A56B074.1080001@aei.ca> Message-ID: <4A56BBB6.6050208@aei.ca> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 09/07/09 11:07 PM, Thomas Guyot-Sionnest wrote: > On 08/07/09 05:25 PM, David Horn wrote: >> This is just a request to please review and/or commit the changes to >> check_dns to support IPv6 AAAA record types (and others). > >> Let me know if there are any test cases you want me to write, or any >> additional information or changes needed to accept this patch. > >> Patch is attached to this tracker entry: >> https://sourceforge.net/tracker/?func=detail&aid=2741269&group_id=29880&atid=397599 > > It looks good. I just have one question - on what basis did you increase > the ADDRESS_LENGTH macro? It would be helpful to know on what it's based > or how it was calculated. > > Also, for inclusion we'll need to add tests too (plugins/t/check_dns.t). > If you can write them that would be awesome, otherwise it would really > help if you could at least give us a list of commands and what to expect > from them (return code and/or text match). > > Thanks > With more in-depth look... > + /* Strip leading spaces */ > + for (; *temp_buffer != '\0' && *temp_buffer == ' '; temp_buffer++) > + /* NOOP */; Testing for *temp_buffer == ' ' is sufficient as \0 will evaluate as false. Even better is using isspace() to remove tabs as well. I would write it as: /* Strip leading spaces */ for (temp_buffer; isspace(temp_buffer[0]); temp_buffer++); The strip() function could be fixed to use isspace too... or just copy the code for np_extract_value in lib/utils_base.c: for (i=strlen(temp_buffer)-1; isspace(temp_buffer[i]); i--) temp_buffer[i] = '\0'; Finally, there's no reason to test if temp_buffer is NULL afterward. It can't be if it wasn't previously (at worse it will still be a pointer pointing to a '\0') and if it is, you crashed already. Note that in the leading strip loop, my code checks if temp_buffer is not null... You could add an if statement before the for loop too - here's my code in lib/utils_base.c: > if (value) for (i=strlen(value)-1; isspace(value[i]); i--) value[i] = '\0'; And then the NULL check could actually make it work if the buffer is passed as a NULL. - -- Thomas -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD4DBQFKVru26dZ+Kt5BchYRAoe/AJ9kn5Ehahb9Xd0MjLQxUqua1sqMZwCXdcbg kyuH8pFZGTQLLfGW6SdSoA== =9tgx -----END PGP SIGNATURE----- From dhorn2000 at gmail.com Sat Jul 11 05:08:53 2009 From: dhorn2000 at gmail.com (David Horn) Date: Fri, 10 Jul 2009 23:08:53 -0400 Subject: [Nagiosplug-devel] check_dns.c patch review request In-Reply-To: <4A56BBB6.6050208@aei.ca> References: <25ff90d60907081425v338f9fbak4d3a8ba2775c3cbd@mail.gmail.com> <4A56B074.1080001@aei.ca> <4A56BBB6.6050208@aei.ca> Message-ID: <25ff90d60907102008i46f1124eu91de87f7cbf3241f@mail.gmail.com> On Thu, Jul 9, 2009 at 11:55 PM, Thomas Guyot-Sionnest wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > On 09/07/09 11:07 PM, Thomas Guyot-Sionnest wrote: >> On 08/07/09 05:25 PM, David Horn wrote: >>> This is just a request to please review and/or commit the changes to >>> check_dns to support IPv6 AAAA record types (and others). >> >>> Let me know if there are any test cases you want me to write, or any >>> additional information or changes needed to accept this patch. >> >>> Patch is attached to this tracker entry: >>> https://sourceforge.net/tracker/?func=detail&aid=2741269&group_id=29880&atid=397599 >> >> It looks good. I just have one question - on what basis did you increase >> the ADDRESS_LENGTH macro? It would be helpful to know on what it's based >> or how it was calculated. I originally increased the ADDRESS_LENGTH macro (incorrectly) thinking that it was needed for IPv6, but after you asked the question, I did some research and found some actual answers: 1) String representations for IPv6 (.ip6.arpa reverse notation or standard presentation notation) do NOT need an increase above the original 256 bytes. 2) Standard "on the wire" DNS ascii notation of domain names result in a maximum length of 255 characters, hence the original setting. (RFC 2181/RFC 1034) 3) With IDN (International Domain Names), the presentation string (displayed to the user) is allocated in bind9 nslookup source as being 1024 bytes since certain country specific domains support multibyte. Since check_dns calls nslookup, the appropriate thing is probably to change this macro to 1024 to match. I will see if I can find some multibyte test cases. lib/dns/include/dns/name.h:#define DNS_NAME_MAXTEXT 1023 lib/dns/include/dns/name.h:#define DNS_NAME_FORMATSIZE (DNS_NAME_MAXTEXT + 1) >> >> Also, for inclusion we'll need to add tests too (plugins/t/check_dns.t). >> If you can write them that would be awesome, otherwise it would really >> help if you could at least give us a list of commands and what to expect >> from them (return code and/or text match). >> I will work on writing the tests needed. >> Thanks >> > > With more in-depth look... > >> + ? ? ?/* Strip leading spaces */ >> + ? ? ?for (; *temp_buffer != '\0' && *temp_buffer == ' '; temp_buffer++) >> + ? ? ? ?/* NOOP */; > 1) I do not mind cleaning up the string parsing a bit (I originally just moved existing code into a function to minimize changes). 2) There is also one "bug" I also did not fix (to preserve backwards compatability), that I can look into here as well. (When a dns query results in a response, but not an answer to the original question) > Testing for *temp_buffer == ' ' is sufficient as \0 will evaluate as > false. Even better is using isspace() to remove tabs as well. I would > write it as: > > ? ?/* Strip leading spaces */ > ? ?for (temp_buffer; isspace(temp_buffer[0]); temp_buffer++); > > The strip() function could be fixed to use isspace too... or just copy > the code for np_extract_value in lib/utils_base.c: > > ? ?for (i=strlen(temp_buffer)-1; isspace(temp_buffer[i]); i--) > ? ? ? ?temp_buffer[i] = '\0'; > > Finally, there's no reason to test if temp_buffer is NULL afterward. It > can't be if it wasn't previously (at worse it will still be a pointer > pointing to a '\0') and if it is, you crashed already. > > > Note that in the leading strip loop, my code checks if temp_buffer is > not null... You could add an if statement before the for loop too - > here's my code in lib/utils_base.c: > >> ? if (value) for (i=strlen(value)-1; isspace(value[i]); i--) value[i] = '\0'; > > And then the NULL check could actually make it work if the buffer is > passed as a NULL. > > - -- > Thomas > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.6 (GNU/Linux) > Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org > > iD4DBQFKVru26dZ+Kt5BchYRAoe/AJ9kn5Ehahb9Xd0MjLQxUqua1sqMZwCXdcbg > kyuH8pFZGTQLLfGW6SdSoA== > =9tgx > -----END PGP SIGNATURE----- > > ------------------------------------------------------------------------------ > Enter the BlackBerry Developer Challenge > This is your chance to win up to $100,000 in prizes! For a limited time, > vendors submitting new applications to BlackBerry App World(TM) will have > the opportunity to enter the BlackBerry Developer Challenge. See full prize > details at: http://p.sf.net/sfu/Challenge > _______________________________________________________ > Nagios Plugin Development Mailing List Nagiosplug-devel at lists.sourceforge.net > Unsubscribe at https://lists.sourceforge.net/lists/listinfo/nagiosplug-devel > ::: Please include plugins version (-v) and OS when reporting any issue. > ::: Messages without supporting info will risk being sent to /dev/null > From Gerhard.Lausser at consol.de Mon Jul 13 10:30:25 2009 From: Gerhard.Lausser at consol.de (Gerhard Lausser) Date: Mon, 13 Jul 2009 10:30:25 +0200 Subject: [Nagiosplug-devel] Perfdata pattern in Nagios::Plugin::Performance.pm Message-ID: <4FE55472156C452F922C652BCBCEEEA4@int.consol.de> Hi, according to the development guidelines, the = character is allowed in a label. 2.label can contain any characters 3.the single quotes for the label are optional. Required if spaces, = or ' are in the label Now i see in the function Nagios::Plugin::Performance::_parse the following pattern: $string =~ /^'?([^'=]+)'?=($value_re)([..... Shouldn't it be /^'?([^']+)'?=($value_re)([..... instead? I see no reason why the = is excluded. The pattern will try to match as much characters as possible so the = in '?=($value_re... will always be the = separating label from value. Do you agree or am i wrong because there is a reason why the = is excluded? Cheers, Gerhard From ton.voon at opsera.com Mon Jul 13 11:18:01 2009 From: ton.voon at opsera.com (Ton Voon) Date: Mon, 13 Jul 2009 10:18:01 +0100 Subject: [Nagiosplug-devel] Perfdata pattern in Nagios::Plugin::Performance.pm In-Reply-To: <4FE55472156C452F922C652BCBCEEEA4@int.consol.de> References: <4FE55472156C452F922C652BCBCEEEA4@int.consol.de> Message-ID: <64C6AC26-49CE-4A54-A897-3EF17397226B@opsera.com> On 13 Jul 2009, at 09:30, Gerhard Lausser wrote: > according to the development guidelines, the = character is allowed > in a > label. > > 2.label can contain any characters > 3.the single quotes for the label are optional. Required if spaces, > = or ' > are in the label > > Now i see in the function Nagios::Plugin::Performance::_parse the > following > pattern: > $string =~ /^'?([^'=]+)'?=($value_re)([..... > > Shouldn't it be /^'?([^']+)'?=($value_re)([..... instead? I see no > reason > why the = is excluded. The pattern will try to match as much > characters as > possible so the = in '?=($value_re... will always be the = > separating label > from value. > > Do you agree or am i wrong because there is a reason why the = is > excluded? One thing I'm learning is to try and keep the design restricted first and then open up as necessary. Trying to do things the other way round leads to holes in implementation. I think the parsing routines could probably do with a bit of work in a different way, rather than using regexps. Happy to take any patches that pass all the test cases. Turning the question around - what use case uses an equal sign in the label? Ton From dermoth at aei.ca Mon Jul 13 14:02:11 2009 From: dermoth at aei.ca (Thomas Guyot-Sionnest) Date: Mon, 13 Jul 2009 08:02:11 -0400 Subject: [Nagiosplug-devel] Perfdata pattern in Nagios::Plugin::Performance.pm In-Reply-To: <64C6AC26-49CE-4A54-A897-3EF17397226B@opsera.com> References: <4FE55472156C452F922C652BCBCEEEA4@int.consol.de> <64C6AC26-49CE-4A54-A897-3EF17397226B@opsera.com> Message-ID: <4A5B2243.6050803@aei.ca> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 13/07/09 05:18 AM, Ton Voon wrote: > On 13 Jul 2009, at 09:30, Gerhard Lausser wrote: > >> according to the development guidelines, the = character is allowed >> in a >> label. >> >> 2.label can contain any characters >> 3.the single quotes for the label are optional. Required if spaces, >> = or ' >> are in the label >> >> Now i see in the function Nagios::Plugin::Performance::_parse the >> following >> pattern: >> $string =~ /^'?([^'=]+)'?=($value_re)([..... >> >> Shouldn't it be /^'?([^']+)'?=($value_re)([..... instead? I see no >> reason >> why the = is excluded. The pattern will try to match as much >> characters as >> possible so the = in '?=($value_re... will always be the = >> separating label >> from value. >> >> Do you agree or am i wrong because there is a reason why the = is >> excluded? > > One thing I'm learning is to try and keep the design restricted first > and then open up as necessary. Trying to do things the other way round > leads to holes in implementation. > > I think the parsing routines could probably do with a bit of work in a > different way, rather than using regexps. Happy to take any patches > that pass all the test cases. > > Turning the question around - what use case uses an equal sign in the > label? Let's just remove the = sign from the label... Even spaces shouldn't be allowed. It makes parsing much simpler. Any plugging actually using quoted spaces or equals? - -- Thomas -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFKWyJD6dZ+Kt5BchYRAjepAJ9AvrL8SJb8PuJUxuVsmm0T+mLllQCg/W/Z +uktfcqbND1qG7BJBQnQF3E= =YwPC -----END PGP SIGNATURE----- From Gerhard.Lausser at consol.de Mon Jul 13 14:26:41 2009 From: Gerhard.Lausser at consol.de (Gerhard Lausser) Date: Mon, 13 Jul 2009 14:26:41 +0200 Subject: [Nagiosplug-devel] Perfdata patternin Nagios::Plugin::Performance.pm In-Reply-To: <4A5B2243.6050803@aei.ca> References: <4FE55472156C452F922C652BCBCEEEA4@int.consol.de><64C6AC26-49CE-4A54-A897-3EF17397226B@opsera.com> <4A5B2243.6050803@aei.ca> Message-ID: <29B0A583AC504F1A9836B9690F7AB189@int.consol.de> > > Any plugging actually using quoted spaces or equals? Yes, i use one: check_jmx4perl --url http://bea.naprax.de:7001/j4p \ --mbean java.lang:type=Memory \ --attr HeapMemoryUsage \ --path used \ --base java.lang:type=Memory/HeapMemoryUsage/max \ --warning 80 --critical 90 OK - [java.lang:type=Memory,HeapMemoryUsage,used] : 12.98 in range | 'java.lang:type=Memory,HeapMemoryUsage,used'=12.98%;80;90 Output/performancedata label are generated automatically from the input parameters. The developer carefully read the guidelines, so he probably saw no reason to clean up the label. It's not a big problem here, because it's possible to replace the generated string with a self-defined one by using the --name parameter. Besides this, i never saw = in a label. Gerhard From ton.voon at opsera.com Tue Jul 14 23:30:11 2009 From: ton.voon at opsera.com (Ton Voon) Date: Tue, 14 Jul 2009 22:30:11 +0100 Subject: [Nagiosplug-devel] Perfdata patternin Nagios::Plugin::Performance.pm In-Reply-To: <29B0A583AC504F1A9836B9690F7AB189@int.consol.de> References: <4FE55472156C452F922C652BCBCEEEA4@int.consol.de><64C6AC26-49CE-4A54-A897-3EF17397226B@opsera.com> <4A5B2243.6050803@aei.ca> <29B0A583AC504F1A9836B9690F7AB189@int.consol.de> Message-ID: On 13 Jul 2009, at 13:26, Gerhard Lausser wrote: > >> >> Any plugging actually using quoted spaces or equals? > Yes, i use one: > check_jmx4perl --url http://bea.naprax.de:7001/j4p \ > --mbean java.lang:type=Memory \ > --attr HeapMemoryUsage \ > --path used \ > --base java.lang:type=Memory/HeapMemoryUsage/max \ > --warning 80 --critical 90 > OK - [java.lang:type=Memory,HeapMemoryUsage,used] : 12.98 in range | > 'java.lang:type=Memory,HeapMemoryUsage,used'=12.98%;80;90 > > Output/performancedata label are generated automatically from the > input > parameters. The developer carefully read the guidelines, so he > probably saw > no reason to clean up the label. It's not a big problem here, > because it's > possible to replace the generated string with a self-defined one by > using > the --name parameter. > Besides this, i never saw = in a label. So am I assuming that it is okay to remove "=" from the guidelines? I think spaces should be allowed because, for instance, filesystems may have them, and I've definitely seen spaces in some window agent responses. Ton -------------- next part -------------- An HTML attachment was scrubbed... URL: From noreply at sourceforge.net Wed Jul 15 00:26:28 2009 From: noreply at sourceforge.net (SourceForge.net) Date: Tue, 14 Jul 2009 22:26:28 +0000 Subject: [Nagiosplug-devel] [ nagiosplug-Patches-2816049 ] Solaris pst3 string functions undeclared Message-ID: Patches item #2816049, was opened at 2009-07-03 01:25 Message generated for change (Comment added) made by tonvoon You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=397599&aid=2816049&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: Grant Byers (dejavu4u2) >Assigned to: Ton Voon (tonvoon) Summary: Solaris pst3 string functions undeclared Initial Comment: pst3.c doesn't include string.h (or unistd.h) root# ./pst3 S UID PID PPID VSZ RSS %CPU COMMAND ARGS Segmentation Fault (core dumped) This is due to string functions such as strdup, strchr & strrchr not being declared, thus returning int. Simply including the necessary headers SunOS unix 5.10 Generic_138888-01 sun4u sparc SUNW,Sun-Fire-V890 Sun Studio Compiler 12 root# /opt/SUNWspro/bin/cc -V cc: Sun C 5.9 SunOS_sparc Patch 124867-01 2007/07/12 /opt/SUNWspro/bin/cc -o pst3 -m64 pst3.c --- pst3.c Fri Jul 3 10:16:28 2009 +++ pst3.c.gbst Fri Jul 3 10:16:39 2009 @@ -43,6 +43,8 @@ #include #include +#include +#include #include #include #include ---------------------------------------------------------------------- >Comment By: Ton Voon (tonvoon) Date: 2009-07-14 23:26 Message: Grant, Thanks. Fixed in git. Should be in the next snapshot at http://nagiosplug.sf.net/snapshot. p.s. Interested in providing a tinderbox build server? http://nagiosplugins.org/tinderbox Ton ---------------------------------------------------------------------- Comment By: Ton Voon (tonvoon) Date: 2009-07-14 23:26 Message: This problem is now fixed in Git. Thank you for your report. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=397599&aid=2816049&group_id=29880 From noreply at sourceforge.net Wed Jul 15 00:33:41 2009 From: noreply at sourceforge.net (SourceForge.net) Date: Tue, 14 Jul 2009 22:33:41 +0000 Subject: [Nagiosplug-devel] [ nagiosplug-Bugs-990948 ] check_disk_smb doesn't allow spaces in share names Message-ID: Bugs item #990948, was opened at 2004-07-14 16:35 Message generated for change (Settings changed) made by tonvoon You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=397597&aid=990948&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: Argument proccessing Group: CVS Status: Open Resolution: None Priority: 5 Private: No Submitted By: Paul Dugas (pdugas) >Assigned to: Ton Voon (tonvoon) Summary: check_disk_smb doesn't allow spaces in share names Initial Comment: Some SOHO NAS devices (i.e. Linksys NSLU2) don't let you change the share names and have spaces in the defaults. I've hacked the script on my server to simply ignore the check on the share name but a better "fix" is needed. ---------------------------------------------------------------------- Comment By: John (relph) Date: 2005-11-30 13:21 Message: Logged In: YES user_id=1169224 See https://sourceforge.net/tracker/index.php?func=detail&aid=1370031&group_id=29880&atid=397597 ---------------------------------------------------------------------- Comment By: Benoit Mortier (opensides) Date: 2005-01-03 01:55 Message: Logged In: YES user_id=388184 Hi, could you attach a patch for the script here so i can review it. thanks. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=397597&aid=990948&group_id=29880 From noreply at sourceforge.net Wed Jul 15 00:33:41 2009 From: noreply at sourceforge.net (SourceForge.net) Date: Tue, 14 Jul 2009 22:33:41 +0000 Subject: [Nagiosplug-devel] [ nagiosplug-Bugs-1108499 ] Ping command with -U option in Debian Message-ID: Bugs item #1108499, was opened at 2005-01-24 17:42 Message generated for change (Settings changed) made by tonvoon You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=397597&aid=1108499&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: Argument proccessing Group: CVS Status: Open Resolution: None Priority: 5 Private: No Submitted By: Guillaume (guiguidoc) >Assigned to: Ton Voon (tonvoon) Summary: Ping command with -U option in Debian Initial Comment: in the configure ping option is : -U and it doesn't work... ./check_ping -H 127.0.0.1 -n -w 2,10% -c 5,20% /bin/ping -n -U -w 10 -c 5 127.0.0.1 CRITIQUE - Impossible d'interprter le rponse de la commande ping ---------------------------------------------------------------------- Comment By: Benoit Mortier (opensides) Date: 2005-01-24 19:36 Message: Logged In: YES user_id=388184 Hi, confirmed in debian sarge will look at it ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=397597&aid=1108499&group_id=29880 From noreply at sourceforge.net Wed Jul 15 00:44:15 2009 From: noreply at sourceforge.net (SourceForge.net) Date: Tue, 14 Jul 2009 22:44:15 +0000 Subject: [Nagiosplug-devel] [ nagiosplug-Bugs-1108499 ] Ping command with -U option in Debian Message-ID: Bugs item #1108499, was opened at 2005-01-24 17:42 Message generated for change (Comment added) made by tonvoon You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=397597&aid=1108499&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: Argument proccessing Group: CVS >Status: Pending Resolution: None Priority: 5 Private: No Submitted By: Guillaume (guiguidoc) Assigned to: Ton Voon (tonvoon) Summary: Ping command with -U option in Debian Initial Comment: in the configure ping option is : -U and it doesn't work... ./check_ping -H 127.0.0.1 -n -w 2,10% -c 5,20% /bin/ping -n -U -w 10 -c 5 127.0.0.1 CRITIQUE - Impossible d'interprter le rponse de la commande ping ---------------------------------------------------------------------- >Comment By: Ton Voon (tonvoon) Date: 2009-07-14 23:44 Message: Hi Guillaume, Given the age of this, I assume it has been fixed. I'm marking this in a pending state. Please update if this is still an issue. Ton ---------------------------------------------------------------------- Comment By: Benoit Mortier (opensides) Date: 2005-01-24 19:36 Message: Logged In: YES user_id=388184 Hi, confirmed in debian sarge will look at it ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=397597&aid=1108499&group_id=29880 From dermoth at aei.ca Wed Jul 15 13:17:40 2009 From: dermoth at aei.ca (Thomas Guyot-Sionnest) Date: Wed, 15 Jul 2009 07:17:40 -0400 Subject: [Nagiosplug-devel] Perfdata patternin Nagios::Plugin::Performance.pm In-Reply-To: References: <4FE55472156C452F922C652BCBCEEEA4@int.consol.de><64C6AC26-49CE-4A54-A897-3EF17397226B@opsera.com> <4A5B2243.6050803@aei.ca> <29B0A583AC504F1A9836B9690F7AB189@int.consol.de> Message-ID: <4A5DBAD4.5090700@aei.ca> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 14/07/09 05:30 PM, Ton Voon wrote: > > So am I assuming that it is okay to remove "=" from the guidelines? > > I think spaces should be allowed because, for instance, filesystems may > have them, and I've definitely seen spaces in some window agent responses. They could be replaced by underscores... Otherwise parsing these strings is much more complex. Also a general use of these labels is matching to RRD data sources, and those can't have spaces either, so most tools out there already replace them with underscores... While we're at it, I'd like to include a label option in the new thresholds format (RFC) so i could be overridden... I have a couple of other changes in mind so I'll start a discussion to see if everyone is happy with them... - -- Thomas -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFKXbrU6dZ+Kt5BchYRAsLQAJ400J9uc6Q0D2cOJWHeGNfa3b0sogCgtJ/7 ebi8R7UH/U7fbghSYHPCXqk= =Go7g -----END PGP SIGNATURE----- From Gerhard.Lausser at consol.de Thu Jul 16 10:26:36 2009 From: Gerhard.Lausser at consol.de (Gerhard Lausser) Date: Thu, 16 Jul 2009 10:26:36 +0200 Subject: [Nagiosplug-devel] Perfdata patternin Nagios::Plugin::Performance.pm In-Reply-To: <4A5DBAD4.5090700@aei.ca> References: <4FE55472156C452F922C652BCBCEEEA4@int.consol.de><64C6AC26-49CE-4A54-A897-3EF17397226B@opsera.com> <4A5B2243.6050803@aei.ca> <29B0A583AC504F1A9836B9690F7AB189@int.consol.de> <4A5DBAD4.5090700@aei.ca> Message-ID: <895D4F21D61A4DE7BBB36E386D73E497@int.consol.de> Hi, the developer of the plugin using = accepted to find a workaround. > > So am I assuming that it is okay to remove "=" from the guidelines? >From my side, yes. I too wrote plugins whre in rare cases a = can appear in the label, but i also provide a --name parameter which then is used as the label instead. Gerhard From dermoth at aei.ca Fri Jul 17 05:11:23 2009 From: dermoth at aei.ca (Thomas Guyot-Sionnest) Date: Thu, 16 Jul 2009 23:11:23 -0400 Subject: [Nagiosplug-devel] Forking the contrib section? Message-ID: <4A5FEBDB.3070500@aei.ca> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I was looking at some repository clone that included patches to /contrib and that got me an idea. The policy right now is to encourage authors to move away contrib plugins to Nagiosexchange. However many need the Nagios-plugins tree to compile, and most lost their original authors. Meanwhile some useful plugins in there get patches from time to time that we don't really want to apply because we don't really want to support that unsupported section. I'd like to fork /contrib to a separate git repository and add a "mob" user (unrestricted check-in access to the "mob" branch) for people to commit things?, then we can do a short review from time to time and merge changes from the mob branch. Think of this as a service to help the community maintaining these plugins without any guarantee regarding the quality and safety of these plugins from the Nagios-Plugins team. I believe that it would relieve us of that plugins section and help the community getting patches in. /contrib could then become a git submodule that can be included for compiling the plugins. Any comments or objections? - -- Thomas -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFKX+vb6dZ+Kt5BchYRAmr0AJ4/tJWKBoRzU6tsfLbilWNjP0/kjQCgiFuk n0H45WHiIEkKp3pA4od1M+k= =AOcL -----END PGP SIGNATURE----- From noreply at sourceforge.net Fri Jul 17 13:12:16 2009 From: noreply at sourceforge.net (SourceForge.net) Date: Fri, 17 Jul 2009 11:12:16 +0000 Subject: [Nagiosplug-devel] [ nagiosplug-Bugs-2823005 ] check_swap returns OK, if no swap activated Message-ID: Bugs item #2823005, was opened at 2009-07-17 13:12 Message generated for change (Tracker Item Submitted) made by ondrejj You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=397597&aid=2823005&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: Jan Ondrej (ondrejj) Assigned to: Nobody/Anonymous (nobody) Summary: check_swap returns OK, if no swap activated Initial Comment: My swap was not activated on boot for unknown reason and nagios does not report this as a problem. Here is an example: [root at kecom ~]# rpm -q nagios-plugins nagios-plugins-1.4.13-11.fc10.i386 [root at kecom ~]# /usr/lib/nagios/plugins/check_swap -w 80% -c 40% -c 1 -w 2 SWAP CRITICAL - 100% free (0 MB out of 0 MB) |swap=0MB;0;0;0;0 If there is no swap and users is trying to test percentage of free swap, consider 0 MB free swap space as problem, or of free/total raises division by zero, then set percentage to 0%, not to 100%. Thank you. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=397597&aid=2823005&group_id=29880 From nagiosplug-devel at lusis.org Fri Jul 17 14:25:12 2009 From: nagiosplug-devel at lusis.org (John Vincent) Date: Fri, 17 Jul 2009 08:25:12 -0400 Subject: [Nagiosplug-devel] XML in plugins Message-ID: All, I just finished watching the interview with Ton and he mentioned wanting XML to be involved with the plugin output in some capacity. I don't recall seeing any emails about this coming across or any formal discussion. I just searched back through my archives and indeed couldn't find anything. I also search over at ideas.nagios.org and didn't see any comments there regarding it. Ton, what exactly is the desire here? I'd love to help if I could. Are you possibly wanting perfdata to move to an XML format or something else? I got the impression that it seemed like a fairly vague idea at this point. To what end would some sort of XML in plugins be useful? Great interview by the way. John E. Vincent From ton.voon at opsera.com Fri Jul 17 18:27:40 2009 From: ton.voon at opsera.com (Ton Voon) Date: Fri, 17 Jul 2009 17:27:40 +0100 Subject: [Nagiosplug-devel] Forking the contrib section? In-Reply-To: <4A5FEBDB.3070500@aei.ca> References: <4A5FEBDB.3070500@aei.ca> Message-ID: On 17 Jul 2009, at 04:11, Thomas Guyot-Sionnest wrote: > I was looking at some repository clone that included patches to / > contrib > and that got me an idea. The policy right now is to encourage > authors to > move away contrib plugins to Nagiosexchange. The official location is exchange.nagios.org. I've just updated the dev guidelines and nagiosplugins.org to reflect. > However many need the > Nagios-plugins tree to compile, and most lost their original authors. > Meanwhile some useful plugins in there get patches from time to time > that we don't really want to apply because we don't really want to > support that unsupported section. Isn't the compile problem one that should be solved with a nagiosplug- dev library? > I'd like to fork /contrib to a separate git repository and add a "mob" > user (unrestricted check-in access to the "mob" branch) for people to > commit things , then we can do a short review from time to time and > merge changes from the mob branch. > > Think of this as a service to help the community maintaining these > plugins without any guarantee regarding the quality and safety of > these > plugins from the Nagios-Plugins team. I believe that it would > relieve us > of that plugins section and help the community getting patches in. > > /contrib could then become a git submodule that can be included for > compiling the plugins. I think this is a good idea, though I have doubts on how used it will be. I think we're getting to the stage where I think we can start accepting some more plugins into the core. I'd welcome any one wishing to join the team and look after specific new plugins. Ton From sbennett at groundworkopensource.com Fri Jul 17 18:42:18 2009 From: sbennett at groundworkopensource.com (Simon Bennett) Date: Fri, 17 Jul 2009 09:42:18 -0700 Subject: [Nagiosplug-devel] Forking the contrib section? In-Reply-To: <4A5FEBDB.3070500@aei.ca> Message-ID: Thomas, I think your proposal is a good one. As a person who had patches caught in the contrib / no author trap I think it would help. I'm happy to volunteer time to help dig up old patches and get them submitted. It would be helpful if there was some mechanism to build a nagios-plugins-experimental package from the mob branch, of course without any guarantees about the behaviour of the result. Is that similar to what you were proposing with the "/contrib git submodule" comment? -Simon On 7/16/09 8:11 PM, "Thomas Guyot-Sionnest" wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > I was looking at some repository clone that included patches to /contrib > and that got me an idea. The policy right now is to encourage authors to > move away contrib plugins to Nagiosexchange. However many need the > Nagios-plugins tree to compile, and most lost their original authors. > Meanwhile some useful plugins in there get patches from time to time > that we don't really want to apply because we don't really want to > support that unsupported section. > > I'd like to fork /contrib to a separate git repository and add a "mob" > user (unrestricted check-in access to the "mob" branch) for people to > commit things?, then we can do a short review from time to time and > merge changes from the mob branch. > > Think of this as a service to help the community maintaining these > plugins without any guarantee regarding the quality and safety of these > plugins from the Nagios-Plugins team. I believe that it would relieve us > of that plugins section and help the community getting patches in. > > /contrib could then become a git submodule that can be included for > compiling the plugins. > > Any comments or objections? > > - -- > Thomas > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.6 (GNU/Linux) > Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org > > iD8DBQFKX+vb6dZ+Kt5BchYRAmr0AJ4/tJWKBoRzU6tsfLbilWNjP0/kjQCgiFuk > n0H45WHiIEkKp3pA4od1M+k= > =AOcL > -----END PGP SIGNATURE----- > > ------------------------------------------------------------------------------ > Enter the BlackBerry Developer Challenge > This is your chance to win up to $100,000 in prizes! For a limited time, > vendors submitting new applications to BlackBerry App World(TM) will have > the opportunity to enter the BlackBerry Developer Challenge. See full prize > details at: http://p.sf.net/sfu/Challenge > _______________________________________________________ > Nagios Plugin Development Mailing List Nagiosplug-devel at lists.sourceforge.net > Unsubscribe at https://lists.sourceforge.net/lists/listinfo/nagiosplug-devel > ::: Please include plugins version (-v) and OS when reporting any issue. > ::: Messages without supporting info will risk being sent to /dev/null -- Simon Bennett Sr. Director of Product Management GROUNDWORK Open Source, Inc. 139 Townsend Street, Suite 100 San Francisco, CA 94107 415-992-4577 (direct) 415-947-0684 (fax) sbennett at gwos.com -------------- next part -------------- An HTML attachment was scrubbed... URL: From shadhin71 at gmail.com Fri Jul 17 22:49:07 2009 From: shadhin71 at gmail.com (shadih rahman) Date: Fri, 17 Jul 2009 16:49:07 -0400 Subject: [Nagiosplug-devel] multiple options with same argument. In-Reply-To: <4A56A9DF.8010401@aei.ca> References: <6db4a4200907081427k6ed707e0k1480bc1bd6a07c12@mail.gmail.com> <4A56A9DF.8010401@aei.ca> Message-ID: <6db4a4200907171349u2856eed3q55986b4c55a24c34@mail.gmail.com> Thanks for the tip. It worked like a charm. On Thu, Jul 9, 2009 at 10:39 PM, Thomas Guyot-Sionnest wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > On 08/07/09 05:27 PM, shadih rahman wrote: > > All, > > how do you parse multiple of same argument in Nagios::Plungin. I am > > calling my check as this > > > > perl check_htturl -H wind.columbia.edu -u > > username -p pass -P /login -q me -q you > > > > when I print -q it should print me&you but its not doing that. This is > > my code. Please advise on this. Thanks > > > > Nagios::Pluin uses Getopt::Long to parse arguments, so its parameters > are pretty much the same. While I doubt you can force N::P to return an > array you can have Getopt::Long return a array reference. > > > $plugin->add_arg( > > spec => 'query|q=s', > > help => "additional query to inject", > > label => [ 'query' ], > > required => 0, > > ); > > try with: spec => 'query|q=s@' > > Since it'll be a ref don't forget to deference it when you get it from > $plugin->opts->query > > - -- > Thomas > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.6 (GNU/Linux) > Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org > > iD8DBQFKVqnf6dZ+Kt5BchYRAqyxAJ0YH3qpu5FZxWDzp+mXu2SAc0oyMgCfYwzy > nD7sZohL3qGiv8XnWkPcJjg= > =E5N0 > -----END PGP SIGNATURE----- > > > ------------------------------------------------------------------------------ > Enter the BlackBerry Developer Challenge > This is your chance to win up to $100,000 in prizes! For a limited time, > vendors submitting new applications to BlackBerry App World(TM) will have > the opportunity to enter the BlackBerry Developer Challenge. See full prize > details at: http://p.sf.net/sfu/Challenge > _______________________________________________________ > Nagios Plugin Development Mailing List > Nagiosplug-devel at lists.sourceforge.net > Unsubscribe at > https://lists.sourceforge.net/lists/listinfo/nagiosplug-devel > ::: Please include plugins version (-v) and OS when reporting any issue. > ::: Messages without supporting info will risk being sent to /dev/null > -- Cordially, Shadhin Rahman -------------- next part -------------- An HTML attachment was scrubbed... URL: From dermoth at aei.ca Sat Jul 18 00:41:48 2009 From: dermoth at aei.ca (Thomas Guyot-Sionnest) Date: Fri, 17 Jul 2009 18:41:48 -0400 Subject: [Nagiosplug-devel] Forking the contrib section? In-Reply-To: References: <4A5FEBDB.3070500@aei.ca> Message-ID: <4A60FE2C.3000608@aei.ca> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 17/07/09 12:27 PM, Ton Voon wrote: > On 17 Jul 2009, at 04:11, Thomas Guyot-Sionnest wrote: > >> However many need the >> Nagios-plugins tree to compile, and most lost their original authors. >> Meanwhile some useful plugins in there get patches from time to time >> that we don't really want to apply because we don't really want to >> support that unsupported section. > > Isn't the compile problem one that should be solved with a nagiosplug- > dev library? Indeed, and I would really like to get this project started. The next step is to decide whenever we want a functional or object-oriented api and start designing it! We had some talks in #nagios about that recently. >> I'd like to fork /contrib to a separate git repository and add a "mob" >> user (unrestricted check-in access to the "mob" branch) for people to >> commit things , then we can do a short review from time to time and >> merge changes from the mob branch. >> >> Think of this as a service to help the community maintaining these >> plugins without any guarantee regarding the quality and safety of >> these >> plugins from the Nagios-Plugins team. I believe that it would >> relieve us >> of that plugins section and help the community getting patches in. >> >> /contrib could then become a git submodule that can be included for >> compiling the plugins. > > I think this is a good idea, though I have doubts on how used it will > be. It can't be worse than what it is now ;) > I think we're getting to the stage where I think we can start > accepting some more plugins into the core. I'd welcome any one wishing > to join the team and look after specific new plugins. Sure, we could start a review of some plugins. Maybe take some interesting ones in Nagiosexange too if they fit. OTOH if we add any new plugin I'd like that at least Perl plugins use N::P and and C plugins do not use any deprecated code, so we don't add ourself more work in the future :). And they should have tests too... - -- Thomas -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFKYP4s6dZ+Kt5BchYRAilxAKDgerO4tgef89JI72txb27B1NOoTwCg4w4r VmPCtUwP9y1h9aGapb/X97w= =yJBH -----END PGP SIGNATURE----- From dermoth at aei.ca Sat Jul 18 06:25:58 2009 From: dermoth at aei.ca (Thomas Guyot-Sionnest) Date: Sat, 18 Jul 2009 00:25:58 -0400 Subject: [Nagiosplug-devel] Forking the contrib section? In-Reply-To: <4A60FE2C.3000608@aei.ca> References: <4A5FEBDB.3070500@aei.ca> <4A60FE2C.3000608@aei.ca> Message-ID: <4A614ED6.8030102@aei.ca> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 17/07/09 06:41 PM, Thomas Guyot-Sionnest wrote: > On 17/07/09 12:27 PM, Ton Voon wrote: >> On 17 Jul 2009, at 04:11, Thomas Guyot-Sionnest wrote: >>> I'd like to fork /contrib to a separate git repository and add a "mob" >>> user (unrestricted check-in access to the "mob" branch) for people to >>> commit things , then we can do a short review from time to time and >>> merge changes from the mob branch. >>> >>> Think of this as a service to help the community maintaining these >>> plugins without any guarantee regarding the quality and safety of >>> these >>> plugins from the Nagios-Plugins team. I believe that it would >>> relieve us >>> of that plugins section and help the community getting patches in. >>> >>> /contrib could then become a git submodule that can be included for >>> compiling the plugins. >> I think this is a good idea, though I have doubts on how used it will >> be. > > It can't be worse than what it is now ;) I played with it a little bit... git filter-branch is pretty damn powerful :) Here's what it would look like as a standalone repository (I removed everything not in contrib*/ and moved contrib-reporting to reporting): http://solaris.beaubien.net/cgi-bin/gitweb.cgi/np_contrib.git - -- Thomas -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFKYU7W6dZ+Kt5BchYRAtbCAKC27HtKAPumznAtR+w8npS/MNT+TQCfe0sC BTiKsZ97rpeS5cRFt5BMxoE= =KIYc -----END PGP SIGNATURE----- From noreply at sourceforge.net Sun Jul 19 10:00:07 2009 From: noreply at sourceforge.net (SourceForge.net) Date: Sun, 19 Jul 2009 08:00:07 +0000 Subject: [Nagiosplug-devel] [ nagiosplug-Bugs-2823005 ] check_swap returns OK, if no swap activated Message-ID: Bugs item #2823005, was opened at 2009-07-17 13:12 Message generated for change (Comment added) made by ondrejj You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=397597&aid=2823005&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: Jan Ondrej (ondrejj) Assigned to: Nobody/Anonymous (nobody) Summary: check_swap returns OK, if no swap activated Initial Comment: My swap was not activated on boot for unknown reason and nagios does not report this as a problem. Here is an example: [root at kecom ~]# rpm -q nagios-plugins nagios-plugins-1.4.13-11.fc10.i386 [root at kecom ~]# /usr/lib/nagios/plugins/check_swap -w 80% -c 40% -c 1 -w 2 SWAP CRITICAL - 100% free (0 MB out of 0 MB) |swap=0MB;0;0;0;0 If there is no swap and users is trying to test percentage of free swap, consider 0 MB free swap space as problem, or of free/total raises division by zero, then set percentage to 0%, not to 100%. Thank you. ---------------------------------------------------------------------- >Comment By: Jan Ondrej (ondrejj) Date: 2009-07-19 10:00 Message: An patch is available in redhat bugzilla. I don't know, how to attach it here. https://bugzilla.redhat.com/show_bug.cgi?id=512559 ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=397597&aid=2823005&group_id=29880 From marc at ena.com Thu Jul 23 22:01:21 2009 From: marc at ena.com (Marc Powell) Date: Thu, 23 Jul 2009 15:01:21 -0500 Subject: [Nagiosplug-devel] My, how the time flies Message-ID: <87BE068F-ADFA-4B59-B002-C4D266F91B93@ena.com> I missed it but I just wanted to say Congratulations to Ethan and all of you for over a decade of Netsaint/Nagios goodness. From the Netsaint Changelog -- 0.0.1 - 03/14/1999 ------------------ - Initial release Thanks for everything all of you have done over the years to make Nagios such a success and so useful for us end-users! -- Marc From amontibello at gmail.com Fri Jul 24 01:38:33 2009 From: amontibello at gmail.com (Anthony Montibello) Date: Thu, 23 Jul 2009 19:38:33 -0400 Subject: [Nagiosplug-devel] XML in plugins In-Reply-To: References: Message-ID: I also do not remember the discussion of XML output from the plugins in any of the official Nagios forums. However I do remember a discussion on XML styled input Arguments Maybe it is the next enhancement after that is completed? Tony (Author of NC_NEt) On Fri, Jul 17, 2009 at 8:25 AM, John Vincent wrote: > All, > > I just finished watching the interview with Ton and he mentioned > wanting XML to be involved with the plugin output in some capacity. I > don't recall seeing any emails about this coming across or any formal > discussion. I just searched back through my archives and indeed > couldn't find anything. I also search over at ideas.nagios.org and > didn't see any comments there regarding it. > > Ton, what exactly is the desire here? I'd love to help if I could. Are > you possibly wanting perfdata to move to an XML format or something > else? I got the impression that it seemed like a fairly vague idea at > this point. To what end would some sort of XML in plugins be useful? > > Great interview by the way. > > John E. Vincent > > > ------------------------------------------------------------------------------ > Enter the BlackBerry Developer Challenge > This is your chance to win up to $100,000 in prizes! For a limited time, > vendors submitting new applications to BlackBerry App World(TM) will have > the opportunity to enter the BlackBerry Developer Challenge. See full prize > details at: http://p.sf.net/sfu/Challenge > _______________________________________________________ > Nagios Plugin Development Mailing List > Nagiosplug-devel at lists.sourceforge.net > Unsubscribe at > https://lists.sourceforge.net/lists/listinfo/nagiosplug-devel > ::: Please include plugins version (-v) and OS when reporting any issue. > ::: Messages without supporting info will risk being sent to /dev/null > -------------- next part -------------- An HTML attachment was scrubbed... URL: From noreply at sourceforge.net Fri Jul 24 15:37:18 2009 From: noreply at sourceforge.net (SourceForge.net) Date: Fri, 24 Jul 2009 13:37:18 +0000 Subject: [Nagiosplug-devel] [ nagiosplug-Bugs-2826570 ] check_http 1.4.13 does not work with some HTTPS servers Message-ID: Bugs item #2826570, was opened at 2009-07-24 15:37 Message generated for change (Tracker Item Submitted) made by steffencl You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=397597&aid=2826570&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: Release (specify) Status: Open Resolution: None Priority: 5 Private: No Submitted By: Steffen (steffencl) Assigned to: Nobody/Anonymous (nobody) Summary: check_http 1.4.13 does not work with some HTTPS servers Initial Comment: Hello, we recently made a nagios-plugin update which introduced check_http v1.4.13 (nagios-plugins 1.4.13) Since then checks of some HTTPS-servers faild with the error "HTTP CRITICAL - Error on receive" A detailed analysis and comparison with older version (1.4.12) revealed the following: For testing we used the plugin on the Linux shell (Debian sid) like this: /usr/lib/nagios/plugins/check_http -4 --ssl -v \ -H -I A tcp-connection from the nagios host to the webserver was opened with the normal TCP-handshakes. After that the nagios-plugin sends it's first SSL handshake packet ("Client Hello") to the webserver which is answered by a TCP-FIN packet to close the connection. The webserver logs a message indicating that the SSL compression method of the client is not supported. I analysed the SSL protocol and found that the old plugin does NOT include a compression method in it's "Client Hello" message while the new one does. The SSL Client Hello Packed decoded by whireshark of the NEW plugin looks like this: ---snip---- Secure Socket Layer SSL Record Layer: Handshake Protocol: Client Hello Content Type: Handshake (22) Version: TLS 1.0 (0x0301) Length: 109 Handshake Protocol: Client Hello Handshake Type: Client Hello (1) Length: 105 Version: TLS 1.0 (0x0301) Random gmt_unix_time: Jul 24, 2009 13:42:28.000000000 random_bytes: 2930D11FA4... Session ID Length: 0 Cipher Suites Length: 38 Cipher Suites (19 suites) Cipher Suite: TLS_DHE_RSA_WITH_AES_256_CBC_SHA (0x0039) Cipher Suite: TLS_DHE_DSS_WITH_AES_256_CBC_SHA (0x0038) Cipher Suite: TLS_RSA_WITH_AES_256_CBC_SHA (0x0035) Cipher Suite: TLS_DHE_RSA_WITH_3DES_EDE_CBC_SHA (0x0016) Cipher Suite: TLS_DHE_DSS_WITH_3DES_EDE_CBC_SHA (0x0013) Cipher Suite: TLS_RSA_WITH_3DES_EDE_CBC_SHA (0x000a) Cipher Suite: TLS_DHE_RSA_WITH_AES_128_CBC_SHA (0x0033) Cipher Suite: TLS_DHE_DSS_WITH_AES_128_CBC_SHA (0x0032) Cipher Suite: TLS_RSA_WITH_AES_128_CBC_SHA (0x002f) Cipher Suite: TLS_RSA_WITH_RC4_128_SHA (0x0005) Cipher Suite: TLS_RSA_WITH_RC4_128_MD5 (0x0004) Cipher Suite: TLS_DHE_RSA_WITH_DES_CBC_SHA (0x0015) Cipher Suite: TLS_DHE_DSS_WITH_DES_CBC_SHA (0x0012) Cipher Suite: TLS_RSA_WITH_DES_CBC_SHA (0x0009) Cipher Suite: TLS_DHE_RSA_EXPORT_WITH_DES40_CBC_SHA (0x0014) Cipher Suite: TLS_DHE_DSS_EXPORT_WITH_DES40_CBC_SHA (0x0011) Cipher Suite: TLS_RSA_EXPORT_WITH_DES40_CBC_SHA (0x0008) Cipher Suite: TLS_RSA_EXPORT_WITH_RC2_CBC_40_MD5 (0x0006) Cipher Suite: TLS_RSA_EXPORT_WITH_RC4_40_MD5 (0x0003) Compression Methods Length: 2 Compression Methods (2 methods) Compression Method: DEFLATE (1) Compression Method: null (0) Extensions Length: 25 Extension: server_name Type: server_name (0x0000) Length: 17 Data (17 bytes) Extension: SessionTicket TLS Type: SessionTicket TLS (0x0023) Length: 0 Data (0 bytes) ---snip---- While the SSL Client Hello Packed of an old plugin looks like this: ---snip---- Secure Socket Layer SSLv2 Record Layer: Client Hello Length: 116 Handshake Message Type: Client Hello (1) Version: TLS 1.0 (0x0301) Cipher Spec Length: 75 Session ID Length: 0 Challenge Length: 32 Cipher Specs (25 specs) Cipher Spec: TLS_DHE_RSA_WITH_AES_256_CBC_SHA (0x000039) Cipher Spec: TLS_DHE_DSS_WITH_AES_256_CBC_SHA (0x000038) Cipher Spec: TLS_RSA_WITH_AES_256_CBC_SHA (0x000035) Cipher Spec: TLS_DHE_RSA_WITH_3DES_EDE_CBC_SHA (0x000016) Cipher Spec: TLS_DHE_DSS_WITH_3DES_EDE_CBC_SHA (0x000013) Cipher Spec: TLS_RSA_WITH_3DES_EDE_CBC_SHA (0x00000a) Cipher Spec: SSL2_DES_192_EDE3_CBC_WITH_MD5 (0x0700c0) Cipher Spec: TLS_DHE_RSA_WITH_AES_128_CBC_SHA (0x000033) Cipher Spec: TLS_DHE_DSS_WITH_AES_128_CBC_SHA (0x000032) Cipher Spec: TLS_RSA_WITH_AES_128_CBC_SHA (0x00002f) Cipher Spec: SSL2_RC2_CBC_128_CBC_WITH_MD5 (0x030080) Cipher Spec: TLS_RSA_WITH_RC4_128_SHA (0x000005) Cipher Spec: TLS_RSA_WITH_RC4_128_MD5 (0x000004) Cipher Spec: SSL2_RC4_128_WITH_MD5 (0x010080) Cipher Spec: TLS_DHE_RSA_WITH_DES_CBC_SHA (0x000015) Cipher Spec: TLS_DHE_DSS_WITH_DES_CBC_SHA (0x000012) Cipher Spec: TLS_RSA_WITH_DES_CBC_SHA (0x000009) Cipher Spec: SSL2_DES_64_CBC_WITH_MD5 (0x060040) Cipher Spec: TLS_DHE_RSA_EXPORT_WITH_DES40_CBC_SHA (0x000014) Cipher Spec: TLS_DHE_DSS_EXPORT_WITH_DES40_CBC_SHA (0x000011) Cipher Spec: TLS_RSA_EXPORT_WITH_DES40_CBC_SHA (0x000008) Cipher Spec: TLS_RSA_EXPORT_WITH_RC2_CBC_40_MD5 (0x000006) Cipher Spec: SSL2_RC2_CBC_128_CBC_WITH_MD5 (0x040080) Cipher Spec: TLS_RSA_EXPORT_WITH_RC4_40_MD5 (0x000003) Cipher Spec: SSL2_RC4_128_EXPORT40_WITH_MD5 (0x020080) Challenge ---snip---- As you see with no compression method field. We had no problems with version 1.4.12, but since 1.4.13 we have the described problems with some servers, primary with older servers and appliences useing HTTPS. There are no problems against apache servers. - Steffen ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=397597&aid=2826570&group_id=29880 From Gerhard.Lausser at consol.de Fri Jul 24 21:37:57 2009 From: Gerhard.Lausser at consol.de (Gerhard Lausser) Date: Fri, 24 Jul 2009 21:37:57 +0200 Subject: [Nagiosplug-devel] Spam@nagiosplugins.org Message-ID: <738B7AF22F5740069FA5A1FCF575B991@int.consol.de> Hi, i just noticed that somebody used the comments on nagiosplugins.org to spread a lot of spam links. http://nagiosplugins.org/extra-opts http://nagiosplugins.org/faq http://nagiosplugins.org/rfc/new_threshold_syntax http://nagiosplugins.org/node/12 ... Cheers, Gerhard From holger at CIS.FU-Berlin.DE Fri Jul 24 23:11:15 2009 From: holger at CIS.FU-Berlin.DE (Holger =?iso-8859-1?Q?Wei=DF?=) Date: Fri, 24 Jul 2009 23:11:15 +0200 Subject: [Nagiosplug-devel] Spam@nagiosplugins.org In-Reply-To: <738B7AF22F5740069FA5A1FCF575B991@int.consol.de> References: <738B7AF22F5740069FA5A1FCF575B991@int.consol.de> Message-ID: <20090724211115.GC60145715@Waran.CIS.FU-Berlin.DE> * Gerhard Lausser [2009-07-24 21:37]: > i just noticed that somebody used the comments on nagiosplugins.org to > spread a lot of spam links. Thanks for the hint, I removed them. Holger -- From noreply at sourceforge.net Sat Jul 25 03:51:09 2009 From: noreply at sourceforge.net (SourceForge.net) Date: Sat, 25 Jul 2009 01:51:09 +0000 Subject: [Nagiosplug-devel] [ nagiosplug-Bugs-2826570 ] check_http 1.4.13 does not work with some HTTPS servers Message-ID: Bugs item #2826570, was opened at 2009-07-24 09:37 Message generated for change (Comment added) made by dermoth You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=397597&aid=2826570&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: Release (specify) Status: Open Resolution: None Priority: 5 Private: No Submitted By: Steffen (steffencl) >Assigned to: Thomas Guyot-Sionnest (dermoth) Summary: check_http 1.4.13 does not work with some HTTPS servers Initial Comment: Hello, we recently made a nagios-plugin update which introduced check_http v1.4.13 (nagios-plugins 1.4.13) Since then checks of some HTTPS-servers faild with the error "HTTP CRITICAL - Error on receive" A detailed analysis and comparison with older version (1.4.12) revealed the following: For testing we used the plugin on the Linux shell (Debian sid) like this: /usr/lib/nagios/plugins/check_http -4 --ssl -v \ -H -I A tcp-connection from the nagios host to the webserver was opened with the normal TCP-handshakes. After that the nagios-plugin sends it's first SSL handshake packet ("Client Hello") to the webserver which is answered by a TCP-FIN packet to close the connection. The webserver logs a message indicating that the SSL compression method of the client is not supported. I analysed the SSL protocol and found that the old plugin does NOT include a compression method in it's "Client Hello" message while the new one does. The SSL Client Hello Packed decoded by whireshark of the NEW plugin looks like this: ---snip---- Secure Socket Layer SSL Record Layer: Handshake Protocol: Client Hello Content Type: Handshake (22) Version: TLS 1.0 (0x0301) Length: 109 Handshake Protocol: Client Hello Handshake Type: Client Hello (1) Length: 105 Version: TLS 1.0 (0x0301) Random gmt_unix_time: Jul 24, 2009 13:42:28.000000000 random_bytes: 2930D11FA4... Session ID Length: 0 Cipher Suites Length: 38 Cipher Suites (19 suites) Cipher Suite: TLS_DHE_RSA_WITH_AES_256_CBC_SHA (0x0039) Cipher Suite: TLS_DHE_DSS_WITH_AES_256_CBC_SHA (0x0038) Cipher Suite: TLS_RSA_WITH_AES_256_CBC_SHA (0x0035) Cipher Suite: TLS_DHE_RSA_WITH_3DES_EDE_CBC_SHA (0x0016) Cipher Suite: TLS_DHE_DSS_WITH_3DES_EDE_CBC_SHA (0x0013) Cipher Suite: TLS_RSA_WITH_3DES_EDE_CBC_SHA (0x000a) Cipher Suite: TLS_DHE_RSA_WITH_AES_128_CBC_SHA (0x0033) Cipher Suite: TLS_DHE_DSS_WITH_AES_128_CBC_SHA (0x0032) Cipher Suite: TLS_RSA_WITH_AES_128_CBC_SHA (0x002f) Cipher Suite: TLS_RSA_WITH_RC4_128_SHA (0x0005) Cipher Suite: TLS_RSA_WITH_RC4_128_MD5 (0x0004) Cipher Suite: TLS_DHE_RSA_WITH_DES_CBC_SHA (0x0015) Cipher Suite: TLS_DHE_DSS_WITH_DES_CBC_SHA (0x0012) Cipher Suite: TLS_RSA_WITH_DES_CBC_SHA (0x0009) Cipher Suite: TLS_DHE_RSA_EXPORT_WITH_DES40_CBC_SHA (0x0014) Cipher Suite: TLS_DHE_DSS_EXPORT_WITH_DES40_CBC_SHA (0x0011) Cipher Suite: TLS_RSA_EXPORT_WITH_DES40_CBC_SHA (0x0008) Cipher Suite: TLS_RSA_EXPORT_WITH_RC2_CBC_40_MD5 (0x0006) Cipher Suite: TLS_RSA_EXPORT_WITH_RC4_40_MD5 (0x0003) Compression Methods Length: 2 Compression Methods (2 methods) Compression Method: DEFLATE (1) Compression Method: null (0) Extensions Length: 25 Extension: server_name Type: server_name (0x0000) Length: 17 Data (17 bytes) Extension: SessionTicket TLS Type: SessionTicket TLS (0x0023) Length: 0 Data (0 bytes) ---snip---- While the SSL Client Hello Packed of an old plugin looks like this: ---snip---- Secure Socket Layer SSLv2 Record Layer: Client Hello Length: 116 Handshake Message Type: Client Hello (1) Version: TLS 1.0 (0x0301) Cipher Spec Length: 75 Session ID Length: 0 Challenge Length: 32 Cipher Specs (25 specs) Cipher Spec: TLS_DHE_RSA_WITH_AES_256_CBC_SHA (0x000039) Cipher Spec: TLS_DHE_DSS_WITH_AES_256_CBC_SHA (0x000038) Cipher Spec: TLS_RSA_WITH_AES_256_CBC_SHA (0x000035) Cipher Spec: TLS_DHE_RSA_WITH_3DES_EDE_CBC_SHA (0x000016) Cipher Spec: TLS_DHE_DSS_WITH_3DES_EDE_CBC_SHA (0x000013) Cipher Spec: TLS_RSA_WITH_3DES_EDE_CBC_SHA (0x00000a) Cipher Spec: SSL2_DES_192_EDE3_CBC_WITH_MD5 (0x0700c0) Cipher Spec: TLS_DHE_RSA_WITH_AES_128_CBC_SHA (0x000033) Cipher Spec: TLS_DHE_DSS_WITH_AES_128_CBC_SHA (0x000032) Cipher Spec: TLS_RSA_WITH_AES_128_CBC_SHA (0x00002f) Cipher Spec: SSL2_RC2_CBC_128_CBC_WITH_MD5 (0x030080) Cipher Spec: TLS_RSA_WITH_RC4_128_SHA (0x000005) Cipher Spec: TLS_RSA_WITH_RC4_128_MD5 (0x000004) Cipher Spec: SSL2_RC4_128_WITH_MD5 (0x010080) Cipher Spec: TLS_DHE_RSA_WITH_DES_CBC_SHA (0x000015) Cipher Spec: TLS_DHE_DSS_WITH_DES_CBC_SHA (0x000012) Cipher Spec: TLS_RSA_WITH_DES_CBC_SHA (0x000009) Cipher Spec: SSL2_DES_64_CBC_WITH_MD5 (0x060040) Cipher Spec: TLS_DHE_RSA_EXPORT_WITH_DES40_CBC_SHA (0x000014) Cipher Spec: TLS_DHE_DSS_EXPORT_WITH_DES40_CBC_SHA (0x000011) Cipher Spec: TLS_RSA_EXPORT_WITH_DES40_CBC_SHA (0x000008) Cipher Spec: TLS_RSA_EXPORT_WITH_RC2_CBC_40_MD5 (0x000006) Cipher Spec: SSL2_RC2_CBC_128_CBC_WITH_MD5 (0x040080) Cipher Spec: TLS_RSA_EXPORT_WITH_RC4_40_MD5 (0x000003) Cipher Spec: SSL2_RC4_128_EXPORT40_WITH_MD5 (0x020080) Challenge ---snip---- As you see with no compression method field. We had no problems with version 1.4.12, but since 1.4.13 we have the described problems with some servers, primary with older servers and appliences useing HTTPS. There are no problems against apache servers. - Steffen ---------------------------------------------------------------------- >Comment By: Thomas Guyot-Sionnest (dermoth) Date: 2009-07-24 21:51 Message: Hi, and thanks for your report. I checked the change logs between these two release and there's absolutely no difference between 1.4.12 and 1.4.13 that could explain this (the only change that affects what check_http sends is that is doesn't send the defaut port anymore on the Host: line - RFC 2616). My best guess would be a change in your OpenSSL installation. Can you try recompiling 1.4.12 from scratch (don't re-use your previous compile tree)? It would also be nice to know: - Your configure parameters - Your OpenSSL version - An externally accessible server to test with, if possible. Thanks ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=397597&aid=2826570&group_id=29880 From dermoth at aei.ca Sat Jul 25 03:32:44 2009 From: dermoth at aei.ca (Thomas Guyot-Sionnest) Date: Fri, 24 Jul 2009 21:32:44 -0400 Subject: [Nagiosplug-devel] Spam@nagiosplugins.org In-Reply-To: <20090724211115.GC60145715@Waran.CIS.FU-Berlin.DE> References: <738B7AF22F5740069FA5A1FCF575B991@int.consol.de> <20090724211115.GC60145715@Waran.CIS.FU-Berlin.DE> Message-ID: <4A6A60BC.9080803@aei.ca> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 24/07/09 05:11 PM, Holger Wei? wrote: > * Gerhard Lausser [2009-07-24 21:37]: >> i just noticed that somebody used the comments on nagiosplugins.org to >> spread a lot of spam links. > > Thanks for the hint, I removed them. Ouch... I also cleared the approval queue, and while doing so I noticed some of them look really like legit (slightly lame) comments but actually the dot ending the phrase is a 1x1 pixel image linking to a site to increase Google ranking. You missed this one (which I missed to even in full view until I found the trick outlined below): - --- update really pleased with, update really pleased with, thanks. - --- When they're not too long you can easily spot them by hovering the link, which shows the code with image link. It would be nice if: 1. We force approval when there is a link 2. Send an email to the team once a day if there are posts waiting to be approved - -- Thomas -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFKamC86dZ+Kt5BchYRAnsqAJ9KJDgKgBmreZeL8iXdQ5zWcalfqwCgkv3N 5LZfjE8UYv7ejnXH/Cvsqko= =XVrS -----END PGP SIGNATURE----- From noreply at sourceforge.net Mon Jul 27 20:58:22 2009 From: noreply at sourceforge.net (SourceForge.net) Date: Mon, 27 Jul 2009 18:58:22 +0000 Subject: [Nagiosplug-devel] [ nagiosplug-Bugs-2826570 ] check_http 1.4.13 does not work with some HTTPS servers Message-ID: Bugs item #2826570, was opened at 2009-07-24 15:37 Message generated for change (Comment added) made by steffencl You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=397597&aid=2826570&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: Release (specify) Status: Open Resolution: None Priority: 5 Private: No Submitted By: Steffen (steffencl) Assigned to: Thomas Guyot-Sionnest (dermoth) Summary: check_http 1.4.13 does not work with some HTTPS servers Initial Comment: Hello, we recently made a nagios-plugin update which introduced check_http v1.4.13 (nagios-plugins 1.4.13) Since then checks of some HTTPS-servers faild with the error "HTTP CRITICAL - Error on receive" A detailed analysis and comparison with older version (1.4.12) revealed the following: For testing we used the plugin on the Linux shell (Debian sid) like this: /usr/lib/nagios/plugins/check_http -4 --ssl -v \ -H -I A tcp-connection from the nagios host to the webserver was opened with the normal TCP-handshakes. After that the nagios-plugin sends it's first SSL handshake packet ("Client Hello") to the webserver which is answered by a TCP-FIN packet to close the connection. The webserver logs a message indicating that the SSL compression method of the client is not supported. I analysed the SSL protocol and found that the old plugin does NOT include a compression method in it's "Client Hello" message while the new one does. The SSL Client Hello Packed decoded by whireshark of the NEW plugin looks like this: ---snip---- Secure Socket Layer SSL Record Layer: Handshake Protocol: Client Hello Content Type: Handshake (22) Version: TLS 1.0 (0x0301) Length: 109 Handshake Protocol: Client Hello Handshake Type: Client Hello (1) Length: 105 Version: TLS 1.0 (0x0301) Random gmt_unix_time: Jul 24, 2009 13:42:28.000000000 random_bytes: 2930D11FA4... Session ID Length: 0 Cipher Suites Length: 38 Cipher Suites (19 suites) Cipher Suite: TLS_DHE_RSA_WITH_AES_256_CBC_SHA (0x0039) Cipher Suite: TLS_DHE_DSS_WITH_AES_256_CBC_SHA (0x0038) Cipher Suite: TLS_RSA_WITH_AES_256_CBC_SHA (0x0035) Cipher Suite: TLS_DHE_RSA_WITH_3DES_EDE_CBC_SHA (0x0016) Cipher Suite: TLS_DHE_DSS_WITH_3DES_EDE_CBC_SHA (0x0013) Cipher Suite: TLS_RSA_WITH_3DES_EDE_CBC_SHA (0x000a) Cipher Suite: TLS_DHE_RSA_WITH_AES_128_CBC_SHA (0x0033) Cipher Suite: TLS_DHE_DSS_WITH_AES_128_CBC_SHA (0x0032) Cipher Suite: TLS_RSA_WITH_AES_128_CBC_SHA (0x002f) Cipher Suite: TLS_RSA_WITH_RC4_128_SHA (0x0005) Cipher Suite: TLS_RSA_WITH_RC4_128_MD5 (0x0004) Cipher Suite: TLS_DHE_RSA_WITH_DES_CBC_SHA (0x0015) Cipher Suite: TLS_DHE_DSS_WITH_DES_CBC_SHA (0x0012) Cipher Suite: TLS_RSA_WITH_DES_CBC_SHA (0x0009) Cipher Suite: TLS_DHE_RSA_EXPORT_WITH_DES40_CBC_SHA (0x0014) Cipher Suite: TLS_DHE_DSS_EXPORT_WITH_DES40_CBC_SHA (0x0011) Cipher Suite: TLS_RSA_EXPORT_WITH_DES40_CBC_SHA (0x0008) Cipher Suite: TLS_RSA_EXPORT_WITH_RC2_CBC_40_MD5 (0x0006) Cipher Suite: TLS_RSA_EXPORT_WITH_RC4_40_MD5 (0x0003) Compression Methods Length: 2 Compression Methods (2 methods) Compression Method: DEFLATE (1) Compression Method: null (0) Extensions Length: 25 Extension: server_name Type: server_name (0x0000) Length: 17 Data (17 bytes) Extension: SessionTicket TLS Type: SessionTicket TLS (0x0023) Length: 0 Data (0 bytes) ---snip---- While the SSL Client Hello Packed of an old plugin looks like this: ---snip---- Secure Socket Layer SSLv2 Record Layer: Client Hello Length: 116 Handshake Message Type: Client Hello (1) Version: TLS 1.0 (0x0301) Cipher Spec Length: 75 Session ID Length: 0 Challenge Length: 32 Cipher Specs (25 specs) Cipher Spec: TLS_DHE_RSA_WITH_AES_256_CBC_SHA (0x000039) Cipher Spec: TLS_DHE_DSS_WITH_AES_256_CBC_SHA (0x000038) Cipher Spec: TLS_RSA_WITH_AES_256_CBC_SHA (0x000035) Cipher Spec: TLS_DHE_RSA_WITH_3DES_EDE_CBC_SHA (0x000016) Cipher Spec: TLS_DHE_DSS_WITH_3DES_EDE_CBC_SHA (0x000013) Cipher Spec: TLS_RSA_WITH_3DES_EDE_CBC_SHA (0x00000a) Cipher Spec: SSL2_DES_192_EDE3_CBC_WITH_MD5 (0x0700c0) Cipher Spec: TLS_DHE_RSA_WITH_AES_128_CBC_SHA (0x000033) Cipher Spec: TLS_DHE_DSS_WITH_AES_128_CBC_SHA (0x000032) Cipher Spec: TLS_RSA_WITH_AES_128_CBC_SHA (0x00002f) Cipher Spec: SSL2_RC2_CBC_128_CBC_WITH_MD5 (0x030080) Cipher Spec: TLS_RSA_WITH_RC4_128_SHA (0x000005) Cipher Spec: TLS_RSA_WITH_RC4_128_MD5 (0x000004) Cipher Spec: SSL2_RC4_128_WITH_MD5 (0x010080) Cipher Spec: TLS_DHE_RSA_WITH_DES_CBC_SHA (0x000015) Cipher Spec: TLS_DHE_DSS_WITH_DES_CBC_SHA (0x000012) Cipher Spec: TLS_RSA_WITH_DES_CBC_SHA (0x000009) Cipher Spec: SSL2_DES_64_CBC_WITH_MD5 (0x060040) Cipher Spec: TLS_DHE_RSA_EXPORT_WITH_DES40_CBC_SHA (0x000014) Cipher Spec: TLS_DHE_DSS_EXPORT_WITH_DES40_CBC_SHA (0x000011) Cipher Spec: TLS_RSA_EXPORT_WITH_DES40_CBC_SHA (0x000008) Cipher Spec: TLS_RSA_EXPORT_WITH_RC2_CBC_40_MD5 (0x000006) Cipher Spec: SSL2_RC2_CBC_128_CBC_WITH_MD5 (0x040080) Cipher Spec: TLS_RSA_EXPORT_WITH_RC4_40_MD5 (0x000003) Cipher Spec: SSL2_RC4_128_EXPORT40_WITH_MD5 (0x020080) Challenge ---snip---- As you see with no compression method field. We had no problems with version 1.4.12, but since 1.4.13 we have the described problems with some servers, primary with older servers and appliences useing HTTPS. There are no problems against apache servers. - Steffen ---------------------------------------------------------------------- >Comment By: Steffen (steffencl) Date: 2009-07-27 20:58 Message: We use Debian "sid". OpenSSL was before the update and still is verion 0.9.8k 25 Mar 2009 According to Debian's update log the following has changed: [UPGRADE] nagios-nrpe-plugin 2.12-3 -> 2.12-3.1 [UPGRADE] nagios-plugins 1.4.12-5 -> 1.4.13+git200906171200-1 [UPGRADE] nagios-plugins-basic 1.4.12-5 -> 1.4.13+git200906171200-1 [UPGRADE] nagios-plugins-standard 1.4.12-5 -> 1.4.13+git200906171200-1 [UPGRADE] nagios3 3.0.6-4 -> 3.0.6-5 [UPGRADE] nagios3-common 3.0.6-4 -> 3.0.6-5 [UPGRADE] nagios3-doc 3.0.6-4 -> 3.0.6-5 Since we use packages of provided by or for the used distribution, we do not compile but use the packagetmanager of the distribution (here Debian sid). - Steffen ---------------------------------------------------------------------- Comment By: Thomas Guyot-Sionnest (dermoth) Date: 2009-07-25 03:51 Message: Hi, and thanks for your report. I checked the change logs between these two release and there's absolutely no difference between 1.4.12 and 1.4.13 that could explain this (the only change that affects what check_http sends is that is doesn't send the defaut port anymore on the Host: line - RFC 2616). My best guess would be a change in your OpenSSL installation. Can you try recompiling 1.4.12 from scratch (don't re-use your previous compile tree)? It would also be nice to know: - Your configure parameters - Your OpenSSL version - An externally accessible server to test with, if possible. Thanks ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=397597&aid=2826570&group_id=29880 From noreply at sourceforge.net Wed Jul 29 04:20:43 2009 From: noreply at sourceforge.net (SourceForge.net) Date: Wed, 29 Jul 2009 02:20:43 +0000 Subject: [Nagiosplug-devel] [ nagiosplug-Bugs-1108499 ] Ping command with -U option in Debian Message-ID: Bugs item #1108499, was opened at 2005-01-24 17:42 Message generated for change (Comment added) made by sf-robot You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=397597&aid=1108499&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: Argument proccessing Group: CVS >Status: Closed Resolution: None Priority: 5 Private: No Submitted By: Guillaume (guiguidoc) Assigned to: Ton Voon (tonvoon) Summary: Ping command with -U option in Debian Initial Comment: in the configure ping option is : -U and it doesn't work... ./check_ping -H 127.0.0.1 -n -w 2,10% -c 5,20% /bin/ping -n -U -w 10 -c 5 127.0.0.1 CRITIQUE - Impossible d'interprter le rponse de la commande ping ---------------------------------------------------------------------- >Comment By: SourceForge Robot (sf-robot) Date: 2009-07-29 02:20 Message: This Tracker item was closed automatically by the system. It was previously set to a Pending status, and the original submitter did not respond within 14 days (the time period specified by the administrator of this Tracker). ---------------------------------------------------------------------- Comment By: Ton Voon (tonvoon) Date: 2009-07-14 22:44 Message: Hi Guillaume, Given the age of this, I assume it has been fixed. I'm marking this in a pending state. Please update if this is still an issue. Ton ---------------------------------------------------------------------- Comment By: Benoit Mortier (opensides) Date: 2005-01-24 19:36 Message: Logged In: YES user_id=388184 Hi, confirmed in debian sarge will look at it ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=397597&aid=1108499&group_id=29880 From sunilnaikwadi04 at indiatimes.com Thu Jul 30 09:03:51 2009 From: sunilnaikwadi04 at indiatimes.com (sunil naik) Date: Thu, 30 Jul 2009 12:33:51 +0530 (IST) Subject: [Nagiosplug-devel] Need to install nagios Nrpe and Plugins on AIX 5.3 and 6.1 Message-ID: <44385446.147391248937431004.JavaMail.root@mbr24.indiatimes.com> Dear Team we setup the Nagios3.0 on RHEL5 and we monitor the hosts LInux , Windows and some Network devices . now we have to Monitoe IBM AiX ..for the we tried to compile plugins and nrep but we get the ssl error. Note: Open ssl package has been already instlled on AIX5.3 we try the below plugins AIX 5.3 NRPE 2.12 NSCA 2.7.2 Nagios-Plugins 1.4.11 Please Suggest us. -- Click for exclusive coverage on the New Bajaj Pulsar 220 the fastest Indian bike http://www.zigwheels.com/Features/Bajaj-Pulsar-220-DTSi-Special-Coverage/Pulsar_20090623-1-1 From eva.keane at tradeweb.com Thu Jul 30 14:33:33 2009 From: eva.keane at tradeweb.com (eva.keane at tradeweb.com) Date: Thu, 30 Jul 2009 08:33:33 -0400 Subject: [Nagiosplug-devel] max clients on nagios host Message-ID: <4D65ACEF6EFDFB48A8F9B57B7D17B9BF05DEEF2D@tfusnjpscmbx03.ERF.THOMSON.COM> Hello, I have added 210 clients for a nagios host to monitor.... I am wondering what the maximum for a host to monitor. I am experience that if I added more hosts; I am experience strange behavior in that I have to refresh to see the new clients services, and if I refresh again... the services disappear...the clients doesn't appear as client unless I search for it... etc.... -Eva -------------- next part -------------- An HTML attachment was scrubbed... URL: From marc at ena.com Thu Jul 30 15:04:57 2009 From: marc at ena.com (Marc Powell) Date: Thu, 30 Jul 2009 08:04:57 -0500 Subject: [Nagiosplug-devel] max clients on nagios host In-Reply-To: <4D65ACEF6EFDFB48A8F9B57B7D17B9BF05DEEF2D@tfusnjpscmbx03.ERF.THOMSON.COM> References: <4D65ACEF6EFDFB48A8F9B57B7D17B9BF05DEEF2D@tfusnjpscmbx03.ERF.THOMSON.COM> Message-ID: <993E312E-1818-4219-9DF2-C85EC6FBD6DC@ena.com> On Jul 30, 2009, at 7:33 AM, wrote: > Hello, > > I have added 210 clients for a nagios host to monitor?. I am > wondering what the maximum for a host to monitor. There are no inherent limits beyond what your hardware is capable of. There are people monitoring (10's of) thousands of hosts/services. > I am experience that if I added more hosts; I am experience strange > behavior in that I have to refresh to see the new clients services, > and if I refresh again? the services disappear?the clients doesn?t > appear as client unless I search for it? etc?. http://support.nagios.com/knowledge-base/index.php?option=com_content&view=article&id=52&catid=35&faq_id=21 -- Marc From rich at richhorner.com Thu Jul 30 16:24:30 2009 From: rich at richhorner.com (Richard Edward Horner) Date: Thu, 30 Jul 2009 14:24:30 +0000 Subject: [Nagiosplug-devel] max clients on nagios host In-Reply-To: <4D65ACEF6EFDFB48A8F9B57B7D17B9BF05DEEF2D@tfusnjpscmbx03.ERF.THOMSON.COM> References: <4D65ACEF6EFDFB48A8F9B57B7D17B9BF05DEEF2D@tfusnjpscmbx03.ERF.THOMSON.COM> Message-ID: <7a65a83a0907300724ub380672qc40cee36dc56bb4f@mail.gmail.com> If your hardware or network is having trouble keeping up, you may want to try increasing the check interval. Richard On Thu, Jul 30, 2009 at 12:33 PM, wrote: > Hello, > > > > I have added 210 clients for a nagios host to monitor?. I am wondering what > the maximum for a host to monitor. I am experience that if I added more > hosts; I am experience strange behavior in that I have to refresh to see the > new clients services, and if I refresh again? the services disappear?the > clients doesn?t appear as client unless I search for it? etc?. > > > > -Eva > > ------------------------------------------------------------------------------ > Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day > trial. Simplify your report design, integration and deployment - and focus > on > what you do best, core application coding. Discover what's new with > Crystal Reports now. ?http://p.sf.net/sfu/bobj-july > _______________________________________________________ > Nagios Plugin Development Mailing List > Nagiosplug-devel at lists.sourceforge.net > Unsubscribe at https://lists.sourceforge.net/lists/listinfo/nagiosplug-devel > ::: Please include plugins version (-v) and OS when reporting any issue. > ::: Messages without supporting info will risk being sent to /dev/null > -- Richard Edward Horner Engineer / Composer / Electric Guitar Virtuoso richhorner.com | rhosts.net | sabayonlinux.org From dermoth at aei.ca Thu Jul 30 23:56:32 2009 From: dermoth at aei.ca (Thomas Guyot-Sionnest) Date: Thu, 30 Jul 2009 17:56:32 -0400 Subject: [Nagiosplug-devel] Regression in check_snmp Message-ID: <4A721710.5040006@aei.ca> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I just installed the latest development head on a nagios server and noticed there's a nasty regression in check_snmp. We don't use the shell anymore, but with an empty miblist we still add single-quotes to mark the required argument: External command error: Cannot find module (''): At line 0 in (none) Obviously the quotes are now part of the argument, just like if we passed this: - -m "''" I may fix it tonight, but I wanted to make sure we don't make the release before it gets fixed :) - -- Thomas -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFKchcQ6dZ+Kt5BchYRAjG4AJ0XeSzP0lpxFl0r5z9XMcJZOATDSQCfU6s/ U697Ob4ZiQ8z+iapnXUysUY= =I1l2 -----END PGP SIGNATURE----- From Ton.Voon at opsera.com Fri Jul 31 08:59:42 2009 From: Ton.Voon at opsera.com (Ton Voon) Date: Fri, 31 Jul 2009 07:59:42 +0100 Subject: [Nagiosplug-devel] Regression in check_snmp In-Reply-To: <4A721710.5040006@aei.ca> References: <4A721710.5040006@aei.ca> Message-ID: Good catch. I'm on holiday for a week so I can't help with it for a few days. That is the only issue I'm aware of at the moment On 30 Jul 2009, at 22:56, "Thomas Guyot-Sionnest" wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > I just installed the latest development head on a nagios server and > noticed there's a nasty regression in check_snmp. We don't use the > shell > anymore, but with an empty miblist we still add single-quotes to mark > the required argument: > > External command error: Cannot find module (''): At line 0 in (none) > > Obviously the quotes are now part of the argument, just like if we > passed this: > > - -m "''" > > I may fix it tonight, but I wanted to make sure we don't make the > release before it gets fixed :) > > - -- > Thomas > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.7 (MingW32) > Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org > > iD8DBQFKchcQ6dZ+Kt5BchYRAjG4AJ0XeSzP0lpxFl0r5z9XMcJZOATDSQCfU6s/ > U697Ob4ZiQ8z+iapnXUysUY= > =I1l2 > -----END PGP SIGNATURE----- From dermoth at aei.ca Fri Jul 31 09:19:47 2009 From: dermoth at aei.ca (Thomas Guyot-Sionnest) Date: Fri, 31 Jul 2009 03:19:47 -0400 Subject: [Nagiosplug-devel] Regression in check_snmp In-Reply-To: References: <4A721710.5040006@aei.ca> Message-ID: <4A729B13.1030302@aei.ca> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 31/07/09 02:59 AM, Ton Voon wrote: > Good catch. I'm on holiday for a week so I can't help with it for a few > days. That is the only issue I'm aware of at the moment Turns out the error I showed was my fault - typo in the hostname - but I'm still wondering how the single quotes turns out to be. Maybe they're being ignored... The problem is actually with multi-line strings. I just committed a new test script using a custom SNMP agent and now I'm able to reproduce the problem (segfault). The simplest fix is easy, just skip any additional lines (i.e. if response if NULL), though if the string contains a delimiter it will likely blow chunks again. I'll try to figure out what the 1.4.13 version did regarding these strings and will reproduce the behavior as much as I can. - -- Thomas -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFKcpsT6dZ+Kt5BchYRArvXAKDJBqH4U/ffxE0XHFYem+NI7bLvWwCggMEK CDIy+tnXtjS9VhcF5TedqWU= =/fg5 -----END PGP SIGNATURE----- From dermoth at aei.ca Fri Jul 31 09:44:53 2009 From: dermoth at aei.ca (Thomas Guyot-Sionnest) Date: Fri, 31 Jul 2009 03:44:53 -0400 Subject: [Nagiosplug-devel] Regression in check_snmp In-Reply-To: <4A729B13.1030302@aei.ca> References: <4A721710.5040006@aei.ca> <4A729B13.1030302@aei.ca> Message-ID: <4A72A0F5.90006@aei.ca> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 31/07/09 03:19 AM, Thomas Guyot-Sionnest wrote: > On 31/07/09 02:59 AM, Ton Voon wrote: >> Good catch. I'm on holiday for a week so I can't help with it for a few >> days. That is the only issue I'm aware of at the moment > > Turns out the error I showed was my fault - typo in the hostname - but > I'm still wondering how the single quotes turns out to be. Maybe they're > being ignored... > > The problem is actually with multi-line strings. I just committed a new > test script using a custom SNMP agent and now I'm able to reproduce the > problem (segfault). > > The simplest fix is easy, just skip any additional lines (i.e. if > response if NULL), though if the string contains a delimiter it will > likely blow chunks again. > > I'll try to figure out what the 1.4.13 version did regarding these > strings and will reproduce the behavior as much as I can. > Duh... The old code was totally ugly, but it accounted for these strings. If the string begins with a " it keeps reading until it find the matching closing quote. It was still broken in that it printed a | on the last line... should appear on the first line as the rest is nagios3 extended output. Trying to join lines back into one would be silly as the data length on the first line if very limited. So I'm tempted to keep the code and fix the perfdata... I would probably append all multi-line output at the end so nagios3 can get it, while fixing the performance data (if you have more than one OID and have thresholds on non-strings). If I do so I will duplicate the first line though so we'll see the whole output in the additional output lines. It's pretty late here now... I'll finish another day :) - -- Thomas -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFKcqD16dZ+Kt5BchYRAjb7AKCBjGyad16Qk8z2/rIfU/eM/fgfYQCgnKjY RhZyp/PTBQObGaLoOSwk/kY= =G0EW -----END PGP SIGNATURE----- From sunilnaikwadi04 at indiatimes.com Fri Jul 31 23:13:44 2009 From: sunilnaikwadi04 at indiatimes.com (sunil naik) Date: Sat, 1 Aug 2009 02:43:44 +0530 (IST) Subject: [Nagiosplug-devel] How to use my shell script in Nagios Message-ID: <607405810.6061249074824571.JavaMail.root@mbr24.indiatimes.com> Dear team Please let us know how i Use my monitor.sh scripts in Nagios plugin Regards Sunil Naikwadi -- Click for exclusive coverage on the New Bajaj Pulsar 220 the fastest Indian bike http://www.zigwheels.com/Features/Bajaj-Pulsar-220-DTSi-Special-Coverage/Pulsar_20090623-1-1