From holger at cis.fu-berlin.de Mon Sep 2 13:26:15 2013 From: holger at cis.fu-berlin.de (Holger =?iso-8859-1?Q?Wei=DF?=) Date: Mon, 2 Sep 2013 13:26:15 +0200 Subject: [Nagiosplug-devel] New release planned next week Message-ID: <20130902112615.GA977898@zedat.fu-berlin.de> As there are quite a few fixes and enhancements? (plus a new plugin!) in the current Git code, we'd like to cut the 1.5 release next week. Until then, only bug fixes and regressions will be addressed. If you could spare a bit of time to test the current snapshot? and report any regressions from the 1.4.16 release, that would be awesome! Holger ? https://raw.github.com/nagios-plugins/nagios-plugins/master/NEWS ? http://nagiosplug.sourceforge.net/snapshot/nagios-plugins-master.tar.gz From palli at ok.is Tue Sep 3 13:43:32 2013 From: palli at ok.is (=?utf-8?Q?P=C3=A1ll_Gu=C3=B0j=C3=B3n_Sigur=C3=B0sson?=) Date: Tue, 03 Sep 2013 11:43:32 -0000 (GMT) Subject: [Nagiosplug-devel] New Threshold Syntax In-Reply-To: <20130821123559.GI282039@zedat.fu-berlin.de> Message-ID: <6df8ede7-b987-4234-ac49-a138061954d8@zimbra.okhysing.is> Holger, we really appreciate all the quality work you guys put into the Nagios Plugins. thanks! I would personally like to see the new threshold syntax move forward once someone is willing to spend the proper resources on it. In the meantime you guys can help out a lot and give this alternative syntax a better name than "the new threshold syntax". We claim to support it in pynag, but 10 years from now my code will look really silly if it references "the new threshold syntax" everywhere. On those notes, we try to follow very closely the guidelines that you guys give us, namely plugin developer guidelines and extra-opts guidelines, no matter what we think of them, but one thing that would help us a lot if you can put a version number (or even just a date) on the guidelines that you post. That way can make a claim like "we support plugin developer guidelines version 6" and not constantly have to worry about you guys updating the standard without us noticing. ----- Original Message ----- From: "Holger Wei?" To: "Nagios Plugins Development" Sent: Wednesday, August 21, 2013 12:35:59 PM Subject: Re: [Nagiosplug-devel] New Threshold Syntax * P?ll Gu?j?n Sigur?sson [2013-07-15 20:57]: > We implemented same RFC in pynag (python modules for nagios related > stuff). We also hit some walls and wanted to make modifications. > Unfortunately, it's been a long time since it was written and author of > the proposal is not answering my emails on the topic. > > I am not sure if there is a lot of motivation among the nagios-plugins > folks to implement this RFC, so i wonder if third party libraries like > you and should coordinate on it anyway ? We (the Plugins Development Team) discussed this internally, but we haven't really reached a consensus on how to proceed. Some concerns have been raised regarding the added complexity and the amount of refactoring necessary to check only for specified thresholds. Either way, I guess we must acknowledge that we currently lack the manpower to implement a new threshold syntax, which means we'll probably stick to the current syntax for the time being. So I'd say yes: Please move ahead independently of us. Personally I quite like the new syntax, and if you settled on the details and it works well for you, we can still decide on whether and how to adopt it :-) Thanks a lot for your work on this! Holger ------------------------------------------------------------------------------ Introducing Performance Central, a new site from SourceForge and AppDynamics. Performance Central is your source for news, insights, analysis and resources for efficient Application Performance Management. Visit us today! http://pubads.g.doubleclick.net/gampad/clk?id=48897511&iu=/4140/ostg.clktrk _______________________________________________________ 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 holger at cis.fu-berlin.de Tue Sep 3 14:13:23 2013 From: holger at cis.fu-berlin.de (Holger =?iso-8859-1?Q?Wei=DF?=) Date: Tue, 3 Sep 2013 14:13:23 +0200 Subject: [Nagiosplug-devel] New Threshold Syntax In-Reply-To: <6df8ede7-b987-4234-ac49-a138061954d8@zimbra.okhysing.is> References: <20130821123559.GI282039@zedat.fu-berlin.de> <6df8ede7-b987-4234-ac49-a138061954d8@zimbra.okhysing.is> Message-ID: <20130903121323.GO282039@zedat.fu-berlin.de> * P?ll Gu?j?n Sigur?sson [2013-09-03 11:43]: > I would personally like to see the new threshold syntax move forward > once someone is willing to spend the proper resources on it. In the > meantime you guys can help out a lot and give this alternative syntax a > better name than "the new threshold syntax". We claim to support it in > pynag, but 10 years from now my code will look really silly if it > references "the new threshold syntax" everywhere. I see you point, but *I* am incredibly bad at naming things, so someone else will have to jump in. > On those notes, we try to follow very closely the guidelines that you > guys give us, namely plugin developer guidelines and extra-opts > guidelines, no matter what we think of them Hehe, I don't know why, but for some reason I get the feeling your're not completely brimmed over with enthusiasm for these terrific standards! > but one thing that would help us a lot if you can put a version number > (or even just a date) on the guidelines that you post. Good point, will do. Holger From ae at op5.se Tue Sep 3 15:40:29 2013 From: ae at op5.se (Andreas Ericsson) Date: Tue, 03 Sep 2013 15:40:29 +0200 Subject: [Nagiosplug-devel] New Threshold Syntax In-Reply-To: <20130903121323.GO282039@zedat.fu-berlin.de> References: <20130821123559.GI282039@zedat.fu-berlin.de> <6df8ede7-b987-4234-ac49-a138061954d8@zimbra.okhysing.is> <20130903121323.GO282039@zedat.fu-berlin.de> Message-ID: <5225E6CD.20405@op5.se> On 2013-09-03 14:13, Holger Wei? wrote: > * P?ll Gu?j?n Sigur?sson [2013-09-03 11:43]: >> I would personally like to see the new threshold syntax move forward >> once someone is willing to spend the proper resources on it. In the >> meantime you guys can help out a lot and give this alternative syntax a >> better name than "the new threshold syntax". We claim to support it in >> pynag, but 10 years from now my code will look really silly if it >> references "the new threshold syntax" everywhere. > > I see you point, but *I* am incredibly bad at naming things, so someone > else will have to jump in. > Nagios Plugin Threshold Syntax 3.0 npts 3.0, for short. 1.0 were wild-wild west, where each plugin had their own. 2.0 are the current ones, so it'll have to be 3.0. -- Andreas Ericsson andreas.ericsson at op5.se OP5 AB www.op5.se Tel: +46 8-230225 Fax: +46 8-230231 Considering the successes of the wars on alcohol, poverty, drugs and terror, I think we should give some serious thought to declaring war on peace. From palli at ok.is Tue Sep 3 15:55:20 2013 From: palli at ok.is (=?utf-8?Q?P=C3=A1ll_Gu=C3=B0j=C3=B3n_Sigur=C3=B0sson?=) Date: Tue, 03 Sep 2013 13:55:20 -0000 (GMT) Subject: [Nagiosplug-devel] New Threshold Syntax In-Reply-To: <20130903121323.GO282039@zedat.fu-berlin.de> Message-ID: <29b89db6-bc28-4bab-a3f7-4ccf7ddc695b@zimbra.okhysing.is> The plugin guidelines are like a bible over here. You will not believe how much work i have saved by following the guidelines instead of inventing the wheel by myself. They are in fact terrific. Its the kinks in extra-opts that is my current source of under enthusiasm. Namely: 1) By observing the examples it seems the following is allowed: # ./check_stuff --extra-opts=@/etc/myconfig.ini # ./check_stuff --extra-opts -jk --some-other-opt The latter one causes confusing ambiguity and its not supported by python's OptionParser. I'd prefer to see it removed from the spec. and replaced with --extra-opts='' to achieve the same end result. ----- Original Message ----- From: "Holger Wei?" To: "Nagios Plugins Development" Sent: Tuesday, September 3, 2013 12:13:23 PM Subject: Re: [Nagiosplug-devel] New Threshold Syntax * P?ll Gu?j?n Sigur?sson [2013-09-03 11:43]: > I would personally like to see the new threshold syntax move forward > once someone is willing to spend the proper resources on it. In the > meantime you guys can help out a lot and give this alternative syntax a > better name than "the new threshold syntax". We claim to support it in > pynag, but 10 years from now my code will look really silly if it > references "the new threshold syntax" everywhere. I see you point, but *I* am incredibly bad at naming things, so someone else will have to jump in. > On those notes, we try to follow very closely the guidelines that you > guys give us, namely plugin developer guidelines and extra-opts > guidelines, no matter what we think of them Hehe, I don't know why, but for some reason I get the feeling your're not completely brimmed over with enthusiasm for these terrific standards! > but one thing that would help us a lot if you can put a version number > (or even just a date) on the guidelines that you post. Good point, will do. Holger ------------------------------------------------------------------------------ Learn the latest--Visual Studio 2012, SharePoint 2013, SQL 2012, more! Discover the easy way to master current and previous Microsoft technologies and advance your career. Get an incredible 1,500+ hours of step-by-step tutorial videos with LearnDevNow. Subscribe today and save! http://pubads.g.doubleclick.net/gampad/clk?id=58040911&iu=/4140/ostg.clktrk _______________________________________________________ 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 Jochen.Bern at LINworks.de Tue Sep 3 16:18:21 2013 From: Jochen.Bern at LINworks.de (Jochen Bern) Date: Tue, 03 Sep 2013 16:18:21 +0200 Subject: [Nagiosplug-devel] New Threshold Syntax In-Reply-To: <20130903121323.GO282039@zedat.fu-berlin.de> References: <20130821123559.GI282039@zedat.fu-berlin.de> <6df8ede7-b987-4234-ac49-a138061954d8@zimbra.okhysing.is> <20130903121323.GO282039@zedat.fu-berlin.de> Message-ID: <5225EFAD.3070607@LINworks.de> On 03.09.2013 14:13, Holger Wei? wrote: > * P?ll Gu?j?n Sigur?sson [2013-09-03 11:43]: >> In the >> meantime you guys can help out a lot and give this alternative syntax a >> better name than "the new threshold syntax". We claim to support it in >> pynag, but 10 years from now my code will look really silly if it >> references "the new threshold syntax" everywhere. You seem to have an idea how many places called "Neufchatel" (literally "new castle") there are in France ... :-) > I see you point, but *I* am incredibly bad at naming things, so someone > else will have to jump in. The core of the respective proposal are what mathematicians call intervals (Ton) or unions thereof, so if you'ld like something other than the version numbers Andreas suggested, "Thresholds as Intervals Notation (TIN)" and "Thresholds as Unions of Intervals Notation (TUIN)" come to mind. (Note: "tuin" is the Dutch term for "garden".) Regards, J. Bern -- *NEU* - NEC IT-Infrastruktur-Produkte im : Server--Storage--Virtualisierung--Management SW--Passion for Performance Jochen Bern, Systemingenieur --- LINworks GmbH Postfach 100121, 64201 Darmstadt | Robert-Koch-Str. 9, 64331 Weiterstadt PGP (1024D/4096g) FP = D18B 41B1 16C0 11BA 7F8C DCF7 E1D5 FAF4 444E 1C27 Tel. +49 6151 9067-231, Zentr. -0, Fax -299 - Amtsg. Darmstadt HRB 85202 Unternehmenssitz Weiterstadt, Gesch?ftsf?hrer Metin Dogan, Oliver Michel From Stephan at quantentunnel.de Tue Sep 3 19:43:05 2013 From: Stephan at quantentunnel.de (Stephan) Date: Tue, 03 Sep 2013 19:43:05 +0200 Subject: [Nagiosplug-devel] New Threshold Syntax In-Reply-To: <5225EFAD.3070607@LINworks.de> References: <20130821123559.GI282039@zedat.fu-berlin.de> <6df8ede7-b987-4234-ac49-a138061954d8@zimbra.okhysing.is> <20130903121323.GO282039@zedat.fu-berlin.de> <5225EFAD.3070607@LINworks.de> Message-ID: <52261FA9.6070109@quantentunnel.de> Am 03.09.13 16:18, schrieb Jochen Bern: > O > The core of the respective proposal are what mathematicians call > intervals (Ton) or unions thereof, so if you'ld like something other > than the version numbers Andreas suggested, "Thresholds as Intervals > Notation (TIN)" and "Thresholds as Unions of Intervals Notation (TUIN)" > come to mind. > > (Note: "tuin" is the Dutch term for "garden".) > TUIN=The Universal Interval Notation or The Useful Interval Notation Tremendously Useful Interval Notation ;) From william at leibzon.org Tue Sep 3 20:59:18 2013 From: william at leibzon.org (William Leibzon) Date: Tue, 3 Sep 2013 11:59:18 -0700 Subject: [Nagiosplug-devel] New Threshold Syntax In-Reply-To: <6df8ede7-b987-4234-ac49-a138061954d8@zimbra.okhysing.is> References: <20130821123559.GI282039@zedat.fu-berlin.de> <6df8ede7-b987-4234-ac49-a138061954d8@zimbra.okhysing.is> Message-ID: Good points about having identifiable specification version number. So unless people have have strong objections when talking about this proposal on Nagios conference BoF, I will use long name of "Nagios Plugins Development Guidelines and Threshold Syntax Specification 2.0 (2013)" with short abbreviations NPDG 2.0 and NPTS 2.0 when talking specifically about threshold syntax and interval notation. This is since in my view 1.0 can not be no guidelines (that is 0.0 if you like) and 1.0 is what is in common use right now. Long name is because documented are more than just threshold and interval specification syntax. If people want some nick name name for 2.0 syntax (like it is done with all OS releases) then TUIN sounds good, in fact I possibly will use this ("Threshold as Unit Intervals") as a slide title. -------------- next part -------------- An HTML attachment was scrubbed... URL: From holger at cis.fu-berlin.de Wed Sep 4 14:04:44 2013 From: holger at cis.fu-berlin.de (Holger =?iso-8859-1?Q?Wei=DF?=) Date: Wed, 4 Sep 2013 14:04:44 +0200 Subject: [Nagiosplug-devel] --extra-opts (was: New Threshold Syntax) In-Reply-To: <29b89db6-bc28-4bab-a3f7-4ccf7ddc695b@zimbra.okhysing.is> References: <20130903121323.GO282039@zedat.fu-berlin.de> <29b89db6-bc28-4bab-a3f7-4ccf7ddc695b@zimbra.okhysing.is> Message-ID: <20130904120444.GP282039@zedat.fu-berlin.de> * P?ll Gu?j?n Sigur?sson [2013-09-03 13:55]: > 1) By observing the examples it seems the following is allowed: > # ./check_stuff --extra-opts=@/etc/myconfig.ini > # ./check_stuff --extra-opts -jk --some-other-opt > > The latter one causes confusing ambiguity and its not supported by > python's OptionParser. Just to clarify: the ambiguity is about -extra-opts=-jk vs. -jk --extra-opts and the thing not supported by Python's OptionParser is options that take an optional argument? I would've thought that "--extra-opts -jk" is quite obviously meant to be equivalent to "-jk --extra-opts"; but if your parser doesn't support this, that's of course a major problem. Hmm. Holger From palli at ok.is Wed Sep 4 14:18:25 2013 From: palli at ok.is (=?utf-8?Q?P=C3=A1ll_Gu=C3=B0j=C3=B3n_Sigur=C3=B0sson?=) Date: Wed, 04 Sep 2013 12:18:25 -0000 (GMT) Subject: [Nagiosplug-devel] --extra-opts (was: New Threshold Syntax) In-Reply-To: <20130904120444.GP282039@zedat.fu-berlin.de> Message-ID: Python's optparse does not support optional arguments and you are right, if what follows extra-opts is an option (like -jk) its easy to make an educated guess. However the spec said that extra-opts can be specified anywhere on the command-line and consider the following scenario: # check_stuff --extra-opts host.example.com In the above example its impossible to tell if "host.example.com" is a section name or an argument to the plugin. For that reason, i'd like to propose that the spec removes the reference to --extra-opts without arguments and instead assumed the following (which are all fairly standard) to achieve the same effect. --extra-opts= --extra-opts='' --extra-opts '' I have no problem with current implementations that support the optional argument, but it feels quite quirky to me, and should be considered a "hidden feature" in current implementations :) Cheers, Palli ----- Original Message ----- From: "Holger Wei?" To: "Nagios Plugins Development" Sent: Wednesday, September 4, 2013 12:04:44 PM Subject: [Nagiosplug-devel] --extra-opts (was: New Threshold Syntax) * P?ll Gu?j?n Sigur?sson [2013-09-03 13:55]: > 1) By observing the examples it seems the following is allowed: > # ./check_stuff --extra-opts=@/etc/myconfig.ini > # ./check_stuff --extra-opts -jk --some-other-opt > > The latter one causes confusing ambiguity and its not supported by > python's OptionParser. Just to clarify: the ambiguity is about -extra-opts=-jk vs. -jk --extra-opts and the thing not supported by Python's OptionParser is options that take an optional argument? I would've thought that "--extra-opts -jk" is quite obviously meant to be equivalent to "-jk --extra-opts"; but if your parser doesn't support this, that's of course a major problem. Hmm. Holger ------------------------------------------------------------------------------ Learn the latest--Visual Studio 2012, SharePoint 2013, SQL 2012, more! Discover the easy way to master current and previous Microsoft technologies and advance your career. Get an incredible 1,500+ hours of step-by-step tutorial videos with LearnDevNow. Subscribe today and save! http://pubads.g.doubleclick.net/gampad/clk?id=58040911&iu=/4140/ostg.clktrk _______________________________________________________ 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 holger at cis.fu-berlin.de Wed Sep 4 14:40:26 2013 From: holger at cis.fu-berlin.de (Holger =?iso-8859-1?Q?Wei=DF?=) Date: Wed, 4 Sep 2013 14:40:26 +0200 Subject: [Nagiosplug-devel] --extra-opts In-Reply-To: References: <20130904120444.GP282039@zedat.fu-berlin.de> Message-ID: <20130904124026.GQ282039@zedat.fu-berlin.de> * P?ll Gu?j?n Sigur?sson [2013-09-04 12:18]: > Python's optparse does not support optional arguments and you are right, > if what follows extra-opts is an option (like -jk) its easy to make an > educated guess. However the spec said that extra-opts can be specified > anywhere on the command-line and consider the following scenario: > > # check_stuff --extra-opts host.example.com > > In the above example its impossible to tell if "host.example.com" is a > section name or an argument to the plugin. I agree this case is less obvious if you're not used to GNU getopt(3)'s semantics (where optional arguments "must be written directly after the long option name, separated by '=', if present"?). > For that reason, i'd like to propose that the spec removes the reference > to --extra-opts without arguments and instead assumed the following > (which are all fairly standard) to achieve the same effect. > > --extra-opts= > --extra-opts='' > --extra-opts '' Fine with me, but I'm not the --extra-opts guy. Thomas, any comments? Holger ? http://man7.org/linux/man-pages/man1/getopt.1.html From noreply at sourceforge.net Wed Sep 4 23:30:59 2013 From: noreply at sourceforge.net (SourceForge.net) Date: Wed, 04 Sep 2013 14:30:59 -0700 Subject: [Nagiosplug-devel] [ nagiosplug-Patches-2975393 ] check_http HTTP CONNECT through proxy patch Message-ID: Patches item #2975393, was opened at 2010-03-23 11:43 Message generated for change (Settings changed) made by hweiss You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=397599&aid=2975393&group_id=29880 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Enhancement Group: release-1.4.14 Status: Open Resolution: None Priority: 5 Private: No Submitted By: mfrostp83 (mfrostp83) >Assigned to: Holger Weiss (hweiss) Summary: check_http HTTP CONNECT through proxy patch Initial Comment: check_http cannot (as of 1.4.14) speak the HTTP CONNECT protocol through a proxy. This is primarily used for checking SSL through a proxy. The attached patch allows this functionality by using the -K or --http-connect flag telling check_http to connect with HTTP CONNECT. Note that this option depends on SSL being enabled and will only connect to a remote host using port 443 which is not adjustable from the command-line. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=397599&aid=2975393&group_id=29880 From noreply at sourceforge.net Wed Sep 4 23:32:41 2013 From: noreply at sourceforge.net (SourceForge.net) Date: Wed, 04 Sep 2013 14:32:41 -0700 Subject: [Nagiosplug-devel] [ nagiosplug-Patches-3414894 ] check_http: add CONNECT method Message-ID: Patches item #3414894, was opened at 2011-09-28 01:21 Message generated for change (Settings changed) made by hweiss You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=397599&aid=3414894&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: None Priority: 5 Private: No Submitted By: Duncan Ferguson (duncan_ferguson) >Assigned to: Holger Weiss (hweiss) Summary: check_http: add CONNECT method Initial Comment: Add 'CONNECT' method to chek+http Patch taken from http://nagios.frank4dd.com/howto/monitor-ssl-websites-through-proxy.htm and reworked slightly for nagios-plugins-1.4.15 The arguments will be check_http_new -I -p -u -S(sl) -j CONNECT -H A suggested test would be check_http_new -I -p -u https://www.verisign.com/ -S -j CONNECT -H www.verisign.com This has been tested by one of our Opsview customers and works as expected Duncs ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=397599&aid=3414894&group_id=29880 From william at leibzon.org Thu Sep 5 21:33:34 2013 From: william at leibzon.org (William Leibzon) Date: Thu, 5 Sep 2013 12:33:34 -0700 Subject: [Nagiosplug-devel] New Threshold Syntax In-Reply-To: <52150774.1070705@LINworks.de> References: <20130821123559.GI282039@zedat.fu-berlin.de> <52150774.1070705@LINworks.de> Message-ID: This was very valuable feedback on current proposal spec I really appreciate Jochen going through it. My reply in regards to the feedback is below and I modified proposal text based on the feedback. Latest version can be found at: https://github.com/willixix/nagios-plugins/wiki/Draft-Proposal:-Nagios-Plugins-Development-Guidelines-and-Threshold-Syntax-Specification-2.0 On Wed, Aug 21, 2013 at 11:31 AM, Jochen Bern wrote: > On 21.08.2013 17:23, William Leibzon wrote: > > I have requested time at upcoming Nagios conference for 30 minute BoF > > session on this topic and to get feedback on any general features people > > may like to see in all the plugins. They have't got back to me yet (only > > sent email on Friday) but this is not a formal session and so I'd not > > expect an issue with holding it after normal sessions are over. > > > > My own plugins library and several plugins will support the syntax at > > https://github.com/willixix/nagios-plugins/wiki/New-Threshold-Syntax by > > conference time (just committed most of the necessary code yesterday). > > I'm afraid I haven't had much time to read up on the discussion ever > since my first reply on the topic (which I made from a cell phone with > an almost-depleted battery, so I'm sorry if I sounded a bit gruff), so > let me take this opportunity to comment on the version currently on that > page: > > ------- > > I'm missing the possibility to supply *different* labels for the same > (numerical) data as presented in the output vs. in the performance data. > Cases where such a differentiation would be useful, off the top of my head: > -- Output (-> notifications) in local staff's primary language, but > perfdata names shall be in English so as to permit *global* > referencing (say, in a performance data backend system's graph > templates) > [Same goes for things like "Houston Interlink" vs. "Interface 4711", > "upstream"/"downstream" vs. "ingress"/"egress", etc. ad nauseam] > I already before added "label" for re-naming data which is meant to be both for status output and perf data. Per you suggestion I now also add "perf_label" that would allow to re-name only perf data label. I think these uses would be quite irregular, but we can allow for it. > -- Continuity of saved performance data, e.g., what the first version > of the plugin reported as "rx pkts" should now be properly called > "received unicast packets to a local MAC" in the output but still > just "rx_pkts" in the performance data > > Note 1: It would be a possibility to use non-{yes_or_no} values for the > "display" and/or "perf" keywords to achieve this. > What is wrong with "yes" and "no"? > Note 2: There are performance data backends which rely on the *order* > of performance data items, rather than their naming, to have > performance data items produced by the current plugin run > correlated to (hopefully) equivalent items of the previous > runs. Do we want to provide a means, however contrived, to > control that order? > I added "order" keyword. But I think plugins should basically process threshold in the same order they are at the options line. That is at least what my own library does and it allows to specify order too but in different way. > Note 3: Restricting the labels to [A-Za-z0-9_-]* means that we're > actually dropping behind the current perfdata spec (which allows > special chars inside quotes). > That is an oversight in draft text. Full range of ascii symbols should be supported for metric name with quotes used just like in current spec. However when creating custom perfdata label I think restricting set of symbols is better. > > ------- > > rrdtool, as the most common basis for performance data backends, allows > you to provide a non-numerical value 'c so that you can provide > complete data*sets* even in cases where single *values* are unknown / > cannot be determined. PNP4Nagios followed suit and now allows plugins to > return 'U' in the performance data (replacing the number, still allowing > the UOM etc.). I think this should make it into an updated perfdata spec > (which is likely to result from *this* activity sooner rather than later). > I added this into spec proposal now too. In case "absent" keyword is present, the plugin should return U in performance data. > ------- > > Speaking of the UOM, your spec for the "uom" keyword mirrors the current > perfdata specs in only allowing UOMs from a given whitelist. [Yes, I'm > aware that the allowed values for your "uom" keyword do not necessarily > imply restrictions on the UOM spec for plugin output, but bear with me.] > > This approach has, in my opinion, proven to be a failure because it is > virtually impossible to provide an all-encompassing list of UOMs that > may occur in the wild. (Off the top of my head, I have "ppm" from ntpd > drift files, several UOMs for bandwidth, "dBm" for GSM reception level, > "degC" for Temperatures, "RPM" for fans, "V" for Voltages, ...) One > consequence of that is that I do not know a *single* perfdata backend > that would try to split the perfdata UOM back into unit and prefix, and > *that* results in output (graphs) where UOMs like "kB" (as output by > "df", for example) get scaled into "MkB" and similar chimeras. Thus, my > first suggestion: Drop the ever-outdated base unit registry! As far as I know PnP and other backends do clearly differentiate 'c' from anything else which they just treat as custom label or not support at all. It is true that multipliers "k", "m", etc are not currently differentiated and perhaps if we make it clear these are si units they will start to be used. I modified proposal text to specify how custom labels can be supported and how to differentiate SI ranges as part of that. Please everyone go through this. Second, if we want a chance to *ever* get proper automatic UOM scaling > back in working order, we need some sort of hint within the perfdata UOM > string that allows the backends to tell prefix from base unit, candela > from centidays, Ampere- from attohours, etc.. I'm thinking of a > separator character, preferably one that results in a small, unobtrusive > representation if *not* caught before Web-UI etc.. (U+00B7 looks like a > good candidate to me, but I'm not very experienced with charset > conversion and compatibility problems ...) > I added two way to do it. One is with a single one-letter UOM followed by custom unit name and 2nd is by specifying full NIST prefix name followed by '-' and then unit name. > > ------- > > The "prefix" keyword *badly* needs a clarification where it shall have > an effect and where not: > My understanding of original proposal is that PREFIX keyword would only effect how data is scaled when plugin does status line output. UOM keyword is used both for both labeling and scaling of data when output goes into performance data. Perhaps these two should be combined or separated differently. Please let me know. The actual list of valid prefixes and how to create custom UOMs and differentiate them should all be more clear from updated text. -- prefixed to string specified with "uom" keyword > -- causing the relevant number output to be rescaled > -- *from* prefixed *to* prefixless UOM > (i.e., "prefix:k" changes original result "3.14" to "3140", > equivalent to the statement "the number obtained by the plugin > up to output formatting *is in* thousands") > -- *from* prefixless *to* prefixed UOM > (i.e., when the plugin's original output is "4711 foo", > "prefix:k" shall change it to "4.7 kfoo" > -- causing the *thresholds* to be rescaled accordingly > -- again, *from* or *to* the given prefix > and most of this could potentially apply to a number's representation in > the output, the perfdata, or both ... > > Kind regards, > J. Bern > -- > *NEU* - NEC IT-Infrastruktur-Produkte im : > Server--Storage--Virtualisierung--Management SW--Passion for Performance > Jochen Bern, Systemingenieur --- LINworks GmbH > Postfach 100121, 64201 Darmstadt | Robert-Koch-Str. 9, 64331 Weiterstadt > PGP (1024D/4096g) FP = D18B 41B1 16C0 11BA 7F8C DCF7 E1D5 FAF4 444E 1C27 > Tel. +49 6151 9067-231, Zentr. -0, Fax -299 - Amtsg. Darmstadt HRB 85202 > Unternehmenssitz Weiterstadt, Gesch?ftsf?hrer Metin Dogan, Oliver Michel > Thanks again for the feedback, William -------------- next part -------------- An HTML attachment was scrubbed... URL: From palli at ok.is Fri Sep 6 13:17:47 2013 From: palli at ok.is (=?utf-8?Q?P=C3=A1ll_Gu=C3=B0j=C3=B3n_Sigur=C3=B0sson?=) Date: Fri, 06 Sep 2013 11:17:47 -0000 (GMT) Subject: [Nagiosplug-devel] New Threshold Syntax In-Reply-To: Message-ID: I appreciate the effort of putting this on github as it gives better view of the changes. I would personally love to limit the scope of that document to the threshold syntax only, so complexity does not grow out of control. Other topics, like perfdata format do definitely go hand in hand with the threshold syntax, and a new spec for that should be drafted as well (but i prefer seperately to keep the new draft smaller and simpler). There are new ideas in the spec since i implemented it in pynag. (like awarn,acrit,label,perf_label keywords) and some of these sound highly niche to me, and maybe (just maybe) they belong more to individual plugins to implement instead of the being in the threshold spec. In any case i would propose to defer them to a later revision, when the new syntax has been established, and we can see for example if any of the official plugins would benefit from these keyworsd. My two cents, Palli ----- Original Message ----- From: "William Leibzon" To: "Jochen Bern" Cc: "Nagios Plugin Development Mailing List" Sent: Thursday, September 5, 2013 7:33:34 PM Subject: Re: [Nagiosplug-devel] New Threshold Syntax This was very valuable feedback on current proposal spec I really appreciate Jochen going through it. My reply in regards to the feedback is below and I modified proposal text based on the feedback. Latest version can be found at: https://github.com/willixix/nagios-plugins/wiki/Draft-Proposal:-Nagios-Plugins-Development-Guidelines-and-Threshold-Syntax-Specification-2.0 On Wed, Aug 21, 2013 at 11:31 AM, Jochen Bern < Jochen.Bern at linworks.de > wrote: On 21.08.2013 17 :23, William Leibzon wrote: > I have requested time at upcoming Nagios conference for 30 minute BoF > session on this topic and to get feedback on any general features people > may like to see in all the plugins. They have't got back to me yet (only > sent email on Friday) but this is not a formal session and so I'd not > expect an issue with holding it after normal sessions are over. > > My own plugins library and several plugins will support the syntax at > https://github.com/willixix/nagios-plugins/wiki/New-Threshold-Syntax by > conference time (just committed most of the necessary code yesterday). I'm afraid I haven't had much time to read up on the discussion ever since my first reply on the topic (which I made from a cell phone with an almost-depleted battery, so I'm sorry if I sounded a bit gruff), so let me take this opportunity to comment on the version currently on that page: ------- I'm missing the possibility to supply *different* labels for the same (numerical) data as presented in the output vs. in the performance data. Cases where such a differentiation would be useful, off the top of my head: -- Output (-> notifications) in local staff's primary language, but perfdata names shall be in English so as to permit *global* referencing (say, in a performance data backend system's graph templates) [Same goes for things like "Houston Interlink" vs. "Interface 4711", "upstream"/"downstream" vs. "ingress"/"egress", etc. ad nauseam] I already before added "label" for re-naming data which is meant to be both for status output and perf data. Per you suggestion I now also add "perf_label" that would allow to re-name only perf data label. I think these uses would be quite irregular, but we can allow for it. -- Continuity of saved performance data, e.g., what the first version of the plugin reported as "rx pkts" should now be properly called "received unicast packets to a local MAC" in the output but still just "rx_pkts" in the performance data Note 1: It would be a possibility to use non-{yes_or_no} values for the "display" and/or "perf" keywords to achieve this. What is wrong with "yes" and "no"? Note 2: There are performance data backends which rely on the *order* of performance data items, rather than their naming, to have performance data items produced by the current plugin run correlated to (hopefully) equivalent items of the previous runs. Do we want to provide a means, however contrived, to control that order? I added "order" keyword. But I think plugins should basically process threshold in the same order they are at the options line. That is at least what my own library does and it allows to specify order too but in different way. Note 3: Restricting the labels to [A-Za-z0-9_-]* means that we're actually dropping behind the current perfdata spec (which allows special chars inside quotes). That is an oversight in draft text. Full range of ascii symbols should be supported for metric name with quotes used just like in current spec. However when creating custom perfdata label I think restricting set of symbols is better. ------- rrdtool, as the most common basis for performance data backends, allows you to provide a non-numerical value 'c so that you can provide complete data*sets* even in cases where single *values* are unknown / cannot be determined. PNP4Nagios followed suit and now allows plugins to return 'U' in the performance data (replacing the number, still allowing the UOM etc.). I think this should make it into an updated perfdata spec (which is likely to result from *this* activity sooner rather than later). I added this into spec proposal now too. In case "absent" keyword is present, the plugin should return U in performance data. ------- Speaking of the UOM, your spec for the "uom" keyword mirrors the current perfdata specs in only allowing UOMs from a given whitelist. [Yes, I'm aware that the allowed values for your "uom" keyword do not necessarily imply restrictions on the UOM spec for plugin output, but bear with me.] This approach has, in my opinion, proven to be a failure because it is virtually impossible to provide an all-encompassing list of UOMs that may occur in the wild. (Off the top of my head, I have "ppm" from ntpd drift files, several UOMs for bandwidth, "dBm" for GSM reception level, "degC" for Temperatures, "RPM" for fans, "V" for Voltages, ...) One consequence of that is that I do not know a *single* perfdata backend that would try to split the perfdata UOM back into unit and prefix, and *that* results in output (graphs) where UOMs like "kB" (as output by "df", for example) get scaled into "MkB" and similar chimeras. Thus, my first suggestion: Drop the ever-outdated base unit registry! As far as I know PnP and other backends do clearly differentiate 'c' from anything else which they just treat as custom label or not support at all. It is true that multipliers "k", "m", etc are not currently differentiated and perhaps if we make it clear these are si units they will start to be used. I modified proposal text to specify how custom labels can be supported and how to differentiate SI ranges as part of that. Please everyone go through this. Second, if we want a chance to *ever* get proper automatic UOM scaling back in working order, we need some sort of hint within the perfdata UOM string that allows the backends to tell prefix from base unit, candela from centidays, Ampere- from attohours, etc.. I'm thinking of a separator character, preferably one that results in a small, unobtrusive representation if *not* caught before Web-UI etc.. (U+00B7 looks like a good candidate to me, but I'm not very experienced with charset conversion and compatibility problems ...) I added two way to do it. One is with a single one-letter UOM followed by custom unit name and 2nd is by specifying full NIST prefix name followed by '-' and then unit name. ------- The "prefix" keyword *badly* needs a clarification where it shall have an effect and where not: My understanding of original proposal is that PREFIX keyword would only effect how data is scaled when plugin does status line output. UOM keyword is used both for both labeling and scaling of data when output goes into performance data. Perhaps these two should be combined or separated differently. Please let me know. The actual list of valid prefixes and how to create custom UOMs and differentiate them should all be more clear from updated text. -- prefixed to string specified with "uom" keyword -- causing the relevant number output to be rescaled -- *from* prefixed *to* prefixless UOM (i.e., "prefix:k" changes original result "3.14" to "3140", equivalent to the statement "the number obtained by the plugin up to output formatting *is in* thousands") -- *from* prefixless *to* prefixed UOM (i.e., when the plugin's original output is "4711 foo", "prefix:k" shall change it to "4.7 kfoo" -- causing the *thresholds* to be rescaled accordingly -- again, *from* or *to* the given prefix and most of this could potentially apply to a number's representation in the output, the perfdata, or both ... Kind regards, J. Bern -- *NEU* - NEC IT-Infrastruktur-Produkte im < http://www.linworks-shop.de/ >: Server--Storage--Virtualisierung--Management SW--Passion for Performance Jochen Bern, Systemingenieur --- LINworks GmbH < http://www.LINworks.de/ > Postfach 100121, 64201 Darmstadt | Robert-Koch-Str. 9, 64331 Weiterstadt PGP (1024D/4096g) FP = D18B 41B1 16C0 11BA 7F8C DCF7 E1D5 FAF4 444E 1C27 Tel. +49 6151 9067-231 , Zentr. -0, Fax -299 - Amtsg. Darmstadt HRB 85202 Unternehmenssitz Weiterstadt, Gesch?ftsf?hrer Metin Dogan, Oliver Michel Thanks again for the feedback, William ------------------------------------------------------------------------------ Learn the latest--Visual Studio 2012, SharePoint 2013, SQL 2012, more! Discover the easy way to master current and previous Microsoft technologies and advance your career. Get an incredible 1,500+ hours of step-by-step tutorial videos with LearnDevNow. Subscribe today and save! http://pubads.g.doubleclick.net/gampad/clk?id=58041391&iu=/4140/ostg.clktrk _______________________________________________________ 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 julio.pedreira at equifax.es Mon Sep 9 15:57:34 2013 From: julio.pedreira at equifax.es (Julio Pedreira Paz) Date: Mon, 9 Sep 2013 13:57:34 +0000 Subject: [Nagiosplug-devel] RV: Problem with "check_tcp" In-Reply-To: References: Message-ID: Hi, While testing a service with "check_tcp" tool, I ran into a estrange behaviour. Running the same check_tcp command several times resulted in random OK / WARNING results. Reading the service server log, I could assert that the server replied always the same response. When using "-v" with "check_tcp" I realized that WARNING messages were due to check_tcp doing an incomplete read of the service response: $ check_tcp -H venus -p 22225 -s "0003000000D360PXXXAAAABBBBBBBB" -e "00028D360RXXX" -v Using service TCP Port: 22225 flags: 0x2 Send string: 0003000000D360PXXXAAAABBBBBBBB server_expect_count: 1 0: 00028D360RXXX received 5 bytes from host #-raw-recv-------# 00028 #-raw-recv-------# looking for [00028D360RXXX] anywhere in [00028] couldn't find it I know that the server performs a "flush" after the first 5 bytes are ready but it does not close the connection. Its just that the server flushes parts of the response as soon as it has them ready. Tracking this to "check_tcp" source code, I found: /* watch for the expect string */ while ((i = my_recv(buffer, sizeof(buffer))) > 0) { status = realloc(status, len + i + 1); memcpy(&status[len], buffer, i); len += i; /* stop reading if user-forced or data-starved */ if(i < sizeof(buffer) || (maxbytes && len >= maxbytes)) break; If I'm not wrong, the "i < sizeof(buffer)" condition means to leave the reading loop if the bytes received are less than the buffer size, wich makes no sense to me, as other bytes may be awainting in the server, as it was my case. In fact, if I comment that condition and recompile, it works as expected. Is it a bug or just something I'm missing? Thank you! Julio Pedreira Paz Enterprise Architect - IT Architecture & Design Equifax Ib?rica Fijo/Land: +34 91 768 773 (7732) M?vil/Cell: +34 626 721 620 (8732) julio.pedreira at equifax.es www.equifax.es Este mensaje se dirige exclusivamente a su destinatario y puede contener informaci?n privilegiada o confidencial. Si no es vd. el destinatario indicado, queda notificado de que la utilizaci?n, divulgaci?n y/o copia sin autorizaci?n est? prohibida en virtud de la legislaci?n vigente. Si ha recibido este mensaje por error, le rogamos que nos lo comunique inmediatamente por esta misma v?a y proceda a su destrucci?n. Esta mensagem destina-se exclusivamente ao destinat?rio e pode conter informa??o privilegiada e/ou confidencial. Se n?o ? o destinat?rio da mensagem, fique ciente que a utiliza??o, divulga??o e/ou c?pia sem autoriza??o, est? proibida pela lei actualmente em vigor. Se recebeu esta mensagem por engano, pedimos-lhe que no-lo comunique imediatamente por esta mesma via, e proceda ? destrui??o da mesma -------------- next part -------------- An HTML attachment was scrubbed... URL: From holger at cis.fu-berlin.de Mon Sep 9 16:37:07 2013 From: holger at cis.fu-berlin.de (Holger =?iso-8859-1?Q?Wei=DF?=) Date: Mon, 9 Sep 2013 16:37:07 +0200 Subject: [Nagiosplug-devel] RV: Problem with "check_tcp" In-Reply-To: References: Message-ID: <20130909143707.GA282039@zedat.fu-berlin.de> * Julio Pedreira Paz [2013-09-09 13:57]: > I know that the server performs a "flush" after the first 5 bytes are > ready but it does not close the connection. Its just that the server > flushes parts of the response as soon as it has them ready. Tracking > this to "check_tcp" source code, I found: > > /* watch for the expect string */ > while ((i = my_recv(buffer, sizeof(buffer))) > 0) { > status = realloc(status, len + i + 1); > memcpy(&status[len], buffer, i); > len += i; > > /* stop reading if user-forced or data-starved */ > if(i < sizeof(buffer) || (maxbytes && len >= maxbytes)) > break; > > If I'm not wrong, the "i < sizeof(buffer)" condition means to leave the > reading loop if the bytes received are less than the buffer size, wich > makes no sense to me, as other bytes may be awainting in the server, as > it was my case. In fact, if I comment that condition and recompile, it > works as expected. > > Is it a bug or just something I'm missing? It's a bug, the author of those lines obviously assumed that check_tcp would always receive the data in one go. Could you submit a pull request on GitHub (or shall I fix this myself)? Holger From julio.pedreira at equifax.es Tue Sep 10 10:13:29 2013 From: julio.pedreira at equifax.es (Julio Pedreira Paz) Date: Tue, 10 Sep 2013 08:13:29 +0000 Subject: [Nagiosplug-devel] [IE]:Re: RV: Problem with "check_tcp" In-Reply-To: <20130909143707.GA282039@zedat.fu-berlin.de> References: <20130909143707.GA282039@zedat.fu-berlin.de> Message-ID: I've then the pull request. Thank you for your kind support. -----Mensaje original----- De: Holger Wei? [mailto:holger at cis.fu-berlin.de] Enviado el: lunes, 09 de septiembre de 2013 16:37 Para: Nagios Plugins Development Asunto: [IE]:Re: [Nagiosplug-devel] RV: Problem with "check_tcp" * Julio Pedreira Paz [2013-09-09 13:57]: > I know that the server performs a "flush" after the first 5 bytes are > ready but it does not close the connection. Its just that the server > flushes parts of the response as soon as it has them ready. Tracking > this to "check_tcp" source code, I found: > > /* watch for the expect string */ > while ((i = my_recv(buffer, sizeof(buffer))) > 0) { > status = realloc(status, len + i + 1); > memcpy(&status[len], buffer, i); > len += i; > > /* stop reading if user-forced or data-starved */ > if(i < sizeof(buffer) || (maxbytes && len >= maxbytes)) > break; > > If I'm not wrong, the "i < sizeof(buffer)" condition means to leave > the reading loop if the bytes received are less than the buffer size, > wich makes no sense to me, as other bytes may be awainting in the > server, as it was my case. In fact, if I comment that condition and > recompile, it works as expected. > > Is it a bug or just something I'm missing? It's a bug, the author of those lines obviously assumed that check_tcp would always receive the data in one go. Could you submit a pull request on GitHub (or shall I fix this myself)? Holger ------------------------------------------------------------------------------ Learn the latest--Visual Studio 2012, SharePoint 2013, SQL 2012, more! Discover the easy way to master current and previous Microsoft technologies and advance your career. Get an incredible 1,500+ hours of step-by-step tutorial videos with LearnDevNow. Subscribe today and save! http://pubads.g.doubleclick.net/gampad/clk?id=58041391&iu=/4140/ostg.clktrk _______________________________________________________ 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 Este mensaje se dirige exclusivamente a su destinatario y puede contener informaci?n privilegiada o confidencial. Si no es vd. el destinatario indicado, queda notificado de que la utilizaci?n, divulgaci?n y/o copia sin autorizaci?n est? prohibida en virtud de la legislaci?n vigente. Si ha recibido este mensaje por error, le rogamos que nos lo comunique inmediatamente por esta misma v?a y proceda a su destrucci?n. Esta mensagem destina-se exclusivamente ao destinat?rio e pode conter informa??o privilegiada e/ou confidencial. Se n?o ? o destinat?rio da mensagem, fique ciente que a utiliza??o, divulga??o e/ou c?pia sem autoriza??o, est? proibida pela lei actualmente em vigor. Se recebeu esta mensagem por engano, pedimos-lhe que no-lo comunique imediatamente por esta mesma via, e proceda ? destrui??o da mesma From holger at cis.fu-berlin.de Tue Sep 10 12:21:48 2013 From: holger at cis.fu-berlin.de (Holger =?iso-8859-1?Q?Wei=DF?=) Date: Tue, 10 Sep 2013 12:21:48 +0200 Subject: [Nagiosplug-devel] Problem with "check_tcp" In-Reply-To: References: <20130909143707.GA282039@zedat.fu-berlin.de> Message-ID: <20130910102148.GA661870@zedat.fu-berlin.de> * Julio Pedreira Paz [2013-09-10 08:13]: > I've then the pull request. Merged, thanks. Holger From holger at cis.fu-berlin.de Thu Sep 12 22:17:19 2013 From: holger at cis.fu-berlin.de (Holger =?iso-8859-1?Q?Wei=DF?=) Date: Thu, 12 Sep 2013 22:17:19 +0200 Subject: [Nagiosplug-devel] New release planned next week In-Reply-To: <20130902112615.GA977898@zedat.fu-berlin.de> References: <20130902112615.GA977898@zedat.fu-berlin.de> Message-ID: <20130912201719.GT282039@zedat.fu-berlin.de> * Holger Wei? [2013-09-02 13:26]: > As there are quite a few fixes and enhancements? (plus a new plugin!) in > the current Git code, we'd like to cut the 1.5 release next week. In the meantime, a few fixes that might have the potential to break other things have been applied, so we'll delay the release until (at least) next week. If some of you could test the current code?, that would be great! Holger ? http://nagiosplug.sourceforge.net/snapshot/nagios-plugins-master.tar.gz From waja at cyconet.org Thu Sep 12 22:28:54 2013 From: waja at cyconet.org (Jan Wagner) Date: Thu, 12 Sep 2013 22:28:54 +0200 Subject: [Nagiosplug-devel] New release planned next week In-Reply-To: <20130912201719.GT282039@zedat.fu-berlin.de> References: <20130902112615.GA977898@zedat.fu-berlin.de> <20130912201719.GT282039@zedat.fu-berlin.de> Message-ID: <52322406.4060004@cyconet.org> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi there, Am 12.09.2013 22:17, schrieb Holger Wei?: > In the meantime, a few fixes that might have the potential to > break other things have been applied, so we'll delay the release > until (at least) next week. If some of you could test the current > code?, that would be great! In the meantime, we found one .. :-) http://bugs.debian.org/722576 Cheers and keep testing (and indeed, sending push requests fixing this), Jan. - -- Never write mail to , you have been warned! - -----BEGIN GEEK CODE BLOCK----- Version: 3.12 GIT d-- s+: a C+++ UL++++ P+ L+++ E--- W+++ N+++ o++ K++ w--- O M V- PS PE Y++ PGP++ t-- 5 X R tv- b+ DI D+ G++ e++ h---- r+++ y++++ - ------END GEEK CODE BLOCK------ -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) iD8DBQFSMiQG9u6Dud+QFyQRAsJ8AKCrVn8NJQ6MYxXjMepRV6glpMiI5QCfYZ3j eMa9IKePzSFytyBUylE6VvU= =U70S -----END PGP SIGNATURE----- From holger at cis.fu-berlin.de Thu Sep 12 22:57:57 2013 From: holger at cis.fu-berlin.de (Holger =?iso-8859-1?Q?Wei=DF?=) Date: Thu, 12 Sep 2013 22:57:57 +0200 Subject: [Nagiosplug-devel] New release planned next week In-Reply-To: <52322406.4060004@cyconet.org> References: <20130902112615.GA977898@zedat.fu-berlin.de> <20130912201719.GT282039@zedat.fu-berlin.de> <52322406.4060004@cyconet.org> Message-ID: <20130912205757.GU282039@zedat.fu-berlin.de> * Jan Wagner [2013-09-12 22:28]: > Am 12.09.2013 22:17, schrieb Holger Wei?: > > In the meantime, a few fixes that might have the potential to > > break other things have been applied, so we'll delay the release > > until (at least) next week. If some of you could test the current > > code?, that would be great! > > In the meantime, we found one .. :-) > > http://bugs.debian.org/722576 This should be fixed by the latest commits. Thanks, Holger From pavlas.p at gmail.com Fri Sep 13 12:05:32 2013 From: pavlas.p at gmail.com (Petr Pavlas) Date: Fri, 13 Sep 2013 12:05:32 +0200 Subject: [Nagiosplug-devel] error check_mrtgtraf performance data Message-ID: Hello, You can fix the check_mrtgtraf output performance data and unify unit. At this point in = kb/s, out = MB/s, see appendix. Graf is absolutely wrong! Thank you for your response. Regards Petr Pavlas -------------- next part -------------- An HTML attachment was scrubbed... URL: From Jochen.Bern at LINworks.de Mon Sep 16 13:58:54 2013 From: Jochen.Bern at LINworks.de (Jochen Bern) Date: Mon, 16 Sep 2013 13:58:54 +0200 Subject: [Nagiosplug-devel] New release planned next week In-Reply-To: <20130912201719.GT282039@zedat.fu-berlin.de> References: <20130902112615.GA977898@zedat.fu-berlin.de> <20130912201719.GT282039@zedat.fu-berlin.de> Message-ID: <5236F27E.7070307@LINworks.de> On 12.09.2013 22:17, Holger Wei? wrote: > In the meantime, a few fixes that might have the potential to break > other things have been applied, so we'll delay the release until (at > least) next week. If some of you could test the current code?, that > would be great! Sorry for the late reply, haven't gotten around to testing 'til today - and while (still) preparing to test, I found that I had written a mini patch for 4.1.16 (sslutils.c and a proof-of-concept use in check_http.c) so that you can not only force a specific SSL version (SSLv2/SSLv3/TLSv1), but also *exclude* just one of the three instead. (Had to start monitoring a web app doing its own SSL which would fail just for one of the three ... don't ask. :-S ) I haven't checked thoroughly, but I'm under the impression that the corresponding feature has been stable in the OpenSSL libs for *quite* a long time now ... Kind regards, J. Bern -- *NEU* - NEC IT-Infrastruktur-Produkte im : Server--Storage--Virtualisierung--Management SW--Passion for Performance Jochen Bern, Systemingenieur --- LINworks GmbH Postfach 100121, 64201 Darmstadt | Robert-Koch-Str. 9, 64331 Weiterstadt PGP (1024D/4096g) FP = D18B 41B1 16C0 11BA 7F8C DCF7 E1D5 FAF4 444E 1C27 Tel. +49 6151 9067-231, Zentr. -0, Fax -299 - Amtsg. Darmstadt HRB 85202 Unternehmenssitz Weiterstadt, Gesch?ftsf?hrer Metin Dogan, Oliver Michel -------------- next part -------------- A non-text attachment was scrubbed... Name: NegSSLVers.patch Type: text/x-patch Size: 2366 bytes Desc: not available URL: From holger at cis.fu-berlin.de Mon Sep 16 14:54:18 2013 From: holger at cis.fu-berlin.de (Holger =?iso-8859-1?Q?Wei=DF?=) Date: Mon, 16 Sep 2013 14:54:18 +0200 Subject: [Nagiosplug-devel] New release planned next week In-Reply-To: <5236F27E.7070307@LINworks.de> References: <20130902112615.GA977898@zedat.fu-berlin.de> <20130912201719.GT282039@zedat.fu-berlin.de> <5236F27E.7070307@LINworks.de> Message-ID: <20130916125418.GC512861@zedat.fu-berlin.de> * Jochen Bern [2013-09-16 13:58]: > Sorry for the late reply, haven't gotten around to testing 'til today - > and while (still) preparing to test, I found that I had written a mini > patch for 4.1.16 (sslutils.c and a proof-of-concept use in check_http.c) > so that you can not only force a specific SSL version > (SSLv2/SSLv3/TLSv1), but also *exclude* just one of the three instead. With newer OpenSSL releases, the semantics are a bit weirdo: | In order to ensure interoperability SSL_OP_NO_protocolX does not disable | just protocol X, but all protocols above X *if* there are protocols | *below* X still enabled. [ http://www.openssl.org/news/changelog.html ] But I guess I'd rather not try to document this in check_http's --help output. More importantly, I guess other users might want to combine e.g. SSL_OP_NO_SSLv2|SSL_OP_NO_SSLv3, so maybe we should support this? Holger From Jochen.Bern at LINworks.de Tue Sep 17 14:30:48 2013 From: Jochen.Bern at LINworks.de (Jochen Bern) Date: Tue, 17 Sep 2013 14:30:48 +0200 Subject: [Nagiosplug-devel] New release planned next week In-Reply-To: <20130916125418.GC512861@zedat.fu-berlin.de> References: <20130902112615.GA977898@zedat.fu-berlin.de> <20130912201719.GT282039@zedat.fu-berlin.de> <5236F27E.7070307@LINworks.de> <20130916125418.GC512861@zedat.fu-berlin.de> Message-ID: <52384B78.5080709@LINworks.de> On 16.09.2013 14:54, Holger Wei? wrote: > With newer OpenSSL releases, the semantics are a bit weirdo: > | In order to ensure interoperability SSL_OP_NO_protocolX does not disable > | just protocol X, but all protocols above X *if* there are protocols > | *below* X still enabled. > [ http://www.openssl.org/news/changelog.html ] It also means that my quick patch is broken *already*, given a sufficiently recent OpenSSL, as is the basic approach (which is assuming that there are N=3 protocols so that there's no uncharted territory between "1 allowed" and "N-1 allowed"). :-/ > More importantly, I guess other users might want to combine e.g. > SSL_OP_NO_SSLv2|SSL_OP_NO_SSLv3, so maybe we should support this? OR'ing constant values together and passing the result to the OpenSSL calls should be easy enough, it might be more of a challenge to come up with a plugin options syntax that can keep up with future protocol designations. Yesterday, we had SSLv2/SSLv3/TLSv1(.0), today, versions 1.1 and 1.2 of TLS have appeared, and there's nothing to keep tomorrow's contender from going by the name of FOOBARBAZ 0.0.7 or requiring an explicit *en*able instead of a *dis*able, I'm afraid ... (If you meant to have the CLI options say "SSL_OP_NO_SSLv2" etc., just as they're called by OpenSSL itself: That solves the naming problem, of course, but it also maximizes the dependency of the parameters I need to put into the Nagios config from the exact version of the underlying OpenSSL library - which yum etc. can happily change with every update window ...) Regards, J. Bern -- *NEU* - NEC IT-Infrastruktur-Produkte im : Server--Storage--Virtualisierung--Management SW--Passion for Performance Jochen Bern, Systemingenieur --- LINworks GmbH Postfach 100121, 64201 Darmstadt | Robert-Koch-Str. 9, 64331 Weiterstadt PGP (1024D/4096g) FP = D18B 41B1 16C0 11BA 7F8C DCF7 E1D5 FAF4 444E 1C27 Tel. +49 6151 9067-231, Zentr. -0, Fax -299 - Amtsg. Darmstadt HRB 85202 Unternehmenssitz Weiterstadt, Gesch?ftsf?hrer Metin Dogan, Oliver Michel From holger at cis.fu-berlin.de Tue Sep 17 15:18:02 2013 From: holger at cis.fu-berlin.de (Holger =?iso-8859-1?Q?Wei=DF?=) Date: Tue, 17 Sep 2013 15:18:02 +0200 Subject: [Nagiosplug-devel] New release planned next week In-Reply-To: <52384B78.5080709@LINworks.de> References: <20130902112615.GA977898@zedat.fu-berlin.de> <20130912201719.GT282039@zedat.fu-berlin.de> <5236F27E.7070307@LINworks.de> <20130916125418.GC512861@zedat.fu-berlin.de> <52384B78.5080709@LINworks.de> Message-ID: <20130917131802.GK512861@zedat.fu-berlin.de> * Jochen Bern [2013-09-17 14:30]: > On 16.09.2013 14:54, Holger Wei? wrote: > > With newer OpenSSL releases, the semantics are a bit weirdo: > > | In order to ensure interoperability SSL_OP_NO_protocolX does not disable > > | just protocol X, but all protocols above X *if* there are protocols > > | *below* X still enabled. > > [ http://www.openssl.org/news/changelog.html ] > > It also means that my quick patch is broken *already*, given a > sufficiently recent OpenSSL, as is the basic approach (which is assuming > that there are N=3 protocols so that there's no uncharted territory > between "1 allowed" and "N-1 allowed"). :-/ > > > More importantly, I guess other users might want to combine e.g. > > SSL_OP_NO_SSLv2|SSL_OP_NO_SSLv3, so maybe we should support this? > > OR'ing constant values together and passing the result to the OpenSSL > calls should be easy enough, it might be more of a challenge to come up > with a plugin options syntax that can keep up with future protocol > designations. Yesterday, we had SSLv2/SSLv3/TLSv1(.0), today, versions > 1.1 and 1.2 of TLS have appeared, and there's nothing to keep tomorrow's > contender from going by the name of FOOBARBAZ 0.0.7 or requiring an > explicit *en*able instead of a *dis*able, I'm afraid ... I'd suggest exposing the options provided by the current OpenSSL API to check_http users without worrying too much about support for future protocols. I think it's acceptable to have check_http users wait for us adding an SSL_OP_NO_TLSvX knob when version X shows up. If their API changes in weird ways, we'll see whether and how we can support the new options. > (If you meant to have the CLI options say "SSL_OP_NO_SSLv2" etc., just > as they're called by OpenSSL itself: That solves the naming problem, of > course, but it also maximizes the dependency of the parameters I need to > put into the Nagios config from the exact version of the underlying > OpenSSL library - which yum etc. can happily change with every update > window ...) OpenSSL tends to be careful about backwards compatibility, so I think it's highly unlikely that any currently supported SSL_OP_NO_* option will be removed by a Yum update. However, I have no strong preference regarding the command line syntax. Maybe I'd go for a comma-separated list of versions to exclude (e.g., --ssl=-2,-3) to keep this somewhat consistent with the current --ssl syntax. Feel free to post the best solution as a pull request on GitHub (preferably with a NEWS file entry describing the change) :-) Cheers, Holger From julio.pedreira at equifax.es Tue Sep 17 15:28:43 2013 From: julio.pedreira at equifax.es (Julio Pedreira Paz) Date: Tue, 17 Sep 2013 13:28:43 +0000 Subject: [Nagiosplug-devel] Problem with check_http Message-ID: Hi, I have realized that in check_http, when -C option is used ("Minimum number of days a certificate has to be valid"), other checks doesn't take effect. This is not documented, nor checked as an options error, so it seem a strange behaviour to me. An example: check_http -I 172.22.192.20 -H server1 -p 443 -S -e "HTTP/1.1 201 " HTTP CRITICAL - Invalid HTTP response received from host on port 443: HTTP/1.1 200 OK check_http -I 172.22.192.20 -H server1 -p 443 -S -e "HTTP/1.1 201 " -C 100 OK - Certificate will expire on 05/09/2016 12:00. Tracking it to the code (check_http): /* try to connect to the host at the given port number */ if (my_tcp_connect (server_address, server_port, &sd) != STATE_OK) die (STATE_CRITICAL, _("HTTP CRITICAL - Unable to open TCP socket\n")); #ifdef HAVE_SSL if (use_ssl == TRUE) { np_net_ssl_init_with_hostname(sd, (use_sni ? host_name : NULL)); if (check_cert == TRUE) { result = np_net_ssl_check_cert(days_till_exp); np_net_ssl_cleanup(); if (sd) close(sd); return result; } } #endif /* HAVE_SSL */ Is this the expected behaviour? Saludos, J. Julio Pedreira Paz Enterprise Architect - IT Architecture & Design Equifax Ib?rica Fijo/Land: +34 91 768 773 (7732) M?vil/Cell: +34 626 721 620 (8732) julio.pedreira at equifax.es www.equifax.es Este mensaje se dirige exclusivamente a su destinatario y puede contener informaci?n privilegiada o confidencial. Si no es vd. el destinatario indicado, queda notificado de que la utilizaci?n, divulgaci?n y/o copia sin autorizaci?n est? prohibida en virtud de la legislaci?n vigente. Si ha recibido este mensaje por error, le rogamos que nos lo comunique inmediatamente por esta misma v?a y proceda a su destrucci?n. Esta mensagem destina-se exclusivamente ao destinat?rio e pode conter informa??o privilegiada e/ou confidencial. Se n?o ? o destinat?rio da mensagem, fique ciente que a utiliza??o, divulga??o e/ou c?pia sem autoriza??o, est? proibida pela lei actualmente em vigor. Se recebeu esta mensagem por engano, pedimos-lhe que no-lo comunique imediatamente por esta mesma via, e proceda ? destrui??o da mesma -------------- next part -------------- An HTML attachment was scrubbed... URL: From holger at cis.fu-berlin.de Wed Sep 25 12:19:46 2013 From: holger at cis.fu-berlin.de (Holger =?iso-8859-1?Q?Wei=DF?=) Date: Wed, 25 Sep 2013 12:19:46 +0200 Subject: [Nagiosplug-devel] [HEADS UP] Trackers moved to GitHub Message-ID: <20130925101946.GZ512861@zedat.fu-berlin.de> We moved our bug trackers from SourceForge to GitHub. The new tracker is here: https://github.com/nagios-plugins/nagios-plugins/issues All existing items have been migrated, so the open issues will be handled on GitHub. The downside is that the original submitters of SF.net bug reports won't be notified of updates on their items automatically. We'll set up notifications so that the nagiosplug-devel@ list will receive them, though. The SourceForge trackers have been disabled, but they're still accessible (read-only). Many thanks go to Jan Wagner and especially Jan H?rsch for their work on the import script and their help with testing the migration, and to their employer TMT (http://www.tmt.de/) for letting them work on this during work hours. Holger From holger at cis.fu-berlin.de Thu Sep 26 12:08:07 2013 From: holger at cis.fu-berlin.de (Holger =?iso-8859-1?Q?Wei=DF?=) Date: Thu, 26 Sep 2013 12:08:07 +0200 Subject: [Nagiosplug-devel] Project server moved Message-ID: <20130926100807.GC512861@zedat.fu-berlin.de> The server that hosts our web site (plus some Cronjobs and whatnot) has been moved to a new place: * https://www.nagios-plugins.org/ While at it, we also moved the release tarballs, snapshots, and the Nagios Plugin Development Guidelines to the new server (these things were previously hosted by SourceForge): * https://www.nagios-plugins.org/download/ * https://www.nagios-plugins.org/download/snapshot/ * https://www.nagios-plugins.org/doc/guidelines.html We're now using a simple static web site generator? instead of Drupal. Some of the contents? are still missing, but they'll come back soon. If you have any suggestions for the new site, please let us know! Lots of kudos go to Ton Voon and Opsview, who generously hosted the server for many years. These guys are awesome, and their service and support has always been fantastic. Thank you! Holger ? https://bitbucket.org/obensonne/poole ? E.g., the FAQ, the news items, and stuff like the Extra-Opts documentation. From notifications at github.com Sat Sep 28 15:39:19 2013 From: notifications at github.com (waja) Date: Sat, 28 Sep 2013 06:39:19 -0700 Subject: [Nagiosplug-devel] [nagios-plugins] Contributed check module (check_ifstatus_errors) [sf#701055] (#184) In-Reply-To: References: Message-ID: Closed #184. --- Reply to this email directly or view it on GitHub: https://github.com/nagios-plugins/nagios-plugins/issues/184 -------------- next part -------------- An HTML attachment was scrubbed... URL: From notifications at github.com Sat Sep 28 15:39:20 2013 From: notifications at github.com (waja) Date: Sat, 28 Sep 2013 06:39:20 -0700 Subject: [Nagiosplug-devel] [nagios-plugins] Contributed check module (check_ifstatus_errors) [sf#701055] (#184) In-Reply-To: References: Message-ID: I would recommand check_webinject for this. See http://labs.consol.de/lang/en/nagios/check_webinject/ --- Reply to this email directly or view it on GitHub: https://github.com/nagios-plugins/nagios-plugins/issues/184#issuecomment-25298285 -------------- next part -------------- An HTML attachment was scrubbed... URL: From notifications at github.com Sat Sep 28 15:52:13 2013 From: notifications at github.com (waja) Date: Sat, 28 Sep 2013 06:52:13 -0700 Subject: [Nagiosplug-devel] [nagios-plugins] Contributed check module (check_ifstatus_errors) [sf#701055] (#184) In-Reply-To: References: Message-ID: Reopened #184. --- Reply to this email directly or view it on GitHub: https://github.com/nagios-plugins/nagios-plugins/issues/184 -------------- next part -------------- An HTML attachment was scrubbed... URL: From notifications at github.com Sat Sep 28 16:17:38 2013 From: notifications at github.com (waja) Date: Sat, 28 Sep 2013 07:17:38 -0700 Subject: [Nagiosplug-devel] [nagios-plugins] check_http needs an option to allow regex to span newlines [sf#666952] (#99) In-Reply-To: References: Message-ID: Closed #99. --- Reply to this email directly or view it on GitHub: https://github.com/nagios-plugins/nagios-plugins/issues/99 -------------- next part -------------- An HTML attachment was scrubbed... URL: From notifications at github.com Sat Sep 28 16:17:38 2013 From: notifications at github.com (waja) Date: Sat, 28 Sep 2013 07:17:38 -0700 Subject: [Nagiosplug-devel] [nagios-plugins] check_http needs an option to allow regex to span newlines [sf#666952] (#99) In-Reply-To: References: Message-ID: I would recommand check_webinject for this. See http://labs.consol.de/lang/en/nagios/check_webinject/ and http://webinject.org/manual.html#passfailverf --- Reply to this email directly or view it on GitHub: https://github.com/nagios-plugins/nagios-plugins/issues/99#issuecomment-25298858 -------------- next part -------------- An HTML attachment was scrubbed... URL: From notifications at github.com Sat Sep 28 16:36:15 2013 From: notifications at github.com (waja) Date: Sat, 28 Sep 2013 07:36:15 -0700 Subject: [Nagiosplug-devel] [nagios-plugins] arbitrary headers in check_http [sf#731555] (#197) In-Reply-To: References: Message-ID: Looks like this was introduced with f8e826df7fc403362563023328cb18e3cc7767db (Fri Nov 19 00:12:55 2004) and included with 1.4.0 --- Reply to this email directly or view it on GitHub: https://github.com/nagios-plugins/nagios-plugins/issues/197#issuecomment-25299142 -------------- next part -------------- An HTML attachment was scrubbed... URL: From notifications at github.com Sat Sep 28 17:05:30 2013 From: notifications at github.com (waja) Date: Sat, 28 Sep 2013 08:05:30 -0700 Subject: [Nagiosplug-devel] [nagios-plugins] check_ping performance data patch [sf#681627] (#147) In-Reply-To: References: Message-ID: Closed #147. --- Reply to this email directly or view it on GitHub: https://github.com/nagios-plugins/nagios-plugins/issues/147 -------------- next part -------------- An HTML attachment was scrubbed... URL: From notifications at github.com Sat Sep 28 17:05:30 2013 From: notifications at github.com (waja) Date: Sat, 28 Sep 2013 08:05:30 -0700 Subject: [Nagiosplug-devel] [nagios-plugins] check_ping performance data patch [sf#681627] (#147) In-Reply-To: References: Message-ID: This was added with 4d157889e3018119e07bdcc7f48afde1422f7396 and 1.4.12 --- Reply to this email directly or view it on GitHub: https://github.com/nagios-plugins/nagios-plugins/issues/147#issuecomment-25299678 -------------- next part -------------- An HTML attachment was scrubbed... URL: From notifications at github.com Sat Sep 28 17:51:10 2013 From: notifications at github.com (waja) Date: Sat, 28 Sep 2013 08:51:10 -0700 Subject: [Nagiosplug-devel] [nagios-plugins] accept environ for check_by_ssh / others [sf#642352] (#255) In-Reply-To: References: Message-ID: Closed #255. --- Reply to this email directly or view it on GitHub: https://github.com/nagios-plugins/nagios-plugins/issues/255 -------------- next part -------------- An HTML attachment was scrubbed... URL: From notifications at github.com Sat Sep 28 17:51:10 2013 From: notifications at github.com (waja) Date: Sat, 28 Sep 2013 08:51:10 -0700 Subject: [Nagiosplug-devel] [nagios-plugins] accept environ for check_by_ssh / others [sf#642352] (#255) In-Reply-To: References: Message-ID: If this isse is still needed, please create a pull request, that will help us to integrate enhancements. --- Reply to this email directly or view it on GitHub: https://github.com/nagios-plugins/nagios-plugins/issues/255#issuecomment-25300485 -------------- next part -------------- An HTML attachment was scrubbed... URL: From notifications at github.com Sat Sep 28 17:54:20 2013 From: notifications at github.com (waja) Date: Sat, 28 Sep 2013 08:54:20 -0700 Subject: [Nagiosplug-devel] [nagios-plugins] Contributed check module (check_ifstatus_errors) [sf#701055] (#184) In-Reply-To: References: Message-ID: We recommand to add such plugin at https://www.monitoringexchange.org/. --- Reply to this email directly or view it on GitHub: https://github.com/nagios-plugins/nagios-plugins/issues/184#issuecomment-25300546 -------------- next part -------------- An HTML attachment was scrubbed... URL: From notifications at github.com Sat Sep 28 17:54:20 2013 From: notifications at github.com (waja) Date: Sat, 28 Sep 2013 08:54:20 -0700 Subject: [Nagiosplug-devel] [nagios-plugins] Contributed check module (check_ifstatus_errors) [sf#701055] (#184) In-Reply-To: References: Message-ID: Closed #184. --- Reply to this email directly or view it on GitHub: https://github.com/nagios-plugins/nagios-plugins/issues/184 -------------- next part -------------- An HTML attachment was scrubbed... URL: From notifications at github.com Sat Sep 28 18:10:14 2013 From: notifications at github.com (waja) Date: Sat, 28 Sep 2013 09:10:14 -0700 Subject: [Nagiosplug-devel] [nagios-plugins] arbitrary headers in check_http [sf#731555] (#197) In-Reply-To: References: Message-ID: Closed #197. --- Reply to this email directly or view it on GitHub: https://github.com/nagios-plugins/nagios-plugins/issues/197 -------------- next part -------------- An HTML attachment was scrubbed... URL: From notifications at github.com Sat Sep 28 18:11:23 2013 From: notifications at github.com (waja) Date: Sat, 28 Sep 2013 09:11:23 -0700 Subject: [Nagiosplug-devel] [nagios-plugins] cpu and memory checker [sf#583042] (#282) In-Reply-To: References: Message-ID: We recommand to add such plugin at https://www.monitoringexchange.org/ or http://exchange.nagios.org/. --- Reply to this email directly or view it on GitHub: https://github.com/nagios-plugins/nagios-plugins/issues/282#issuecomment-25300887 -------------- next part -------------- An HTML attachment was scrubbed... URL: From notifications at github.com Sat Sep 28 18:11:23 2013 From: notifications at github.com (waja) Date: Sat, 28 Sep 2013 09:11:23 -0700 Subject: [Nagiosplug-devel] [nagios-plugins] cpu and memory checker [sf#583042] (#282) In-Reply-To: References: Message-ID: Closed #282. --- Reply to this email directly or view it on GitHub: https://github.com/nagios-plugins/nagios-plugins/issues/282 -------------- next part -------------- An HTML attachment was scrubbed... URL: From notifications at github.com Sat Sep 28 18:12:47 2013 From: notifications at github.com (waja) Date: Sat, 28 Sep 2013 09:12:47 -0700 Subject: [Nagiosplug-devel] [nagios-plugins] add check_snmp_mgeups.pl [sf#1297601] (#482) In-Reply-To: References: Message-ID: We recommand to add such plugin at https://www.monitoringexchange.org/ or http://exchange.nagios.org/. --- Reply to this email directly or view it on GitHub: https://github.com/nagios-plugins/nagios-plugins/issues/482#issuecomment-25300915 -------------- next part -------------- An HTML attachment was scrubbed... URL: From notifications at github.com Sat Sep 28 18:12:48 2013 From: notifications at github.com (waja) Date: Sat, 28 Sep 2013 09:12:48 -0700 Subject: [Nagiosplug-devel] [nagios-plugins] add check_snmp_mgeups.pl [sf#1297601] (#482) In-Reply-To: References: Message-ID: Closed #482. --- Reply to this email directly or view it on GitHub: https://github.com/nagios-plugins/nagios-plugins/issues/482 -------------- next part -------------- An HTML attachment was scrubbed... URL: From notifications at github.com Sat Sep 28 18:18:04 2013 From: notifications at github.com (waja) Date: Sat, 28 Sep 2013 09:18:04 -0700 Subject: [Nagiosplug-devel] [nagios-plugins] check_ram plugin (based on check_swap) [sf#1847879] (#749) In-Reply-To: References: Message-ID: We recommand to add such plugin at https://www.monitoringexchange.org/ or http://exchange.nagios.org/. --- Reply to this email directly or view it on GitHub: https://github.com/nagios-plugins/nagios-plugins/issues/749#issuecomment-25301024 -------------- next part -------------- An HTML attachment was scrubbed... URL: From notifications at github.com Sat Sep 28 18:18:04 2013 From: notifications at github.com (waja) Date: Sat, 28 Sep 2013 09:18:04 -0700 Subject: [Nagiosplug-devel] [nagios-plugins] check_ram plugin (based on check_swap) [sf#1847879] (#749) In-Reply-To: References: Message-ID: Closed #749. --- Reply to this email directly or view it on GitHub: https://github.com/nagios-plugins/nagios-plugins/issues/749 -------------- next part -------------- An HTML attachment was scrubbed... URL: From notifications at github.com Sat Sep 28 18:20:21 2013 From: notifications at github.com (waja) Date: Sat, 28 Sep 2013 09:20:21 -0700 Subject: [Nagiosplug-devel] [nagios-plugins] tls support for check_smtp [sf#634393] (#87) In-Reply-To: References: Message-ID: Closed #87. --- Reply to this email directly or view it on GitHub: https://github.com/nagios-plugins/nagios-plugins/issues/87 -------------- next part -------------- An HTML attachment was scrubbed... URL: From notifications at github.com Sat Sep 28 18:20:21 2013 From: notifications at github.com (waja) Date: Sat, 28 Sep 2013 09:20:21 -0700 Subject: [Nagiosplug-devel] [nagios-plugins] tls support for check_smtp [sf#634393] (#87) In-Reply-To: References: Message-ID: If this isse is still needed, please create a pull request, that will help us to integrate enhancements. --- Reply to this email directly or view it on GitHub: https://github.com/nagios-plugins/nagios-plugins/issues/87#issuecomment-25301074 -------------- next part -------------- An HTML attachment was scrubbed... URL: From notifications at github.com Sat Sep 28 18:23:13 2013 From: notifications at github.com (waja) Date: Sat, 28 Sep 2013 09:23:13 -0700 Subject: [Nagiosplug-devel] [nagios-plugins] utils.pm patch to read Nagios config file [sf#672841] (#129) In-Reply-To: References: Message-ID: Closed #129. --- Reply to this email directly or view it on GitHub: https://github.com/nagios-plugins/nagios-plugins/issues/129 -------------- next part -------------- An HTML attachment was scrubbed... URL: From notifications at github.com Sat Sep 28 18:23:13 2013 From: notifications at github.com (waja) Date: Sat, 28 Sep 2013 09:23:13 -0700 Subject: [Nagiosplug-devel] [nagios-plugins] utils.pm patch to read Nagios config file [sf#672841] (#129) In-Reply-To: References: Message-ID: If this issue is still needed, please create a pull request, that will help us to integrate enhancements. --- Reply to this email directly or view it on GitHub: https://github.com/nagios-plugins/nagios-plugins/issues/129#issuecomment-25301131 -------------- next part -------------- An HTML attachment was scrubbed... URL: From notifications at github.com Sat Sep 28 18:23:56 2013 From: notifications at github.com (waja) Date: Sat, 28 Sep 2013 09:23:56 -0700 Subject: [Nagiosplug-devel] [nagios-plugins] check_tcp w/ expect string doesn't work w/ nulls in data [sf#1348595] (#495) In-Reply-To: References: Message-ID: If this issue is still needed, please create a pull request, that will help us to integrate enhancements. --- Reply to this email directly or view it on GitHub: https://github.com/nagios-plugins/nagios-plugins/issues/495#issuecomment-25301142 -------------- next part -------------- An HTML attachment was scrubbed... URL: From notifications at github.com Sat Sep 28 18:23:56 2013 From: notifications at github.com (waja) Date: Sat, 28 Sep 2013 09:23:56 -0700 Subject: [Nagiosplug-devel] [nagios-plugins] check_tcp w/ expect string doesn't work w/ nulls in data [sf#1348595] (#495) In-Reply-To: References: Message-ID: Closed #495. --- Reply to this email directly or view it on GitHub: https://github.com/nagios-plugins/nagios-plugins/issues/495 -------------- next part -------------- An HTML attachment was scrubbed... URL: From notifications at github.com Sat Sep 28 18:29:12 2013 From: notifications at github.com (waja) Date: Sat, 28 Sep 2013 09:29:12 -0700 Subject: [Nagiosplug-devel] [nagios-plugins] subst problem [sf#1341531] (#503) In-Reply-To: References: Message-ID: Closed #503. --- Reply to this email directly or view it on GitHub: https://github.com/nagios-plugins/nagios-plugins/issues/503 -------------- next part -------------- An HTML attachment was scrubbed... URL: From notifications at github.com Sat Sep 28 18:29:12 2013 From: notifications at github.com (waja) Date: Sat, 28 Sep 2013 09:29:12 -0700 Subject: [Nagiosplug-devel] [nagios-plugins] subst problem [sf#1341531] (#503) In-Reply-To: References: Message-ID: If this issue is still needed, please create a pull request, that will help us to integrate enhancements. --- Reply to this email directly or view it on GitHub: https://github.com/nagios-plugins/nagios-plugins/issues/503#issuecomment-25301270 -------------- next part -------------- An HTML attachment was scrubbed... URL: From notifications at github.com Sat Sep 28 18:30:41 2013 From: notifications at github.com (waja) Date: Sat, 28 Sep 2013 09:30:41 -0700 Subject: [Nagiosplug-devel] [nagios-plugins] need common name flag for check_ldaps [sf#1466432] (#548) In-Reply-To: References: Message-ID: Closed #548. --- Reply to this email directly or view it on GitHub: https://github.com/nagios-plugins/nagios-plugins/issues/548 -------------- next part -------------- An HTML attachment was scrubbed... URL: From notifications at github.com Sat Sep 28 18:30:41 2013 From: notifications at github.com (waja) Date: Sat, 28 Sep 2013 09:30:41 -0700 Subject: [Nagiosplug-devel] [nagios-plugins] need common name flag for check_ldaps [sf#1466432] (#548) In-Reply-To: References: Message-ID: If this issue is still needed, please create a pull request, that will help us to integrate enhancements. --- Reply to this email directly or view it on GitHub: https://github.com/nagios-plugins/nagios-plugins/issues/548#issuecomment-25301314 -------------- next part -------------- An HTML attachment was scrubbed... URL: From notifications at github.com Sat Sep 28 18:31:06 2013 From: notifications at github.com (waja) Date: Sat, 28 Sep 2013 09:31:06 -0700 Subject: [Nagiosplug-devel] [nagios-plugins] Support HP-UX Ansi C [sf#1481689] (#552) In-Reply-To: References: Message-ID: If this issue is still needed, please create a pull request, that will help us to integrate enhancements. --- Reply to this email directly or view it on GitHub: https://github.com/nagios-plugins/nagios-plugins/issues/552#issuecomment-25301328 -------------- next part -------------- An HTML attachment was scrubbed... URL: From notifications at github.com Sat Sep 28 18:31:06 2013 From: notifications at github.com (waja) Date: Sat, 28 Sep 2013 09:31:06 -0700 Subject: [Nagiosplug-devel] [nagios-plugins] Support HP-UX Ansi C [sf#1481689] (#552) In-Reply-To: References: Message-ID: Closed #552. --- Reply to this email directly or view it on GitHub: https://github.com/nagios-plugins/nagios-plugins/issues/552 -------------- next part -------------- An HTML attachment was scrubbed... URL: From notifications at github.com Sat Sep 28 18:31:34 2013 From: notifications at github.com (waja) Date: Sat, 28 Sep 2013 09:31:34 -0700 Subject: [Nagiosplug-devel] [nagios-plugins] check_mailq and clientmqueue checks [sf#1502024] (#571) In-Reply-To: References: Message-ID: If this issue is still needed, please create a pull request, that will help us to integrate enhancements. --- Reply to this email directly or view it on GitHub: https://github.com/nagios-plugins/nagios-plugins/issues/571#issuecomment-25301345 -------------- next part -------------- An HTML attachment was scrubbed... URL: From notifications at github.com Sat Sep 28 18:31:34 2013 From: notifications at github.com (waja) Date: Sat, 28 Sep 2013 09:31:34 -0700 Subject: [Nagiosplug-devel] [nagios-plugins] check_mailq and clientmqueue checks [sf#1502024] (#571) In-Reply-To: References: Message-ID: Closed #571. --- Reply to this email directly or view it on GitHub: https://github.com/nagios-plugins/nagios-plugins/issues/571 -------------- next part -------------- An HTML attachment was scrubbed... URL: From notifications at github.com Sat Sep 28 18:35:20 2013 From: notifications at github.com (waja) Date: Sat, 28 Sep 2013 09:35:20 -0700 Subject: [Nagiosplug-devel] [nagios-plugins] check_mysql.c improvements to support MySQL5 [sf#1509752] (#574) In-Reply-To: References: Message-ID: The actual check_mysql works without issues even with MySQL 5.5. If this issue is still needed, please create a pull request, that will help us to integrate enhancements. --- Reply to this email directly or view it on GitHub: https://github.com/nagios-plugins/nagios-plugins/issues/574#issuecomment-25301573 -------------- next part -------------- An HTML attachment was scrubbed... URL: From notifications at github.com Sat Sep 28 18:35:22 2013 From: notifications at github.com (waja) Date: Sat, 28 Sep 2013 09:35:22 -0700 Subject: [Nagiosplug-devel] [nagios-plugins] check_mysql.c improvements to support MySQL5 [sf#1509752] (#574) In-Reply-To: References: Message-ID: Closed #574. --- Reply to this email directly or view it on GitHub: https://github.com/nagios-plugins/nagios-plugins/issues/574 -------------- next part -------------- An HTML attachment was scrubbed... URL: From notifications at github.com Sat Sep 28 18:36:06 2013 From: notifications at github.com (waja) Date: Sat, 28 Sep 2013 09:36:06 -0700 Subject: [Nagiosplug-devel] [nagios-plugins] check_disk not only for free space, but also used space [sf#1512436] (#576) In-Reply-To: References: Message-ID: Closed #576. --- Reply to this email directly or view it on GitHub: https://github.com/nagios-plugins/nagios-plugins/issues/576 -------------- next part -------------- An HTML attachment was scrubbed... URL: From notifications at github.com Sat Sep 28 18:36:07 2013 From: notifications at github.com (waja) Date: Sat, 28 Sep 2013 09:36:07 -0700 Subject: [Nagiosplug-devel] [nagios-plugins] check_disk not only for free space, but also used space [sf#1512436] (#576) In-Reply-To: References: Message-ID: If this issue is still needed, please create a pull request, that will help us to integrate enhancements. --- Reply to this email directly or view it on GitHub: https://github.com/nagios-plugins/nagios-plugins/issues/576#issuecomment-25301591 -------------- next part -------------- An HTML attachment was scrubbed... URL: From notifications at github.com Sat Sep 28 18:39:14 2013 From: notifications at github.com (waja) Date: Sat, 28 Sep 2013 09:39:14 -0700 Subject: [Nagiosplug-devel] [nagios-plugins] check_pgsql.c check plugin for Postgres DB [sf#1516150] (#579) In-Reply-To: References: Message-ID: Closed #579. --- Reply to this email directly or view it on GitHub: https://github.com/nagios-plugins/nagios-plugins/issues/579 -------------- next part -------------- An HTML attachment was scrubbed... URL: From notifications at github.com Sat Sep 28 18:39:14 2013 From: notifications at github.com (waja) Date: Sat, 28 Sep 2013 09:39:14 -0700 Subject: [Nagiosplug-devel] [nagios-plugins] check_pgsql.c check plugin for Postgres DB [sf#1516150] (#579) In-Reply-To: References: Message-ID: We have a check_pgsql since over 12 years. If this issue is still needed, please create a pull request, that will help us to integrate enhancements. --- Reply to this email directly or view it on GitHub: https://github.com/nagios-plugins/nagios-plugins/issues/579#issuecomment-25301653 -------------- next part -------------- An HTML attachment was scrubbed... URL: From notifications at github.com Sat Sep 28 21:03:59 2013 From: notifications at github.com (waja) Date: Sat, 28 Sep 2013 12:03:59 -0700 Subject: [Nagiosplug-devel] [nagios-plugins] scaling for check_nt [sf#1671141] (#657) In-Reply-To: References: Message-ID: If this issue is still needed, please create a pull request, that will help us to integrate enhancements. --- Reply to this email directly or view it on GitHub: https://github.com/nagios-plugins/nagios-plugins/issues/657#issuecomment-25306273 -------------- next part -------------- An HTML attachment was scrubbed... URL: From notifications at github.com Sat Sep 28 21:03:59 2013 From: notifications at github.com (waja) Date: Sat, 28 Sep 2013 12:03:59 -0700 Subject: [Nagiosplug-devel] [nagios-plugins] scaling for check_nt [sf#1671141] (#657) In-Reply-To: References: Message-ID: Closed #657. --- Reply to this email directly or view it on GitHub: https://github.com/nagios-plugins/nagios-plugins/issues/657 -------------- next part -------------- An HTML attachment was scrubbed... URL: From notifications at github.com Sat Sep 28 21:09:05 2013 From: notifications at github.com (waja) Date: Sat, 28 Sep 2013 12:09:05 -0700 Subject: [Nagiosplug-devel] [nagios-plugins] check_http is missing http Accept: header [sf#1652471] (#685) In-Reply-To: References: Message-ID: Looks like this was introduced with f8e826d (Fri Nov 19 00:12:55 2004) and included with 1.4.0 --- Reply to this email directly or view it on GitHub: https://github.com/nagios-plugins/nagios-plugins/issues/685#issuecomment-25306387 -------------- next part -------------- An HTML attachment was scrubbed... URL: From notifications at github.com Sat Sep 28 21:09:06 2013 From: notifications at github.com (waja) Date: Sat, 28 Sep 2013 12:09:06 -0700 Subject: [Nagiosplug-devel] [nagios-plugins] check_http is missing http Accept: header [sf#1652471] (#685) In-Reply-To: References: Message-ID: Closed #685. --- Reply to this email directly or view it on GitHub: https://github.com/nagios-plugins/nagios-plugins/issues/685 -------------- next part -------------- An HTML attachment was scrubbed... URL: From notifications at github.com Sat Sep 28 21:21:56 2013 From: notifications at github.com (waja) Date: Sat, 28 Sep 2013 12:21:56 -0700 Subject: [Nagiosplug-devel] [nagios-plugins] NTP limit number of hosts [sf#1727485] (#692) In-Reply-To: References: Message-ID: Checking again this seems with the actual plugin no problem. # host 0.uk.pool.ntp.org 0.uk.pool.ntp.org has address 194.1.151.226 0.uk.pool.ntp.org has address 143.210.16.201 0.uk.pool.ntp.org has address 178.79.177.120 0.uk.pool.ntp.org has address 178.79.144.248 # /usr/lib/nagios/plugins/check_ntp -H 0.uk.pool.ntp.org NTP OK: Offset -0,008026952797 secs|offset=-0,008027s;60,000000;120,000000; If this issue is still needed, please explain why and create a pull request, that will help us to integrate enhancements. --- Reply to this email directly or view it on GitHub: https://github.com/nagios-plugins/nagios-plugins/issues/692#issuecomment-25306651 -------------- next part -------------- An HTML attachment was scrubbed... URL: From notifications at github.com Sat Sep 28 21:21:56 2013 From: notifications at github.com (waja) Date: Sat, 28 Sep 2013 12:21:56 -0700 Subject: [Nagiosplug-devel] [nagios-plugins] NTP limit number of hosts [sf#1727485] (#692) In-Reply-To: References: Message-ID: Closed #692. --- Reply to this email directly or view it on GitHub: https://github.com/nagios-plugins/nagios-plugins/issues/692 -------------- next part -------------- An HTML attachment was scrubbed... URL: From notifications at github.com Sat Sep 28 21:29:07 2013 From: notifications at github.com (waja) Date: Sat, 28 Sep 2013 12:29:07 -0700 Subject: [Nagiosplug-devel] [nagios-plugins] check_oracle check for valid login [sf#1838837] (#744) In-Reply-To: References: Message-ID: Closed #744. --- Reply to this email directly or view it on GitHub: https://github.com/nagios-plugins/nagios-plugins/issues/744 -------------- next part -------------- An HTML attachment was scrubbed... URL: From notifications at github.com Sat Sep 28 21:29:06 2013 From: notifications at github.com (waja) Date: Sat, 28 Sep 2013 12:29:06 -0700 Subject: [Nagiosplug-devel] [nagios-plugins] check_oracle check for valid login [sf#1838837] (#744) In-Reply-To: References: Message-ID: If this issue is still needed, please create a pull request, that will help us to integrate enhancements. --- Reply to this email directly or view it on GitHub: https://github.com/nagios-plugins/nagios-plugins/issues/744#issuecomment-25306790 -------------- next part -------------- An HTML attachment was scrubbed... URL: From notifications at github.com Sat Sep 28 21:34:55 2013 From: notifications at github.com (waja) Date: Sat, 28 Sep 2013 12:34:55 -0700 Subject: [Nagiosplug-devel] [nagios-plugins] check_dns should use c library functions, not nslookup binar [sf#2015822] (#811) In-Reply-To: References: Message-ID: Closed #811. --- Reply to this email directly or view it on GitHub: https://github.com/nagios-plugins/nagios-plugins/issues/811 -------------- next part -------------- An HTML attachment was scrubbed... URL: From notifications at github.com Sat Sep 28 21:34:55 2013 From: notifications at github.com (waja) Date: Sat, 28 Sep 2013 12:34:55 -0700 Subject: [Nagiosplug-devel] [nagios-plugins] check_dns should use c library functions, not nslookup binar [sf#2015822] (#811) In-Reply-To: References: Message-ID: If this issue is still needed, please create a pull request, that will help us to integrate enhancements. --- Reply to this email directly or view it on GitHub: https://github.com/nagios-plugins/nagios-plugins/issues/811#issuecomment-25306898 -------------- next part -------------- An HTML attachment was scrubbed... URL: From notifications at github.com Sat Sep 28 21:36:02 2013 From: notifications at github.com (waja) Date: Sat, 28 Sep 2013 12:36:02 -0700 Subject: [Nagiosplug-devel] [nagios-plugins] "Thresholds" syntax to support enumerated values as well [sf#2100684] (#819) In-Reply-To: References: Message-ID: If this issue is still needed, please create a pull request, that will help us to integrate enhancements. --- Reply to this email directly or view it on GitHub: https://github.com/nagios-plugins/nagios-plugins/issues/819#issuecomment-25306919 -------------- next part -------------- An HTML attachment was scrubbed... URL: From notifications at github.com Sat Sep 28 21:36:01 2013 From: notifications at github.com (waja) Date: Sat, 28 Sep 2013 12:36:01 -0700 Subject: [Nagiosplug-devel] [nagios-plugins] "Thresholds" syntax to support enumerated values as well [sf#2100684] (#819) In-Reply-To: References: Message-ID: Closed #819. --- Reply to this email directly or view it on GitHub: https://github.com/nagios-plugins/nagios-plugins/issues/819 -------------- next part -------------- An HTML attachment was scrubbed... URL: From notifications at github.com Sat Sep 28 21:36:45 2013 From: notifications at github.com (waja) Date: Sat, 28 Sep 2013 12:36:45 -0700 Subject: [Nagiosplug-devel] [nagios-plugins] check_versions via NRPE [sf#2542428] (#843) In-Reply-To: References: Message-ID: Closed #843. --- Reply to this email directly or view it on GitHub: https://github.com/nagios-plugins/nagios-plugins/issues/843 -------------- next part -------------- An HTML attachment was scrubbed... URL: From notifications at github.com Sat Sep 28 21:36:45 2013 From: notifications at github.com (waja) Date: Sat, 28 Sep 2013 12:36:45 -0700 Subject: [Nagiosplug-devel] [nagios-plugins] check_versions via NRPE [sf#2542428] (#843) In-Reply-To: References: Message-ID: We recommand to add such plugin at https://www.monitoringexchange.org/ or http://exchange.nagios.org/. --- Reply to this email directly or view it on GitHub: https://github.com/nagios-plugins/nagios-plugins/issues/843#issuecomment-25306934 -------------- next part -------------- An HTML attachment was scrubbed... URL: From notifications at github.com Sat Sep 28 21:46:22 2013 From: notifications at github.com (waja) Date: Sat, 28 Sep 2013 12:46:22 -0700 Subject: [Nagiosplug-devel] [nagios-plugins] check_procs - return critical error when 0 procs [sf#2906507] (#920) In-Reply-To: References: Message-ID: Closed #920. --- Reply to this email directly or view it on GitHub: https://github.com/nagios-plugins/nagios-plugins/issues/920 -------------- next part -------------- An HTML attachment was scrubbed... URL: From notifications at github.com Sat Sep 28 21:46:26 2013 From: notifications at github.com (waja) Date: Sat, 28 Sep 2013 12:46:26 -0700 Subject: [Nagiosplug-devel] [nagios-plugins] check_procs - return critical error when 0 procs [sf#2906507] (#920) In-Reply-To: References: Message-ID: This should be possible with the range support of -w and -c. If this issue is still needed, please create a pull request, that will help us to integrate enhancements. --- Reply to this email directly or view it on GitHub: https://github.com/nagios-plugins/nagios-plugins/issues/920#issuecomment-25307103 -------------- next part -------------- An HTML attachment was scrubbed... URL: From notifications at github.com Sat Sep 28 21:52:50 2013 From: notifications at github.com (waja) Date: Sat, 28 Sep 2013 12:52:50 -0700 Subject: [Nagiosplug-devel] [nagios-plugins] check_snmp - add unit in performance data [sf#2951604] (#928) In-Reply-To: References: Message-ID: If this issue is still needed, please create a pull request, that will help us to integrate enhancements. --- Reply to this email directly or view it on GitHub: https://github.com/nagios-plugins/nagios-plugins/issues/928#issuecomment-25307211 -------------- next part -------------- An HTML attachment was scrubbed... URL: From notifications at github.com Sat Sep 28 21:52:50 2013 From: notifications at github.com (waja) Date: Sat, 28 Sep 2013 12:52:50 -0700 Subject: [Nagiosplug-devel] [nagios-plugins] check_snmp - add unit in performance data [sf#2951604] (#928) In-Reply-To: References: Message-ID: Closed #928. --- Reply to this email directly or view it on GitHub: https://github.com/nagios-plugins/nagios-plugins/issues/928 -------------- next part -------------- An HTML attachment was scrubbed... URL: From notifications at github.com Sat Sep 28 21:58:37 2013 From: notifications at github.com (waja) Date: Sat, 28 Sep 2013 12:58:37 -0700 Subject: [Nagiosplug-devel] [nagios-plugins] check_procs and Solaris Zones [sf#2998166] (#959) In-Reply-To: References: Message-ID: If this issue is still needed, please create a pull request, that will help us to integrate enhancements. --- Reply to this email directly or view it on GitHub: https://github.com/nagios-plugins/nagios-plugins/issues/959#issuecomment-25307296 -------------- next part -------------- An HTML attachment was scrubbed... URL: From notifications at github.com Sat Sep 28 21:58:37 2013 From: notifications at github.com (waja) Date: Sat, 28 Sep 2013 12:58:37 -0700 Subject: [Nagiosplug-devel] [nagios-plugins] check_procs and Solaris Zones [sf#2998166] (#959) In-Reply-To: References: Message-ID: Closed #959. --- Reply to this email directly or view it on GitHub: https://github.com/nagios-plugins/nagios-plugins/issues/959 -------------- next part -------------- An HTML attachment was scrubbed... URL: From notifications at github.com Sat Sep 28 22:08:44 2013 From: notifications at github.com (waja) Date: Sat, 28 Sep 2013 13:08:44 -0700 Subject: [Nagiosplug-devel] [nagios-plugins] check_hpjd port option (#1160) Message-ID: Closing github issue #973 You can merge this Pull Request by running: git pull https://github.com/waja/nagios-plugins github973 Or you can view, comment on it, or merge it online at: https://github.com/nagios-plugins/nagios-plugins/pull/1160 -- Commit Summary -- * check_hpjd port option -- File Changes -- M plugins/check_hpjd.c (10) -- Patch Links -- https://github.com/nagios-plugins/nagios-plugins/pull/1160.patch https://github.com/nagios-plugins/nagios-plugins/pull/1160.diff -------------- next part -------------- An HTML attachment was scrubbed... URL: From notifications at github.com Sat Sep 28 22:09:47 2013 From: notifications at github.com (waja) Date: Sat, 28 Sep 2013 13:09:47 -0700 Subject: [Nagiosplug-devel] [nagios-plugins] check_hpjd port option [sf#3123438] (#973) In-Reply-To: References: Message-ID: Created pull request #1160 for this. --- Reply to this email directly or view it on GitHub: https://github.com/nagios-plugins/nagios-plugins/issues/973#issuecomment-25307482 -------------- next part -------------- An HTML attachment was scrubbed... URL: From notifications at github.com Sat Sep 28 22:10:43 2013 From: notifications at github.com (waja) Date: Sat, 28 Sep 2013 13:10:43 -0700 Subject: [Nagiosplug-devel] [nagios-plugins] check_icmp: option number of decimal places specification [sf#3164725] (#983) In-Reply-To: References: Message-ID: Closed #983. --- Reply to this email directly or view it on GitHub: https://github.com/nagios-plugins/nagios-plugins/issues/983 -------------- next part -------------- An HTML attachment was scrubbed... URL: From notifications at github.com Sat Sep 28 22:10:43 2013 From: notifications at github.com (waja) Date: Sat, 28 Sep 2013 13:10:43 -0700 Subject: [Nagiosplug-devel] [nagios-plugins] check_icmp: option number of decimal places specification [sf#3164725] (#983) In-Reply-To: References: Message-ID: If this issue is still needed, please create a pull request, that will help us to integrate enhancements. --- Reply to this email directly or view it on GitHub: https://github.com/nagios-plugins/nagios-plugins/issues/983#issuecomment-25307504 -------------- next part -------------- An HTML attachment was scrubbed... URL: From notifications at github.com Sat Sep 28 23:50:57 2013 From: notifications at github.com (waja) Date: Sat, 28 Sep 2013 14:50:57 -0700 Subject: [Nagiosplug-devel] [nagios-plugins] check_by_ssh -H hostname:port [sf#3518544] (#1045) In-Reply-To: References: Message-ID: Closed #1045. --- Reply to this email directly or view it on GitHub: https://github.com/nagios-plugins/nagios-plugins/issues/1045 -------------- next part -------------- An HTML attachment was scrubbed... URL: From notifications at github.com Sat Sep 28 23:50:57 2013 From: notifications at github.com (waja) Date: Sat, 28 Sep 2013 14:50:57 -0700 Subject: [Nagiosplug-devel] [nagios-plugins] check_by_ssh -H hostname:port [sf#3518544] (#1045) In-Reply-To: References: Message-ID: If this issue is still needed, please create a pull request, that will help us to integrate enhancements. --- Reply to this email directly or view it on GitHub: https://github.com/nagios-plugins/nagios-plugins/issues/1045#issuecomment-25309207 -------------- next part -------------- An HTML attachment was scrubbed... URL: From notifications at github.com Sat Sep 28 23:56:06 2013 From: notifications at github.com (waja) Date: Sat, 28 Sep 2013 14:56:06 -0700 Subject: [Nagiosplug-devel] [nagios-plugins] check_dig should have -4 and -6 options [sf#3586320] (#1107) In-Reply-To: References: Message-ID: Closed #1107. --- Reply to this email directly or view it on GitHub: https://github.com/nagios-plugins/nagios-plugins/issues/1107 -------------- next part -------------- An HTML attachment was scrubbed... URL: From notifications at github.com Sat Sep 28 23:56:07 2013 From: notifications at github.com (waja) Date: Sat, 28 Sep 2013 14:56:07 -0700 Subject: [Nagiosplug-devel] [nagios-plugins] check_dig should have -4 and -6 options [sf#3586320] (#1107) In-Reply-To: References: Message-ID: This was fixed with 261ad186706422af00ec7e67dc128a99c4603b8c --- Reply to this email directly or view it on GitHub: https://github.com/nagios-plugins/nagios-plugins/issues/1107#issuecomment-25309451 -------------- next part -------------- An HTML attachment was scrubbed... URL: From notifications at github.com Sun Sep 29 00:02:15 2013 From: notifications at github.com (waja) Date: Sat, 28 Sep 2013 15:02:15 -0700 Subject: [Nagiosplug-devel] [nagios-plugins] check_http -M should also look for Age header [sf#3593130] (#1120) In-Reply-To: References: Message-ID: If this issue is still needed, please create a pull request, that will help us to integrate enhancements. --- Reply to this email directly or view it on GitHub: https://github.com/nagios-plugins/nagios-plugins/issues/1120#issuecomment-25309551 -------------- next part -------------- An HTML attachment was scrubbed... URL: From notifications at github.com Sun Sep 29 00:02:15 2013 From: notifications at github.com (waja) Date: Sat, 28 Sep 2013 15:02:15 -0700 Subject: [Nagiosplug-devel] [nagios-plugins] check_http -M should also look for Age header [sf#3593130] (#1120) In-Reply-To: References: Message-ID: Closed #1120. --- Reply to this email directly or view it on GitHub: https://github.com/nagios-plugins/nagios-plugins/issues/1120 -------------- next part -------------- An HTML attachment was scrubbed... URL: From notifications at github.com Sun Sep 29 00:11:21 2013 From: notifications at github.com (waja) Date: Sat, 28 Sep 2013 15:11:21 -0700 Subject: [Nagiosplug-devel] [nagios-plugins] NTLM auth support for check_http [sf#3613438] (#1141) In-Reply-To: References: Message-ID: Closed #1141. --- Reply to this email directly or view it on GitHub: https://github.com/nagios-plugins/nagios-plugins/issues/1141 -------------- next part -------------- An HTML attachment was scrubbed... URL: From notifications at github.com Sun Sep 29 00:11:21 2013 From: notifications at github.com (waja) Date: Sat, 28 Sep 2013 15:11:21 -0700 Subject: [Nagiosplug-devel] [nagios-plugins] NTLM auth support for check_http [sf#3613438] (#1141) In-Reply-To: References: Message-ID: If this issue is still needed, please create a pull request, that will help us to integrate enhancements. --- Reply to this email directly or view it on GitHub: https://github.com/nagios-plugins/nagios-plugins/issues/1141#issuecomment-25309856 -------------- next part -------------- An HTML attachment was scrubbed... URL: From notifications at github.com Sun Sep 29 00:14:24 2013 From: notifications at github.com (waja) Date: Sat, 28 Sep 2013 15:14:24 -0700 Subject: [Nagiosplug-devel] [nagios-plugins] check_disk segfault on freebsd 7 if using -p option [sf#2075933] (#901) In-Reply-To: References: Message-ID: Closed #901. --- Reply to this email directly or view it on GitHub: https://github.com/nagios-plugins/nagios-plugins/issues/901 -------------- next part -------------- An HTML attachment was scrubbed... URL: From notifications at github.com Sun Sep 29 00:14:24 2013 From: notifications at github.com (waja) Date: Sat, 28 Sep 2013 15:14:24 -0700 Subject: [Nagiosplug-devel] [nagios-plugins] check_disk segfault on freebsd 7 if using -p option [sf#2075933] (#901) In-Reply-To: References: Message-ID: If this issue is still a problem, please create a pull request, that will help us to integrate such fixes. --- Reply to this email directly or view it on GitHub: https://github.com/nagios-plugins/nagios-plugins/issues/901#issuecomment-25309914 -------------- next part -------------- An HTML attachment was scrubbed... URL: From notifications at github.com Sun Sep 29 00:15:31 2013 From: notifications at github.com (waja) Date: Sat, 28 Sep 2013 15:15:31 -0700 Subject: [Nagiosplug-devel] [nagios-plugins] check_nt - add check USEDDISKSPACE against remaining Mb [sf#854538] (#851) In-Reply-To: References: Message-ID: Closed #851. --- Reply to this email directly or view it on GitHub: https://github.com/nagios-plugins/nagios-plugins/issues/851 -------------- next part -------------- An HTML attachment was scrubbed... URL: From notifications at github.com Sun Sep 29 00:15:31 2013 From: notifications at github.com (waja) Date: Sat, 28 Sep 2013 15:15:31 -0700 Subject: [Nagiosplug-devel] [nagios-plugins] check_nt - add check USEDDISKSPACE against remaining Mb [sf#854538] (#851) In-Reply-To: References: Message-ID: If this issue is still needed, please create a pull request, that will help us to integrate enhancements. --- Reply to this email directly or view it on GitHub: https://github.com/nagios-plugins/nagios-plugins/issues/851#issuecomment-25309940 -------------- next part -------------- An HTML attachment was scrubbed... URL: From notifications at github.com Sun Sep 29 00:33:14 2013 From: notifications at github.com (waja) Date: Sat, 28 Sep 2013 15:33:14 -0700 Subject: [Nagiosplug-devel] [nagios-plugins] Unspecified performance data format for threshold ranges [sf#2952850] (#929) In-Reply-To: References: Message-ID: An up to date version can be found at https://www.nagios-plugins.org/doc/guidelines.html#THRESHOLDFORMAT --- Reply to this email directly or view it on GitHub: https://github.com/nagios-plugins/nagios-plugins/issues/929#issuecomment-25310198 -------------- next part -------------- An HTML attachment was scrubbed... URL: From notifications at github.com Sun Sep 29 00:53:55 2013 From: notifications at github.com (waja) Date: Sat, 28 Sep 2013 15:53:55 -0700 Subject: [Nagiosplug-devel] [nagios-plugins] check_pop3.pl fixup [sf#740125] (#209) In-Reply-To: References: Message-ID: Closed #209. --- Reply to this email directly or view it on GitHub: https://github.com/nagios-plugins/nagios-plugins/issues/209 -------------- next part -------------- An HTML attachment was scrubbed... URL: From notifications at github.com Sun Sep 29 00:53:55 2013 From: notifications at github.com (waja) Date: Sat, 28 Sep 2013 15:53:55 -0700 Subject: [Nagiosplug-devel] [nagios-plugins] check_pop3.pl fixup [sf#740125] (#209) In-Reply-To: References: Message-ID: check_pop3.pl was never part of our distribution. --- Reply to this email directly or view it on GitHub: https://github.com/nagios-plugins/nagios-plugins/issues/209#issuecomment-25310466 -------------- next part -------------- An HTML attachment was scrubbed... URL: From notifications at github.com Sun Sep 29 00:55:11 2013 From: notifications at github.com (waja) Date: Sat, 28 Sep 2013 15:55:11 -0700 Subject: [Nagiosplug-devel] [nagios-plugins] configure.in test for radiusclient on Solaris [sf#752864] (#217) In-Reply-To: References: Message-ID: If this issue is still a problem, please create a pull request, that will help us to integrate such fixes. --- Reply to this email directly or view it on GitHub: https://github.com/nagios-plugins/nagios-plugins/issues/217#issuecomment-25310494 -------------- next part -------------- An HTML attachment was scrubbed... URL: From notifications at github.com Sun Sep 29 00:55:11 2013 From: notifications at github.com (waja) Date: Sat, 28 Sep 2013 15:55:11 -0700 Subject: [Nagiosplug-devel] [nagios-plugins] configure.in test for radiusclient on Solaris [sf#752864] (#217) In-Reply-To: References: Message-ID: Closed #217. --- Reply to this email directly or view it on GitHub: https://github.com/nagios-plugins/nagios-plugins/issues/217 -------------- next part -------------- An HTML attachment was scrubbed... URL: From notifications at github.com Sun Sep 29 00:55:30 2013 From: notifications at github.com (waja) Date: Sat, 28 Sep 2013 15:55:30 -0700 Subject: [Nagiosplug-devel] [nagios-plugins] check_ldap bug fix [sf#836010] (#277) In-Reply-To: References: Message-ID: Closed #277. --- Reply to this email directly or view it on GitHub: https://github.com/nagios-plugins/nagios-plugins/issues/277 -------------- next part -------------- An HTML attachment was scrubbed... URL: From notifications at github.com Sun Sep 29 00:55:30 2013 From: notifications at github.com (waja) Date: Sat, 28 Sep 2013 15:55:30 -0700 Subject: [Nagiosplug-devel] [nagios-plugins] check_ldap bug fix [sf#836010] (#277) In-Reply-To: References: Message-ID: If this issue is still a problem, please create a pull request, that will help us to integrate such fixes. --- Reply to this email directly or view it on GitHub: https://github.com/nagios-plugins/nagios-plugins/issues/277#issuecomment-25310496 -------------- next part -------------- An HTML attachment was scrubbed... URL: From notifications at github.com Sun Sep 29 00:58:34 2013 From: notifications at github.com (waja) Date: Sat, 28 Sep 2013 15:58:34 -0700 Subject: [Nagiosplug-devel] [nagios-plugins] fixes for check_log [sf#1025841] (#289) In-Reply-To: References: Message-ID: If this issue is still a problem, please create a pull request, that will help us to integrate such fixes. --- Reply to this email directly or view it on GitHub: https://github.com/nagios-plugins/nagios-plugins/issues/289#issuecomment-25310533 -------------- next part -------------- An HTML attachment was scrubbed... URL: From notifications at github.com Sun Sep 29 00:58:34 2013 From: notifications at github.com (waja) Date: Sat, 28 Sep 2013 15:58:34 -0700 Subject: [Nagiosplug-devel] [nagios-plugins] fixes for check_log [sf#1025841] (#289) In-Reply-To: References: Message-ID: Closed #289. --- Reply to this email directly or view it on GitHub: https://github.com/nagios-plugins/nagios-plugins/issues/289 -------------- next part -------------- An HTML attachment was scrubbed... URL: From notifications at github.com Sun Sep 29 01:03:05 2013 From: notifications at github.com (waja) Date: Sat, 28 Sep 2013 16:03:05 -0700 Subject: [Nagiosplug-devel] [nagios-plugins] Fixes bug with new vmstat version [sf#895671] (#365) In-Reply-To: References: Message-ID: Since we droped contrib/ also this plugins isn't distributed anymore. --- Reply to this email directly or view it on GitHub: https://github.com/nagios-plugins/nagios-plugins/issues/365#issuecomment-25310589 -------------- next part -------------- An HTML attachment was scrubbed... URL: From notifications at github.com Sun Sep 29 01:03:05 2013 From: notifications at github.com (waja) Date: Sat, 28 Sep 2013 16:03:05 -0700 Subject: [Nagiosplug-devel] [nagios-plugins] Fixes bug with new vmstat version [sf#895671] (#365) In-Reply-To: References: Message-ID: Closed #365. --- Reply to this email directly or view it on GitHub: https://github.com/nagios-plugins/nagios-plugins/issues/365 -------------- next part -------------- An HTML attachment was scrubbed... URL: From notifications at github.com Sun Sep 29 01:05:55 2013 From: notifications at github.com (waja) Date: Sat, 28 Sep 2013 16:05:55 -0700 Subject: [Nagiosplug-devel] [nagios-plugins] update checkNT -mostly string fixes [sf#1107259] (#391) In-Reply-To: References: Message-ID: Closed #391. --- Reply to this email directly or view it on GitHub: https://github.com/nagios-plugins/nagios-plugins/issues/391 -------------- next part -------------- An HTML attachment was scrubbed... URL: From notifications at github.com Sun Sep 29 01:05:55 2013 From: notifications at github.com (waja) Date: Sat, 28 Sep 2013 16:05:55 -0700 Subject: [Nagiosplug-devel] [nagios-plugins] update checkNT -mostly string fixes [sf#1107259] (#391) In-Reply-To: References: Message-ID: There are to much changes since this patch was commited. If this issue is still a problem, please create a pull request, that will help us to integrate such fixes. --- Reply to this email directly or view it on GitHub: https://github.com/nagios-plugins/nagios-plugins/issues/391#issuecomment-25310626 -------------- next part -------------- An HTML attachment was scrubbed... URL: From notifications at github.com Sun Sep 29 01:08:48 2013 From: notifications at github.com (waja) Date: Sat, 28 Sep 2013 16:08:48 -0700 Subject: [Nagiosplug-devel] [nagios-plugins] check_nt COUNTER rewriten with perfomance data [sf#1188568] (#423) In-Reply-To: References: Message-ID: Closed #423. --- Reply to this email directly or view it on GitHub: https://github.com/nagios-plugins/nagios-plugins/issues/423 -------------- next part -------------- An HTML attachment was scrubbed... URL: From notifications at github.com Sun Sep 29 01:08:47 2013 From: notifications at github.com (waja) Date: Sat, 28 Sep 2013 16:08:47 -0700 Subject: [Nagiosplug-devel] [nagios-plugins] check_nt COUNTER rewriten with perfomance data [sf#1188568] (#423) In-Reply-To: References: Message-ID: There are to much changes since this patch was commited. If this issue is still a problem, please create a pull request, that will help us to integrate such fixes. --- Reply to this email directly or view it on GitHub: https://github.com/nagios-plugins/nagios-plugins/issues/423#issuecomment-25310657 -------------- next part -------------- An HTML attachment was scrubbed... URL: From notifications at github.com Sun Sep 29 01:11:31 2013 From: notifications at github.com (waja) Date: Sat, 28 Sep 2013 16:11:31 -0700 Subject: [Nagiosplug-devel] [nagios-plugins] Make check_disk_smb work with both Samba 2.x.x and Samba 3.x [sf#1217379] (#467) In-Reply-To: References: Message-ID: Closed #467. --- Reply to this email directly or view it on GitHub: https://github.com/nagios-plugins/nagios-plugins/issues/467 -------------- next part -------------- An HTML attachment was scrubbed... URL: From notifications at github.com Sun Sep 29 01:11:31 2013 From: notifications at github.com (waja) Date: Sat, 28 Sep 2013 16:11:31 -0700 Subject: [Nagiosplug-devel] [nagios-plugins] Make check_disk_smb work with both Samba 2.x.x and Samba 3.x [sf#1217379] (#467) In-Reply-To: References: Message-ID: As Samba 3 is used since ages and Samba is a recent version, I guess this problem was fixed a while ago. If this issue is still a problem, please create a pull request, that will help us to integrate such fixes. --- Reply to this email directly or view it on GitHub: https://github.com/nagios-plugins/nagios-plugins/issues/467#issuecomment-25310684 -------------- next part -------------- An HTML attachment was scrubbed... URL: From notifications at github.com Sun Sep 29 01:40:03 2013 From: notifications at github.com (waja) Date: Sat, 28 Sep 2013 16:40:03 -0700 Subject: [Nagiosplug-devel] [nagios-plugins] time in rtc 822 (#1161) Message-ID: This is a pull request for issue #975 You can merge this Pull Request by running: git pull https://github.com/waja/nagios-plugins github975 Or you can view, comment on it, or merge it online at: https://github.com/nagios-plugins/nagios-plugins/pull/1161 -- Commit Summary -- * time in rtc 822 -- File Changes -- M plugins/sslutils.c (9) -- Patch Links -- https://github.com/nagios-plugins/nagios-plugins/pull/1161.patch https://github.com/nagios-plugins/nagios-plugins/pull/1161.diff -------------- next part -------------- An HTML attachment was scrubbed... URL: From notifications at github.com Sun Sep 29 01:57:29 2013 From: notifications at github.com (waja) Date: Sat, 28 Sep 2013 16:57:29 -0700 Subject: [Nagiosplug-devel] [nagios-plugins] Fix smart attribute comparation (#1162) Message-ID: This is a patch for github issue #1040 (just turned the attached patch into a pull request) You can merge this Pull Request by running: git pull https://github.com/waja/nagios-plugins github1040 Or you can view, comment on it, or merge it online at: https://github.com/nagios-plugins/nagios-plugins/pull/1162 -- Commit Summary -- * Fix smart attribute comparation -- File Changes -- M plugins/check_ide_smart.c (6) -- Patch Links -- https://github.com/nagios-plugins/nagios-plugins/pull/1162.patch https://github.com/nagios-plugins/nagios-plugins/pull/1162.diff -------------- next part -------------- An HTML attachment was scrubbed... URL: From notifications at github.com Sun Sep 29 02:09:12 2013 From: notifications at github.com (waja) Date: Sat, 28 Sep 2013 17:09:12 -0700 Subject: [Nagiosplug-devel] [nagios-plugins] check_snmp: fix for multiple non numeric OIDs (#1163) Message-ID: Just turning attached patch of github issue #1013 into a push request. You can merge this Pull Request by running: git pull https://github.com/waja/nagios-plugins github1013 Or you can view, comment on it, or merge it online at: https://github.com/nagios-plugins/nagios-plugins/pull/1163 -- Commit Summary -- * check_snmp: fix for multiple non numeric OIDs -- File Changes -- M plugins/check_snmp.c (3) -- Patch Links -- https://github.com/nagios-plugins/nagios-plugins/pull/1163.patch https://github.com/nagios-plugins/nagios-plugins/pull/1163.diff -------------- next part -------------- An HTML attachment was scrubbed... URL: From notifications at github.com Sun Sep 29 02:25:47 2013 From: notifications at github.com (waja) Date: Sat, 28 Sep 2013 17:25:47 -0700 Subject: [Nagiosplug-devel] [nagios-plugins] check_dns: returns incorrect state when specifying server (#1164) Message-ID: Just turned patch from github issue #981 into a pull request which fixes gihub issue 982 You can merge this Pull Request by running: git pull https://github.com/waja/nagios-plugins github981 Or you can view, comment on it, or merge it online at: https://github.com/nagios-plugins/nagios-plugins/pull/1164 -- Commit Summary -- * check_dns: returns incorrect state when specifying server -- File Changes -- M plugins/check_dns.c (22) -- Patch Links -- https://github.com/nagios-plugins/nagios-plugins/pull/1164.patch https://github.com/nagios-plugins/nagios-plugins/pull/1164.diff -------------- next part -------------- An HTML attachment was scrubbed... URL: From notifications at github.com Sun Sep 29 02:33:41 2013 From: notifications at github.com (waja) Date: Sat, 28 Sep 2013 17:33:41 -0700 Subject: [Nagiosplug-devel] [nagios-plugins] check_ping: Fixing "time of day goes back" (#1165) Message-ID: Just turning attached patch of github issue #809 into a push request. You can merge this Pull Request by running: git pull https://github.com/waja/nagios-plugins github809 Or you can view, comment on it, or merge it online at: https://github.com/nagios-plugins/nagios-plugins/pull/1165 -- Commit Summary -- * check_ping: Fixing "time of day goes back" -- File Changes -- M plugins/check_ping.c (6) -- Patch Links -- https://github.com/nagios-plugins/nagios-plugins/pull/1165.patch https://github.com/nagios-plugins/nagios-plugins/pull/1165.diff -------------- next part -------------- An HTML attachment was scrubbed... URL: From palli at ok.is Sun Sep 29 19:36:15 2013 From: palli at ok.is (=?utf-8?Q?P=C3=A1ll_Gu=C3=B0j=C3=B3n_Sigur=C3=B0sson?=) Date: Sun, 29 Sep 2013 17:36:15 -0000 (GMT) Subject: [Nagiosplug-devel] New Threshold Syntax In-Reply-To: Message-ID: I have arrived in St. Paul and i am looking forward to the conference. If anyone is interested in meeting up to discuss plugin guidelines, thresholds, pynag or just to meet up over a pint. Hesitate to contact me. In the meantime if we get a dedicated slot somewhere around the presentations i'll make sure to show up. Cheers, Pall ----- Original Message ----- From: "William Leibzon" To: "Nagios Plugin Development Mailing List" Sent: Wednesday, August 21, 2013 3:23:41 PM Subject: Re: [Nagiosplug-devel] New Threshold Syntax I have requested time at upcoming Nagios conference for 30 minute BoF session on this topic and to get feedback on any general features people may like to see in all the plugins. They have't got back to me yet (only sent email on Friday) but this is not a formal session and so I'd not expect an issue with holding it after normal sessions are over. My own plugins library and several plugins will support the syntax at https://github.com/willixix/nagios-plugins/wiki/New-Threshold-Syntax by conference time (just committed most of the necessary code yesterday). I hope that as independent library authors move in to this syntax, the official plugins can too although I totally understand about the manpower in the open-source effort. Still I'd like to see it a a future long-term goal to support this. William On Wed, Aug 21, 2013 at 5:35 AM, Holger Wei? < holger at cis.fu-berlin.de > wrote: * P?ll Gu?j?n Sigur?sson < palli at ok.is > [2013-07-15 20:57]: > We implemented same RFC in pynag (python modules for nagios related > stuff). We also hit some walls and wanted to make modifications. > Unfortunately, it's been a long time since it was written and author of > the proposal is not answering my emails on the topic. > > I am not sure if there is a lot of motivation among the nagios-plugins > folks to implement this RFC, so i wonder if third party libraries like > you and should coordinate on it anyway ? We (the Plugins Development Team) discussed this internally, but we haven't really reached a consensus on how to proceed. Some concerns have been raised regarding the added complexity and the amount of refactoring necessary to check only for specified thresholds. Either way, I guess we must acknowledge that we currently lack the manpower to implement a new threshold syntax, which means we'll probably stick to the current syntax for the time being. So I'd say yes: Please move ahead independently of us. Personally I quite like the new syntax, and if you settled on the details and it works well for you, we can still decide on whether and how to adopt it :-) Thanks a lot for your work on this! Holger ------------------------------------------------------------------------------ Introducing Performance Central, a new site from SourceForge and AppDynamics. Performance Central is your source for news, insights, analysis and resources for efficient Application Performance Management. Visit us today! http://pubads.g.doubleclick.net/gampad/clk?id=48897511&iu=/4140/ostg.clktrk _______________________________________________________ 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 ------------------------------------------------------------------------------ Introducing Performance Central, a new site from SourceForge and AppDynamics. Performance Central is your source for news, insights, analysis and resources for efficient Application Performance Management. Visit us today! http://pubads.g.doubleclick.net/gampad/clk?id=48897511&iu=/4140/ostg.clktrk _______________________________________________________ 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 william at leibzon.org Mon Sep 30 04:47:27 2013 From: william at leibzon.org (William Leibzon) Date: Sun, 29 Sep 2013 19:47:27 -0700 Subject: [Nagiosplug-devel] New Threshold Syntax In-Reply-To: References: Message-ID: I'll arrive Monday night and will only be on the conference for 1.5 days. I did update my wiki spec draft based on all comments on the mail list (last change was to make supporting any keyword optional i.e. plugin writers can pick and choose what to support which is what it always has been in nagios and current spec). What I have in github wikii is current base for proposal and presentation: https://github.com/willixix/nagios-plugins/wiki/New-Threshold-Syntax We have a BoF scheduled for 30 minutes during Tuesday lunch time: *Lunch BoF Session (12:30-1:00):*Nagios Plugin Thresholds - William Leibzon I haven't even started on slides for it (have another full session to prepare for), would expect to need 4-8 slides for first 10-15 minutes, then discussion. If people want to help create some slides and/or wants to co-present let me know quickly. On Sun, Sep 29, 2013 at 10:36 AM, P?ll Gu?j?n Sigur?sson wrote: > I have arrived in St. Paul and i am looking forward to the conference. > > If anyone is interested in meeting up to discuss plugin guidelines, > thresholds, pynag or just to meet up over a pint. Hesitate to contact me. > > In the meantime if we get a dedicated slot somewhere around the > presentations i'll make sure to show up. > > Cheers, > Pall > > ----- Original Message ----- > From: "William Leibzon" > To: "Nagios Plugin Development Mailing List" < > nagiosplug-devel at lists.sourceforge.net> > Sent: Wednesday, August 21, 2013 3:23:41 PM > Subject: Re: [Nagiosplug-devel] New Threshold Syntax > > > > I have requested time at upcoming Nagios conference for 30 minute BoF > session on this topic and to get feedback on any general features people > may like to see in all the plugins. They have't got back to me yet (only > sent email on Friday) but this is not a formal session and so I'd not > expect an issue with holding it after normal sessions are over. > > > My own plugins library and several plugins will support the syntax at > https://github.com/willixix/nagios-plugins/wiki/New-Threshold-Syntax by > conference time (just committed most of the necessary code yesterday). > > > I hope that as independent library authors move in to this syntax, the > official plugins can too although I totally understand about the manpower > in the open-source effort. Still I'd like to see it a a future long-term > goal to support this. > > > William > > > > On Wed, Aug 21, 2013 at 5:35 AM, Holger Wei? < holger at cis.fu-berlin.de > > wrote: > > > * P?ll Gu?j?n Sigur?sson < palli at ok.is > [2013-07-15 20:57]: > > > We implemented same RFC in pynag (python modules for nagios related > > stuff). We also hit some walls and wanted to make modifications. > > Unfortunately, it's been a long time since it was written and author of > > the proposal is not answering my emails on the topic. > > > > I am not sure if there is a lot of motivation among the nagios-plugins > > folks to implement this RFC, so i wonder if third party libraries like > > you and should coordinate on it anyway ? > > We (the Plugins Development Team) discussed this internally, but we > haven't really reached a consensus on how to proceed. Some concerns > have been raised regarding the added complexity and the amount of > refactoring necessary to check only for specified thresholds. > > Either way, I guess we must acknowledge that we currently lack the > manpower to implement a new threshold syntax, which means we'll probably > stick to the current syntax for the time being. So I'd say yes: Please > move ahead independently of us. Personally I quite like the new syntax, > and if you settled on the details and it works well for you, we can > still decide on whether and how to adopt it :-) > > Thanks a lot for your work on this! > > Holger > > > ------------------------------------------------------------------------------ > Introducing Performance Central, a new site from SourceForge and > AppDynamics. Performance Central is your source for news, insights, > analysis and resources for efficient Application Performance Management. > Visit us today! > http://pubads.g.doubleclick.net/gampad/clk?id=48897511&iu=/4140/ostg.clktrk > > > _______________________________________________________ > 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 > > > > ------------------------------------------------------------------------------ > Introducing Performance Central, a new site from SourceForge and > AppDynamics. Performance Central is your source for news, insights, > analysis and resources for efficient Application Performance Management. > Visit us today! > http://pubads.g.doubleclick.net/gampad/clk?id=48897511&iu=/4140/ostg.clktrk > _______________________________________________________ > 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 > > > ------------------------------------------------------------------------------ > October Webinars: Code for Performance > Free Intel webinars can help you accelerate application performance. > Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most > from > the latest Intel processors and coprocessors. See abstracts and register > > http://pubads.g.doubleclick.net/gampad/clk?id=60133471&iu=/4140/ostg.clktrk > _______________________________________________________ > 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 notifications at github.com Mon Sep 30 16:21:17 2013 From: notifications at github.com (waja) Date: Mon, 30 Sep 2013 07:21:17 -0700 Subject: [Nagiosplug-devel] [nagios-plugins] check_ntp_time: Bug in average calculation (#1166) Message-ID: Just turning attached patch of github issue #956 into a push request You can merge this Pull Request by running: git pull https://github.com/waja/nagios-plugins github956 Or you can view, comment on it, or merge it online at: https://github.com/nagios-plugins/nagios-plugins/pull/1166 -- Commit Summary -- * check_ntp_time: Bug in average calculation -- File Changes -- M plugins/check_ntp_time.c (4) -- Patch Links -- https://github.com/nagios-plugins/nagios-plugins/pull/1166.patch https://github.com/nagios-plugins/nagios-plugins/pull/1166.diff -------------- next part -------------- An HTML attachment was scrubbed... URL: From notifications at github.com Mon Sep 30 16:27:51 2013 From: notifications at github.com (waja) Date: Mon, 30 Sep 2013 07:27:51 -0700 Subject: [Nagiosplug-devel] [nagios-plugins] nrpe - negative command line params [sf#2661823] (#855) In-Reply-To: References: Message-ID: Closed #855. --- Reply to this email directly or view it on GitHub: https://github.com/nagios-plugins/nagios-plugins/issues/855 -------------- next part -------------- An HTML attachment was scrubbed... URL: From notifications at github.com Mon Sep 30 16:27:51 2013 From: notifications at github.com (waja) Date: Mon, 30 Sep 2013 07:27:51 -0700 Subject: [Nagiosplug-devel] [nagios-plugins] nrpe - negative command line params [sf#2661823] (#855) In-Reply-To: References: Message-ID: This is plugin wasn't part of nagios-plugins. --- Reply to this email directly or view it on GitHub: https://github.com/nagios-plugins/nagios-plugins/issues/855#issuecomment-25366583 -------------- next part -------------- An HTML attachment was scrubbed... URL: From notifications at github.com Mon Sep 30 16:34:34 2013 From: notifications at github.com (waja) Date: Mon, 30 Sep 2013 07:34:34 -0700 Subject: [Nagiosplug-devel] [nagios-plugins] check_http: timeout problem on http redirection case (#1167) Message-ID: Just turning attached patch of github issue #826 into a push request You can merge this Pull Request by running: git pull https://github.com/waja/nagios-plugins github826 Or you can view, comment on it, or merge it online at: https://github.com/nagios-plugins/nagios-plugins/pull/1167 -- Commit Summary -- * check_http: timeout problem on http redirection case -- File Changes -- M plugins/check_http.c (5) -- Patch Links -- https://github.com/nagios-plugins/nagios-plugins/pull/1167.patch https://github.com/nagios-plugins/nagios-plugins/pull/1167.diff -------------- next part -------------- An HTML attachment was scrubbed... URL: From notifications at github.com Mon Sep 30 16:54:24 2013 From: notifications at github.com (waja) Date: Mon, 30 Sep 2013 07:54:24 -0700 Subject: [Nagiosplug-devel] [nagios-plugins] check_dig: patch to make dig honor -t option (#1168) Message-ID: Just turning attached patch of github issue #774 into a push request You can merge this Pull Request by running: git pull https://github.com/waja/nagios-plugins github774 Or you can view, comment on it, or merge it online at: https://github.com/nagios-plugins/nagios-plugins/pull/1168 -- Commit Summary -- * check_dig: patch to make dig honor -t option -- File Changes -- M plugins/check_dig.c (11) -- Patch Links -- https://github.com/nagios-plugins/nagios-plugins/pull/1168.patch https://github.com/nagios-plugins/nagios-plugins/pull/1168.diff -------------- next part -------------- An HTML attachment was scrubbed... URL: From notifications at github.com Mon Sep 30 17:10:26 2013 From: notifications at github.com (waja) Date: Mon, 30 Sep 2013 08:10:26 -0700 Subject: [Nagiosplug-devel] [nagios-plugins] check_ups has only shows Fahrenheit in perf data [sf#1381999] (#510) In-Reply-To: References: Message-ID: Looks good for me in the recent version: perfdata ("temp", (long)ups_temperature, tunits, FALSE, 0, FALSE, 0, TRUE, 0, FALSE, 0)); --- Reply to this email directly or view it on GitHub: https://github.com/nagios-plugins/nagios-plugins/issues/510#issuecomment-25370819 -------------- next part -------------- An HTML attachment was scrubbed... URL: From notifications at github.com Mon Sep 30 17:38:37 2013 From: notifications at github.com (waja) Date: Mon, 30 Sep 2013 08:38:37 -0700 Subject: [Nagiosplug-devel] [nagios-plugins] check_ups has only shows Fahrenheit in perf data [sf#1381999] (#510) In-Reply-To: References: Message-ID: Closed #510. --- Reply to this email directly or view it on GitHub: https://github.com/nagios-plugins/nagios-plugins/issues/510 -------------- next part -------------- An HTML attachment was scrubbed... URL: From notifications at github.com Mon Sep 30 17:38:39 2013 From: notifications at github.com (waja) Date: Mon, 30 Sep 2013 08:38:39 -0700 Subject: [Nagiosplug-devel] [nagios-plugins] check_ups has only shows Fahrenheit in perf data [sf#1381999] (#510) In-Reply-To: References: Message-ID: Fix should be 279a93caa8b0 --- Reply to this email directly or view it on GitHub: https://github.com/nagios-plugins/nagios-plugins/issues/510#issuecomment-25373878 -------------- next part -------------- An HTML attachment was scrubbed... URL: From notifications at github.com Mon Sep 30 17:58:32 2013 From: notifications at github.com (waja) Date: Mon, 30 Sep 2013 08:58:32 -0700 Subject: [Nagiosplug-devel] [nagios-plugins] check_ifstatus: perfdata bug (#1169) Message-ID: Just turning attached patch of github issue #721 into a push request You can merge this Pull Request by running: git pull https://github.com/waja/nagios-plugins github721 Or you can view, comment on it, or merge it online at: https://github.com/nagios-plugins/nagios-plugins/pull/1169 -- Commit Summary -- * check_ifstatus: perfdata bug -- File Changes -- M THANKS.in (1) M plugins-scripts/check_ifstatus.pl (2) -- Patch Links -- https://github.com/nagios-plugins/nagios-plugins/pull/1169.patch https://github.com/nagios-plugins/nagios-plugins/pull/1169.diff -------------- next part -------------- An HTML attachment was scrubbed... URL: From palli at ok.is Mon Sep 30 19:11:15 2013 From: palli at ok.is (=?utf-8?Q?P=C3=A1ll_Gu=C3=B0j=C3=B3n_Sigur=C3=B0sson?=) Date: Mon, 30 Sep 2013 17:11:15 -0000 (GMT) Subject: [Nagiosplug-devel] New Threshold Syntax In-Reply-To: Message-ID: Yeah i have some slides to get us started. http://pall.sigurdsson.is/filez/new-threshold-syntax.svg Cheers, Palli ----- Original Message ----- From: "William Leibzon" To: "Nagios Plugin Development Mailing List" Sent: Sunday, September 29, 2013 9:47:27 PM Subject: Re: [Nagiosplug-devel] New Threshold Syntax I'll arrive Monday night and will only be on the conference for 1.5 days. I did update my wiki spec draft based on all comments on the mail list (last change was to make supporting any keyword optional i.e. plugin writers can pick and choose what to support which is what it always has been in nagios and current spec). What I have in github wikii is current base for proposal and presentation: https://github.com/willixix/nagios-plugins/wiki/New-Threshold-Syntax We have a BoF scheduled for 30 minutes during Tuesday lunch time: Lunch BoF Session (12:30-1:00): Nagios Plugin Thresholds - William Leibzon I haven't even started on slides for it (have another full session to prepare for), would expect to need 4-8 slides for first 10-15 minutes, then discussion. If people want to help create some slides and/or wants to co-present let me know quickly. On Sun, Sep 29, 2013 at 10:36 AM, P?ll Gu?j?n Sigur?sson < palli at ok.is > wrote: I have arrived in St. Paul and i am looking forward to the conference. If anyone is interested in meeting up to discuss plugin guidelines, thresholds, pynag or just to meet up over a pint. Hesitate to contact me. In the meantime if we get a dedicated slot somewhere around the presentations i'll make sure to show up. Cheers, Pall ----- Original Message ----- From: "William Leibzon" < william at leibzon.org > To: "Nagios Plugin Development Mailing List" < nagiosplug-devel at lists.sourceforge.net > Sent: Wednesday, August 21, 2013 3:23:41 PM Subject: Re: [Nagiosplug-devel] New Threshold Syntax I have requested time at upcoming Nagios conference for 30 minute BoF session on this topic and to get feedback on any general features people may like to see in all the plugins. They have't got back to me yet (only sent email on Friday) but this is not a formal session and so I'd not expect an issue with holding it after normal sessions are over. My own plugins library and several plugins will support the syntax at https://github.com/willixix/nagios-plugins/wiki/New-Threshold-Syntax by conference time (just committed most of the necessary code yesterday). I hope that as independent library authors move in to this syntax, the official plugins can too although I totally understand about the manpower in the open-source effort. Still I'd like to see it a a future long-term goal to support this. William On Wed, Aug 21, 2013 at 5:35 AM, Holger Wei? < holger at cis.fu-berlin.de > wrote: * P?ll Gu?j?n Sigur?sson < palli at ok.is > [2013-07-15 20:57]: > We implemented same RFC in pynag (python modules for nagios related > stuff). We also hit some walls and wanted to make modifications. > Unfortunately, it's been a long time since it was written and author of > the proposal is not answering my emails on the topic. > > I am not sure if there is a lot of motivation among the nagios-plugins > folks to implement this RFC, so i wonder if third party libraries like > you and should coordinate on it anyway ? We (the Plugins Development Team) discussed this internally, but we haven't really reached a consensus on how to proceed. Some concerns have been raised regarding the added complexity and the amount of refactoring necessary to check only for specified thresholds. Either way, I guess we must acknowledge that we currently lack the manpower to implement a new threshold syntax, which means we'll probably stick to the current syntax for the time being. So I'd say yes: Please move ahead independently of us. Personally I quite like the new syntax, and if you settled on the details and it works well for you, we can still decide on whether and how to adopt it :-) Thanks a lot for your work on this! Holger ------------------------------------------------------------------------------ Introducing Performance Central, a new site from SourceForge and AppDynamics. Performance Central is your source for news, insights, analysis and resources for efficient Application Performance Management. Visit us today! http://pubads.g.doubleclick.net/gampad/clk?id=48897511&iu=/4140/ostg.clktrk _______________________________________________________ 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 ------------------------------------------------------------------------------ Introducing Performance Central, a new site from SourceForge and AppDynamics. Performance Central is your source for news, insights, analysis and resources for efficient Application Performance Management. Visit us today! http://pubads.g.doubleclick.net/gampad/clk?id=48897511&iu=/4140/ostg.clktrk _______________________________________________________ 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 ------------------------------------------------------------------------------ October Webinars: Code for Performance Free Intel webinars can help you accelerate application performance. Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from the latest Intel processors and coprocessors. See abstracts and register > http://pubads.g.doubleclick.net/gampad/clk?id=60133471&iu=/4140/ostg.clktrk _______________________________________________________ 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 ------------------------------------------------------------------------------ October Webinars: Code for Performance Free Intel webinars can help you accelerate application performance. Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from the latest Intel processors and coprocessors. See abstracts and register > http://pubads.g.doubleclick.net/gampad/clk?id=60133471&iu=/4140/ostg.clktrk _______________________________________________________ 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 Stephan at quantentunnel.de Mon Sep 30 19:35:35 2013 From: Stephan at quantentunnel.de (Stephan) Date: Mon, 30 Sep 2013 19:35:35 +0200 Subject: [Nagiosplug-devel] New Threshold Syntax In-Reply-To: References: Message-ID: <5249B667.6020104@quantentunnel.de> Am 30.09.13 19:11, schrieb P?ll Gu?j?n Sigur?sson: > Yeah i have some slides to get us started. > > http://pall.sigurdsson.is/filez/new-threshold-syntax.svg > I'm missing the option to define that the endpoints are NOT within the range. Like we discussed on the list: [start..end] : Includes endpoints ]start..end[ : excludes endpoints (or use round brackets) ]start..end] : mixed notation: Excluding start including end From william at leibzon.org Mon Sep 30 19:38:09 2013 From: william at leibzon.org (William Leibzon) Date: Mon, 30 Sep 2013 10:38:09 -0700 Subject: [Nagiosplug-devel] New Threshold Syntax In-Reply-To: References: Message-ID: if you have it in openoffiice format and can send in the next hour, it'd be great. I'm leaving in an hour, will work on the plane. On Mon, Sep 30, 2013 at 10:11 AM, P?ll Gu?j?n Sigur?sson wrote: > Yeah i have some slides to get us started. > > http://pall.sigurdsson.is/filez/new-threshold-syntax.svg > > Cheers, > Palli > > > ----- Original Message ----- > From: "William Leibzon" > To: "Nagios Plugin Development Mailing List" < > nagiosplug-devel at lists.sourceforge.net> > Sent: Sunday, September 29, 2013 9:47:27 PM > Subject: Re: [Nagiosplug-devel] New Threshold Syntax > > > > I'll arrive Monday night and will only be on the conference for 1.5 days. > > > I did update my wiki spec draft based on all comments on the mail list > (last change was to make supporting any keyword optional i.e. plugin > writers can pick and choose what to support which is what it always has > been in nagios and current spec). What I have in github wikii is current > base for proposal and presentation: > https://github.com/willixix/nagios-plugins/wiki/New-Threshold-Syntax > > > We have a BoF scheduled for 30 minutes during Tuesday lunch time: > Lunch BoF Session (12:30-1:00): Nagios Plugin Thresholds - William Leibzon > > > I haven't even started on slides for it (have another full session to > prepare for), would expect to need 4-8 slides for first 10-15 minutes, then > discussion. If people want to help create some slides and/or wants to > co-present let me know quickly. > > > > On Sun, Sep 29, 2013 at 10:36 AM, P?ll Gu?j?n Sigur?sson < palli at ok.is > > wrote: > > > I have arrived in St. Paul and i am looking forward to the conference. > > If anyone is interested in meeting up to discuss plugin guidelines, > thresholds, pynag or just to meet up over a pint. Hesitate to contact me. > > In the meantime if we get a dedicated slot somewhere around the > presentations i'll make sure to show up. > > Cheers, > Pall > > > ----- Original Message ----- > From: "William Leibzon" < william at leibzon.org > > > To: "Nagios Plugin Development Mailing List" < > nagiosplug-devel at lists.sourceforge.net > > Sent: Wednesday, August 21, 2013 3:23:41 PM > Subject: Re: [Nagiosplug-devel] New Threshold Syntax > > > > > > I have requested time at upcoming Nagios conference for 30 minute BoF > session on this topic and to get feedback on any general features people > may like to see in all the plugins. They have't got back to me yet (only > sent email on Friday) but this is not a formal session and so I'd not > expect an issue with holding it after normal sessions are over. > > > My own plugins library and several plugins will support the syntax at > https://github.com/willixix/nagios-plugins/wiki/New-Threshold-Syntax by > conference time (just committed most of the necessary code yesterday). > > > I hope that as independent library authors move in to this syntax, the > official plugins can too although I totally understand about the manpower > in the open-source effort. Still I'd like to see it a a future long-term > goal to support this. > > > William > > > > On Wed, Aug 21, 2013 at 5:35 AM, Holger Wei? < holger at cis.fu-berlin.de > > wrote: > > > * P?ll Gu?j?n Sigur?sson < palli at ok.is > [2013-07-15 20:57]: > > > We implemented same RFC in pynag (python modules for nagios related > > stuff). We also hit some walls and wanted to make modifications. > > Unfortunately, it's been a long time since it was written and author of > > the proposal is not answering my emails on the topic. > > > > I am not sure if there is a lot of motivation among the nagios-plugins > > folks to implement this RFC, so i wonder if third party libraries like > > you and should coordinate on it anyway ? > > We (the Plugins Development Team) discussed this internally, but we > haven't really reached a consensus on how to proceed. Some concerns > have been raised regarding the added complexity and the amount of > refactoring necessary to check only for specified thresholds. > > Either way, I guess we must acknowledge that we currently lack the > manpower to implement a new threshold syntax, which means we'll probably > stick to the current syntax for the time being. So I'd say yes: Please > move ahead independently of us. Personally I quite like the new syntax, > and if you settled on the details and it works well for you, we can > still decide on whether and how to adopt it :-) > > Thanks a lot for your work on this! > > Holger > > > ------------------------------------------------------------------------------ > Introducing Performance Central, a new site from SourceForge and > AppDynamics. Performance Central is your source for news, insights, > analysis and resources for efficient Application Performance Management. > Visit us today! > http://pubads.g.doubleclick.net/gampad/clk?id=48897511&iu=/4140/ostg.clktrk > > > _______________________________________________________ > 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 > > > > ------------------------------------------------------------------------------ > Introducing Performance Central, a new site from SourceForge and > AppDynamics. Performance Central is your source for news, insights, > analysis and resources for efficient Application Performance Management. > Visit us today! > http://pubads.g.doubleclick.net/gampad/clk?id=48897511&iu=/4140/ostg.clktrk > _______________________________________________________ > 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 > > > ------------------------------------------------------------------------------ > October Webinars: Code for Performance > Free Intel webinars can help you accelerate application performance. > Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most > from > the latest Intel processors and coprocessors. See abstracts and register > > http://pubads.g.doubleclick.net/gampad/clk?id=60133471&iu=/4140/ostg.clktrk > > > _______________________________________________________ > 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 > > > ------------------------------------------------------------------------------ > October Webinars: Code for Performance > Free Intel webinars can help you accelerate application performance. > Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most > from > the latest Intel processors and coprocessors. See abstracts and register > > http://pubads.g.doubleclick.net/gampad/clk?id=60133471&iu=/4140/ostg.clktrk > _______________________________________________________ > 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 > > > ------------------------------------------------------------------------------ > October Webinars: Code for Performance > Free Intel webinars can help you accelerate application performance. > Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most > from > the latest Intel processors and coprocessors. See abstracts and register > > http://pubads.g.doubleclick.net/gampad/clk?id=60133471&iu=/4140/ostg.clktrk > _______________________________________________________ > 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 notifications at github.com Mon Sep 30 21:23:34 2013 From: notifications at github.com (waja) Date: Mon, 30 Sep 2013 12:23:34 -0700 Subject: [Nagiosplug-devel] [nagios-plugins] check_disk: precise the help output (#1170) Message-ID: Fixing issue #1118 You can merge this Pull Request by running: git pull https://github.com/waja/nagios-plugins github1118 Or you can view, comment on it, or merge it online at: https://github.com/nagios-plugins/nagios-plugins/pull/1170 -- Commit Summary -- * check_disk: precise the help output -- File Changes -- M plugins/check_disk.c (2) -- Patch Links -- https://github.com/nagios-plugins/nagios-plugins/pull/1170.patch https://github.com/nagios-plugins/nagios-plugins/pull/1170.diff -------------- next part -------------- An HTML attachment was scrubbed... URL: From notifications at github.com Mon Sep 30 21:48:11 2013 From: notifications at github.com (waja) Date: Mon, 30 Sep 2013 12:48:11 -0700 Subject: [Nagiosplug-devel] [nagios-plugins] check_disk_smb requires DNS agree with NetBIOS names [sf#1370031] (#505) In-Reply-To: References: Message-ID: This was fixed with 5a1babdae87 and the release of 1.4.15. --- Reply to this email directly or view it on GitHub: https://github.com/nagios-plugins/nagios-plugins/issues/505#issuecomment-25398251 -------------- next part -------------- An HTML attachment was scrubbed... URL: From notifications at github.com Mon Sep 30 21:48:11 2013 From: notifications at github.com (waja) Date: Mon, 30 Sep 2013 12:48:11 -0700 Subject: [Nagiosplug-devel] [nagios-plugins] check_disk_smb requires DNS agree with NetBIOS names [sf#1370031] (#505) In-Reply-To: References: Message-ID: Closed #505. --- Reply to this email directly or view it on GitHub: https://github.com/nagios-plugins/nagios-plugins/issues/505 -------------- next part -------------- An HTML attachment was scrubbed... URL: From notifications at github.com Mon Sep 30 21:50:46 2013 From: notifications at github.com (waja) Date: Mon, 30 Sep 2013 12:50:46 -0700 Subject: [Nagiosplug-devel] =?utf-8?q?=5Bnagios-plugins=5D_check=5Fdisk_sh?= =?utf-8?b?b3dzIMOi4oKsxZMvIG5vdCBmb3VuZMOi4oKswp0gb24gU29sYXJpcyBbc2Yj?= =?utf-8?b?Mjg3NDU4MV0gKCM5MTMp?= In-Reply-To: References: Message-ID: Anybody with Slowlaris who can reproduce this issue? --- Reply to this email directly or view it on GitHub: https://github.com/nagios-plugins/nagios-plugins/issues/913#issuecomment-25398520 -------------- next part -------------- An HTML attachment was scrubbed... URL: From notifications at github.com Mon Sep 30 22:40:04 2013 From: notifications at github.com (waja) Date: Mon, 30 Sep 2013 13:40:04 -0700 Subject: [Nagiosplug-devel] [nagios-plugins] check_mailq: add sudo support (#1171) Message-ID: Just turning attached patch of github issue #1099 into a push request (with some modifications) You can merge this Pull Request by running: git pull https://github.com/waja/nagios-plugins github1099 Or you can view, comment on it, or merge it online at: https://github.com/nagios-plugins/nagios-plugins/pull/1171 -- Commit Summary -- * check_mailq: add sudo support -- File Changes -- M THANKS.in (1) M plugins-scripts/check_mailq.pl (19) -- Patch Links -- https://github.com/nagios-plugins/nagios-plugins/pull/1171.patch https://github.com/nagios-plugins/nagios-plugins/pull/1171.diff -------------- next part -------------- An HTML attachment was scrubbed... URL: From notifications at github.com Mon Sep 30 22:56:10 2013 From: notifications at github.com (waja) Date: Mon, 30 Sep 2013 13:56:10 -0700 Subject: [Nagiosplug-devel] [nagios-plugins] Fix UNIX socket check for check_pgsql [sf#3510397] (#1039) In-Reply-To: References: Message-ID: Fixed with a241ab0b9d and should be fixed in the next release. --- Reply to this email directly or view it on GitHub: https://github.com/nagios-plugins/nagios-plugins/issues/1039#issuecomment-25405512 -------------- next part -------------- An HTML attachment was scrubbed... URL: From notifications at github.com Mon Sep 30 22:56:10 2013 From: notifications at github.com (waja) Date: Mon, 30 Sep 2013 13:56:10 -0700 Subject: [Nagiosplug-devel] [nagios-plugins] Fix UNIX socket check for check_pgsql [sf#3510397] (#1039) In-Reply-To: References: Message-ID: Closed #1039. --- Reply to this email directly or view it on GitHub: https://github.com/nagios-plugins/nagios-plugins/issues/1039 -------------- next part -------------- An HTML attachment was scrubbed... URL: From notifications at github.com Mon Sep 30 23:11:09 2013 From: notifications at github.com (waja) Date: Mon, 30 Sep 2013 14:11:09 -0700 Subject: [Nagiosplug-devel] [nagios-plugins] check_icmp : disable rtmin/rtmax perfomance data (#1172) Message-ID: Just turning attached patch of github issue #1036 into a push request You can merge this Pull Request by running: git pull https://github.com/waja/nagios-plugins github1036 Or you can view, comment on it, or merge it online at: https://github.com/nagios-plugins/nagios-plugins/pull/1172 -- Commit Summary -- * check_icmp : disable rtmin/rtmax perfomance data -- File Changes -- M plugins-root/check_icmp.c (15) -- Patch Links -- https://github.com/nagios-plugins/nagios-plugins/pull/1172.patch https://github.com/nagios-plugins/nagios-plugins/pull/1172.diff -------------- next part -------------- An HTML attachment was scrubbed... URL: From notifications at github.com Mon Sep 30 23:17:03 2013 From: notifications at github.com (waja) Date: Mon, 30 Sep 2013 14:17:03 -0700 Subject: [Nagiosplug-devel] [nagios-plugins] check_fping: IPv6 support [sf#3490731] (#1035) In-Reply-To: References: Message-ID: This was fixed with 6515124a and 108baeca and should be fixed in the next release. --- Reply to this email directly or view it on GitHub: https://github.com/nagios-plugins/nagios-plugins/issues/1035#issuecomment-25407131 -------------- next part -------------- An HTML attachment was scrubbed... URL: From notifications at github.com Mon Sep 30 23:23:23 2013 From: notifications at github.com (waja) Date: Mon, 30 Sep 2013 14:23:23 -0700 Subject: [Nagiosplug-devel] [nagios-plugins] Patch to specify critical threshold for cert expiration [sf#3473669] (#1034) In-Reply-To: References: Message-ID: Fixed with fa3d2a40 and 6b844aea and should be fixed in the next release. --- Reply to this email directly or view it on GitHub: https://github.com/nagios-plugins/nagios-plugins/issues/1034#issuecomment-25407556 -------------- next part -------------- An HTML attachment was scrubbed... URL: From notifications at github.com Mon Sep 30 23:23:23 2013 From: notifications at github.com (waja) Date: Mon, 30 Sep 2013 14:23:23 -0700 Subject: [Nagiosplug-devel] [nagios-plugins] Patch to specify critical threshold for cert expiration [sf#3473669] (#1034) In-Reply-To: References: Message-ID: Closed #1034. --- Reply to this email directly or view it on GitHub: https://github.com/nagios-plugins/nagios-plugins/issues/1034 -------------- next part -------------- An HTML attachment was scrubbed... URL: From notifications at github.com Mon Sep 30 23:26:39 2013 From: notifications at github.com (waja) Date: Mon, 30 Sep 2013 14:26:39 -0700 Subject: [Nagiosplug-devel] [nagios-plugins] Add regex for header checks in check_http [sf#3469275] (#1032) In-Reply-To: References: Message-ID: Closed #1032. --- Reply to this email directly or view it on GitHub: https://github.com/nagios-plugins/nagios-plugins/issues/1032 -------------- next part -------------- An HTML attachment was scrubbed... URL: From notifications at github.com Mon Sep 30 23:26:39 2013 From: notifications at github.com (waja) Date: Mon, 30 Sep 2013 14:26:39 -0700 Subject: [Nagiosplug-devel] [nagios-plugins] Add regex for header checks in check_http [sf#3469275] (#1032) In-Reply-To: References: Message-ID: This was fixed with 2a8eab6b and should be fixed in the next release. --- Reply to this email directly or view it on GitHub: https://github.com/nagios-plugins/nagios-plugins/issues/1032#issuecomment-25407818 -------------- next part -------------- An HTML attachment was scrubbed... URL: From notifications at github.com Mon Sep 30 23:34:55 2013 From: notifications at github.com (waja) Date: Mon, 30 Sep 2013 14:34:55 -0700 Subject: [Nagiosplug-devel] [nagios-plugins] check_snmp: small improvement (#1173) Message-ID: Just turning attached patch of github issue #1029 into a push request You can merge this Pull Request by running: git pull https://github.com/waja/nagios-plugins github1029 Or you can view, comment on it, or merge it online at: https://github.com/nagios-plugins/nagios-plugins/pull/1173 -- Commit Summary -- * check_snmp: small improvement -- File Changes -- M plugins/check_snmp.c (4) -- Patch Links -- https://github.com/nagios-plugins/nagios-plugins/pull/1173.patch https://github.com/nagios-plugins/nagios-plugins/pull/1173.diff -------------- next part -------------- An HTML attachment was scrubbed... URL: