From notifications at github.com Thu Mar 5 11:53:09 2015 From: notifications at github.com (Oliver Skibbe) Date: Thu, 05 Mar 2015 02:53:09 -0800 Subject: check_by_ssh: Add option to force pseudo tty allocation (#1303) In-Reply-To: References: Message-ID: Yeah, you're right that seems to be a better solution :) -- Reply to this email on GitHub: https://github.com/monitoring-plugins/monitoring-plugins/pull/1303#issuecomment-77344044 -------------- next part -------------- An HTML attachment was scrubbed... URL: From notifications at github.com Thu Mar 5 12:16:24 2015 From: notifications at github.com (Oliver Skibbe) Date: Thu, 05 Mar 2015 03:16:24 -0800 Subject: * check_snmp.c: switched DEFAULT_TIMEOUT to DEFAULT_SOCKET_TIMEOUT (prov... (#1324) Message-ID: As noted in issue #1318 there's an inconsistency between help function (uses constanct DEFAULT_SOCKET_TIMEOUT from utils.h) and actual code (uses DEFAULT_TIMEOUT constant) So i removed DEFAULT_TIMEOUT and added DEFAULT_SOCKET_TIMEOUT to timeout_interval You can view, comment on, or merge this pull request online at: https://github.com/monitoring-plugins/monitoring-plugins/pull/1324 -- Commit Summary -- * * check_snmp.c: switched DEFAULT_TIMEOUT to DEFAULT_SOCKET_TIMEOUT (provided by utils.h), already used by help description, see issue #1318 -- File Changes -- M plugins/check_snmp.c (3) -- Patch Links -- https://github.com/monitoring-plugins/monitoring-plugins/pull/1324.patch https://github.com/monitoring-plugins/monitoring-plugins/pull/1324.diff -- Reply to this email on GitHub: https://github.com/monitoring-plugins/monitoring-plugins/pull/1324 -------------- next part -------------- An HTML attachment was scrubbed... URL: From notifications at github.com Fri Mar 6 10:57:20 2015 From: notifications at github.com (Oliver Skibbe) Date: Fri, 06 Mar 2015 01:57:20 -0800 Subject: * check_snmp.c: switched DEFAULT_TIMEOUT to DEFAULT_SOCKET_TIMEOUT (prov... (#1324) In-Reply-To: References: Message-ID: Closed #1324. -- Reply to this email on GitHub: https://github.com/monitoring-plugins/monitoring-plugins/pull/1324#event-247395856 -------------- next part -------------- An HTML attachment was scrubbed... URL: From notifications at github.com Fri Mar 6 11:08:38 2015 From: notifications at github.com (Oliver Skibbe) Date: Fri, 06 Mar 2015 02:08:38 -0800 Subject: * check_snmp.c: switched DEFAULT_TIMEOUT to DEFAULT_SOCKET_TIMEOUT (prov... (#1324) In-Reply-To: References: Message-ID: Closed #1324. -- Reply to this email on GitHub: https://github.com/monitoring-plugins/monitoring-plugins/pull/1324#event-247401527 -------------- next part -------------- An HTML attachment was scrubbed... URL: From notifications at github.com Fri Mar 6 11:53:06 2015 From: notifications at github.com (Oliver Skibbe) Date: Fri, 06 Mar 2015 02:53:06 -0800 Subject: check_snmp.c: switched DEFAULT_TIMEOUT to DEFAULT_SOCKET_TIMEOUT (provid... (#1325) Message-ID: check_snmp.c: switched DEFAULT_TIMEOUT to DEFAULT_SOCKET_TIMEOUT (provided by utils.h), already used by help description, see issue #1318 You can view, comment on, or merge this pull request online at: https://github.com/monitoring-plugins/monitoring-plugins/pull/1325 -- Commit Summary -- * check_snmp.c: switched DEFAULT_TIMEOUT to DEFAULT_SOCKET_TIMEOUT (provided by utils.h), already used by help description, see issue #1318 -- File Changes -- M plugins/check_snmp.c (3) -- Patch Links -- https://github.com/monitoring-plugins/monitoring-plugins/pull/1325.patch https://github.com/monitoring-plugins/monitoring-plugins/pull/1325.diff -- Reply to this email on GitHub: https://github.com/monitoring-plugins/monitoring-plugins/pull/1325 -------------- next part -------------- An HTML attachment was scrubbed... URL: From notifications at github.com Fri Mar 6 12:01:17 2015 From: notifications at github.com (Oliver Skibbe) Date: Fri, 06 Mar 2015 03:01:17 -0800 Subject: check_disk: reduced compiler warnings (#1326) Message-ID: with fixing verbose printfs and fixed printf arguments printf line 1046: missing argument, switched llu int to uintmax_t printf line 1067: wrong arguments, switched llu int to uintmax_t You can view, comment on, or merge this pull request online at: https://github.com/monitoring-plugins/monitoring-plugins/pull/1326 -- Commit Summary -- * check_disk: reduced compiler warnings -- File Changes -- M plugins/check_disk.c (15) -- Patch Links -- https://github.com/monitoring-plugins/monitoring-plugins/pull/1326.patch https://github.com/monitoring-plugins/monitoring-plugins/pull/1326.diff -- Reply to this email on GitHub: https://github.com/monitoring-plugins/monitoring-plugins/pull/1326 -------------- next part -------------- An HTML attachment was scrubbed... URL: From notifications at github.com Fri Mar 6 12:56:48 2015 From: notifications at github.com (Oliver Skibbe) Date: Fri, 06 Mar 2015 03:56:48 -0800 Subject: check_snmp.c: switched DEFAULT_TIMEOUT to DEFAULT_SOCKET_TIMEOUT (provid... (#1325) In-Reply-To: References: Message-ID: @waja done -- Reply to this email on GitHub: https://github.com/monitoring-plugins/monitoring-plugins/pull/1325#issuecomment-77548284 -------------- next part -------------- An HTML attachment was scrubbed... URL: From eponymousalias at yahoo.com Mon Mar 9 22:38:00 2015 From: eponymousalias at yahoo.com (eponymous alias) Date: Mon, 9 Mar 2015 14:38:00 -0700 Subject: check_procs -a limitation Message-ID: <1425937080.87964.YahooMailBasic@web160706.mail.bf1.yahoo.com> The following is being reported against monitoring-plugins-v2.1.1-39-g8095, though it applies as well to earlier releases. There is a problem with the manner in which check_procs looks for command-line arguments (the "-a" option): -a, --argument-array=STRING Only scan for processes with args that contain STRING. The problem is that internally, check_procs depends on some variant of "ps" to scan for processes. And these days, many operating systems by default limit the length of the command-line string returned by "ps" to perhaps 80 characters or so. In the configuration and compilation of check_procs, an attempt is being made to overcome this limit, via the configured definition of PS_COMMAND placed into the config.h file by configure. Here I show the value produced on my Linux machine: #define PS_COMMAND "/bin/ps axwo 'stat uid pid ppid vsz rss pcpu comm args'" The problem is, a single "w" option only widens the "ps" output a bit, and not necessarily enough to encompass the target string a user is looking for with the check_procs -a option. (Processes can have very long argument lists, and the distinguishing string you need to identify a particular process of interest might not appear until close to the end.) The Linux "man ps" output says this about the "w" option: w Wide output. Use this option twice for unlimited width. So my request here is that the derivation of the PS_COMMAND value, at least on Linux platforms, be modified to use the "axwwo" options instead of the "axwo" options. Alas, my configure-fu is quite limited, and my git-fu is nonexistent, so I can't propose exact code changes. From eponymousalias at yahoo.com Mon Mar 9 23:12:09 2015 From: eponymousalias at yahoo.com (eponymous alias) Date: Mon, 9 Mar 2015 15:12:09 -0700 Subject: check_disk is missing -lrt on Solaris Message-ID: <1425939129.5725.YahooMailBasic@web160704.mail.bf1.yahoo.com> The following is being reported against monitoring-plugins-v2.1.1-39-g8095. In the link of check_disk.o on Solaris 8, I get: Undefined first referenced symbol in file nanosleep check_disk.o ld: fatal: Symbol referencing errors. No output written to check_disk *** Error code 1 make: Fatal error: Command failed for target `check_disk' A look at the man page for nanosleep(3RT) on this platform shows that it requires the -lrt library to be linked in, to access this function. From eponymousalias at yahoo.com Mon Mar 9 23:14:39 2015 From: eponymousalias at yahoo.com (eponymous alias) Date: Mon, 9 Mar 2015 15:14:39 -0700 Subject: check_icmp is missing -D_XPG4_2 on Solaris Message-ID: <1425939279.53508.YahooMailBasic@web160705.mail.bf1.yahoo.com> The following is being reported against monitoring-plugins-v2.1.1-39-g8095. In the compilation of plugins-root/check_icmp.c on Solaris 8, I get: "check_icmp.c", line 948: undefined struct/union member: msg_control "check_icmp.c", line 948: warning: improper pointer/integer combination: op "=" "check_icmp.c", line 949: undefined struct/union member: msg_controllen cc: acomp failed for check_icmp.c *** Error code 2 make: Fatal error: Command failed for target `check_icmp.o' because struct msghdr is defined in /usr/include/sys/socket.h with these protections around the affected fields within the structure: #if defined(_XPG4_2) || defined(_KERNEL) void *msg_control; /* ancillary data */ socklen_t msg_controllen; /* ancillary data buffer len */ int msg_flags; /* flags on received message */ #else caddr_t msg_accrights; /* access rights sent/received */ int msg_accrightslen; #endif /* defined(_XPG4_2) || defined(_KERNEL) */ and the check_icmp.c code is referencing the msg_control and msg_controllen fields. Clearly, _XPG4_2 needs to be defined automatically for this compilation, when the Makefile is built in the plugins-root directory for Solaris. From waja at cyconet.org Tue Mar 10 09:59:26 2015 From: waja at cyconet.org (Jan Wagner) Date: Tue, 10 Mar 2015 09:59:26 +0100 Subject: check_procs -a limitation In-Reply-To: <1425937080.87964.YahooMailBasic@web160706.mail.bf1.yahoo.com> References: <1425937080.87964.YahooMailBasic@web160706.mail.bf1.yahoo.com> Message-ID: <54FEB26E.8090402@cyconet.org> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Hi there, Am 09.03.15 um 22:38 schrieb eponymous alias: > The following is being reported against > monitoring-plugins-v2.1.1-39-g8095, though it applies as well to > earlier releases. thanks for taking time and reporting your issues. Anyway, we would prefer if issues are reported at https://github.com/monitoring-plugins/monitoring-plugins/issues/new, like documented at https://www.monitoring-plugins.org/support.html This helps us keeping track issues we need to tackle. Many thanks, Jan. - -- Never write mail to , you have been warned! - -----BEGIN GEEK CODE BLOCK----- Version: 3.12 GIT d-- s+: a C+++ UL++++ P+ L+++ E--- W+++ N+++ o++ K++ w--- O M V- PS PE Y++ PGP++ t-- 5 X R tv- b+ DI D+ G++ e++ h---- r+++ y++++ - ------END GEEK CODE BLOCK------ -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.22 (Darwin) Comment: GPGTools - https://gpgtools.org iQIcBAEBCgAGBQJU/rJtAAoJEAxwVXtaBlE+fE8QAIGhDMDHbq3tqcVoHEzm2Qfx qbmCKAteoUmNkR7hwVZ9Qisu4ClDsNJaL1L3lHjiNj+LsAg6hvsRG61Sm/KkxT0L /96QtuMIasco7TFwpCkJHCyvyL4T+B2YJeeoQw/5HgD1twNf7WFgHohKBqEFPwAh 2SN/o2w/j3/+a6IvknXl2eUmfGKcru4y+5t9s8gcdkT0e6yUZM5SRSv+sHgSqARa VyPlo5ByJyNOmo1oRm6P1zRHHiM1lA2GOQJkP35VmPJH0kIRd47t5kmIzUoL3/bb lf9DQthM35FDjJuPeXom8GH2EpuMHAe1azDyX/Ej8j9uh0n/L521af5i+GRo6Sp7 xBWvt05ZEAc+gtqAQXwbQXk8NO0XPV40am2w8IgPbrPIZUYPAAhAM4ADUE7WzKnC PQTTVcKvcecd70ukpXWcwyK+bl3xBis6PKFtkxdhLbhPpAfM6jwjE5FQWa5wqxqO l9hXWA6Q3FjyK1RIvbNvGktnM6LLVy3CTgox1DPtMib71jwCWKfUcPWXKP87filu 54xu/qCq6pvdBSa9fWo3QE7G2+cID2vKDScPzmiT13G4iMDVBtPvek6kD1i+k2iB 0ZiplAeiCvOTJeawgaQNXW/lgqU3rHX0wcMg6bO5kYE4SMe4TaF3wB8m6BH9y22r lgAHZYRKQbXQyc27w66B =5wH/ -----END PGP SIGNATURE----- From notifications at github.com Tue Mar 10 15:30:17 2015 From: notifications at github.com (Alexander) Date: Tue, 10 Mar 2015 07:30:17 -0700 Subject: check_http asks for HTTP/1.1, but doesn't understand chunked [sf#2786808] (#1122) In-Reply-To: References: Message-ID: It's 2015 and the problem still exists? As I did not find this issue here, I reported it in [nagios-plugins: check_http - Chunked Transfer Encoding leaks TCP header text into checked text, causing content checks to fail #76](https://github.com/nagios-plugins/nagios-plugins/issues/76)? :( --- Reply to this email directly or view it on GitHub: https://github.com/monitoring-plugins/monitoring-plugins/issues/1122#issuecomment-78064629 -------------- next part -------------- An HTML attachment was scrubbed... URL: From notifications at github.com Tue Mar 10 16:08:05 2015 From: notifications at github.com (s3ta) Date: Tue, 10 Mar 2015 08:08:05 -0700 Subject: check_snmp performance data includes warning/critical thresholds wrong w/ multiple OIDS (#1327) Message-ID: Refering to the NEWS: 2.2 [...] ENHANCEMENTS check_snmp's performance data now also includes warning/critical thresholds I tried it, since I am waiting for the feature. My tests / example for a Switch port ( w/ current git-version) looked like this: /usr/local/libexec/check_snmp -H 192.168.2.1 --rate -C public-P 2c -o ifInOctets.1,ifOutOctets.1,ifInUcastPkts.1,ifOutUcastPkts.1,ifInErrors.1,ifOutErrors.1 -m IF-MIB -l in,out,inucast,outucast,inerr,outerr -w 230400,230400,1000000000,1000000000,0.01,0.01 -c 230400,230400,1000000000,1000000000,0.01,0.01 SNMP RATE OK - in 8273.875 out 31296.25 inucast 92.125 outucast 64.5 inerr 0 outerr 0 | in=8273.875;230400,230400,1000000000,1000000000,0.01,0.01;230400,230400,1000000000,1000000000,0.01,0.01 out=31296.25;230400,230400,1000000000,1000000000,0.01,0.01;230400,230400,1000000000,1000000000,0.01,0.01 inucast=92.125;230400,230400,1000000000,1000000000,0.01,0.01;230400,230400,1000000000,1000000000,0.01,0.01 outucast=64.5;230400,230400,1000000000,1000000000,0.01,0.01;230400,230400,1000000000,1000000000,0.01,0.01 inerr=0;230400,230400,1000000000,1000000000,0.01,0.01;230400,230400,1000000000,1000000000,0.01,0.01 outerr=0;230400,230400,1000000000,1000000000,0.01,0.01;230400,230400,1000000000,1000000000,0.01,0.01 The warning/critical include in the perfdata are the complete strings of w/c - not just the value used for the check against it. For the sake of understanding corectly I expected as result: SNMP RATE OK - in 8273.875 out 31296.25 inucast 92.125 outucast 64.5 inerr 0 outerr 0 | in=8273.875;230400;230400 out=31296.25;230400;230400 inucast=92.125;1000000000;1000000000 outucast=64.5;1000000000;1000000000 inerr=0;0.01;0.01 outerr=0;0.01;0.01 -- Reply to this email on GitHub: https://github.com/monitoring-plugins/monitoring-plugins/issues/1327 -------------- next part -------------- An HTML attachment was scrubbed... URL: From notifications at github.com Wed Mar 11 07:57:11 2015 From: notifications at github.com (nameless-user) Date: Tue, 10 Mar 2015 23:57:11 -0700 Subject: check_procs -a limitation (#1328) Message-ID: The following is being reported against monitoring-plugins-v2.1.1-39-g8095, though it applies as well to earlier releases. There is a problem with the manner in which check_procs looks for command-line arguments (the "-a" option): -a, --argument-array=STRING Only scan for processes with args that contain STRING. The problem is that internally, check_procs depends on some variant of "ps" to scan for processes. And these days, many operating systems by default limit the length of the command-line string returned by "ps" to perhaps 80 characters or so. In the configuration and compilation of check_procs, an attempt is being made to overcome this limit, via the configured definition of PS_COMMAND placed into the config.h file by configure. Here I show the value produced on my Linux machine: #define PS_COMMAND "/bin/ps axwo 'stat uid pid ppid vsz rss pcpu comm args'" The problem is, a single "w" option only widens the "ps" output a bit, and not necessarily enough to encompass the target string a user is looking for with the check_procs -a option. (Processes can have very long argument lists, and the distinguishing string you need to identify a particular process of interest might not appear until close to the end.) The Linux "man ps" output says this about the "w" option: w Wide output. Use this option twice for unlimited width. So my request here is that the derivation of the PS_COMMAND value, at least on Linux platforms, be modified to use the "axwwo" options instead of the "axwo" options. Alas, my configure-fu is quite limited, and my git-fu is nonexistent, so I can't propose exact code changes. -- Reply to this email on GitHub: https://github.com/monitoring-plugins/monitoring-plugins/issues/1328 -------------- next part -------------- An HTML attachment was scrubbed... URL: From notifications at github.com Wed Mar 11 08:00:44 2015 From: notifications at github.com (nameless-user) Date: Wed, 11 Mar 2015 00:00:44 -0700 Subject: check_disk is missing -lrt on Solaris (#1329) Message-ID: The following is being reported against monitoring-plugins-v2.1.1-39-g8095. In the link of `check_disk.o` on Solaris 8, I get: Undefined first referenced symbol in file nanosleep check_disk.o ld: fatal: Symbol referencing errors. No output written to check_disk *** Error code 1 make: Fatal error: Command failed for target `check_disk' A look at the man page for nanosleep(3RT) on this platform shows that it requires the `-lrt` library to be linked in, to access this function. -- Reply to this email on GitHub: https://github.com/monitoring-plugins/monitoring-plugins/issues/1329 -------------- next part -------------- An HTML attachment was scrubbed... URL: From Thao-Chi.Phan at allina.com Tue Mar 31 21:48:42 2015 From: Thao-Chi.Phan at allina.com (Phan, Thao-Chi X) Date: Tue, 31 Mar 2015 19:48:42 -0000 Subject: check_disk command Message-ID: <5cf930f880a049d9868b7c4f78212a37@xchsrv02.allina.com> Please explain to me why the /usr/local/groundwork/nagios/libexec/check_disk doesn't report the correct disk space free on 2 mount points /data02b and /data02a on a server. root at abc2/usr/local/groundwork/nagios/libexec# df -m Filesystem MB blocks Free %Used Iused %Iused Mounted on /dev/hd4 512.00 336.67 35% 5761 3% / /dev/hd2 5120.00 2051.53 60% 44310 4% /usr /dev/hd9var 512.00 228.29 56% 26189 20% /var /dev/hd3 3072.00 2973.20 4% 101 1% /tmp /dev/hd1 7168.00 4794.46 34% 1854 1% /home /proc - - - - - /proc /dev/hd10opt 1024.00 320.47 69% 9826 4% /opt /dev/locallv 2048.00 1136.73 45% 720 1% /usr/local /dev/hd11admin 128.00 123.93 4% 20 1% /admin /dev/oralv 143360.00 100961.11 30% 203739 1% /oracle /dev/data01lv 276224.00 124619.55 55% 86 1% /data01 /dev/eplv 256.00 253.61 1% 6 1% /epic /dev/clarlv 303104.00 89595.34 71% 67974 1% /epic/clarity /dev/ftplv 512.00 507.60 1% 4 1% /ftpdir /dev/dbkuplv 97792.00 67809.48 31% 3748 1% /dbkup /dev/data03lv 215040.00 32499.46 85% 89 1% /data03 /dev/ctmaglv 5120.00 4587.26 11% 3301 1% /ctmag /dev/dump_cp 5120.00 5098.90 1% 4 1% /var/adm/ras/dump_cp /dev/lv00 27873280.00 11204341.16 60% 880 1% /data02b /dev/lv02 5120.00 5027.61 2% 12 1% /data04b /dev/lv01 46080.00 16327.36 65% 14 1% /oraredob /dev/lv04a 27873280.00 2550106.27 91% 880 1% /data02a /dev/lv06a 5120.00 5027.61 2% 12 1% /data04a /dev/lv05a 46080.00 16327.36 65% 14 1% /oraredoa -------INCORRECT --- 0 MB is not correct. 0% free is not correct. root at abc2 /usr/local/groundwork/nagios/libexec# ./check_disk -w 2% -c 0% -p /data02b DISK CRITICAL - free space: /data02b 0 MB (0% inode=99%);| /data02b=2147483647MB;10874142;11096064;0;11096064 -------INCORRECT ---- 22% free is not correct root at abc2 /usr/local/groundwork/nagios/libexec# ./check_disk -w 2% -c 0% -p /data02a DISK OK - free space: /data02a 2550106 MB (22% inode=99%);| /data02a=8545957MB;10874142;11096064;0;11096064 -------CORRECT root at abc2 /usr/local/groundwork/nagios/libexec# ./check_disk -w 2% -c 0% -p /data04a DISK OK - free space: /data04a 5027 MB (98% inode=99%);| /data04a=92MB;5017;5120;0;5120 -------CORRECT root at abc2 /usr/local/groundwork/nagios/libexec# ./check_disk -w 2% -c 0% -p /oracle DISK OK - free space: /oracle 100961 MB (70% inode=99%);| /oracle=42398MB;140492;143360;0;143360 Thanks a lot. Thao-Chi This message contains information that is confidential and may be privileged. Unless you are the addressee (or authorized to receive for the addressee), you may not use, copy or disclose to anyone the message or any information contained in the message. If you have received the message in error, please advise the sender by reply e-mail and delete the message. -------------- next part -------------- An HTML attachment was scrubbed... URL: