From notifications at github.com Wed Mar 2 16:43:08 2016 From: notifications at github.com (Cameron Moore) Date: Wed, 02 Mar 2016 07:43:08 -0800 Subject: check_ifoperstatus.pl: Add -N and --namekey search options (#978) In-Reply-To: References: Message-ID: Abandoning this PR since this repo and the old nagios-plugins repo have diverged. -- Reply to this email on GitHub: https://github.com/monitoring-plugins/monitoring-plugins/pull/978#issuecomment-191293269 -------------- next part -------------- An HTML attachment was scrubbed... URL: From notifications at github.com Wed Mar 2 16:43:09 2016 From: notifications at github.com (Cameron Moore) Date: Wed, 02 Mar 2016 07:43:09 -0800 Subject: check_ifoperstatus.pl: Add -N and --namekey search options (#978) In-Reply-To: References: Message-ID: Closed #978. -- Reply to this email on GitHub: https://github.com/monitoring-plugins/monitoring-plugins/pull/978#event-574839169 -------------- next part -------------- An HTML attachment was scrubbed... URL: From notifications at github.com Wed Mar 2 19:46:33 2016 From: notifications at github.com (Cameron Moore) Date: Wed, 02 Mar 2016 10:46:33 -0800 Subject: check_ifoperstatus.pl: add ifName search key option (#1407) Message-ID: Dell's PowerConnect switches store the interface name (ie. Te1/0/1) in ifName and not in ifDescr, so doing `... -d Te1/0/1` doesn't work. This commit adds a new `-N|--namekey` option that allows you to search against the ifName field. You can view, comment on, or merge this pull request online at: https://github.com/monitoring-plugins/monitoring-plugins/pull/1407 -- Commit Summary -- * check_ifoperstatus.pl: add ifName search key option -- File Changes -- M plugins-scripts/check_ifoperstatus.pl (17) -- Patch Links -- https://github.com/monitoring-plugins/monitoring-plugins/pull/1407.patch https://github.com/monitoring-plugins/monitoring-plugins/pull/1407.diff -- Reply to this email on GitHub: https://github.com/monitoring-plugins/monitoring-plugins/pull/1407 -------------- next part -------------- An HTML attachment was scrubbed... URL: From notifications at github.com Thu Mar 3 08:54:26 2016 From: notifications at github.com (=?UTF-8?B?RWxhbiBSdXVzYW3DpGU=?=) Date: Wed, 02 Mar 2016 23:54:26 -0800 Subject: check_http asks for HTTP/1.1, but doesn't understand chunked [sf#2786808] (#1122) In-Reply-To: References: Message-ID: i do not think this applies to monitoring-plugins, nagios-plugins added this in [2.1.0](https://nagios-plugins.org/nagios-plugins-2-1-0-released/), but this project never got it according to my diffs: https://gist.github.com/glensc/f2f0dfa36d2e369a6493 which is good as the implementation i see is very broken, internet is full of the bugreports and np project does nothing to handle them: - https://sourceforge.net/p/nagiosplug/bugs/446/ - https://support.nagios.com/forum/viewtopic.php?f=35&t=34548 - https://github.com/nagios-plugins/nagios-plugins/issues/103 - https://github.com/nagios-plugins/nagios-plugins/issues/98 - https://github.com/nagios-plugins/nagios-plugins/issues/104 - https://github.com/nagios-plugins/nagios-plugins/issues/121 - https://github.com/nagios-plugins/nagios-plugins/issues/76 only one i see related to this is unmerged PR to add chunked encoding to this mp project: #1286 -- Reply to this email on GitHub: https://github.com/monitoring-plugins/monitoring-plugins/issues/1122#issuecomment-191639766 -------------- next part -------------- An HTML attachment was scrubbed... URL: From notifications at github.com Thu Mar 3 20:35:31 2016 From: notifications at github.com (=?UTF-8?B?RWxhbiBSdXVzYW3DpGU=?=) Date: Thu, 03 Mar 2016 11:35:31 -0800 Subject: prevent segfault on rc_avpair_add. (#1408) Message-ID: patch from debian (#nagios-plugins_1.4.11-2.diff.gz) originated from pld linux https://github.com/pld-linux/monitoring-plugins/blob/auto/th/monitoring-plugins-2.1.2-1/nagios-plugins-check_radius_segfault.patch You can view, comment on, or merge this pull request online at: https://github.com/monitoring-plugins/monitoring-plugins/pull/1408 -- Commit Summary -- * prevent segfault on rc_avpair_add. -- File Changes -- M plugins/check_radius.c (8) -- Patch Links -- https://github.com/monitoring-plugins/monitoring-plugins/pull/1408.patch https://github.com/monitoring-plugins/monitoring-plugins/pull/1408.diff -- Reply to this email on GitHub: https://github.com/monitoring-plugins/monitoring-plugins/pull/1408 -------------- next part -------------- An HTML attachment was scrubbed... URL: From notifications at github.com Thu Mar 3 20:36:59 2016 From: notifications at github.com (=?UTF-8?B?RWxhbiBSdXVzYW3DpGU=?=) Date: Thu, 03 Mar 2016 11:36:59 -0800 Subject: ignore "WARNING: failed to install socket filter" messages (#1409) Message-ID: originated from pld-linux: https://github.com/pld-linux/monitoring-plugins/blob/auto/th/monitoring-plugins-2.1.2-1/nagios-plugins-check_ping-socket-filter-warning.patch You can view, comment on, or merge this pull request online at: https://github.com/monitoring-plugins/monitoring-plugins/pull/1409 -- Commit Summary -- * ignore "WARNING: failed to install socket filter: Protocol not available" message -- File Changes -- M plugins/check_ping.c (1) -- Patch Links -- https://github.com/monitoring-plugins/monitoring-plugins/pull/1409.patch https://github.com/monitoring-plugins/monitoring-plugins/pull/1409.diff -- Reply to this email on GitHub: https://github.com/monitoring-plugins/monitoring-plugins/pull/1409 -------------- next part -------------- An HTML attachment was scrubbed... URL: From notifications at github.com Fri Mar 4 21:38:42 2016 From: notifications at github.com (waja) Date: Fri, 04 Mar 2016 12:38:42 -0800 Subject: [check_radius.c] prevent segfault on rc_avpair_add. (#1408) In-Reply-To: References: Message-ID: @glensc I dropped the patch via https://github.com/waja/pkg-monitoring-plugins/blob/master/debian/changelog#L529-L531. Is this problem still reproducible for you? -- Reply to this email on GitHub: https://github.com/monitoring-plugins/monitoring-plugins/pull/1408#issuecomment-192458806 -------------- next part -------------- An HTML attachment was scrubbed... URL: From frnkblk at iname.com Sat Mar 5 21:56:22 2016 From: frnkblk at iname.com (Frank Bulk) Date: Sat, 5 Mar 2016 14:56:22 -0600 Subject: IPv6 support check_dhcp Message-ID: <000501d17721$79642f50$6c2c8df0$@iname.com> Could someone code support for DHCPv6? It's a gap in our monitoring today. Kind regards, Frank From notifications at github.com Thu Mar 10 21:36:06 2016 From: notifications at github.com (Sven Nierlein) Date: Thu, 10 Mar 2016 12:36:06 -0800 Subject: check_by_ssh: print command output in verbose mode (#1414) Message-ID: right now it is not possible to print the command output of ssh. check_by_ssh only prints the command itself. This patchs adds printing the output too. This makes it possible to use ssh with verbose logging which helps debuging any connection, key or other ssh problems. Note: you must use -E,--skip-stderr=, otherwise check_by_ssh would always exit with unknown state. Example: ./check_by_ssh -H localhost -o LogLevel=DEBUG3 -C "sleep 1" -E 999 -v Signed-off-by: Sven Nierlein You can view, comment on, or merge this pull request online at: https://github.com/monitoring-plugins/monitoring-plugins/pull/1414 -- Commit Summary -- * check_by_ssh: print command output in verbose mode -- File Changes -- M plugins/check_by_ssh.c (7) -- Patch Links -- https://github.com/monitoring-plugins/monitoring-plugins/pull/1414.patch https://github.com/monitoring-plugins/monitoring-plugins/pull/1414.diff -- Reply to this email on GitHub: https://github.com/monitoring-plugins/monitoring-plugins/pull/1414 -------------- next part -------------- An HTML attachment was scrubbed... URL: From notifications at github.com Tue Mar 15 21:20:57 2016 From: notifications at github.com (Sami Kerola) Date: Tue, 15 Mar 2016 13:20:57 -0700 Subject: check_timex: add new plugin (#1344) In-Reply-To: References: Message-ID: Hello. What is going on with getting review to this pull request? --- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/monitoring-plugins/monitoring-plugins/pull/1344#issuecomment-197004956 -------------- next part -------------- An HTML attachment was scrubbed... URL: From notifications at github.com Tue Mar 15 21:27:54 2016 From: notifications at github.com (Sami Kerola) Date: Tue, 15 Mar 2016 13:27:54 -0700 Subject: check_timex: add new plugin (#1415) Message-ID: This plugin uses ntp_adjtime() function to read and report system time using struct timex values. Check is similar to check_ntp_time, but with a difference being completely local execution. This has some desirable effects, such as: 1) This check runs very quickly. 2) The status of clock is reported from solely systems point of view, i.e., a small network hiccup or public DNS failure will not cause spurious failures 3) The check works when clock is syncronized with something else than ntp, such as ptp. Main difference of the check_timex and check_ntp_time is units used in --warning and --critical arguments. This check is using microseconds, while the check_ntp_time is using seconds. That means one should not interchange these checks without additional configuration changes. You can view, comment on, or merge this pull request online at: https://github.com/monitoring-plugins/monitoring-plugins/pull/1415 -- Commit Summary -- * check_timex: add new plugin -- File Changes -- M .gitignore (1) M THANKS.in (1) M configure.ac (5) M plugins/Makefile.am (5) A plugins/check_timex.c (175) M po/POTFILES.in (1) -- Patch Links -- https://github.com/monitoring-plugins/monitoring-plugins/pull/1415.patch https://github.com/monitoring-plugins/monitoring-plugins/pull/1415.diff --- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/monitoring-plugins/monitoring-plugins/pull/1415 -------------- next part -------------- An HTML attachment was scrubbed... URL: From notifications at github.com Wed Mar 16 14:36:24 2016 From: notifications at github.com (Oliver Skibbe) Date: Wed, 16 Mar 2016 06:36:24 -0700 Subject: check_smtp: extended support for expect option (#1382) In-Reply-To: References: Message-ID: Hey all, what do you think about my changes? I think they're safe and will not only be an enhancement, but more a bug fix. Because by now the check is only looking for the first line of response. BR Oliver --- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/monitoring-plugins/monitoring-plugins/pull/1382#issuecomment-197333659 -------------- next part -------------- An HTML attachment was scrubbed... URL: From notifications at github.com Thu Mar 24 14:53:17 2016 From: notifications at github.com (Casper Langemeijer) Date: Thu, 24 Mar 2016 06:53:17 -0700 Subject: Add commandline -T switch to check_time and check_ntp_time (#1246) In-Reply-To: References: Message-ID: Closed #1246. --- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/monitoring-plugins/monitoring-plugins/pull/1246#event-601765724 -------------- next part -------------- An HTML attachment was scrubbed... URL: From notifications at github.com Thu Mar 31 20:36:14 2016 From: notifications at github.com (Paul Dugas) Date: Thu, 31 Mar 2016 11:36:14 -0700 Subject: [monitoring-plugins/monitoring-plugin-perl] Add LONGOUTPUT parameter to plugin_exit (#9) Message-ID: I'd like to be able to use something like the code below to emit additional lines of LONGOUTPUT from a plugin. ``` $plugin->plugin_exit(OK, "All good", "additional\ndetails\nhere") ``` The output from this would be something like ``` OK - All good additional details here|perfdata... ``` --- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/monitoring-plugins/monitoring-plugin-perl/issues/9 -------------- next part -------------- An HTML attachment was scrubbed... URL: From notifications at github.com Thu Mar 31 20:39:11 2016 From: notifications at github.com (Sven Nierlein) Date: Thu, 31 Mar 2016 11:39:11 -0700 Subject: [monitoring-plugins/monitoring-plugin-perl] Add LONGOUTPUT parameter to plugin_exit (#9) In-Reply-To: References: Message-ID: does ```$plugin->plugin_exit(OK, "All good\nadditional\ndetails\nhere")```work? --- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/monitoring-plugins/monitoring-plugin-perl/issues/9#issuecomment-204070769 -------------- next part -------------- An HTML attachment was scrubbed... URL: From notifications at github.com Thu Mar 31 20:45:05 2016 From: notifications at github.com (Paul Dugas) Date: Thu, 31 Mar 2016 11:45:05 -0700 Subject: [monitoring-plugins/monitoring-plugin-perl] Add LONGOUTPUT parameter to plugin_exit (#9) In-Reply-To: References: Message-ID: That's what I'm doing in the interim. However, when the $message is empty we call `$plugin->plugin_exit(OK, "\nadditional\ndetails\nhere")` and end up with output like so ``` OK - additional details here|perfdata ``` The extra dash in the output is apparently annoying so some of my people. Maybe it'd be easier to just look for a leading \n in $message and skip the dash in that case. --- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/monitoring-plugins/monitoring-plugin-perl/issues/9#issuecomment-204072475 -------------- next part -------------- An HTML attachment was scrubbed... URL: From notifications at github.com Thu Mar 31 20:55:49 2016 From: notifications at github.com (Paul Dugas) Date: Thu, 31 Mar 2016 11:55:49 -0700 Subject: [monitoring-plugins/monitoring-plugin-perl] Add LONGOUTPUT parameter to plugin_exit (#9) In-Reply-To: References: Message-ID: ``` --- Functions.pm.orig 2016-03-31 14:50:52.295849074 -0400 +++ Functions.pm 2016-03-31 14:55:17.350834574 -0400 @@ -118,7 +118,10 @@ # Setup output my $output = "$STATUS_TEXT{$code}"; - $output .= " - $message" if defined $message && $message ne ''; + if (defined $message && $message ne '') { + $output .= " - " unless $message =~ /^ *\n/; + $output .= $message; + } my $shortname = ($arg->{plugin} ? $arg->{plugin}->shortname : undef); $shortname ||= get_shortname(); # Should happen only if funnctions are called directly $output = "$shortname $output" if $shortname; ``` --- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/monitoring-plugins/monitoring-plugin-perl/issues/9#issuecomment-204077168 -------------- next part -------------- An HTML attachment was scrubbed... URL: From notifications at github.com Thu Mar 31 20:57:08 2016 From: notifications at github.com (Sven Nierlein) Date: Thu, 31 Mar 2016 11:57:08 -0700 Subject: [monitoring-plugins/monitoring-plugin-perl] Add LONGOUTPUT parameter to plugin_exit (#9) In-Reply-To: References: Message-ID: Sounds ok for me, could you create a pull request? Then i could just merge it and you get proper credits. --- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/monitoring-plugins/monitoring-plugin-perl/issues/9#issuecomment-204077805 -------------- next part -------------- An HTML attachment was scrubbed... URL: From notifications at github.com Thu Mar 31 22:32:22 2016 From: notifications at github.com (Sven Nierlein) Date: Thu, 31 Mar 2016 13:32:22 -0700 Subject: [monitoring-plugins/monitoring-plugin-perl] Add LONGOUTPUT parameter to plugin_exit (#9) In-Reply-To: References: Message-ID: ah yes, you are right :-) --- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/monitoring-plugins/monitoring-plugin-perl/issues/9#issuecomment-204114074 -------------- next part -------------- An HTML attachment was scrubbed... URL: From elfakih.fatima at gmail.com Wed Mar 23 13:24:40 2016 From: elfakih.fatima at gmail.com (Fatima Elfakih) Date: Wed, 23 Mar 2016 12:24:40 -0000 Subject: check_load Message-ID: Hi I have a problem with critical value, i can't determinate this value; I have some machines with 2cores and others with 4cors -- *ELFAKIH Fatima* *Ing?nieur d??tat en t?l?communication et technologies d'information * *Option R?seau Syst?me et Services * *T?l *:*0651359133* *Email* : *elfakih.fatima at gmail.com* -------------- next part -------------- An HTML attachment was scrubbed... URL: