From Willis.Ralph at asx.com.au Fri Mar 1 05:52:15 2013 From: Willis.Ralph at asx.com.au (Willis Ralph) Date: Fri, 1 Mar 2013 15:52:15 +1100 Subject: [Nagiosplug-devel] question about check_log2.pl In-Reply-To: References: <20327_1361932578_r1R2aIfW017110_55C0E0E4978E0E42A6036F2DA27F8405012E882FC9@PMAIL204.asxprod.asx.com.au> Message-ID: <20340_1362113546_r214qPOT031438_55C0E0E4978E0E42A6036F2DA27F8405012E9A4CDA@PMAIL204.asxprod.asx.com.au> Thanks for the help. The extra quotes didn?t help , Nagios still removes the string at the first ?|? Your post made me think and I ended up changing the $pattern_line before it is sent to Nagios. my $x = '\|'; $pattern_line =~ s/$x/*/g; print "($pattern_count): $pattern_line"; This code changed the | to a * which solved my problem Thanks for the help Regards, Willis From: lists [mailto:lists at catsnest.co.uk] Sent: Wednesday, 27 February 2013 11:07 PM To: Nagios Plugin Development Mailing List Subject: Re: [Nagiosplug-devel] question about check_log2.pl On 27 February 2013 02:36, Willis Ralph > wrote: Hi, I have been making use of check_log2.pl. It works fine. When I ran it from the command line on my Nagios server the output is correct. /usr/local/nagios/libexec/check_nrpe -H server111 -c check_logfiles This brings back WARNING: (3): [LOG|ERROR|27 Feb 2013 10:52:36,683|com.example.Bean|Worker-2|-] The trouble is that the Nagios monitoring screen output in the Status Information field treats the first ?| ? as a delimiter and truncates the output to [LOG| Is there a way to make Nagios display the complete line ? This will be becouse Nagios treats anything after a | in the output of a check as performance data. You will need to etit the script to work with your data, I think if the output is quoted the | will be ignored, if that does not work try urlencoding it instead. e.g. In the version of check_log2.pl.i have the output line looks like this: print "($pattern_count): $pattern_line"; you could try print "($pattern_count): \"$pattern_line\""; -- Regards, Ritchie Regards, Willis Willis Ralph | Systems Administrator ASX Limited | 20 Bridge Street | Sydney NSW 2000 t: +61 2 9227 0661 | m: 0417 652755 | e: w: www.asx.com.au P Please consider the environment before printing this email PRIVACY COLLECTION STATEMENT ASX uses and discloses your personal information only for the purpose for which you provided it. Your personal information will not be disclosed or used for any other purpose unless you consent or ASX is otherwise permitted to do so under the Privacy Act 1988 (Cth). CONFIDENTIAL EMAIL The information in this email is confidential and may be privileged or subject to copyright. It is intended for the exclusive use of the addressee(s). If you are not an addressee, do not copy, distribute or otherwise act on the email. If you have received the email in error, please contact the sender immediately and delete the email. The unauthorised use of this email may result in liability for breach of confidentiality, privilege or copyright. E-mail transmissions cannot be guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. The sender therefore does not accept liability for errors or omissions in the contents of this message which arise as a result of e-mail transmission. ------------------------------------------------------------------------------ Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_d2d_feb _______________________________________________________ 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 PRIVACY COLLECTION STATEMENT ASX uses and discloses your personal information only for the purpose for which you provided it. Your personal information will not be disclosed or used for any other purpose unless you consent or ASX is otherwise permitted to do so under the Privacy Act 1988 (Cth). CONFIDENTIAL EMAIL The information in this email is confidential and may be privileged or subject to copyright. It is intended for the exclusive use of the addressee(s). If you are not an addressee, do not copy, distribute or otherwise act on the email. If you have received the email in error, please contact the sender immediately and delete the email. The unauthorised use of this email may result in liability for breach of confidentiality, privilege or copyright. E-mail transmissions cannot be guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. The sender therefore does not accept liability for errors or omissions in the contents of this message which arise as a result of e-mail transmission. -------------- next part -------------- An HTML attachment was scrubbed... URL: From noreply at sourceforge.net Fri Mar 15 10:24:28 2013 From: noreply at sourceforge.net (SourceForge.net) Date: Fri, 15 Mar 2013 02:24:28 -0700 Subject: [Nagiosplug-devel] [ nagiosplug-Bugs-3608135 ] check_smtp -D (1.4.16) doesn't QUIT Message-ID: Bugs item #3608135, was opened at 2013-03-15 02:24 Message generated for change (Tracker Item Submitted) made by j-bern You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=397597&aid=3608135&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: J. Bern (j-bern) Assigned to: Nobody/Anonymous (nobody) Summary: check_smtp -D (1.4.16) doesn't QUIT Initial Comment: Plugin Version (-V output): 1.4.16 Plugin Name: check_smtp Plugin Commandline showing issues: check_smtp -H [postfix-MTA-IP] -F nagios.[domain] -S -D 5,2 -v Operating System: CentOS Architecture: x86_64 Compiler: (from repos) check_smtp -D executes the "if ( check_cert )" branch, which calls my_close(), which closes the connection. No SMTP QUIT command is being sent, which makes the (postfix) MTA log "lost connection after EHLO" warning messages. Please include an smtp_quit() somewhere along this code path. (I'm not submitting a patch myself because I don't know offhand whether the smtp_quit() should go into the "if ( check_cert )" branch alone, or become part of my_close(), which also handles two EHLO error cases.) ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=397597&aid=3608135&group_id=29880 From noreply at sourceforge.net Fri Mar 15 12:15:07 2013 From: noreply at sourceforge.net (SourceForge.net) Date: Fri, 15 Mar 2013 04:15:07 -0700 Subject: [Nagiosplug-devel] [ nagiosplug-Bugs-3608135 ] check_smtp -D (1.4.16) doesn't QUIT Message-ID: Bugs item #3608135, was opened at 2013-03-15 02:24 Message generated for change (Settings changed) made by hweiss You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=397597&aid=3608135&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: J. Bern (j-bern) >Assigned to: Holger Weiss (hweiss) Summary: check_smtp -D (1.4.16) doesn't QUIT Initial Comment: Plugin Version (-V output): 1.4.16 Plugin Name: check_smtp Plugin Commandline showing issues: check_smtp -H [postfix-MTA-IP] -F nagios.[domain] -S -D 5,2 -v Operating System: CentOS Architecture: x86_64 Compiler: (from repos) check_smtp -D executes the "if ( check_cert )" branch, which calls my_close(), which closes the connection. No SMTP QUIT command is being sent, which makes the (postfix) MTA log "lost connection after EHLO" warning messages. Please include an smtp_quit() somewhere along this code path. (I'm not submitting a patch myself because I don't know offhand whether the smtp_quit() should go into the "if ( check_cert )" branch alone, or become part of my_close(), which also handles two EHLO error cases.) ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=397597&aid=3608135&group_id=29880 From noreply at sourceforge.net Sat Mar 16 13:29:08 2013 From: noreply at sourceforge.net (SourceForge.net) Date: Sat, 16 Mar 2013 05:29:08 -0700 Subject: [Nagiosplug-devel] [ nagiosplug-Bugs-3031365 ] check_ntp_time picks IPv6 address when no IPv6 is available Message-ID: Bugs item #3031365, was opened at 2010-07-18 16:22 Message generated for change (Comment added) made by tarvin You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=397597&aid=3031365&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: Troels Arvin (tarvin) Assigned to: Nobody/Anonymous (nobody) Summary: check_ntp_time picks IPv6 address when no IPv6 is available Initial Comment: Example: $ check_ntp_time -H ns.tele.dk Address family not supported by protocol can not create new socket ns.tele.dk has two A records: ns.tele.dk. 85584 IN AAAA 2001:6c8:2:100::53 ns.tele.dk. 15704 IN A 193.162.159.194 The server where check_ntp_time is run on has no IPv6 address. Now, $ check_ntp_time -H 193.162.159.194 NTP OK: Offset 5.13792038e-05 secs|offset=0.000051s;60.000000;120.000000; In other words: If I hardcode the IP-address to check, and choose an IPv4 address, things work. But if I leave it up to check_ntp_time to choose among the available A records, it chooses the IPv6 one, even though the server being run from doesn't have any IPv6 address. Other apps on the server seem to be better at choosing the IPv4 address when there is a choice between IPv4 and IPv6. Example: The ftp.sunet.se site has both an IPv4 (194.71.11.69) and an IPv6 address (2001:6b0:19::64); and it responds to both FTP and HTTP. Both "elinks" and "curl" pick the right (IPv4) address when accessing ftp.sunet.se, using either protocol; e.g.: $ curl -v --head http://ftp.sunet.se * About to connect() to ftp.sunet.se port 80 * Trying 194.71.11.69... connected * Connected to ftp.sunet.se (194.71.11.69) port 80 > HEAD / HTTP/1.1 > User-Agent: curl/7.15.5 (x86_64-redhat-linux-gnu) libcurl/7.15.5 OpenSSL/0.9.8b zlib/1.2.3 libidn/0.6.5 > Host: ftp.sunet.se > Accept: */* > < HTTP/1.1 200 OK HTTP/1.1 200 OK < Date: Sun, 18 Jul 2010 23:20:38 GMT Date: Sun, 18 Jul 2010 23:20:38 GMT < Server: Apache/2.2.14 (Unix) Server: Apache/2.2.14 (Unix) < Accept-Ranges: bytes Accept-Ranges: bytes < Content-Type: text/html Content-Type: text/html * Connection #0 to host ftp.sunet.se left intact * Closing connection #0 ---------------------------------------------------------------------- >Comment By: Troels Arvin (tarvin) Date: 2013-03-16 05:29 Message: Adding a "-4" argument helps, thanks. ---------------------------------------------------------------------- Comment By: Thomas Gelf (thomas_gelf) Date: 2010-07-22 01:06 Message: Sorry, I confused it with check_ntp.pl: http://nagiosplug.git.sourceforge.net/git/gitweb.cgi?p=nagiosplug/nagiosplug;a=blob;f=plugins-scripts/check_ntp.pl Using "-4" would probably help in your case too, but check_ntp_time.c should definitively be fixed. ---------------------------------------------------------------------- Comment By: Troels Arvin (tarvin) Date: 2010-07-21 14:34 Message: By the way: I have observed this problem on Red Hat Enterprise Linux 5.5 and Fedora Linux 13. ---------------------------------------------------------------------- Comment By: Troels Arvin (tarvin) Date: 2010-07-21 13:23 Message: Thomas: check_ntp_time doesn't call my system's ntpdate. check_ntp_time is a binary - not a script. And it only links to the most basic libraries (i.e.: it doesn't link to any NTP-related libraries). The code for the plugin: http://nagiosplug.git.sourceforge.net/git/gitweb.cgi?p=nagiosplug/nagiosplug;a=blob;f=plugins/check_ntp_time.c ---------------------------------------------------------------------- Comment By: Thomas Gelf (thomas_gelf) Date: 2010-07-21 09:32 Message: Hi Troels, I stumbled over your bug report - and I guess your ntpdate is the one to blame for this. What ntpdate version are you currently using? It seems that this issue has been fixed somewhere by mid-2009. Before this those tools just checked whether you have IPv6 support - right now they also verify whether your IPv6-Connectivity will work. As a workaround you can pass "-4" as an additional parameter to your call to check_ntp_time, that should help. I'd therefore suggest to close this bug report - check_ntp_time is IMO not the right place to fix this. Regards, Thomas Gelf NB: If I'm wrong please feel free to correct me! As this is the very first time I ever gave a closer look to a a Nagios component, you shouldn't trust my words at all ;-) ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=397597&aid=3031365&group_id=29880 From galvao.m at gmail.com Tue Mar 19 12:20:45 2013 From: galvao.m at gmail.com (Mauro) Date: Tue, 19 Mar 2013 11:20:45 +0000 Subject: [Nagiosplug-devel] Status flags supported by check_procs Message-ID: Hello, I would like to monitor a daemon, by checking that there is exactly 1 "parent" running, to avoid the process to be run twice on the same box. The daemon itself forks at certain times, so you can have a parent and multiple children. I have other various ways of doing it, but as first solution I wanted to try using nagios. My idea was to use the following command, by checking the "s" status flag from ps. /usr/lib64/nagios/plugins/check_procs -C schedule_cron -sSs This doesn't work, as check_procs doesn't seem to be checking the "s" flag. With the -vv option to check_procs, I can see that the ps command used is: CMD: /bin/ps -eo '*s* uid pid ppid vsz rss pcpu etime comm args' Instead of the "s" column, "stat" would do the job I need. I wonder if it would be possible to change the default format from s to stat, or to not alter an existing behaviour, provide an option -o or similar for users customisations. I'm running nagios plugins 1.4.15, nagios 3.2.2, installed from rpm on a redhat based distribution. Regards, Mauro -------------- next part -------------- An HTML attachment was scrubbed... URL: From galvao.m at gmail.com Tue Mar 19 13:04:09 2013 From: galvao.m at gmail.com (Mauro) Date: Tue, 19 Mar 2013 12:04:09 +0000 Subject: [Nagiosplug-devel] Status flags supported by check_procs In-Reply-To: <51484F94.9030305@LINworks.de> References: <51484F94.9030305@LINworks.de> Message-ID: Hello, I thought to have mentioned it, but I'll clarify now. Note that I asked for a command line option, not a compile one, but I understand this could not be feasible. > I'm running nagios plugins 1.4.15, nagios 3.2.2, installed from rpm on a redhat based distribution. Distribution is quite old, but I cannot upgrade it. I can try to re-compile nagios plugins with the last source and see how it goes though. ~ > rpm -qi nagios-plugins-procs Name : nagios-plugins-procs Relocations: (not relocatable) Version : 1.4.15 Vendor: Amazon.com Release : 2.1.amzn1 Build Date: Fri 29 Oct 2010 01:12:18 AM BST Install Date: Tue 19 Mar 2013 08:56:31 AM GMT Build Host: build-31002.build Group : Applications/System Source RPM: nagios-plugins-1.4.15-2.1.amzn1.src.rpm Size : 118688 License: GPLv2+ Signature : RSA/8, Wed 03 Nov 2010 06:46:25 PM GMT, Key ID bcb4a85b21c0f39f Packager : Amazon.com, Inc. URL : http://nagiosplug.sourceforge.net/ Summary : Nagios Plugin - check_procs Description : Provides check_procs support for Nagios. ~ > uname -a Linux content-build-1.build.uk 2.6.34.7-56.40.amzn1.x86_64 #1 SMP Fri Oct 22 18:48:49 UTC 2010 x86_64 x86_64 x86_64 GNU/Linux On 19 March 2013 11:44, Jochen Bern wrote: > On 19.03.2013 12:20, Mauro wrote: > > My idea was to use the following command, by checking the "s" status flag > > from ps. > > > > /usr/lib64/nagios/plugins/check_procs -C schedule_cron -sSs > > > > This doesn't work, as check_procs doesn't seem to be checking the "s" > flag. > > With the -vv option to check_procs, I can see that the ps command used > is: > > > > CMD: /bin/ps -eo '*s* uid pid ppid vsz rss pcpu etime comm args' > > > > Instead of the "s" column, "stat" would do the job I need. > > > > I wonder if it would be possible to change the default format from s to > > stat, or to not alter an existing behaviour, provide an option -o or > > similar for users customisations. > > You didn't mention where you got your check_procs from. When installing > from sources, the "ps" command to use is usually determined > automatically during the "./configure", but things can also be > manipulated with the "--with-ps-..." options; see the output of > "./configure --help". > > Note that incompatibilities between "ps" outputs are a common occurence > when using check_procs (try matching a string waaaay into a long command > line ...), and compiling a check_procs version with a "ps" command to > match *one* specific need isn't going to help much with that, to say the > least. > > 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 -------------- An HTML attachment was scrubbed... URL: From Jochen.Bern at LINworks.de Tue Mar 19 12:44:20 2013 From: Jochen.Bern at LINworks.de (Jochen Bern) Date: Tue, 19 Mar 2013 12:44:20 +0100 Subject: [Nagiosplug-devel] Status flags supported by check_procs In-Reply-To: References: Message-ID: <51484F94.9030305@LINworks.de> On 19.03.2013 12:20, Mauro wrote: > My idea was to use the following command, by checking the "s" status flag > from ps. > > /usr/lib64/nagios/plugins/check_procs -C schedule_cron -sSs > > This doesn't work, as check_procs doesn't seem to be checking the "s" flag. > With the -vv option to check_procs, I can see that the ps command used is: > > CMD: /bin/ps -eo '*s* uid pid ppid vsz rss pcpu etime comm args' > > Instead of the "s" column, "stat" would do the job I need. > > I wonder if it would be possible to change the default format from s to > stat, or to not alter an existing behaviour, provide an option -o or > similar for users customisations. You didn't mention where you got your check_procs from. When installing from sources, the "ps" command to use is usually determined automatically during the "./configure", but things can also be manipulated with the "--with-ps-..." options; see the output of "./configure --help". Note that incompatibilities between "ps" outputs are a common occurence when using check_procs (try matching a string waaaay into a long command line ...), and compiling a check_procs version with a "ps" command to match *one* specific need isn't going to help much with that, to say the least. 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 Jochen.Bern at LINworks.de Tue Mar 19 14:00:05 2013 From: Jochen.Bern at LINworks.de (Jochen Bern) Date: Tue, 19 Mar 2013 14:00:05 +0100 Subject: [Nagiosplug-devel] Status flags supported by check_procs In-Reply-To: References: <51484F94.9030305@LINworks.de> Message-ID: <51486155.8060505@LINworks.de> On 19.03.2013 13:04, Mauro wrote: > Note that I asked for a command line option, not a compile one, but I > understand this could not be feasible. I can't speak for the maintainers, but seeing that the necessary adaptations to the OS-provided "ps" include the command, a format string to parse the output, *and* a list of *internal variables to parse into*, I'ld say that an execution-time override would be difficult to use at best, and likely quite difficult to implement ... > [root at nagios nagios-plugins-1.4.16]# grep -A 1 -B 1 '[^A-Z_]PS_' config.h > /* Number of columns in ps command */ > #define PS_COLS 9 > > /* Verbatim command to execute for ps in check_procs */ > #define PS_COMMAND "/bin/ps axwo 'stat uid pid ppid vsz rss pcpu comm args'" > > /* Format string for scanning ps output in check_procs */ > #define PS_FORMAT "%s %d %d %d %d %d %f %s %n" > > /* Whether the ps utility uses the "procetime" field */ > /* #undef PS_USES_PROCETIME */ > > /* Variable list for sscanf of 'ps' output */ > #define PS_VARLIST procstat,&procuid,&procpid,&procppid,&procvsz,&procrss,&procpcpu,procprog,&pos > I'm running nagios plugins 1.4.15, nagios 3.2.2, installed from rpm on a > redhat based distribution. > Distribution is quite old, but I cannot upgrade it. I can try to re-compile > nagios plugins with the last source and see how it goes though. I'ld assume that if you cannot get away from an aged OS distrib, you're unlikely to find a newer plugin version on a reputed repo, anyway, and command line control of the "ps" command is definitely absent from versions up to and including the current 1.4.16. If so, I don't see any way for you *other* than giving sources and (*if* necessary - see the 'stat' in my command above) explicit "./configure" options a try. Another word of warning, though: Have a look at the plugin's help text: > -s, --state=STATUSFLAGS > Only scan for processes that have, in the output of `ps`, one or > more of the status flags you specify (for example R, Z, S, RS, > RSZDT, plus others based on the output of your 'ps' command). The listed process state( char)s are *mutually exclusive*, and the interpretation of the --state option is that processes will be included into the selection if *ANY* of the chars appear in their s/stat column. In other words, you can select for 's'(ession leaders), but won't be able to make sure that it's not, e.g., 'Zs' or otherwise defunct within the same check. (Been there, done that, wrote my own check_nagios_procs explicitly telling the '^[RS]sl$' master process from its temporary children. :-} ) 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 galvao.m at gmail.com Tue Mar 19 22:56:40 2013 From: galvao.m at gmail.com (Mauro) Date: Tue, 19 Mar 2013 21:56:40 +0000 Subject: [Nagiosplug-devel] Status flags supported by check_procs In-Reply-To: <51486155.8060505@LINworks.de> References: <51484F94.9030305@LINworks.de> <51486155.8060505@LINworks.de> Message-ID: Hi Jochen, I'ld assume that if you cannot get away from an aged OS distrib, you're > unlikely to find a newer plugin version on a reputed repo, anyway, and > command line control of the "ps" command is definitely absent from > versions up to and including the current 1.4.16. If so, I don't see any > way for you *other* than giving sources and (*if* necessary - see the > 'stat' in my command above) explicit "./configure" options a try. > > I tried to configure both 1.4.15 and 1.4.16, and on the same box where the rpm is compiled I see the same ps command you see: /usr/local/src/nagios-plugins-1.4.16 > grep -A 1 -B 1 '[^A-Z_]PS_' config.h /* Number of columns in ps command */ #define PS_COLS 9 /* Verbatim command to execute for ps in check_procs */ #define PS_COMMAND "/bin/ps axwo 'stat uid pid ppid vsz rss pcpu comm args'" /* Format string for scanning ps output in check_procs */ #define PS_FORMAT "%s %d %d %d %d %d %f %s %n" /* Whether the ps utility uses the "procetime" field */ /* #undef PS_USES_PROCETIME */ /* Variable list for sscanf of 'ps' output */ #define PS_VARLIST procstat,&procuid,&procpid,&procppid,&procvsz,&procrss,&procpcpu,procprog,&pos Problem is then the repo, but the OS seem fine to compile nagios-plugins on my own. Even if I'm sure something won't be right with dependencies. > Another word of warning, though: Have a look at the plugin's help text: > > > -s, --state=STATUSFLAGS > > Only scan for processes that have, in the output of `ps`, one or > > more of the status flags you specify (for example R, Z, S, RS, > > RSZDT, plus others based on the output of your 'ps' command). > > The listed process state( char)s are *mutually exclusive*, and the > interpretation of the --state option is that processes will be included > into the selection if *ANY* of the chars appear in their s/stat column. > In other words, you can select for 's'(ession leaders), but won't be > able to make sure that it's not, e.g., 'Zs' or otherwise defunct within > the same check. > I think -ss would be enough for me, as my final checker would be: /usr/lib64/nagios/plugins/check_procs -c 1:1 -ss -C schedule_cron > > (Been there, done that, wrote my own check_nagios_procs explicitly > telling the '^[RS]sl$' master process from its temporary children. :-} ) > > 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 -------------- An HTML attachment was scrubbed... URL: From laurent.devignes at c-s.fr Wed Mar 20 11:41:40 2013 From: laurent.devignes at c-s.fr (Laurent DEVIGNES) Date: Wed, 20 Mar 2013 11:41:40 +0100 Subject: [Nagiosplug-devel] check_hpjd (HP JetDirect Printers) and SNMPv3 Message-ID: <51499264.6040008@c-s.fr> Hi everybody, is there any way to deal withcheck_hpjd (SNMP Plugin) and SNMPv3. Actually, it works with SNMPv2c. Any idea for this plugin to accept SNMPv3 requests ? Regards, -- Laurent. -------------- next part -------------- An HTML attachment was scrubbed... URL: From me at g0hl1n.net Wed Mar 20 18:25:14 2013 From: me at g0hl1n.net (Richard Leitner) Date: Wed, 20 Mar 2013 18:25:14 +0100 Subject: [Nagiosplug-devel] Some pull requests on Github Message-ID: <1363800314.16380.8.camel@frodo.Mittelerde> Dear Nagios Plugins Devel Team, I've currently forked your git repository on Github (Nickname: g0hl1n). There I started to fix some Bugs from the SourceForge.net Bugtracker. For two of them I created the following Pull-Requests on Github: https://github.com/nagios-plugins/nagios-plugins/pull/42 https://github.com/nagios-plugins/nagios-plugins/pull/43 Due to the fact I got no response until now I'd like to ask if it was the correct way to do these changes? Or would a patch via email be better? regards, -- Richard Leitner www.g0hl1n.net -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 230 bytes Desc: This is a digitally signed message part URL: From lsantagostini at gmail.com Wed Mar 20 19:08:31 2013 From: lsantagostini at gmail.com (Leonardo Santagostini) Date: Wed, 20 Mar 2013 15:08:31 -0300 Subject: [Nagiosplug-devel] Presentation and Question Message-ID: Hello all. My name is Leonardo Santagostini from Argentina. I am actually working with nagios monitoring my corporate services and hosts. I was noticed that a must make a new Nagios server, doing checks over more than 22000 web sites. I have all the information of this sites, in a mysql serving a bind+dlz solution. So, it is possible to use that database trough one plugin? Or you recommend to me that i must write a sheel script for this. Thanks in advance and sorry if this is no the adequeate list. Saludos / Regards Leonardo Santagostini -------------- next part -------------- An HTML attachment was scrubbed... URL: From wferi at niif.hu Wed Mar 20 21:14:13 2013 From: wferi at niif.hu (Ferenc Wagner) Date: Wed, 20 Mar 2013 21:14:13 +0100 Subject: [Nagiosplug-devel] Presentation and Question In-Reply-To: (Leonardo Santagostini's message of "Wed, 20 Mar 2013 15:08:31 -0300") References: Message-ID: <87mwtxbzhm.fsf@lant.ki.iif.hu> Leonardo Santagostini writes: > I was noticed that a must make a new Nagios server, doing checks over more > than 22000 web sites. > > I have all the information of this sites, in a mysql serving a bind+dlz > solution. > > So, it is possible to use that database trough one plugin? Or you recommend > to me that i must write a sheel script for this. First you'll have to generate a Nagios configuration from your database, since there's no way to get Nagios build its internal configuration data from any other source (to my best knowledge). Once you do that, it's no problem to pass the needed parameters to you check command, so the plugin needn't use the database thus you can use stock check_http. >From a different angle, a setup of such size will probably require some thought. I'd advise against shell scripts, those will kill your performance. The embedded Perl interpreter is a better choice, but look into the tuning chapter of the Nagios documentation for further tips. -- Regards, Feri. From holger at cis.fu-berlin.de Wed Mar 20 22:59:49 2013 From: holger at cis.fu-berlin.de (Holger =?iso-8859-1?Q?Wei=DF?=) Date: Wed, 20 Mar 2013 22:59:49 +0100 Subject: [Nagiosplug-devel] Some pull requests on Github In-Reply-To: <1363800314.16380.8.camel@frodo.Mittelerde> References: <1363800314.16380.8.camel@frodo.Mittelerde> Message-ID: <20130320215949.GB17856@zedat.fu-berlin.de> * Richard Leitner [2013-03-20 18:25]: > I've currently forked your git repository on Github (Nickname: g0hl1n). > There I started to fix some Bugs from the SourceForge.net Bugtracker. > > For two of them I created the following Pull-Requests on Github: > https://github.com/nagios-plugins/nagios-plugins/pull/42 > https://github.com/nagios-plugins/nagios-plugins/pull/43 > > Due to the fact I got no response until now I'd like to ask if it was > the correct way to do these changes? I've seen your pull requests, and they look just fine to me. We're all a bit busy right now (the main project server has to be moved to a new home and stuff like that), but I'll probably be able to look into the open pull requests (and then preparing a new release) relatively soon. Thanks a lot for your contributions, they're much appreciated! Holger From ae at op5.se Thu Mar 21 11:00:00 2013 From: ae at op5.se (Andreas Ericsson) Date: Thu, 21 Mar 2013 11:00:00 +0100 Subject: [Nagiosplug-devel] Some pull requests on Github In-Reply-To: <20130320215949.GB17856@zedat.fu-berlin.de> References: <1363800314.16380.8.camel@frodo.Mittelerde> <20130320215949.GB17856@zedat.fu-berlin.de> Message-ID: <514ADA20.5050405@op5.se> On 03/20/2013 10:59 PM, Holger Wei? wrote: > * Richard Leitner [2013-03-20 18:25]: >> I've currently forked your git repository on Github (Nickname: g0hl1n). >> There I started to fix some Bugs from the SourceForge.net Bugtracker. >> >> For two of them I created the following Pull-Requests on Github: >> https://github.com/nagios-plugins/nagios-plugins/pull/42 >> https://github.com/nagios-plugins/nagios-plugins/pull/43 >> >> Due to the fact I got no response until now I'd like to ask if it was >> the correct way to do these changes? > > I've seen your pull requests, and they look just fine to me. We're all > a bit busy right now (the main project server has to be moved to a new > home and stuff like that), but I'll probably be able to look into the > open pull requests (and then preparing a new release) relatively soon. > A new release probably won't be necessary. One patch is a spelling fix only (which is trivially correct). Adding --timeout to check_nagios is obviously good, but since it runs locally I doubt it'll ever have time to trigger. ACK on both patches from me though, for what it's worth. They're both correct and follow the plugin coding standards as far as I could see. -- 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 me at g0hl1n.net Thu Mar 21 11:41:58 2013 From: me at g0hl1n.net (Richard Leitner) Date: Thu, 21 Mar 2013 11:41:58 +0100 Subject: [Nagiosplug-devel] Some pull requests on Github In-Reply-To: <514ADA20.5050405@op5.se> References: <1363800314.16380.8.camel@frodo.Mittelerde> <20130320215949.GB17856@zedat.fu-berlin.de> <514ADA20.5050405@op5.se> Message-ID: <012282e0-b9c1-42d8-ac49-2d3a5419fdff@email.android.com> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 I don't wanted to trigger a new release. I just wanted to know if my patches follow your guidlines, so I can continue fixing some bugs for you ;-) So thanks for your acknowledgement Andreas. And I'll add some more bug-fixing PullRequests for you. regards, Richard - -------- Original-Nachricht -------- Von: Andreas Ericsson Gesendet: Thu Mar 21 11:00:00 MEZ 2013 An: Nagios Plugin Development Mailing List Betreff: Re: [Nagiosplug-devel] Some pull requests on Github On 03/20/2013 10:59 PM, Holger Wei? wrote: > * Richard Leitner [2013-03-20 18:25]: >> I've currently forked your git repository on Github (Nickname: g0hl1n). >> There I started to fix some Bugs from the SourceForge.net Bugtracker. >> >> For two of them I created the following Pull-Requests on Github: >> https://github.com/nagios-plugins/nagios-plugins/pull/42 >> https://github.com/nagios-plugins/nagios-plugins/pull/43 >> >> Due to the fact I got no response until now I'd like to ask if it was >> the correct way to do these changes? > > I've seen your pull requests, and they look just fine to me. We're all > a bit busy right now (the main project server has to be moved to a new > home and stuff like that), but I'll probably be able to look into the > open pull requests (and then preparing a new release) relatively soon. > A new release probably won't be necessary. One patch is a spelling fix only (which is trivially correct). Adding --timeout to check_nagios is obviously good, but since it runs locally I doubt it'll ever have time to trigger. ACK on both patches from me though, for what it's worth. They're both correct and follow the plugin coding standards as far as I could see. - -- 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. - ------------------------------------------------------------------------------ Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_d2d_mar _______________________________________________________ Nagios Plugin Development Mailing List Nagiosplug-devel at lists.sourceforge.net Unsubscribe at https://lists.sourceforge.net/lists/listinfo/nagiosplug-devel ::: Please include plugins version (-v) and OS when reporting any issue. ::: Messages without supporting info will risk being sent to /dev/null - --- Richard Leitner www.g0hl1n.net -----BEGIN PGP SIGNATURE----- Version: APG v1.0.8 iQFNBAEBCAA3BQJRSuP2MBxSaWNoYXJkIExlaXRuZXIgKEFQRyA0IEFuZHJvaWQp IDxtZUBnMGhsMW4ubmV0PgAKCRBsKKZVLXbz7bFWCACdOUsgx3k9kMFwUHVewVv3 AAPyJT3P6XHKKZL67JM/2mWHd4oPIyqMNZ8PI4v4VNIL0Bvtw0MTxDRaBYs2jhd6 hNKn+XPYCx9I5Jv/KPsH60ofejmHON+TbGIy2qbUDecfCRiVLhZkEH4E+x8hSosm R7994vhL7wwNKr4v1cRe4jw4kNAQjh1ytB3uqf9e7kKmwb3xFCOgeVPvkSh0vWJN sX7zz3Vga8/2SvW+eeCQdTmI7xxiQE6iTYPor5CFyhOAAAEsJ3RB130gNsDEBhbo cUkpLUVhKgMM2M2SCdC0SSOJNXEG60cPTlbSamkf1b6PpFBbgqpaL6bgK4zVC0By =B6tV -----END PGP SIGNATURE----- From holger at cis.fu-berlin.de Thu Mar 21 12:15:10 2013 From: holger at cis.fu-berlin.de (Holger =?iso-8859-1?Q?Wei=DF?=) Date: Thu, 21 Mar 2013 12:15:10 +0100 Subject: [Nagiosplug-devel] Some pull requests on Github In-Reply-To: <514ADA20.5050405@op5.se> References: <1363800314.16380.8.camel@frodo.Mittelerde> <20130320215949.GB17856@zedat.fu-berlin.de> <514ADA20.5050405@op5.se> Message-ID: <20130321111509.GC17856@zedat.fu-berlin.de> * Andreas Ericsson [2013-03-21 11:00]: > On 03/20/2013 10:59 PM, Holger Wei? wrote: > > * Richard Leitner [2013-03-20 18:25]: > >> I've currently forked your git repository on Github (Nickname: g0hl1n). > >> There I started to fix some Bugs from the SourceForge.net Bugtracker. > >> > >> For two of them I created the following Pull-Requests on Github: > >> https://github.com/nagios-plugins/nagios-plugins/pull/42 > >> https://github.com/nagios-plugins/nagios-plugins/pull/43 > >> > >> Due to the fact I got no response until now I'd like to ask if it was > >> the correct way to do these changes? > > > > I've seen your pull requests, and they look just fine to me. We're all > > a bit busy right now (the main project server has to be moved to a new > > home and stuff like that), but I'll probably be able to look into the > > open pull requests (and then preparing a new release) relatively soon. > > A new release probably won't be necessary. :-) Not just for these two patches, but there are quite a few open pull requests, plus some stuff already in Git. > ACK on both patches from me though, for what it's worth. Thanks! Holger From palli at ok.is Thu Mar 21 13:58:35 2013 From: palli at ok.is (=?utf-8?Q?P=C3=A1ll_Gu=C3=B0j=C3=B3n_Sigur=C3=B0sson?=) Date: Thu, 21 Mar 2013 12:58:35 -0000 (GMT) Subject: [Nagiosplug-devel] Some pull requests on Github In-Reply-To: <20130321111509.GC17856@zedat.fu-berlin.de> Message-ID: A little bit off topic, but in the same spirit. I have patches for nagios core documentation, but cannot find a repository to open a pull request on. Is there anyone on this list that can accept patches for nagios core documentation ? I tried asking on nagios-devel but it seems that the moderators, haven't accepted the message yet. Kind regards, Palli ----- Original Message ----- From: "Holger Wei?" To: "Nagios Plugins Development" Sent: Thursday, March 21, 2013 11:15:10 AM Subject: Re: [Nagiosplug-devel] Some pull requests on Github * Andreas Ericsson [2013-03-21 11:00]: > On 03/20/2013 10:59 PM, Holger Wei? wrote: > > * Richard Leitner [2013-03-20 18:25]: > >> I've currently forked your git repository on Github (Nickname: g0hl1n). > >> There I started to fix some Bugs from the SourceForge.net Bugtracker. > >> > >> For two of them I created the following Pull-Requests on Github: > >> https://github.com/nagios-plugins/nagios-plugins/pull/42 > >> https://github.com/nagios-plugins/nagios-plugins/pull/43 > >> > >> Due to the fact I got no response until now I'd like to ask if it was > >> the correct way to do these changes? > > > > I've seen your pull requests, and they look just fine to me. We're all > > a bit busy right now (the main project server has to be moved to a new > > home and stuff like that), but I'll probably be able to look into the > > open pull requests (and then preparing a new release) relatively soon. > > A new release probably won't be necessary. :-) Not just for these two patches, but there are quite a few open pull requests, plus some stuff already in Git. > ACK on both patches from me though, for what it's worth. Thanks! Holger ------------------------------------------------------------------------------ Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_d2d_mar _______________________________________________________ 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 roel.vanmeer at bokxing.nl Fri Mar 22 10:58:26 2013 From: roel.vanmeer at bokxing.nl (Roel van Meer) Date: Fri, 22 Mar 2013 10:58:26 +0100 Subject: [Nagiosplug-devel] =?iso-8859-1?q?=5BPATCH=5D_check=5Ffping_and_n?= =?iso-8859-1?q?etwork_unreachable?= Message-ID: Hi list, I ran into a problem where check_fping falsely reports nodes to be OK. This happened when no packets could be transmitted due to a prohibiting route. This patch fixes that by checking if the number of transmitted packets is greater than zero. Best regards, Roel -------------- next part -------------- If a host cannot be contacted due to a prohibiting route, check_fping falsely reports OK. This patch fixes that by only reporting OK if packet loss is 0 if the number of transmitted packets is > 0. If the number of transmitted packets is 0 report CRITICAL and set loss to 100%. root at polar:~# ip route show | grep 10 prohibit 10.0.0.0/8 root at polar:~# ip route get 10.17.5.1 RTNETLINK answers: Network is unreachable root at polar:~# ping 10.17.5.1 connect: Network is unreachable root at polar:~# fping 10.17.5.1 10.17.5.1 error while sending ping: Network is unreachable 10.17.5.1 is unreachable root at polar:~# fping -b 56 -c 3 10.17.5.1 10.17.5.1 : xmt/rcv/%loss = 0/0/0% root at polar:~# check_fping 10.17.5.1 FPING OK - 10.17.5.1 (loss=0% )|loss=0%;;;0;100 root at polar:~# fping -v fping: Version 2.4b2_to $Date: 2013/03/22 09:57:13 $ fping: comments to noc at zerohype.com diff -ruN nagios-plugins-1.4.15.a/plugins/check_fping.c nagios-plugins-1.4.15.b/plugins/check_fping.c --- nagios-plugins-1.4.15.a/plugins/check_fping.c 2010-07-27 22:47:16.000000000 +0200 +++ nagios-plugins-1.4.15.b/plugins/check_fping.c 2013-03-22 10:34:03.469606400 +0100 @@ -146,7 +146,9 @@ { char *rtastr = NULL; char *losstr = NULL; + char *xmtstr = NULL; double loss; + double xmt; double rta; int status = STATE_UNKNOWN; @@ -198,14 +200,20 @@ losstr = strstr (buf, "="); losstr = 1 + strstr (losstr, "/"); losstr = 1 + strstr (losstr, "/"); + xmtstr = strstr (buf, "="); + xmtstr = 1 + strstr (xmtstr, " "); loss = strtod (losstr, NULL); + xmt = strtod (xmtstr, NULL); if (atoi(losstr) == 100) status = STATE_CRITICAL; else if (cpl_p == TRUE && loss > cpl) status = STATE_CRITICAL; else if (wpl_p == TRUE && loss > wpl) status = STATE_WARNING; - else + else if (atoi(losstr) == 0 && atoi(xmtstr) == 0) { + status = STATE_CRITICAL; + loss = 100; + } else status = STATE_OK; /* loss=%.0f%%;%d;%d;0;100 */ die (status, _("FPING %s - %s (loss=%.0f%% )|%s\n"), From noreply at sourceforge.net Fri Mar 22 16:29:49 2013 From: noreply at sourceforge.net (SourceForge.net) Date: Fri, 22 Mar 2013 08:29:49 -0700 Subject: [Nagiosplug-devel] [ nagiosplug-Bugs-3560976 ] check_disk: implement --include-type Message-ID: Bugs item #3560976, was opened at 2012-08-23 04:42 Message generated for change (Comment added) made by g0hl1n You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=397597&aid=3560976&group_id=29880 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: C?lestyo (calestyo) Assigned to: Nobody/Anonymous (nobody) Summary: check_disk: implement --include-type Initial Comment: Hi. It would be great if, in addition to -X, --exclude-type=TYPE, there was a --include-type option.... If include-type is given (first) then per default no fs type shall be included but the ones given there. Cheers, Chris. ---------------------------------------------------------------------- Comment By: Richard Leitner (g0hl1n) Date: 2013-03-22 08:29 Message: Hi, i've wrote a patch for that issue and opened a PullRequest for it on Github. Here's the link: https://github.com/nagios-plugins/nagios-plugins/pull/44 regards, Richard ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=397597&aid=3560976&group_id=29880 From noreply at sourceforge.net Fri Mar 22 16:32:21 2013 From: noreply at sourceforge.net (SourceForge.net) Date: Fri, 22 Mar 2013 08:32:21 -0700 Subject: [Nagiosplug-devel] [ nagiosplug-Bugs-3539317 ] potential typo in the --help text of check_apt Message-ID: Bugs item #3539317, was opened at 2012-07-01 11:55 Message generated for change (Comment added) made by g0hl1n You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=397597&aid=3539317&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: C?lestyo (calestyo) Assigned to: Nobody/Anonymous (nobody) Summary: potential typo in the --help text of check_apt Initial Comment: From: http://tracker.nagios.org/view.php?id=299 Hi. The --help text of the check_apt check says: > -i, --include=REGEXP > Include only packages matching REGEXP. Can be specified multiple times > the values will be combined together. Any patches matching this list > cause the plugin to return WARNING status. Others will be ignored. > Default is to include all packages. I guess in the second line, this should read "Any packages" instead of "Any patches". Cheers, Chris ---------------------------------------------------------------------- Comment By: Richard Leitner (g0hl1n) Date: 2013-03-22 08:32 Message: Hi, I've wrote a patch for that typo and opened a PullRequest on Github. Here's the link: https://github.com/nagios-plugins/nagios-plugins/pull/42 regards, Richard ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=397597&aid=3539317&group_id=29880 From noreply at sourceforge.net Fri Mar 22 16:33:44 2013 From: noreply at sourceforge.net (SourceForge.net) Date: Fri, 22 Mar 2013 08:33:44 -0700 Subject: [Nagiosplug-devel] [ nagiosplug-Bugs-3602586 ] check_nagios has hard coded timeout Message-ID: Bugs item #3602586, was opened at 2013-01-29 14:27 Message generated for change (Comment added) made by g0hl1n You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=397597&aid=3602586&group_id=29880 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Argument proccessing Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Paul M. Dubuc (dubuc) Assigned to: Nobody/Anonymous (nobody) Summary: check_nagios has hard coded timeout Initial Comment: The check_nagios plugin in release 1.4.16 has a hard coded timeout of 10 seconds. Could a -t option be added to override this default? On my our load testing system, I could use a longer timeout for this plugin. ---------------------------------------------------------------------- Comment By: Richard Leitner (g0hl1n) Date: 2013-03-22 08:33 Message: Hi, I've fixed that issue and opened a PullRequest on Github for it. Here's the link: 3602586 regards, Richard ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=397597&aid=3602586&group_id=29880 From ae at op5.se Mon Mar 25 11:02:47 2013 From: ae at op5.se (Andreas Ericsson) Date: Mon, 25 Mar 2013 11:02:47 +0100 Subject: [Nagiosplug-devel] Some pull requests on Github In-Reply-To: References: Message-ID: <515020C7.40109@op5.se> On 03/21/2013 01:58 PM, P?ll Gu?j?n Sigur?sson wrote: > A little bit off topic, but in the same spirit. I have patches for > nagios core documentation, but cannot find a repository to open a > pull request on. Is there anyone on this list that can accept patches > for nagios core documentation ? > Try emailing estanley at nagios.com and mguthrie at nagios.com. One of them is most likely your best bet. -- 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 noreply at sourceforge.net Mon Mar 25 23:30:27 2013 From: noreply at sourceforge.net (SourceForge.net) Date: Mon, 25 Mar 2013 15:30:27 -0700 Subject: [Nagiosplug-devel] [ nagiosplug-Bugs-3539317 ] potential typo in the --help text of check_apt Message-ID: Bugs item #3539317, was opened at 2012-07-01 11:55 Message generated for change (Comment added) made by hweiss You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=397597&aid=3539317&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: Closed >Resolution: Fixed Priority: 5 Private: No Submitted By: C?lestyo (calestyo) Assigned to: Nobody/Anonymous (nobody) Summary: potential typo in the --help text of check_apt Initial Comment: From: http://tracker.nagios.org/view.php?id=299 Hi. The --help text of the check_apt check says: > -i, --include=REGEXP > Include only packages matching REGEXP. Can be specified multiple times > the values will be combined together. Any patches matching this list > cause the plugin to return WARNING status. Others will be ignored. > Default is to include all packages. I guess in the second line, this should read "Any packages" instead of "Any patches". Cheers, Chris ---------------------------------------------------------------------- >Comment By: Holger Weiss (hweiss) Date: 2013-03-25 15:30 Message: Fixed, thanks. ---------------------------------------------------------------------- Comment By: Richard Leitner (g0hl1n) Date: 2013-03-22 08:32 Message: Hi, I've wrote a patch for that typo and opened a PullRequest on Github. Here's the link: https://github.com/nagios-plugins/nagios-plugins/pull/42 regards, Richard ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=397597&aid=3539317&group_id=29880 From noreply at sourceforge.net Mon Mar 25 23:40:34 2013 From: noreply at sourceforge.net (SourceForge.net) Date: Mon, 25 Mar 2013 15:40:34 -0700 Subject: [Nagiosplug-devel] [ nagiosplug-Bugs-3602586 ] check_nagios has hard coded timeout Message-ID: Bugs item #3602586, was opened at 2013-01-29 14:27 Message generated for change (Comment added) made by hweiss You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=397597&aid=3602586&group_id=29880 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Argument proccessing Group: None >Status: Closed >Resolution: Fixed Priority: 5 Private: No Submitted By: Paul M. Dubuc (dubuc) Assigned to: Nobody/Anonymous (nobody) Summary: check_nagios has hard coded timeout Initial Comment: The check_nagios plugin in release 1.4.16 has a hard coded timeout of 10 seconds. Could a -t option be added to override this default? On my our load testing system, I could use a longer timeout for this plugin. ---------------------------------------------------------------------- >Comment By: Holger Weiss (hweiss) Date: 2013-03-25 15:40 Message: A patch that adds such an option has been applied. ---------------------------------------------------------------------- Comment By: Richard Leitner (g0hl1n) Date: 2013-03-22 08:33 Message: Hi, I've fixed that issue and opened a PullRequest on Github for it. Here's the link: 3602586 regards, Richard ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=397597&aid=3602586&group_id=29880 From noreply at sourceforge.net Mon Mar 25 23:59:27 2013 From: noreply at sourceforge.net (SourceForge.net) Date: Mon, 25 Mar 2013 15:59:27 -0700 Subject: [Nagiosplug-devel] [ nagiosplug-Bugs-3560976 ] check_disk: implement --include-type Message-ID: Bugs item #3560976, was opened at 2012-08-23 04:42 Message generated for change (Comment added) made by hweiss You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=397597&aid=3560976&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: Closed >Resolution: Fixed Priority: 5 Private: No Submitted By: C?lestyo (calestyo) Assigned to: Nobody/Anonymous (nobody) Summary: check_disk: implement --include-type Initial Comment: Hi. It would be great if, in addition to -X, --exclude-type=TYPE, there was a --include-type option.... If include-type is given (first) then per default no fs type shall be included but the ones given there. Cheers, Chris. ---------------------------------------------------------------------- >Comment By: Holger Weiss (hweiss) Date: 2013-03-25 15:59 Message: A patch that adds such an option has been applied. ---------------------------------------------------------------------- Comment By: Richard Leitner (g0hl1n) Date: 2013-03-22 08:29 Message: Hi, i've wrote a patch for that issue and opened a PullRequest for it on Github. Here's the link: https://github.com/nagios-plugins/nagios-plugins/pull/44 regards, Richard ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=397597&aid=3560976&group_id=29880 From manu at netbsd.org Tue Mar 26 06:12:08 2013 From: manu at netbsd.org (Emmanuel Dreyfus) Date: Tue, 26 Mar 2013 06:12:08 +0100 Subject: [Nagiosplug-devel] A few plugins Message-ID: <1l0bssn.2dccwffu2xxjM%manu@netbsd.org> Hi I would like to share a few plugins for whoever is interested: https://ftp.espci.fr/pub/nagios-local/check_dnsrbl-0.1.tgz Check various DNSRBL status. There are many plugins doing this, the only specific thing about this one is that it is written in C, and hence does not require an interpreter. https://ftp.espci.fr/pub/nagios-local/check_dotpid-0.1.tgz Check that daemons that saved /var/run/*.pid files are still alive. This is a cheap method that does not require any configuration for checking that daemons are still alive. https://ftp.espci.fr/pub/nagios-local/check_dumpdates-0.1.tgz Check that backup status in /etc/dumpdates is fresh enough https://ftp.espci.fr/pub/nagios-local/check_syncrepl-0.1.tgz Check OpenLDAP syncrepl status. Again, there are a few plugins doing it, the advantage of this one is that is is written in C https://ftp.espci.fr/pub/nagios-local/check_raidctl-0.1.tgz Check NetBSD RAIDframe status. That one is NetBSD specific. -- Emmanuel Dreyfus http://hcpnet.free.fr/pubz manu at netbsd.org From holger at cis.fu-berlin.de Tue Mar 26 12:46:42 2013 From: holger at cis.fu-berlin.de (Holger =?iso-8859-1?Q?Wei=DF?=) Date: Tue, 26 Mar 2013 12:46:42 +0100 Subject: [Nagiosplug-devel] A few plugins In-Reply-To: <1l0bssn.2dccwffu2xxjM%manu@netbsd.org> References: <1l0bssn.2dccwffu2xxjM%manu@netbsd.org> Message-ID: <20130326114642.GQ17856@zedat.fu-berlin.de> * Emmanuel Dreyfus [2013-03-26 06:12]: > I would like to share a few plugins for whoever is interested: Nice! You might want to submit your plugins to http://exchange.nagios.org/ so that others can easily find them. > https://ftp.espci.fr/pub/nagios-local/check_dotpid-0.1.tgz > Check that daemons that saved /var/run/*.pid files are still alive. This > is a cheap method that does not require any configuration for checking > that daemons are still alive. To me, this one looks neat and generally useful. I'd be interested in including it with the standard Plugins package. An option for specifying the PID file directory (or directories) would have to be added, plus the usual --help/--version/--timeout boilerplate, but that's trivial. However, this is only an option if you'd be fine with transferring copyright to the Nagios Plugins Development Team (and with us releasing the code under the GPLv3). > https://ftp.espci.fr/pub/nagios-local/check_raidctl-0.1.tgz > Check NetBSD RAIDframe status. That one is NetBSD specific. I use a quick'n'dirty raidctl(8) wrapper[*] for checking my own NetBSD systems; your plugin is of course much nicer, thanks! (I'd just call it "check_raidframe" instead.) Holger [*] ftp://ftp.in-berlin.de/pub/users/weiss/nagios/plugins/check_raidframe.sh