From noreply at sourceforge.net Sun Nov 1 22:15:54 2009 From: noreply at sourceforge.net (SourceForge.net) Date: Sun, 01 Nov 2009 21:15:54 +0000 Subject: [Nagiosplug-devel] [ nagiosplug-Bugs-2890436 ] contrib/check_asterisk.pl stops working with new Asterisk Message-ID: Bugs item #2890436, was opened at 2009-11-01 21:15 Message generated for change (Tracker Item Submitted) made by You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=397597&aid=2890436&group_id=29880 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Ernesto Ongaro () Assigned to: Nobody/Anonymous (nobody) Summary: contrib/check_asterisk.pl stops working with new Asterisk Initial Comment: ** I see the "Do not post bugs for plugins inside the contrib directory or from third party websites. Instead contact the respective developer directly." - unfortunately there is no name on this plugin, the original svn commit from 2005 didn't cite the source so I'm putting it here. Plugin Version (-V output): no version in plugin Plugin Name: contrib/check_asterisk.pl Example Plugin Commandline: ./check_asterisk.pl -h iax -h 127.0.0.1 Tested on operating system: Linux 2.6 Tested on architecture: i386 Tested with compiler: Perl v5.8.5 The current Nagios plugin for Asterisk when in IAX2 mode only works because the host on the other end replies with INVALID. Not a good way to test something, it didn't bother me until Asterisk 1.4.26.2 stopped working. This patch uses IAX2 POKE to get an answer from the Asterisk host ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=397597&aid=2890436&group_id=29880 From Goesta.Smekal at it-novum.com Tue Nov 3 16:22:25 2009 From: Goesta.Smekal at it-novum.com (Smekal, Goesta) Date: Tue, 3 Nov 2009 16:22:25 +0100 Subject: [Nagiosplug-devel] Nagios::Plugin uom Bug? Message-ID: Hello List, trying to output perfdata from my perl plugin I miss the "uom" output. My code looks like this: if ( defined $plugin->opts->perfdata) { $plugin->add_perfdata( label => $re_label, value => $re_value, oum => $re_uom, warning => $plugin->opts->warning, critical => $plugin->opts->critical, ); } and as a result I get ($re_* contain 'host_mem', '52.15', '%'): ESX_CLIENT OK - overall memory usage:52.15 % | host_mem=52.15;75;90 The perfdata is there, except for the uom. Yes, $re_uom is set and contains a valid string, and yes, I tried things like "uom => '%'" for testing purposes. No matter what I put in "uom", nothing ends up in the response. Is this a (known) bug or am I missing something? regards P.S.: sorry for the junk at the end of this message - server adds it. i.A. Goesta Smekal Tel: +43 (0)1 23060 4151 (-333) Fax: (-334) mailto:Goesta.Smekal at it-novum.com it-novum GmbH . Edelzeller Strasse 44 . 36043 Fulda . http://www.it-novum.com Handelsregister Amtsgericht Fulda, HRB 1934 . Geschaftsfuhrer: Michael Kienle . Sitz der Gesellschaft: Fulda Der Inhalt dieser E-Mail ist vertraulich. Wenn Sie nicht der eigentliche Empfaenger sein sollten, informieren Sie bitte sofort den Absender oder vernichten umgehend diese Mail. Jegliche unerlaubte Vervielfaeltigung oder Weiterleitung dieser Mail ist strengstens verboten. This e-mail may contain confidential and/or priviledged information. If you are not the intended recepient (or have received this e-mail in error) please notify the sender immediately and destroy this e-mail. Any unauthorised copying, disclosure or distribution of material in this e-mail is strictly forbidden. From dermoth at aei.ca Wed Nov 4 00:23:47 2009 From: dermoth at aei.ca (Thomas Guyot-Sionnest) Date: Tue, 03 Nov 2009 18:23:47 -0500 Subject: [Nagiosplug-devel] Nagios::Plugin uom Bug? In-Reply-To: References: Message-ID: <4AF0BB83.7070703@aei.ca> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 03/11/09 10:22 AM, Smekal, Goesta wrote: > Hello List, > > trying to output perfdata from my perl plugin I miss the "uom" output. > My code looks like this: > > if ( defined $plugin->opts->perfdata) { > $plugin->add_perfdata( > label => $re_label, > value => $re_value, > oum => $re_uom, > warning => $plugin->opts->warning, > critical => $plugin->opts->critical, > ); > } "oum" is not the same as "uom" ;) - -- Thomas -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFK8LuC6dZ+Kt5BchYRArAMAKCXqWDJIpl/FDDTwTNqOg3OclvhjQCfRmEZ qpWJ8zJi2CH32ooTC0jxUlQ= =xwSh -----END PGP SIGNATURE----- From Goesta.Smekal at it-novum.com Wed Nov 4 08:29:56 2009 From: Goesta.Smekal at it-novum.com (Smekal, Goesta) Date: Wed, 4 Nov 2009 08:29:56 +0100 Subject: [Nagiosplug-devel] Nagios::Plugin uom Bug? References: <4AF0BB83.7070703@aei.ca> Message-ID: i.A. Goesta Smekal Tel: +43 (0)1 23060 4151 (-333) Fax: (-334) mailto:Goesta.Smekal at it-novum.com it-novum GmbH . Edelzeller Strasse 44 . 36043 Fulda . http://www.it-novum.com Handelsregister Amtsgericht Fulda, HRB 1934 . Gesch?ftsf?hrer: Michael Kienle . Sitz der Gesellschaft: Fulda Der Inhalt dieser E-Mail ist vertraulich. Wenn Sie nicht der eigentliche Empfaenger sein sollten, informieren Sie bitte sofort den Absender oder vernichten umgehend diese Mail. Jegliche unerlaubte Vervielfaeltigung oder Weiterleitung dieser Mail ist strengstens verboten. This e-mail may contain confidential and/or priviledged information. If you are not the intended recepient (or have received this e-mail in error) please notify the sender immediately and destroy this e-mail. Any unauthorised copying, disclosure or distribution of material in this e-mail is strictly forbidden. -----Original Message----- > From: Thomas Guyot-Sionnest [mailto:dermoth at aei.ca] > Sent: Wed 04-Nov-09 00:23 > To: Nagios Plugin Development Mailing List > Subject: Re: [Nagiosplug-devel] Nagios::Plugin uom Bug? > > > oum => $re_uom, > > "oum" is not the same as "uom" ;) You are definitely right. What a pitty. Nice way to introduce myself to the list ;-) Thank you very much and sorry for the silly posting ... From holger at CIS.FU-Berlin.DE Fri Nov 6 12:45:20 2009 From: holger at CIS.FU-Berlin.DE (Holger =?iso-8859-1?Q?Wei=DF?=) Date: Fri, 6 Nov 2009 12:45:20 +0100 Subject: [Nagiosplug-devel] [HEADS UP] Git repositories moved to SourceForge Message-ID: <20091106114520.GK86195564@Waran.CIS.FU-Berlin.DE> I moved our Git repositories from repo.or.cz to SourceForge today. They can now be cloned using: $ git clone git://nagiosplug.git.sourceforge.net/gitroot/nagiosplug/nagiosplug $ git clone git://nagiosplug.git.sourceforge.net/gitroot/nagiosplug/nagiosmib $ git clone git://nagiosplug.git.sourceforge.net/gitroot/nagiosplug/Nagios-Plugin The Gitweb interface to these repositories can be viewed at: http://nagiosplug.git.sourceforge.net/ The old repositories at repo.or.cz now mirror the SourceForge repositories (once an hour), so local read-only clones should continue to work without modification. However, the configuration of local clones can be updated as follows to use the new location instead: $ git remote rm origin $ git remote add origin git://nagiosplug.git.sourceforge.net/gitroot/nagiosplug/ $ git config branch.master.remote origin $ git config branch.master.merge refs/heads/master where is the repository name, that is: nagiosplug, nagiosmib, or Nagios-Plugin. Developers with push access can update the configuration of their local clones like this: $ git remote rm origin $ git remote add origin ssh://@nagiosplug.git.sourceforge.net/gitroot/nagiosplug/ $ git config branch.master.remote origin $ git config branch.master.merge refs/heads/master where is the user name at SourceForge and is the repository name. Apart from that, I disabled the Subversion commit notifications we received so far and activated the new git-notify hook instead. As far as I can see, this means that we could finally switch off the Subversion mirror of our Git repositories. Any objections? Is anyone (or any script) still using them? Holger From holger at CIS.FU-Berlin.DE Fri Nov 6 15:32:19 2009 From: holger at CIS.FU-Berlin.DE (Holger =?iso-8859-1?Q?Wei=DF?=) Date: Fri, 6 Nov 2009 15:32:19 +0100 Subject: [Nagiosplug-devel] New subject [tag] for commit notifications? Message-ID: <20091106143219.GN86195564@Waran.CIS.FU-Berlin.DE> Commit notifications sent to the "nagiosplug-checkins" list are currently tagged with [Nagiosplug-checkins] in the subject line. Thomas suggested to use the name of the repository which got updated instead, that is: [nagiosplug], [nagiosmib], or [Nagios-Plugin].? Any objections? Holger ? Actually, Thomas suggested [nagiosplug-checkin], [nagiosmib-checkin], and [Nagios-Plugin-checkin], but I'd prefer the shorter versions. From ton.voon at opsera.com Fri Nov 6 16:15:42 2009 From: ton.voon at opsera.com (Ton Voon) Date: Fri, 6 Nov 2009 15:15:42 +0000 Subject: [Nagiosplug-devel] New subject [tag] for commit notifications? In-Reply-To: <20091106143219.GN86195564@Waran.CIS.FU-Berlin.DE> References: <20091106143219.GN86195564@Waran.CIS.FU-Berlin.DE> Message-ID: On 6 Nov 2009, at 14:32, Holger Wei? wrote: > Commit notifications sent to the "nagiosplug-checkins" list are > currently tagged with [Nagiosplug-checkins] in the subject line. > Thomas > suggested to use the name of the repository which got updated instead, > that is: [nagiosplug], [nagiosmib], or [Nagios-Plugin].? Any > objections? Good idea. [nagiosplug-checkins] was a mailman setting, I believe. Let me know if you need permissions to access this. Ton From ingo.kley at web.de Sat Nov 7 13:56:04 2009 From: ingo.kley at web.de (Ingo Kley) Date: Sat, 07 Nov 2009 13:56:04 +0100 Subject: [Nagiosplug-devel] Nagios Plugin check_ssh Message-ID: <4AF56E64.6060604@web.de> Hallo, we are using the nagios plugin check_ssh (2007-11-09 13:08:43Z). Because ssh protocol 1 insn't secure, it would be nice, if the check would reply Critical if only protocol 1 is used. This may be the default or by an option like (-p 2) where "2" is the smallest version of the expected protocol. Kind regards Ingo From holger at CIS.FU-Berlin.DE Sat Nov 7 17:22:15 2009 From: holger at CIS.FU-Berlin.DE (Holger =?iso-8859-1?Q?Wei=DF?=) Date: Sat, 7 Nov 2009 17:22:15 +0100 Subject: [Nagiosplug-devel] Nagios Plugin check_ssh In-Reply-To: <4AF56E64.6060604@web.de> References: <4AF56E64.6060604@web.de> Message-ID: <20091107162215.GQ86195564@Waran.CIS.FU-Berlin.DE> * Ingo Kley [2009-11-07 13:56]: > we are using the nagios plugin check_ssh (2007-11-09 13:08:43Z). > > Because ssh protocol 1 insn't secure, it would be nice, if the check would > reply Critical if only protocol 1 is used. > > This may be the default or by an option like (-p 2) > where "2" is the smallest version of the expected protocol. It should be an option so that it doesn't break existing configurations. Other than that, good idea. Patches welcome :-) It should be trivial to implement; see RFC 4253, #4.2 and #5: http://tools.ietf.org/html/rfc4253#section-4.2 Holger From william at leibzon.org Sat Nov 7 17:23:05 2009 From: william at leibzon.org (William Leibzon) Date: Sat, 7 Nov 2009 08:23:05 -0800 Subject: [Nagiosplug-devel] Nagios Plugin check_ssh In-Reply-To: <4AF56E64.6060604@web.de> References: <4AF56E64.6060604@web.de> Message-ID: I have implimented this almost 3 years ago. Enclosed is the patch. It is for older version of check_ssh though. On Sat, Nov 7, 2009 at 4:56 AM, Ingo Kley wrote: > Hallo, > > we are using the nagios plugin check_ssh (2007-11-09 13:08:43Z). > > Because ssh protocol 1 insn't secure, it would be nice, if the check would > reply Critical if only protocol 1 is used. > > This may be the default or by an option like (-p 2) > where "2" is the smallest version of the expected protocol. > > Kind regards > Ingo > > > > ------------------------------------------------------------------------------ > Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day > trial. Simplify your report design, integration and deployment - and focus > on > what you do best, core application coding. Discover what's new with > Crystal Reports now. http://p.sf.net/sfu/bobj-july > _______________________________________________________ > Nagios Plugin Development Mailing List > Nagiosplug-devel at lists.sourceforge.net > Unsubscribe at > https://lists.sourceforge.net/lists/listinfo/nagiosplug-devel > ::: Please include plugins version (-v) and OS when reporting any issue. > ::: Messages without supporting info will risk being sent to /dev/null > -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: check_ssh.c.diff Type: text/x-diff Size: 2648 bytes Desc: not available URL: From dermoth at aei.ca Sat Nov 7 21:01:01 2009 From: dermoth at aei.ca (Thomas Guyot-Sionnest) Date: Sat, 07 Nov 2009 15:01:01 -0500 Subject: [Nagiosplug-devel] Nagios Plugin check_ssh In-Reply-To: <20091107162215.GQ86195564@Waran.CIS.FU-Berlin.DE> References: <4AF56E64.6060604@web.de> <20091107162215.GQ86195564@Waran.CIS.FU-Berlin.DE> Message-ID: <4AF5D1FD.9090606@aei.ca> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 07/11/09 11:22 AM, Holger Wei? wrote: > * Ingo Kley [2009-11-07 13:56]: >> we are using the nagios plugin check_ssh (2007-11-09 13:08:43Z). >> >> Because ssh protocol 1 insn't secure, it would be nice, if the check would >> reply Critical if only protocol 1 is used. >> >> This may be the default or by an option like (-p 2) >> where "2" is the smallest version of the expected protocol. > > It should be an option so that it doesn't break existing configurations. > Other than that, good idea. Patches welcome :-) It should be trivial > to implement; see RFC 4253, #4.2 and #5: > > http://tools.ietf.org/html/rfc4253#section-4.2 I agree, however I'm thinking it would fit better with the new thresholds syntax as it would allow selecting the criticality of the alert as well. My experience with this kind of flag arguments is that I often end up patching the plugins because it either return WARNING when I want CRITICAL or the other way round, and sometimes using negate also mess up with other possible results. - -- Thomas -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFK9dH96dZ+Kt5BchYRAlpBAJwMP/azv+zcQ40rEdLocVXPCUOSRgCdEIpn 3UEBtbtct93STNeur1ULujc= =n+II -----END PGP SIGNATURE----- From shadhin71 at gmail.com Mon Nov 9 21:27:42 2009 From: shadhin71 at gmail.com (shadih rahman) Date: Mon, 9 Nov 2009 15:27:42 -0500 Subject: [Nagiosplug-devel] check_mailq adding age option Message-ID: <6db4a4200911091227l1639bb47w84ea6c655ddfe126@mail.gmail.com> check_mailq plugin is great but it does not allow to check for message age. Can we add message age option, so one can check for the following scenario. message age more than 60 days > 2000 warning messages age more than 60 days > 3000 critical -- Cordially, Shadhin Rahman -------------- next part -------------- An HTML attachment was scrubbed... URL: From dermoth at aei.ca Tue Nov 10 00:52:48 2009 From: dermoth at aei.ca (Thomas Guyot-Sionnest) Date: Mon, 09 Nov 2009 18:52:48 -0500 Subject: [Nagiosplug-devel] check_mailq adding age option In-Reply-To: <6db4a4200911091227l1639bb47w84ea6c655ddfe126@mail.gmail.com> References: <6db4a4200911091227l1639bb47w84ea6c655ddfe126@mail.gmail.com> Message-ID: <4AF8AB50.3020705@aei.ca> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 09/11/09 03:27 PM, shadih rahman wrote: > check_mailq plugin is great but it does not allow to check for message > age. Can we add message age option, so one can check for the following > scenario. > > message age more than 60 days > 2000 warning > messages age more than 60 days > 3000 critical I fail to see what this is for. Messages in a mail queue shouldn't stay forever in it. Most mailers drop messages after 2-6 days, and it is expected to have messages waiting in the queue until the expiration (most common causes are spam and mistyped emails). However the queue size is a fairly good indication of the failure rate, as the size is roughly proportional to the number of mails that never get sent versus the time they can stay in the queue. - -- Thomas -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFK+KtQ6dZ+Kt5BchYRAr56AJ9m+PnpzG11r9CO7hhbIcvXIMFbAwCgllZr utBCSjpuaDW3wYTHsSn/Fh4= =IsN9 -----END PGP SIGNATURE----- From dermoth at aei.ca Tue Nov 10 11:54:48 2009 From: dermoth at aei.ca (Thomas Guyot-Sionnest) Date: Tue, 10 Nov 2009 05:54:48 -0500 Subject: [Nagiosplug-devel] oddity about check_procs plugin and solaris In-Reply-To: <49CBC85E.1070009@usc.edu> References: <49CAAAC3.4010606@usc.edu> <4B5A67AF-C7CF-492A-A44C-8E8A3B67443E@opsera.com> <49CBC097.701@usc.edu> <49CBC85E.1070009@usc.edu> Message-ID: <4AF94678.8020709@aei.ca> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 26/03/09 02:24 PM, Philip Brown wrote: > BTW, there is a bug in the pst3 configuration: > > if test `isainfo -b` = 64 ; then > PST3CFLAGS="-m64" > > is inappropriate. -m64 is a compiler-specific flag. > I just did some browsing through the libtool docs. I'm stunned that with all > the OTHER flags it has, there is no "bittedness" flag yet. > > SO i guess you should do a check for CC=gcc vs CC=cc there and select > appropriate 64bit flag? Hi, A wile ago I patched configure.in to try detecting it but never sent out the patch. It seems to work well for me, unfortunately I have no sun cc nor x86-64 architectures to test with. You can test the attached patch if you wish... There should also soon be a snapshot there if you don't have autoconf/automake installed on your solaris servers (use nagios-plugins-pst3_suncc_fix.tar.gz): http://dermoth.users.sourceforge.net/snapshot/ Thanks - -- Thomas -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFK+UZ46dZ+Kt5BchYRArlpAJwMQWCakMKv70JqY2bKgerXGDmi/gCg3ctW NHa7+vIUXAICQTv4ubbnB2Y= =OkKF -----END PGP SIGNATURE----- -------------- next part -------------- A non-text attachment was scrubbed... Name: 0001-Attempt-at-detecting-64bit-compilation-flags-between.patch Type: text/x-patch Size: 2575 bytes Desc: not available URL: From noreply at sourceforge.net Tue Nov 10 12:01:20 2009 From: noreply at sourceforge.net (SourceForge.net) Date: Tue, 10 Nov 2009 11:01:20 +0000 Subject: [Nagiosplug-devel] [ nagiosplug-Bugs-2632995 ] check_procs fails on Solaris Message-ID: Bugs item #2632995, was opened at 2009-02-24 04:08 Message generated for change (Comment added) made by dermoth You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=397597&aid=2632995&group_id=29880 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: General plugin execution Group: v1.4.14 Status: Open Resolution: None Priority: 5 Private: No Submitted By: Werner (forsbring) Assigned to: Thomas Guyot-Sionnest (dermoth) Summary: check_procs fails on Solaris Initial Comment: Hi, check_procs v2019 (nagios-plugins 1.4.13) exits with "Unable to read output" on most of our Solaris8 and Solaris 10 servers (I do not have access to any Solaris9 servers). 1.4.11 works just fine. I've attached the truss output. - Werner ---------------------------------------------------------------------- >Comment By: Thomas Guyot-Sionnest (dermoth) Date: 2009-11-10 06:01 Message: So one ever replied to this. Please try the pst3_suncc_fix snapshot here (or use the attached patch 0001-Attempt-at-detecting-64bit-compilation-flags-between.patch): http://dermoth.users.sourceforge.net/snapshot/nagios-plugins-pst3_suncc_fix.tar.gz It works for me on gcc; if it work with suncc as well it will be included. Thank you ---------------------------------------------------------------------- Comment By: Thomas Guyot-Sionnest (dermoth) Date: 2009-08-05 03:05 Message: Please try the attached patch. If you don't have the required tools to run tools/setup (can be done from another machine; it doesn't have to be solaris) let me know and I'll make you a snapshot. ---------------------------------------------------------------------- Comment By: Thomas Guyot-Sionnest (dermoth) Date: 2009-03-17 03:42 Message: Sorry for the late reply... According pst3 header comment (I have no idea how it compares to "ps" though): * This executable works by reading process address structures, so needs * to be executed as root Regarding 64bits, I might be wrong but IIRC that's needed to get data about 64bit processes. Maybe that's somehow related to the root requisite as well, since it's probably a different way than "ps". I will have to look for a way to support cleanly both compilers, probably using autoconf. I'll look further into this when I can. Thanks ---------------------------------------------------------------------- Comment By: Werner (forsbring) Date: 2009-03-12 09:23 Message: Nope, not trying to run from source repository. But after looking into the buildlogs I guess I found the problem. You assume we use gcc, and the compiler option -m64 is used for pst3, which is not working with cc from older SunStudio. Why do pst3 have to be setuid root when /usr/bin/ps and /usr/ucp/ps don't? And regarding the 64-bit requirement, why? Almost no other binaries on Solaris is 64-bit. The pst3-thing seems like a ugly hack to me, sorry. :) - Werner ---------------------------------------------------------------------- Comment By: Thomas Guyot-Sionnest (dermoth) Date: 2009-02-24 04:29 Message: Thanks for the debug output. Nagios-plugins now use pst3 to get the process list and this program needs to be installed and setuid root (I think old versions of nagios-plugins used it too, so you may have it already on some servers). It looks like you're trying to run from the source repository. Be sure to install the plugins, or at least hand-install pst3 (in plugins-root/ directory, don't forget to setuit root). If you still have issues I'll be able to help you is you can send the truss output again with the option to follow forks (-f). ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=397597&aid=2632995&group_id=29880 From noreply at sourceforge.net Tue Nov 10 18:01:03 2009 From: noreply at sourceforge.net (SourceForge.net) Date: Tue, 10 Nov 2009 17:01:03 +0000 Subject: [Nagiosplug-devel] [ nagiosplug-Patches-2895334 ] Added -F configfile option to check_by_ssh Message-ID: Patches item #2895334, was opened at 2009-11-10 17:01 Message generated for change (Tracker Item Submitted) made by svennierlein You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=397599&aid=2895334&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: sni (svennierlein) Assigned to: Nobody/Anonymous (nobody) Summary: Added -F configfile option to check_by_ssh Initial Comment: This patch adds a new option to check_by_ssh. Example Commandline: ./check_by_ssh -F ~/.ssh/config -H localhost -C /bin/true Patch is against: %>./plugins/check_by_ssh -V check_by_ssh vtrunk.2272.dirty (nagios-plugins 1.4.14) The new -F option is directly passed through to ssh. >From the ssh man page: -F configfile Specifies an alternative per-user configuration file. If a configuration file is given on the command line, the system-wide configuration file (/etc/ssh/ssh_config) will be ignored. The default for the per-user configuration file is ~/.ssh/config. With such a config file, you dont have to add multiple -o options to check_by_ssh. And you can maintain your ssh configuration from one place. I would be happy to see this patch applied. (2 new tests are included) ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=397599&aid=2895334&group_id=29880 From shadhin71 at gmail.com Tue Nov 10 21:38:32 2009 From: shadhin71 at gmail.com (shadih rahman) Date: Tue, 10 Nov 2009 15:38:32 -0500 Subject: [Nagiosplug-devel] [ nagiosplug-Bugs-2632995 ] check_procs fails on Solaris In-Reply-To: References: Message-ID: <6db4a4200911101238v30a3c408te51fa3dbdf7cac0b@mail.gmail.com> Solaris 9 still having issues. ld: fatal: Symbol referencing errors. No output written to pst3 collect2: ld returned 1 exit status make[2]: *** [pst3] Error 1 make[2]: Leaving directory `/tmp/shadhintest/nagios-plugins-1.4.14-53-gc6ec4/plugins-root' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/tmp/shadhintest/nagios-plugins-1.4.14-53-gc6ec4' make: *** [all] Error 2 [sr2690 at mustard]>uname -a SunOS mustard 5.9 Generic_122300-45 sun4u sparc SUNW,UltraAX-i2 Solaris On Tue, Nov 10, 2009 at 6:01 AM, SourceForge.net wrote: > Bugs item #2632995, was opened at 2009-02-24 04:08 > Message generated for change (Comment added) made by dermoth > You can respond by visiting: > > https://sourceforge.net/tracker/?func=detail&atid=397597&aid=2632995&group_id=29880 > > Please note that this message will contain a full copy of the comment > thread, > including the initial issue submission, for this request, > not just the latest update. > Category: General plugin execution > Group: v1.4.14 > Status: Open > Resolution: None > Priority: 5 > Private: No > Submitted By: Werner (forsbring) > Assigned to: Thomas Guyot-Sionnest (dermoth) > Summary: check_procs fails on Solaris > > Initial Comment: > Hi, > > check_procs v2019 (nagios-plugins 1.4.13) exits with "Unable to read > output" on most of our Solaris8 and Solaris 10 servers (I do not have access > to any Solaris9 servers). 1.4.11 works just fine. I've attached the truss > output. > > > - Werner > > > ---------------------------------------------------------------------- > > >Comment By: Thomas Guyot-Sionnest (dermoth) > Date: 2009-11-10 06:01 > > Message: > So one ever replied to this. Please try the pst3_suncc_fix snapshot here > (or use the attached patch > 0001-Attempt-at-detecting-64bit-compilation-flags-between.patch): > > > http://dermoth.users.sourceforge.net/snapshot/nagios-plugins-pst3_suncc_fix.tar.gz > > It works for me on gcc; if it work with suncc as well it will be > included. > > Thank you > > ---------------------------------------------------------------------- > > Comment By: Thomas Guyot-Sionnest (dermoth) > Date: 2009-08-05 03:05 > > Message: > Please try the attached patch. > > If you don't have the required tools to run tools/setup (can be done from > another machine; it doesn't have to be solaris) let me know and I'll make > you a snapshot. > > ---------------------------------------------------------------------- > > Comment By: Thomas Guyot-Sionnest (dermoth) > Date: 2009-03-17 03:42 > > Message: > Sorry for the late reply... According pst3 header comment (I have no idea > how it compares to "ps" though): > * This executable works by reading process address structures, so needs > * to be executed as root > > Regarding 64bits, I might be wrong but IIRC that's needed to get data > about 64bit processes. Maybe that's somehow related to the root requisite > as well, since it's probably a different way than "ps". > > I will have to look for a way to support cleanly both compilers, probably > using autoconf. I'll look further into this when I can. > > Thanks > > ---------------------------------------------------------------------- > > Comment By: Werner (forsbring) > Date: 2009-03-12 09:23 > > Message: > Nope, not trying to run from source repository. But after looking into the > buildlogs I guess I found the problem. You assume we use gcc, and the > compiler option -m64 is used for pst3, which is not working with cc from > older SunStudio. > > Why do pst3 have to be setuid root when /usr/bin/ps and /usr/ucp/ps don't? > And regarding the 64-bit requirement, why? Almost no other binaries on > Solaris is 64-bit. The pst3-thing seems like a ugly hack to me, sorry. :) > > > - Werner > > ---------------------------------------------------------------------- > > Comment By: Thomas Guyot-Sionnest (dermoth) > Date: 2009-02-24 04:29 > > Message: > Thanks for the debug output. Nagios-plugins now use pst3 to get the process > list and this program needs to be installed and setuid root (I think old > versions of nagios-plugins used it too, so you may have it already on some > servers). > > It looks like you're trying to run from the source repository. Be sure to > install the plugins, or at least hand-install pst3 (in plugins-root/ > directory, don't forget to setuit root). > > If you still have issues I'll be able to help you is you can send the > truss output again with the option to follow forks (-f). > > ---------------------------------------------------------------------- > > You can respond by visiting: > > https://sourceforge.net/tracker/?func=detail&atid=397597&aid=2632995&group_id=29880 > > > ------------------------------------------------------------------------------ > Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day > trial. Simplify your report design, integration and deployment - and focus > on > what you do best, core application coding. Discover what's new with > Crystal Reports now. http://p.sf.net/sfu/bobj-july > _______________________________________________________ > Nagios Plugin Development Mailing List > Nagiosplug-devel at lists.sourceforge.net > Unsubscribe at > https://lists.sourceforge.net/lists/listinfo/nagiosplug-devel > ::: Please include plugins version (-v) and OS when reporting any issue. > ::: Messages without supporting info will risk being sent to /dev/null > -- Cordially, Shadhin Rahman -------------- next part -------------- An HTML attachment was scrubbed... URL: From noreply at sourceforge.net Wed Nov 11 21:37:10 2009 From: noreply at sourceforge.net (SourceForge.net) Date: Wed, 11 Nov 2009 20:37:10 +0000 Subject: [Nagiosplug-devel] [ nagiosplug-Bugs-2896201 ] check_ping depends on iputils-ping Message-ID: Bugs item #2896201, was opened at 2009-11-11 21:37 Message generated for change (Tracker Item Submitted) made by cyco_dd You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=397597&aid=2896201&group_id=29880 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: General plugin execution Group: v1.4.14 Status: Open Resolution: None Priority: 5 Private: No Submitted By: Jan Wagner (cyco_dd) Assigned to: Nobody/Anonymous (nobody) Summary: check_ping depends on iputils-ping Initial Comment: The following Bugreport we got against our debian package: Hi, it seems that the nagios related packages need an ping command available. They choose iputils-ping, which is rather linux specific. Could be possible to switch (at least on non-linux) to inetutils-ping (already available) or fping (modulo #555398 available). It will help to kfreebsd-i386, kfreebsd-amd64 and hurd architectures. Thanks for considering it. You can track the bugreport via http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=555532 check_ping could maybe rewritten/patched to use liboping [1]? Thanks and kind regards, Jan. [1] http://verplant.org/liboping/ ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=397597&aid=2896201&group_id=29880 From noreply at sourceforge.net Wed Nov 11 23:29:14 2009 From: noreply at sourceforge.net (SourceForge.net) Date: Wed, 11 Nov 2009 22:29:14 +0000 Subject: [Nagiosplug-devel] [ nagiosplug-Bugs-2896201 ] check_ping depends on iputils-ping Message-ID: Bugs item #2896201, was opened at 2009-11-11 15:37 Message generated for change (Comment added) made by dermoth You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=397597&aid=2896201&group_id=29880 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: General plugin execution Group: v1.4.14 Status: Open Resolution: None Priority: 5 Private: No Submitted By: Jan Wagner (cyco_dd) >Assigned to: Thomas Guyot-Sionnest (dermoth) Summary: check_ping depends on iputils-ping Initial Comment: The following Bugreport we got against our debian package: Hi, it seems that the nagios related packages need an ping command available. They choose iputils-ping, which is rather linux specific. Could be possible to switch (at least on non-linux) to inetutils-ping (already available) or fping (modulo #555398 available). It will help to kfreebsd-i386, kfreebsd-amd64 and hurd architectures. Thanks for considering it. You can track the bugreport via http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=555532 check_ping could maybe rewritten/patched to use liboping [1]? Thanks and kind regards, Jan. [1] http://verplant.org/liboping/ ---------------------------------------------------------------------- >Comment By: Thomas Guyot-Sionnest (dermoth) Date: 2009-11-11 17:29 Message: Normally configure decides which ping command and syntax to use, so it really depend on which packages you have installed. You can force the command to use with --with-ping-command=SYNTAX and --with-ping6-command=SYNTAX. An easy way to find the syntax it to look at a generated config.h when only the wanted ping commands are available. Search for #define PING_COMMAND and #define PING6_COMMAND. Let me know if you have any problem with specific ping variants. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=397597&aid=2896201&group_id=29880 From gr at bitbyte.eu Thu Nov 12 13:59:32 2009 From: gr at bitbyte.eu (Gernot Riedel) Date: Thu, 12 Nov 2009 13:59:32 +0100 Subject: [Nagiosplug-devel] check_hpjd does not work Message-ID: <4AFC06B4.3010102@bitbyte.eu> Hello i?m using NAGIOS 3.2.0 with Plugins 1.4.13 and NRPE 2.12 on a SUSE SLES 10 machine. I want to check a printer HP Deskjez 9640. An other HP Laserjet 4 works fine with check_hpjd. A command like snmpwalk -v 1 -c public mib-2.43.18.1.1.8.1.4 shows the status of the toner as welll. But when i send the command check_hpjd -H -C public i get the output Error in packet () CAn anybody help me? -- Freundliche Gr??e, Dr. Gernot Riedel bit & byte GmbH, EDV-Planung und Beratung ePost: gr at bitbyte.eu ----------------------------------------- bit & byte GmbH, EDV-Planung und Beratung Sitz der Gesellschaft: 86807 Buchloe Gesch?ftsf?hrer: Andreas Trunk Handelsregister: Kempten HRB 8024 ----------------------------------------- From dermoth at aei.ca Thu Nov 12 14:31:21 2009 From: dermoth at aei.ca (Thomas Guyot-Sionnest) Date: Thu, 12 Nov 2009 08:31:21 -0500 Subject: [Nagiosplug-devel] check_hpjd does not work In-Reply-To: <4AFC06B4.3010102@bitbyte.eu> References: <4AFC06B4.3010102@bitbyte.eu> Message-ID: <4AFC0E29.1020104@aei.ca> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 12/11/09 07:59 AM, Gernot Riedel wrote: > Hello > > i?m using NAGIOS 3.2.0 with Plugins 1.4.13 and NRPE 2.12 on > a SUSE SLES 10 machine. > I want to check a printer HP Deskjez 9640. > An other HP Laserjet 4 works fine with check_hpjd. > A command like snmpwalk -v 1 -c public > mib-2.43.18.1.1.8.1.4 > shows the status of the toner as welll. > But when i send the command check_hpjd -H -C public > i get the output > Error in packet () > CAn anybody help me? The most likely causes are: 1. The printer do not support SNMP 2. The printer is configured with a different SNMP community 3. The printer has IP-based access lists or is behind a firewall - -- Thomas -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFK/A4p6dZ+Kt5BchYRAkotAJ9HdQJMqPTX5R9TJr0sQKxm8OpepACg0+iI uJEHuy9MEwWUbIxSwFSYu80= =frBO -----END PGP SIGNATURE----- From shadhin71 at gmail.com Fri Nov 13 20:54:09 2009 From: shadhin71 at gmail.com (shadih rahman) Date: Fri, 13 Nov 2009 14:54:09 -0500 Subject: [Nagiosplug-devel] Preferred method for perl plugin Message-ID: <6db4a4200911131154i18bb0eese5bffea7e0187920@mail.gmail.com> What is the preferred method of using Nagios exit code? Should I use the utils.pm that is distributed with Nagios plugin package? or should I use the cpan Nagios::Plugins ? Please advise on this. Thanks -- Cordially, Shadhin Rahman -------------- next part -------------- An HTML attachment was scrubbed... URL: From Guillaume.Rousse at inria.fr Sun Nov 15 19:59:51 2009 From: Guillaume.Rousse at inria.fr (Guillaume Rousse) Date: Sun, 15 Nov 2009 19:59:51 +0100 Subject: [Nagiosplug-devel] Preferred method for perl plugin In-Reply-To: <6db4a4200911131154i18bb0eese5bffea7e0187920@mail.gmail.com> References: <6db4a4200911131154i18bb0eese5bffea7e0187920@mail.gmail.com> Message-ID: <4B004FA7.4060803@inria.fr> shadih rahman a ?crit : > What is the preferred method of using Nagios exit code? Should I use > the utils.pm that is distributed with Nagios plugin > package? or should I use the cpan Nagios::Plugins ? Please advise on > this. Thanks There no actual 'prefered' method, it's up to you. Using 'utils.pm' requires you to know the physical location of this file, which may change between hosts. And it doesn't bring much more than constants for the 4 exist status. Using Nagios::Plugin change the first constraint to ensure it is installed on your target host, but you don't need to know where it is exactly. And it brings much more than 4 constants... All in all, if your only need is to use named constants instead of numeric values, you can also just hardcode them in your plugin, they don't change too often... -- BOFH excuse #119: evil hackers from Serbia. From noreply at sourceforge.net Tue Nov 17 11:19:15 2009 From: noreply at sourceforge.net (SourceForge.net) Date: Tue, 17 Nov 2009 10:19:15 +0000 Subject: [Nagiosplug-devel] [ nagiosplug-Patches-2898995 ] New parameter for check_nwstat Message-ID: Patches item #2898995, was opened at 2009-11-17 11:19 Message generated for change (Tracker Item Submitted) made by jottschi You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=397599&aid=2898995&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: Ralph Gottschalkson (jottschi) Assigned to: Nobody/Anonymous (nobody) Summary: New parameter for check_nwstat Initial Comment: This adds the new VPU parameter to the check_nwstat plugin. This parameter returns the percentage used space on a Netware volume. Now you can monitor your Netware volumes easy. We use it with a warning 85% and critical 90%. eg: check_nwstat -H your.netware.host -v VPUvol1 -c 85 -w 90 returns 324653 MB (95%) used on volume vol1 - total 340212 MB|Used space in percent on vol1=95;90;80;0;100. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=397599&aid=2898995&group_id=29880 From noreply at sourceforge.net Tue Nov 17 12:35:06 2009 From: noreply at sourceforge.net (SourceForge.net) Date: Tue, 17 Nov 2009 11:35:06 +0000 Subject: [Nagiosplug-devel] [ nagiosplug-Bugs-2872843 ] check_disk reports disk usage on bind mounted volumes Message-ID: Bugs item #2872843, was opened at 2009-10-05 04:44 Message generated for change (Settings changed) made by dermoth You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=397597&aid=2872843&group_id=29880 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: General plugin execution >Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Troy Rose (troyjrose) Assigned to: Nobody/Anonymous (nobody) Summary: check_disk reports disk usage on bind mounted volumes Initial Comment: The check disk usage reports disk usage on bind mounted filesystems when specifying local only filesystems. This in itself isn't a problem but the problem comes when the filesystem being bind mounted is not a local filesystem I'm using the latest version of the nagios plugins (1.14). I'm submitted a patch to check disk that allows excluding of partitions that match certain mount options. ---------------------------------------------------------------------- Comment By: Troy Rose (troyjrose) Date: 2009-10-07 05:14 Message: I've noticed that on RHEL4 systems the bind mounts are not set as filesystem type "none", and are still displayed. So I've added in another macro to mountlist.c to fix this and check for a bind mounted option, and set it as a dummy filesystem. I've attached the patch. ---------------------------------------------------------------------- Comment By: Troy Rose (troyjrose) Date: 2009-10-07 03:56 Message: Okay, I've gotten to the bottom of it. There is an almost unsed static variable in the check_disk plugin which is used to display or not display dummy filesystems (like proc etc). So, setting that to disabled, everything works as expected, and bind filesystesm (which show up as type "none") dont get displayed anymore. ---------------------------------------------------------------------- Comment By: Troy Rose (troyjrose) Date: 2009-10-05 04:46 Message: Oopps I meant I'm using the latest public release 1.4.14 of the nagios-plugins. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=397597&aid=2872843&group_id=29880 From noreply at sourceforge.net Tue Nov 17 12:35:06 2009 From: noreply at sourceforge.net (SourceForge.net) Date: Tue, 17 Nov 2009 11:35:06 +0000 Subject: [Nagiosplug-devel] [ nagiosplug-Bugs-2832884 ] translation of --help broken Message-ID: Bugs item #2832884, was opened at 2009-08-05 18:48 Message generated for change (Settings changed) made by dermoth You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=397597&aid=2832884&group_id=29880 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Interface (example) >Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Jan Wagner (cyco_dd) Assigned to: Nobody/Anonymous (nobody) Summary: translation of --help broken Initial Comment: Hi there, looks like the translation of the help is somewhat broken in general. At least for LANG=de_DE.UTF-8, LANG=fr_FR.UTF-8 and check_dhcp, check_disk, where I can confirm the problem. The following Bugreport we got against our debian package: On my french system : ====================================== [root at kayak]:~ # /usr/lib/nagios/plugins/check_dhcp --help check_dhcp v1991 (nagios-plugins 1.4.12) Copyright (c) 2001-2004 Ethan Galstad (nagios at nagios.org) Copyright (c) 2001-2007 Nagios Plugin Development Team Ce plugin teste la disponibilit? de serveurs DHCP dans un r?seau. Utilisation: check_dhcp [-v] [-u] [-s serverip] [-r requestedip] [-t timeout] [-i interface] [-m mac] Options: -h, --help Print detailed help screen -V, --version Print version information Project-Id-Version: fr Report-Msgid-Bugs-To: nagiosplug-devel at lists.sourceforge.net POT-Creation-Date: 2008-05-27 23:06+0100 PO-Revision-Date: 2007-12-10 02:10-0500 Last-Translator: Thomas Guyot-Sionnest Language-Team: MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Plural-Forms: nplurals=2; plural=(n != 1); X-Generator: KBabel 1.11.4 -v, --verbose Show details for command-line debugging (Nagios may truncate output) -s, --serverip=IPADDRESS IP address of DHCP server that we must hear from -r, --requestedip=IPADDRESS IP address that should be offered by at least one DHCP server -t, --timeout=INTEGER Seconds to wait for DHCPOFFER before timeout occurs -i, --interface=STRING Interface to to use for listening (i.e. eth0) -m, --mac=STRING MAC address to use in the DHCP request -u, --unicast Unicast testing: mimic a DHCP relay, requires -s Send email to nagios-users at lists.sourceforge.net if you have questions regarding use of this software. To submit patches or suggest improvements, send email to nagiosplug-devel at lists.sourceforge.net ======================================= There is the translator info into the translation... You can track the bugreport via http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=522631 Thanks and kind regards, Jan. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=397597&aid=2832884&group_id=29880 From noreply at sourceforge.net Tue Nov 17 12:35:06 2009 From: noreply at sourceforge.net (SourceForge.net) Date: Tue, 17 Nov 2009 11:35:06 +0000 Subject: [Nagiosplug-devel] [ nagiosplug-Bugs-2896201 ] check_ping depends on iputils-ping Message-ID: Bugs item #2896201, was opened at 2009-11-11 15:37 Message generated for change (Settings changed) made by dermoth You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=397597&aid=2896201&group_id=29880 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: General plugin execution >Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Jan Wagner (cyco_dd) Assigned to: Thomas Guyot-Sionnest (dermoth) Summary: check_ping depends on iputils-ping Initial Comment: The following Bugreport we got against our debian package: Hi, it seems that the nagios related packages need an ping command available. They choose iputils-ping, which is rather linux specific. Could be possible to switch (at least on non-linux) to inetutils-ping (already available) or fping (modulo #555398 available). It will help to kfreebsd-i386, kfreebsd-amd64 and hurd architectures. Thanks for considering it. You can track the bugreport via http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=555532 check_ping could maybe rewritten/patched to use liboping [1]? Thanks and kind regards, Jan. [1] http://verplant.org/liboping/ ---------------------------------------------------------------------- Comment By: Thomas Guyot-Sionnest (dermoth) Date: 2009-11-11 17:29 Message: Normally configure decides which ping command and syntax to use, so it really depend on which packages you have installed. You can force the command to use with --with-ping-command=SYNTAX and --with-ping6-command=SYNTAX. An easy way to find the syntax it to look at a generated config.h when only the wanted ping commands are available. Search for #define PING_COMMAND and #define PING6_COMMAND. Let me know if you have any problem with specific ping variants. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=397597&aid=2896201&group_id=29880 From noreply at sourceforge.net Tue Nov 17 12:35:06 2009 From: noreply at sourceforge.net (SourceForge.net) Date: Tue, 17 Nov 2009 11:35:06 +0000 Subject: [Nagiosplug-devel] [ nagiosplug-Bugs-2632995 ] check_procs fails on Solaris Message-ID: Bugs item #2632995, was opened at 2009-02-24 04:08 Message generated for change (Settings changed) made by dermoth You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=397597&aid=2632995&group_id=29880 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: General plugin execution >Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Werner (forsbring) Assigned to: Thomas Guyot-Sionnest (dermoth) Summary: check_procs fails on Solaris Initial Comment: Hi, check_procs v2019 (nagios-plugins 1.4.13) exits with "Unable to read output" on most of our Solaris8 and Solaris 10 servers (I do not have access to any Solaris9 servers). 1.4.11 works just fine. I've attached the truss output. - Werner ---------------------------------------------------------------------- Comment By: Thomas Guyot-Sionnest (dermoth) Date: 2009-11-10 06:01 Message: So one ever replied to this. Please try the pst3_suncc_fix snapshot here (or use the attached patch 0001-Attempt-at-detecting-64bit-compilation-flags-between.patch): http://dermoth.users.sourceforge.net/snapshot/nagios-plugins-pst3_suncc_fix.tar.gz It works for me on gcc; if it work with suncc as well it will be included. Thank you ---------------------------------------------------------------------- Comment By: Thomas Guyot-Sionnest (dermoth) Date: 2009-08-05 03:05 Message: Please try the attached patch. If you don't have the required tools to run tools/setup (can be done from another machine; it doesn't have to be solaris) let me know and I'll make you a snapshot. ---------------------------------------------------------------------- Comment By: Thomas Guyot-Sionnest (dermoth) Date: 2009-03-17 03:42 Message: Sorry for the late reply... According pst3 header comment (I have no idea how it compares to "ps" though): * This executable works by reading process address structures, so needs * to be executed as root Regarding 64bits, I might be wrong but IIRC that's needed to get data about 64bit processes. Maybe that's somehow related to the root requisite as well, since it's probably a different way than "ps". I will have to look for a way to support cleanly both compilers, probably using autoconf. I'll look further into this when I can. Thanks ---------------------------------------------------------------------- Comment By: Werner (forsbring) Date: 2009-03-12 09:23 Message: Nope, not trying to run from source repository. But after looking into the buildlogs I guess I found the problem. You assume we use gcc, and the compiler option -m64 is used for pst3, which is not working with cc from older SunStudio. Why do pst3 have to be setuid root when /usr/bin/ps and /usr/ucp/ps don't? And regarding the 64-bit requirement, why? Almost no other binaries on Solaris is 64-bit. The pst3-thing seems like a ugly hack to me, sorry. :) - Werner ---------------------------------------------------------------------- Comment By: Thomas Guyot-Sionnest (dermoth) Date: 2009-02-24 04:29 Message: Thanks for the debug output. Nagios-plugins now use pst3 to get the process list and this program needs to be installed and setuid root (I think old versions of nagios-plugins used it too, so you may have it already on some servers). It looks like you're trying to run from the source repository. Be sure to install the plugins, or at least hand-install pst3 (in plugins-root/ directory, don't forget to setuit root). If you still have issues I'll be able to help you is you can send the truss output again with the option to follow forks (-f). ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=397597&aid=2632995&group_id=29880 From noreply at sourceforge.net Tue Nov 17 12:35:45 2009 From: noreply at sourceforge.net (SourceForge.net) Date: Tue, 17 Nov 2009 11:35:45 +0000 Subject: [Nagiosplug-devel] [ nagiosplug-Patches-2898995 ] New parameter for check_nwstat Message-ID: Patches item #2898995, was opened at 2009-11-17 05:19 Message generated for change (Settings changed) made by dermoth You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=397599&aid=2898995&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: Ralph Gottschalkson (jottschi) Assigned to: Nobody/Anonymous (nobody) Summary: New parameter for check_nwstat Initial Comment: This adds the new VPU parameter to the check_nwstat plugin. This parameter returns the percentage used space on a Netware volume. Now you can monitor your Netware volumes easy. We use it with a warning 85% and critical 90%. eg: check_nwstat -H your.netware.host -v VPUvol1 -c 85 -w 90 returns 324653 MB (95%) used on volume vol1 - total 340212 MB|Used space in percent on vol1=95;90;80;0;100. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=397599&aid=2898995&group_id=29880 From cbaker at nuvox.com Thu Nov 19 22:38:47 2009 From: cbaker at nuvox.com (Charles H. Baker) Date: Thu, 19 Nov 2009 16:38:47 -0500 Subject: [Nagiosplug-devel] check_swap on solaris 10 Message-ID: <1258666727.27389.11.camel@rain> It appears that check_swap is not working correctly on Solaris 10. It reports 100% free even when it is clear that swap is being used. [Thu Nov 19 16:25:44 root at bulldog: libexec] # ./check_swap.csw -V check_swap v1859 (nagios-plugins 1.4.11) [Thu Nov 19 16:25:48 root at bulldog: libexec] # ./check_swap.csw -w 20% -c 10% SWAP OK - 100% free (69800 MB out of 69800 MB) | swap=69800MB;13960;6980;0;69800 [Thu Nov 19 16:25:50 root at bulldog: libexec] # swap -s total: 17959192k bytes allocated + 632304k reserved = 18591496k used, 100584528k available [Thu Nov 19 16:25:54 root at bulldog: libexec] # This email and any attachments ("Message") may contain legally privileged and/or confidential information. If you are not the addressee, or if this Message has been addressed to you in error, you are not authorized to read, copy, or distribute it, and we ask that you please delete it (including all copies) and notify the sender by return email. Delivery of this Message to any person other than the intended recipient(s) shall not be deemed a waiver of confidentiality and/or a privilege. From cbaker at nuvox.com Thu Nov 19 23:04:06 2009 From: cbaker at nuvox.com (Charles H. Baker) Date: Thu, 19 Nov 2009 17:04:06 -0500 Subject: [Nagiosplug-devel] configure nagios plugins for building on solaris 10 -> checking for socklen_t... no Message-ID: <1258668246.27389.12.camel@rain> I've tried to compile nagios plugins 1.4.13 and 1.4.14 on Sparc Solaris 10. When I run configure it halts with the following error. Has anyone encountered this? Fixed it? I've googled but found no definitive answer. Thanks. checking for socklen_t... no checking for socklen_t equivalent... configure: error: Cannot find a type to use in place of socklen_t The config.log shows In file included from /usr/include/sys/socket.h:45, from conftest.c:54: /usr/include/netinet/in.h:54: error: expected '=', ',', ';', 'asm' or '__attribute__' before 'socklen_t' /usr/include/netinet/in.h:60: error: storage class specified for parameter 'Psocklen_t' In file included from /usr/include/sys/t_lock.h:18, from /usr/include/sys/vnode.h:40, from /usr/include/sys/stream.h:22, from /usr/include/netinet/in.h:66, from /usr/include/sys/socket.h:45, from conftest.c:54: /usr/include/sys/machlock.h:37: error: expected '=', ',', ';', 'asm' or '__attribute__' before 'disp_lock_t' /usr/include/sys/machlock.h:56: error: storage class specified for parameter 'hres_lock' In file included from /usr/include/sys/t_lock.h:19, from /usr/include/sys/vnode.h:40, from /usr/include/sys/stream.h:22, from /usr/include/netinet/in.h:66, from /usr/include/sys/socket.h:45, from conftest.c:54: /usr/include/sys/param.h:445: error: storage class specified for parameter '_sysconf' /usr/include/sys/param.h:445: error: redefinition of parameter '_sysconf' /usr/include/sys/iso/signal_iso.h:83: error: previous definition of '_sysconf' was here In file included from /usr/include/sys/t_lock.h:20, from /usr/include/sys/vnode.h:40, from /usr/include/sys/stream.h:22, from /usr/include/netinet/in.h:66, from /usr/include/sys/socket.h:45, from conftest.c:54: /usr/include/sys/mutex.h:44: error: storage class specified for parameter 'kmutex_type_t' /usr/include/sys/mutex.h:52: error: storage class specified for parameter 'kmutex_t' In file included from /usr/include/sys/t_lock.h:21, from /usr/include/sys/vnode.h:40, from /usr/include/sys/stream.h:22, from /usr/include/netinet/in.h:66, from /usr/include/sys/socket.h:45, from conftest.c:54: /usr/include/sys/rwlock.h:26: error: storage class specified for parameter 'krw_type_t' /usr/include/sys/rwlock.h:31: error: storage class specified for parameter 'krw_t' /usr/include/sys/rwlock.h:35: error: storage class specified for parameter 'krwlock_t' In file included from /usr/include/sys/t_lock.h:22, from /usr/include/sys/vnode.h:40, from /usr/include/sys/stream.h:22, from /usr/include/netinet/in.h:66, from /usr/include/sys/socket.h:45, from conftest.c:54: /usr/include/sys/semaphore.h:28: error: storage class specified for parameter 'ksema_type_t' /usr/include/sys/semaphore.h:32: error: storage class specified for parameter 'ksema_t' In file included from /usr/include/sys/t_lock.h:23, from /usr/include/sys/vnode.h:40, from /usr/include/sys/stream.h:22, from /usr/include/netinet/in.h:66, from /usr/include/sys/socket.h:45, This email and any attachments ("Message") may contain legally privileged and/or confidential information. If you are not the addressee, or if this Message has been addressed to you in error, you are not authorized to read, copy, or distribute it, and we ask that you please delete it (including all copies) and notify the sender by return email. Delivery of this Message to any person other than the intended recipient(s) shall not be deemed a waiver of confidentiality and/or a privilege. From noreply at sourceforge.net Fri Nov 20 17:31:41 2009 From: noreply at sourceforge.net (SourceForge.net) Date: Fri, 20 Nov 2009 16:31:41 +0000 Subject: [Nagiosplug-devel] [ nagiosplug-Bugs-2901240 ] check_snmp has problem parsing snmpget output Message-ID: Bugs item #2901240, was opened at 2009-11-20 16:31 Message generated for change (Tracker Item Submitted) made by oernii You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=397597&aid=2901240&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: Parsing problem Group: Release (specify) Status: Open Resolution: None Priority: 5 Private: No Submitted By: Ernest Beinrohr (oernii) Assigned to: Nobody/Anonymous (nobody) Summary: check_snmp has problem parsing snmpget output Initial Comment: Hi, I have a command like: $ check_snmp -P 3 -U username -A password -X password -a MD5 -H server.domain.com -o host.hrSystem.hrSystemProcesses.0 -L authPriv -v /usr/bin/snmpget -t 1 -r 5 -m ALL -v 3 -l authPriv -a MD5 -u username -A password -x DES -X password server.domain.com:161 host.hrSystem.hrSystemProcesses.0 HOST-RESOURCES-MIB::hrSystemProcesses.0 98 SNMP problem - No data received from host CMD: /usr/bin/snmpget -t 1 -r 5 -m ALL -v 3 [authpriv] server.domain.com:161 host.hrSystem.hrSystemProcesses.0 as you can see snmpget RETURNS a value of 98, but check_snmp fails to see it somehow. PS: check_snmp v2021 (nagios-plugins 1.4.13) Also I checked out the current GIT repo and build it. Another error: /usr/bin/snmpget -t 1 -r 5 -m ALL -v 3 [authpriv] server:161 host.hrSystem.hrSystemProcesses.0 HOST-RESOURCES-MIB::hrSystemProcesses.0 100 SNMP UNKNOWN - | ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=397597&aid=2901240&group_id=29880 From noreply at sourceforge.net Sun Nov 22 17:18:00 2009 From: noreply at sourceforge.net (SourceForge.net) Date: Sun, 22 Nov 2009 16:18:00 +0000 Subject: [Nagiosplug-devel] [ nagiosplug-Bugs-2902089 ] Move nagios_die out of N::P::Thresholds Message-ID: Bugs item #2902089, was opened at 2009-11-22 17:18 Message generated for change (Tracker Item Submitted) made by datamuc You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=397597&aid=2902089&group_id=29880 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Interface (example) Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: DaTa (datamuc) Assigned to: Nobody/Anonymous (nobody) Summary: Move nagios_die out of N::P::Thresholds Initial Comment: N::P::Thresholds uses nagios_die. This is suboptimal for using that Class in other Projects. Though one can set N::P::F::_use_die, but then $@ contains get_shortname and a STATUS_TEXT, which feels odd. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=397597&aid=2902089&group_id=29880 From noreply at sourceforge.net Sun Nov 22 17:29:08 2009 From: noreply at sourceforge.net (SourceForge.net) Date: Sun, 22 Nov 2009 16:29:08 +0000 Subject: [Nagiosplug-devel] [ nagiosplug-Bugs-2902089 ] Move nagios_die out of N::P::Thresholds Message-ID: Bugs item #2902089, was opened at 2009-11-22 11:18 Message generated for change (Comment added) made by dermoth You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=397597&aid=2902089&group_id=29880 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Interface (example) Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: DaTa (datamuc) Assigned to: Nobody/Anonymous (nobody) Summary: Move nagios_die out of N::P::Thresholds Initial Comment: N::P::Thresholds uses nagios_die. This is suboptimal for using that Class in other Projects. Though one can set N::P::F::_use_die, but then $@ contains get_shortname and a STATUS_TEXT, which feels odd. ---------------------------------------------------------------------- >Comment By: Thomas Guyot-Sionnest (dermoth) Date: 2009-11-22 11:29 Message: Can't you just trap it? IIRC nagios_die uses die() to terminate the program, and die can be trapped with $SIG{__DIE__}. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=397597&aid=2902089&group_id=29880 From noreply at sourceforge.net Sun Nov 22 21:25:04 2009 From: noreply at sourceforge.net (SourceForge.net) Date: Sun, 22 Nov 2009 20:25:04 +0000 Subject: [Nagiosplug-devel] [ nagiosplug-Bugs-2902089 ] Move nagios_die out of N::P::Thresholds Message-ID: Bugs item #2902089, was opened at 2009-11-22 17:18 Message generated for change (Comment added) made by datamuc You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=397597&aid=2902089&group_id=29880 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Interface (example) Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: DaTa (datamuc) Assigned to: Nobody/Anonymous (nobody) Summary: Move nagios_die out of N::P::Thresholds Initial Comment: N::P::Thresholds uses nagios_die. This is suboptimal for using that Class in other Projects. Though one can set N::P::F::_use_die, but then $@ contains get_shortname and a STATUS_TEXT, which feels odd. ---------------------------------------------------------------------- >Comment By: DaTa (datamuc) Date: 2009-11-22 21:25 Message: That's the point, nagios_die only uses die, if $Nagios::Plugin::Functions::_use_die is true, otherwise it calls nagios_exit. And when you do that, $@ contains get_shortname and a STATUS_TEXT. i.e.: Nagios::Plugin:Thresholds->new(warning => 'x:y'); throws "NAGIOS-PLUGIN-01 UNKNOWN - Cannot parse warning range: 'x:y'". IMHO, it should die with "Cannot parse warning range: 'x:y'" without "NAGIOS-PLUGIN01 UNKNOWN -". This should be added as late as possible. This is what my patch does. Well, it's just my opinion. Close with "Wont Fix" if it's not your point of view. ---------------------------------------------------------------------- Comment By: Thomas Guyot-Sionnest (dermoth) Date: 2009-11-22 17:29 Message: Can't you just trap it? IIRC nagios_die uses die() to terminate the program, and die can be trapped with $SIG{__DIE__}. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=397597&aid=2902089&group_id=29880 From noreply at sourceforge.net Mon Nov 23 16:47:05 2009 From: noreply at sourceforge.net (SourceForge.net) Date: Mon, 23 Nov 2009 15:47:05 +0000 Subject: [Nagiosplug-devel] [ nagiosplug-Bugs-2896201 ] check_ping depends on iputils-ping Message-ID: Bugs item #2896201, was opened at 2009-11-11 21:37 Message generated for change (Comment added) made by cyco_dd You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=397597&aid=2896201&group_id=29880 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: General plugin execution Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Jan Wagner (cyco_dd) Assigned to: Thomas Guyot-Sionnest (dermoth) Summary: check_ping depends on iputils-ping Initial Comment: The following Bugreport we got against our debian package: Hi, it seems that the nagios related packages need an ping command available. They choose iputils-ping, which is rather linux specific. Could be possible to switch (at least on non-linux) to inetutils-ping (already available) or fping (modulo #555398 available). It will help to kfreebsd-i386, kfreebsd-amd64 and hurd architectures. Thanks for considering it. You can track the bugreport via http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=555532 check_ping could maybe rewritten/patched to use liboping [1]? Thanks and kind regards, Jan. [1] http://verplant.org/liboping/ ---------------------------------------------------------------------- >Comment By: Jan Wagner (cyco_dd) Date: 2009-11-23 16:47 Message: Unfortunately I have. :( Maybe you can have a look: normal debian package - using iputils-ping and compile following flags: --with-ping-command="/bin/ping -n -U -w %d -c %d %s" \ --with-ping6-command="/bin/ping6 -n -U -w %d -c %d %s" \ sid:~# /usr/lib/nagios/plugins/check_ping 127.0.0.1 -w 2,20% -c 5,30% PING OK - Packet loss = 0%, RTA = 0.00 ms| rta=0.000000ms;2.000000;5.000000;0.000000 pl=0%;20;30;0 Okay ... thats fine, like always. ---- pc1 - using iputils-ping and following compile flags: --with-ping-command="/bin/ping -n -c %d %s" \ --with-ping6-command="/bin/ping6 -n -c %d %s" \ sid:/tmp# LANG=C /usr/lib/nagios/plugins/check_ping 127.0.0.1 -w 2,20% -c 5,30% Speicherzugriffsfehler Okay ... here are just the ping commands wrong ---- pc2 - using iputils-ping and without specific compile flags (iputils-ping installed at compile time), but: checking for ICMP ping syntax... /bin/ping -n -U -w %d -c %d %s checking for ICMPv6 ping syntax... /bin/ping6 -n -U -w %d -c %d %s sid:/tmp# LANG=C /usr/lib/nagios/plugins/check_ping 127.0.0.1 -w 2,20% -c 5,30% PING OK - Packet loss = 0%, RTA = 0.00 ms| rta=0.000000ms;2.000000;5.000000;0.000000 pl=0%;20;30;0 Thats also fine, the commands are autodetected. ---- pc3 - using inetutils-ping and without specific compile flags (inetutils-ping installed at compile time), but: checking for ICMP ping syntax... /bin/ping -n -c %d %s checking for ICMPv6 ping syntax... /bin/ping6 -n -c %d %s sid:/tmp# LANG=C /usr/lib/nagios/plugins/check_ping 127.0.0.1 -w 2,20% -c 5,30% PING OK - Packet loss = 0%, RTA = 0.00 ms| rta=0.000000ms;2.000000;5.000000;0.000000 pl=0%;20;30;0 Looks great, command are autodetected and inetutils-ping works ---- pc4 - using inetutils-ping and the following compile flags (inetutils-ping NOT installed at compile time): --with-ping6-command="/bin/ping6 -n -c %d %s" \ --with-ping-command="/bin/ping -n -c %d %s" \ sid:/tmp# LANG=C /usr/lib/nagios/plugins/check_ping 127.0.0.1 -w 2,20% -c 5,30% Speicherzugriffsfehler This is the point I don't get. I'm using the same commands like the once when they where autodetected, but check_ping segfaults .... I'm missing something? Thanks for your help, Jan. ---------------------------------------------------------------------- Comment By: Thomas Guyot-Sionnest (dermoth) Date: 2009-11-11 23:29 Message: Normally configure decides which ping command and syntax to use, so it really depend on which packages you have installed. You can force the command to use with --with-ping-command=SYNTAX and --with-ping6-command=SYNTAX. An easy way to find the syntax it to look at a generated config.h when only the wanted ping commands are available. Search for #define PING_COMMAND and #define PING6_COMMAND. Let me know if you have any problem with specific ping variants. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=397597&aid=2896201&group_id=29880 From bruno.grondin at fr.bertrandt.com Wed Nov 25 17:45:28 2009 From: bruno.grondin at fr.bertrandt.com (Bruno Grondin) Date: Wed, 25 Nov 2009 17:45:28 +0100 Subject: [Nagiosplug-devel] TR: Check_snmp Problem Message-ID: Dear Support, I'm using the new check_snmp plugin (1.4.14) and I'm having a problem with it. I'm using the verbose mode for debugging (-v options). I obtain the following result below [root at YEN ~]# check_snmp -H 192.168.20.227 -C public -o 1.3.6.1.4.1.3854.1.2.2.1.16.1.3.0 -l Temperature -v /usr/bin/snmpget -t 1 -r 5 -m '' -v 1 [authpriv] 192.168.20.227:161 1.3.6.1.4.1.3854.1.2.2.1.16.1.3.0 iso.3.6.1.4.1.3854.1.2.2.1.16.1.3.0 17 Temperature UNKNOWN - | I can see that snmpget is OK because it return 17 which is the correct result but from check_snmp it always give a wrong result "UNKNOW". Please could you correct the bug ? Thanks for your help, Yours Faithfully Bruno -------------- next part -------------- An HTML attachment was scrubbed... URL: From dermoth at aei.ca Wed Nov 25 20:58:25 2009 From: dermoth at aei.ca (Thomas Guyot-Sionnest) Date: Wed, 25 Nov 2009 14:58:25 -0500 Subject: [Nagiosplug-devel] TR: Check_snmp Problem In-Reply-To: References: Message-ID: <4B0D8C61.4010907@aei.ca> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Bruno Grondin wrote: > Dear Support, > > I'm using the new check_snmp plugin (1.4.14) and I'm having a problem > with it. > I'm using the verbose mode for debugging (-v options). I obtain the > following result below > > *[root at YEN ~]# check_snmp -H 192.168.20.227 -C public -o > 1.3.6.1.4.1.3854.1.2.2.1.16.1.3.0 -l Temperature -v > /usr/bin/snmpget -t 1 -r 5 -m '' -v 1 [authpriv] 192.168.20.227:161 > 1.3.6.1.4.1.3854.1.2.2.1.16.1.3.0 > iso.3.6.1.4.1.3854.1.2.2.1.16.1.3.0 17 > Temperature UNKNOWN - |* > > I can see that snmpget is OK because it return 17 which is the correct > result but > from check_snmp it always give a wrong result "UNKNOW". > > Please could you correct the bug ? I don't think it's a bug, though I have now received any confirmation this is the issue. See: http://article.gmane.org/gmane.network.nagios.plugins/4519 If that helps please let me know and I will add a FAQ entry for this. - -- Thomas -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAksNjGAACgkQ6dZ+Kt5Bchai2gCfaUqLAtsuZNxhxidpIF8Fn5K9 GqEAoPj0P6PgVvVA2XKKhXhe1baciYBr =+cU1 -----END PGP SIGNATURE----- From bruno.grondin at fr.bertrandt.com Thu Nov 26 12:49:04 2009 From: bruno.grondin at fr.bertrandt.com (Bruno Grondin) Date: Thu, 26 Nov 2009 12:49:04 +0100 Subject: [Nagiosplug-devel] TR: Check_snmp Problem In-Reply-To: <4B0D8C61.4010907@aei.ca> Message-ID: <20091126114907.282662B205@fr-sv-003.fr.bertrandt.net> Hi Thomas You are right, it's not a bug. This article resolved the problem. http://article.gmane.org/gmane.network.nagios.plugins/4519 It's run very well now. Many thanks for your help Bruno -----Message d'origine----- De : Thomas Guyot-Sionnest [mailto:dermoth at aei.ca] Envoy? : mercredi 25 novembre 2009 20:58 ? : Nagios Plugin Development Mailing List Objet : Re: [Nagiosplug-devel] TR: Check_snmp Problem -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Bruno Grondin wrote: > Dear Support, > > I'm using the new check_snmp plugin (1.4.14) and I'm having a problem > with it. > I'm using the verbose mode for debugging (-v options). I obtain the > following result below > > *[root at YEN ~]# check_snmp -H 192.168.20.227 -C public -o > 1.3.6.1.4.1.3854.1.2.2.1.16.1.3.0 -l Temperature -v /usr/bin/snmpget > -t 1 -r 5 -m '' -v 1 [authpriv] 192.168.20.227:161 > 1.3.6.1.4.1.3854.1.2.2.1.16.1.3.0 iso.3.6.1.4.1.3854.1.2.2.1.16.1.3.0 > 17 Temperature UNKNOWN - |* > > I can see that snmpget is OK because it return 17 which is the correct > result but from check_snmp it always give a wrong result "UNKNOW". > > Please could you correct the bug ? I don't think it's a bug, though I have now received any confirmation this is the issue. See: http://article.gmane.org/gmane.network.nagios.plugins/4519 If that helps please let me know and I will add a FAQ entry for this. - -- Thomas -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAksNjGAACgkQ6dZ+Kt5Bchai2gCfaUqLAtsuZNxhxidpIF8Fn5K9 GqEAoPj0P6PgVvVA2XKKhXhe1baciYBr =+cU1 -----END PGP SIGNATURE----- ---------------------------------------------------------------------------- -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________________ Nagios Plugin Development Mailing List Nagiosplug-devel at lists.sourceforge.net Unsubscribe at https://lists.sourceforge.net/lists/listinfo/nagiosplug-devel ::: Please include plugins version (-v) and OS when reporting any issue. ::: Messages without supporting info will risk being sent to /dev/null From bruno.grondin at fr.bertrandt.com Thu Nov 26 16:25:40 2009 From: bruno.grondin at fr.bertrandt.com (Bruno Grondin) Date: Thu, 26 Nov 2009 16:25:40 +0100 Subject: [Nagiosplug-devel] TR: TR: Check_snmp Problem Message-ID: <20091126152543.3D1F72B205@fr-sv-003.fr.bertrandt.net> Hi thomas, How can I add the option "-Oq" into the check_snmp.c source for the snmpget commandline ? Thanks for your help. Greetings Bruno -----Message d'origine----- De : Bruno Grondin [mailto:bruno.grondin at fr.bertrandt.com] Envoy? : jeudi 26 novembre 2009 12:49 ? : 'Nagios Plugin Development Mailing List' Objet : RE: [Nagiosplug-devel] TR: Check_snmp Problem Hi Thomas You are right, it's not a bug. This article resolved the problem. http://article.gmane.org/gmane.network.nagios.plugins/4519 It's run very well now. Many thanks for your help Bruno -----Message d'origine----- De : Thomas Guyot-Sionnest [mailto:dermoth at aei.ca] Envoy? : mercredi 25 novembre 2009 20:58 ? : Nagios Plugin Development Mailing List Objet : Re: [Nagiosplug-devel] TR: Check_snmp Problem -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Bruno Grondin wrote: > Dear Support, > > I'm using the new check_snmp plugin (1.4.14) and I'm having a problem > with it. > I'm using the verbose mode for debugging (-v options). I obtain the > following result below > > *[root at YEN ~]# check_snmp -H 192.168.20.227 -C public -o > 1.3.6.1.4.1.3854.1.2.2.1.16.1.3.0 -l Temperature -v /usr/bin/snmpget > -t 1 -r 5 -m '' -v 1 [authpriv] 192.168.20.227:161 > 1.3.6.1.4.1.3854.1.2.2.1.16.1.3.0 iso.3.6.1.4.1.3854.1.2.2.1.16.1.3.0 > 17 Temperature UNKNOWN - |* > > I can see that snmpget is OK because it return 17 which is the correct > result but from check_snmp it always give a wrong result "UNKNOW". > > Please could you correct the bug ? I don't think it's a bug, though I have now received any confirmation this is the issue. See: http://article.gmane.org/gmane.network.nagios.plugins/4519 If that helps please let me know and I will add a FAQ entry for this. - -- Thomas -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAksNjGAACgkQ6dZ+Kt5Bchai2gCfaUqLAtsuZNxhxidpIF8Fn5K9 GqEAoPj0P6PgVvVA2XKKhXhe1baciYBr =+cU1 -----END PGP SIGNATURE----- ---------------------------------------------------------------------------- -- Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________________ Nagios Plugin Development Mailing List Nagiosplug-devel at lists.sourceforge.net Unsubscribe at https://lists.sourceforge.net/lists/listinfo/nagiosplug-devel ::: Please include plugins version (-v) and OS when reporting any issue. ::: Messages without supporting info will risk being sent to /dev/null From anish.patel at bt.com Thu Nov 26 16:29:56 2009 From: anish.patel at bt.com (anish.patel at bt.com) Date: Thu, 26 Nov 2009 15:29:56 -0000 Subject: [Nagiosplug-devel] HTTP check In-Reply-To: <20091126114907.282662B205@fr-sv-003.fr.bertrandt.net> Message-ID: Hi would anyone know of a http check that uses a proxy and can follow a redirect, as the check http check uses a proxy but does not find the sting on the redirect url page. Please I am desperate Regards Anish From mitsuto at gmail.com Thu Nov 26 21:54:05 2009 From: mitsuto at gmail.com (Marcel) Date: Thu, 26 Nov 2009 18:54:05 -0200 Subject: [Nagiosplug-devel] HTTP check In-Reply-To: References: <20091126114907.282662B205@fr-sv-003.fr.bertrandt.net> Message-ID: <2dfcbd1b0911261254n15fa5053t645a5f714f8c0773@mail.gmail.com> well, you could first READ the --help ; then ask here AFTER try something about YOUR PROBLEM. but to save you some time, try the -f follow flag On Thu, Nov 26, 2009 at 1:29 PM, wrote: > > > Hi would anyone know of a http check that uses a proxy and can follow a > redirect, as the check http check uses a proxy but does not find the > sting on the redirect url page. Please I am desperate > > Regards Anish > > > ------------------------------------------------------------------------------ > Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day > trial. Simplify your report design, integration and deployment - and focus > on > what you do best, core application coding. Discover what's new with > Crystal Reports now. http://p.sf.net/sfu/bobj-july > _______________________________________________________ > Nagios Plugin Development Mailing List > Nagiosplug-devel at lists.sourceforge.net > Unsubscribe at > https://lists.sourceforge.net/lists/listinfo/nagiosplug-devel > ::: Please include plugins version (-v) and OS when reporting any issue. > ::: Messages without supporting info will risk being sent to /dev/null > -------------- next part -------------- An HTML attachment was scrubbed... URL: From dermoth at aei.ca Thu Nov 26 23:11:13 2009 From: dermoth at aei.ca (Thomas Guyot-Sionnest) Date: Thu, 26 Nov 2009 17:11:13 -0500 Subject: [Nagiosplug-devel] TR: TR: Check_snmp Problem In-Reply-To: <20091126152543.3D1F72B205@fr-sv-003.fr.bertrandt.net> References: <20091126152543.3D1F72B205@fr-sv-003.fr.bertrandt.net> Message-ID: <4B0EFD01.1080909@aei.ca> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Bruno Grondin wrote: > Hi thomas, > > How can I add the option "-Oq" into the > check_snmp.c source for the snmpget commandline ? If you use nagios_plugins 1.4.13 or older it's very easy, just find any argument in plugins/check_snmp.c and add it there. You can even add it to config.h after the defines for PATH_TO_SNMPGET and PATH_TO_SNMPGETNEXT. For v1.4.14 and up it's more tricky because we use a command argument array and there appear to be some parameters that assume a fixed size. The easiest way is to squeeze some arguments to make room for it... ex: Remove: - - command_line[7] = "-v"; - - command_line[8] = strdup (proto); And replace with: + command_line[7] = malloc(strlen(proto)+3); + strcpy(command_line[7], "-v"); + strcpy(command_line[7]+2, proto); + command_line[8] = strdup ("-Oq"); This replace "-v {proto}" with "-v{proto}", which is still valid (for example with version 2c: "-v 2c" becomes "-v2c"), leaving the position 8 for your "-Oq" argument. Note that the debug output (-v) needs to be modified as well, so you won't see any difference in what check_snmp say it will execute unless you also modify the line starting with: asprintf(&cl_hidden_auth, [...] Which is about 10 lines below what I have shown above. This is just cosmetic. - -- Thomas -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAksO/QEACgkQ6dZ+Kt5BchYgoQCeJRVUTqBYqgrA9u0OikPxROFu PfYAn20/FcX9D9gtdgfuJ0s1NX9VKefp =0te+ -----END PGP SIGNATURE----- From ppb at usc.edu Mon Nov 30 19:45:59 2009 From: ppb at usc.edu (Philip Brown) Date: Mon, 30 Nov 2009 10:45:59 -0800 Subject: [Nagiosplug-devel] oddity about check_procs plugin and solaris In-Reply-To: <4AF94678.8020709@aei.ca> References: <49CAAAC3.4010606@usc.edu> <4B5A67AF-C7CF-492A-A44C-8E8A3B67443E@opsera.com> <49CBC097.701@usc.edu> <49CBC85E.1070009@usc.edu> <4AF94678.8020709@aei.ca> Message-ID: <4B1412E7.7040409@usc.edu> Thomas Guyot-Sionnest wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > On 26/03/09 02:24 PM, Philip Brown wrote: >> BTW, there is a bug in the pst3 configuration: >> >> if test `isainfo -b` = 64 ; then >> PST3CFLAGS="-m64" >> >> is inappropriate. -m64 is a compiler-specific flag. >>.... > > A wile ago I patched configure.in to try detecting it but never sent out > the patch. It seems to work well for me, unfortunately I have no sun cc > nor x86-64 architectures to test with. > I did a quick ./configure with http://dermoth.users.sourceforge.net/snapshot/nagios-plugins-pst3_suncc_fix.tar.gz Seems to be better: $ grep PST3CFLAGS */Makefile gl/Makefile:PST3CFLAGS = -xarch=v9 lib/Makefile:PST3CFLAGS = -xarch=v9 perlmods/Makefile:PST3CFLAGS = -xarch=v9 plugins-root/Makefile:PST3CFLAGS = -xarch=v9 plugins-scripts/Makefile:PST3CFLAGS = -xarch=v9 plugins/Makefile:PST3CFLAGS = -xarch=v9 tap/Makefile:PST3CFLAGS = -xarch=v9