From noreply at sourceforge.net Tue Dec 1 05:16:29 2009 From: noreply at sourceforge.net (SourceForge.net) Date: Tue, 01 Dec 2009 04:16:29 +0000 Subject: [Nagiosplug-devel] [ nagiosplug-Feature Requests-2906507 ] check_procs - return critical error when 0 procs Message-ID: Feature Requests item #2906507, was opened at 2009-12-01 15:16 Message generated for change (Tracker Item Submitted) made by martyone You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=397600&aid=2906507&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 Priority: 5 Private: No Submitted By: Martin Emptage (martyone) Assigned to: Nobody/Anonymous (nobody) Summary: check_procs - return critical error when 0 procs Initial Comment: I would like to see an option in the check_procs program return a criticial error when checking for a specific process in memory and there are 0 occurences of the process. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=397600&aid=2906507&group_id=29880 From noreply at sourceforge.net Tue Dec 1 05:30:15 2009 From: noreply at sourceforge.net (SourceForge.net) Date: Tue, 01 Dec 2009 04:30:15 +0000 Subject: [Nagiosplug-devel] [ nagiosplug-Feature Requests-2906513 ] check_procs - return critical error when 0 procs Message-ID: Feature Requests item #2906513, was opened at 2009-12-01 15:30 Message generated for change (Tracker Item Submitted) made by martyone You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=397600&aid=2906513&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 Priority: 5 Private: No Submitted By: Martin Emptage (martyone) Assigned to: Nobody/Anonymous (nobody) Summary: check_procs - return critical error when 0 procs Initial Comment: I would like to see an option in the check_procs program return a criticial error when checking for a specific process in memory and there are 0 occurences of the process. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=397600&aid=2906513&group_id=29880 From noreply at sourceforge.net Tue Dec 1 05:30:58 2009 From: noreply at sourceforge.net (SourceForge.net) Date: Tue, 01 Dec 2009 04:30:58 +0000 Subject: [Nagiosplug-devel] [ nagiosplug-Feature Requests-2906513 ] check_procs - return critical error when 0 procs Message-ID: Feature Requests item #2906513, was opened at 2009-12-01 15:30 Message generated for change (Comment added) made by martyone You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=397600&aid=2906513&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: Deleted Priority: 5 Private: No Submitted By: Martin Emptage (martyone) Assigned to: Nobody/Anonymous (nobody) Summary: check_procs - return critical error when 0 procs Initial Comment: I would like to see an option in the check_procs program return a criticial error when checking for a specific process in memory and there are 0 occurences of the process. ---------------------------------------------------------------------- >Comment By: Martin Emptage (martyone) Date: 2009-12-01 15:30 Message: duplicate ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=397600&aid=2906513&group_id=29880 From noreply at sourceforge.net Thu Dec 3 17:00:19 2009 From: noreply at sourceforge.net (SourceForge.net) Date: Thu, 03 Dec 2009 16:00:19 +0000 Subject: [Nagiosplug-devel] [ nagiosplug-Patches-2908236 ] Support for larger numbers in the perfdata utility function Message-ID: Patches item #2908236, was opened at 2009-12-03 17:00 Message generated for change (Tracker Item Submitted) made by rakhun You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=397599&aid=2908236&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: Perf data Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Henrik Nilsson (rakhun) Assigned to: Nobody/Anonymous (nobody) Summary: Support for larger numbers in the perfdata utility function Initial Comment: Hi, this patch enables the perfdata utility function to work with larger numbers, such as check_disk with bytes as output unit, which would otherwise return large, negative numbers ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=397599&aid=2908236&group_id=29880 From noreply at sourceforge.net Fri Dec 4 21:48:46 2009 From: noreply at sourceforge.net (SourceForge.net) Date: Fri, 04 Dec 2009 20:48:46 +0000 Subject: [Nagiosplug-devel] [ nagiosplug-Bugs-2896201 ] check_ping depends on iputils-ping Message-ID: Bugs item #2896201, was opened at 2009-11-11 15:37 Message generated for change (Comment added) made by dermoth You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=397597&aid=2896201&group_id=29880 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: General plugin execution Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Jan Wagner (cyco_dd) Assigned to: Thomas Guyot-Sionnest (dermoth) Summary: check_ping depends on iputils-ping Initial Comment: The following Bugreport we got against our debian package: Hi, it seems that the nagios related packages need an ping command available. They choose iputils-ping, which is rather linux specific. Could be possible to switch (at least on non-linux) to inetutils-ping (already available) or fping (modulo #555398 available). It will help to kfreebsd-i386, kfreebsd-amd64 and hurd architectures. Thanks for considering it. You can track the bugreport via http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=555532 check_ping could maybe rewritten/patched to use liboping [1]? Thanks and kind regards, Jan. [1] http://verplant.org/liboping/ ---------------------------------------------------------------------- >Comment By: Thomas Guyot-Sionnest (dermoth) Date: 2009-12-04 15:48 Message: Gotchya. --with-ping[6]-command expected three arguments - two numeric and one string. I try to detect it now (attached patch) - will go upstream it it works for you... ---------------------------------------------------------------------- Comment By: Jan Wagner (cyco_dd) Date: 2009-11-23 10:47 Message: Unfortunately I have. :( Maybe you can have a look: normal debian package - using iputils-ping and compile following flags: --with-ping-command="/bin/ping -n -U -w %d -c %d %s" \ --with-ping6-command="/bin/ping6 -n -U -w %d -c %d %s" \ sid:~# /usr/lib/nagios/plugins/check_ping 127.0.0.1 -w 2,20% -c 5,30% PING OK - Packet loss = 0%, RTA = 0.00 ms| rta=0.000000ms;2.000000;5.000000;0.000000 pl=0%;20;30;0 Okay ... thats fine, like always. ---- pc1 - using iputils-ping and following compile flags: --with-ping-command="/bin/ping -n -c %d %s" \ --with-ping6-command="/bin/ping6 -n -c %d %s" \ sid:/tmp# LANG=C /usr/lib/nagios/plugins/check_ping 127.0.0.1 -w 2,20% -c 5,30% Speicherzugriffsfehler Okay ... here are just the ping commands wrong ---- pc2 - using iputils-ping and without specific compile flags (iputils-ping installed at compile time), but: checking for ICMP ping syntax... /bin/ping -n -U -w %d -c %d %s checking for ICMPv6 ping syntax... /bin/ping6 -n -U -w %d -c %d %s sid:/tmp# LANG=C /usr/lib/nagios/plugins/check_ping 127.0.0.1 -w 2,20% -c 5,30% PING OK - Packet loss = 0%, RTA = 0.00 ms| rta=0.000000ms;2.000000;5.000000;0.000000 pl=0%;20;30;0 Thats also fine, the commands are autodetected. ---- pc3 - using inetutils-ping and without specific compile flags (inetutils-ping installed at compile time), but: checking for ICMP ping syntax... /bin/ping -n -c %d %s checking for ICMPv6 ping syntax... /bin/ping6 -n -c %d %s sid:/tmp# LANG=C /usr/lib/nagios/plugins/check_ping 127.0.0.1 -w 2,20% -c 5,30% PING OK - Packet loss = 0%, RTA = 0.00 ms| rta=0.000000ms;2.000000;5.000000;0.000000 pl=0%;20;30;0 Looks great, command are autodetected and inetutils-ping works ---- pc4 - using inetutils-ping and the following compile flags (inetutils-ping NOT installed at compile time): --with-ping6-command="/bin/ping6 -n -c %d %s" \ --with-ping-command="/bin/ping -n -c %d %s" \ sid:/tmp# LANG=C /usr/lib/nagios/plugins/check_ping 127.0.0.1 -w 2,20% -c 5,30% Speicherzugriffsfehler This is the point I don't get. I'm using the same commands like the once when they where autodetected, but check_ping segfaults .... I'm missing something? Thanks for your help, Jan. ---------------------------------------------------------------------- Comment By: Thomas Guyot-Sionnest (dermoth) Date: 2009-11-11 17:29 Message: Normally configure decides which ping command and syntax to use, so it really depend on which packages you have installed. You can force the command to use with --with-ping-command=SYNTAX and --with-ping6-command=SYNTAX. An easy way to find the syntax it to look at a generated config.h when only the wanted ping commands are available. Search for #define PING_COMMAND and #define PING6_COMMAND. Let me know if you have any problem with specific ping variants. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=397597&aid=2896201&group_id=29880 From noreply at sourceforge.net Fri Dec 4 21:49:12 2009 From: noreply at sourceforge.net (SourceForge.net) Date: Fri, 04 Dec 2009 20:49:12 +0000 Subject: [Nagiosplug-devel] [ nagiosplug-Bugs-2896201 ] check_ping depends on iputils-ping Message-ID: Bugs item #2896201, was opened at 2009-11-11 15:37 Message generated for change (Settings changed) made by dermoth You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=397597&aid=2896201&group_id=29880 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: General plugin execution >Group: release-1.4.15 Status: Open Resolution: None Priority: 5 Private: No Submitted By: Jan Wagner (cyco_dd) Assigned to: Thomas Guyot-Sionnest (dermoth) Summary: check_ping depends on iputils-ping Initial Comment: The following Bugreport we got against our debian package: Hi, it seems that the nagios related packages need an ping command available. They choose iputils-ping, which is rather linux specific. Could be possible to switch (at least on non-linux) to inetutils-ping (already available) or fping (modulo #555398 available). It will help to kfreebsd-i386, kfreebsd-amd64 and hurd architectures. Thanks for considering it. You can track the bugreport via http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=555532 check_ping could maybe rewritten/patched to use liboping [1]? Thanks and kind regards, Jan. [1] http://verplant.org/liboping/ ---------------------------------------------------------------------- Comment By: Thomas Guyot-Sionnest (dermoth) Date: 2009-12-04 15:48 Message: Gotchya. --with-ping[6]-command expected three arguments - two numeric and one string. I try to detect it now (attached patch) - will go upstream it it works for you... ---------------------------------------------------------------------- Comment By: Jan Wagner (cyco_dd) Date: 2009-11-23 10:47 Message: Unfortunately I have. :( Maybe you can have a look: normal debian package - using iputils-ping and compile following flags: --with-ping-command="/bin/ping -n -U -w %d -c %d %s" \ --with-ping6-command="/bin/ping6 -n -U -w %d -c %d %s" \ sid:~# /usr/lib/nagios/plugins/check_ping 127.0.0.1 -w 2,20% -c 5,30% PING OK - Packet loss = 0%, RTA = 0.00 ms| rta=0.000000ms;2.000000;5.000000;0.000000 pl=0%;20;30;0 Okay ... thats fine, like always. ---- pc1 - using iputils-ping and following compile flags: --with-ping-command="/bin/ping -n -c %d %s" \ --with-ping6-command="/bin/ping6 -n -c %d %s" \ sid:/tmp# LANG=C /usr/lib/nagios/plugins/check_ping 127.0.0.1 -w 2,20% -c 5,30% Speicherzugriffsfehler Okay ... here are just the ping commands wrong ---- pc2 - using iputils-ping and without specific compile flags (iputils-ping installed at compile time), but: checking for ICMP ping syntax... /bin/ping -n -U -w %d -c %d %s checking for ICMPv6 ping syntax... /bin/ping6 -n -U -w %d -c %d %s sid:/tmp# LANG=C /usr/lib/nagios/plugins/check_ping 127.0.0.1 -w 2,20% -c 5,30% PING OK - Packet loss = 0%, RTA = 0.00 ms| rta=0.000000ms;2.000000;5.000000;0.000000 pl=0%;20;30;0 Thats also fine, the commands are autodetected. ---- pc3 - using inetutils-ping and without specific compile flags (inetutils-ping installed at compile time), but: checking for ICMP ping syntax... /bin/ping -n -c %d %s checking for ICMPv6 ping syntax... /bin/ping6 -n -c %d %s sid:/tmp# LANG=C /usr/lib/nagios/plugins/check_ping 127.0.0.1 -w 2,20% -c 5,30% PING OK - Packet loss = 0%, RTA = 0.00 ms| rta=0.000000ms;2.000000;5.000000;0.000000 pl=0%;20;30;0 Looks great, command are autodetected and inetutils-ping works ---- pc4 - using inetutils-ping and the following compile flags (inetutils-ping NOT installed at compile time): --with-ping6-command="/bin/ping6 -n -c %d %s" \ --with-ping-command="/bin/ping -n -c %d %s" \ sid:/tmp# LANG=C /usr/lib/nagios/plugins/check_ping 127.0.0.1 -w 2,20% -c 5,30% Speicherzugriffsfehler This is the point I don't get. I'm using the same commands like the once when they where autodetected, but check_ping segfaults .... I'm missing something? Thanks for your help, Jan. ---------------------------------------------------------------------- Comment By: Thomas Guyot-Sionnest (dermoth) Date: 2009-11-11 17:29 Message: Normally configure decides which ping command and syntax to use, so it really depend on which packages you have installed. You can force the command to use with --with-ping-command=SYNTAX and --with-ping6-command=SYNTAX. An easy way to find the syntax it to look at a generated config.h when only the wanted ping commands are available. Search for #define PING_COMMAND and #define PING6_COMMAND. Let me know if you have any problem with specific ping variants. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=397597&aid=2896201&group_id=29880 From noreply at sourceforge.net Sat Dec 5 06:02:21 2009 From: noreply at sourceforge.net (SourceForge.net) Date: Sat, 05 Dec 2009 05:02:21 +0000 Subject: [Nagiosplug-devel] [ nagiosplug-Bugs-2896201 ] check_ping depends on iputils-ping Message-ID: Bugs item #2896201, was opened at 2009-11-11 15:37 Message generated for change (Comment added) made by dermoth You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=397597&aid=2896201&group_id=29880 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: General plugin execution Group: release-1.4.15 Status: Open Resolution: None Priority: 5 Private: No Submitted By: Jan Wagner (cyco_dd) Assigned to: Thomas Guyot-Sionnest (dermoth) Summary: check_ping depends on iputils-ping Initial Comment: The following Bugreport we got against our debian package: Hi, it seems that the nagios related packages need an ping command available. They choose iputils-ping, which is rather linux specific. Could be possible to switch (at least on non-linux) to inetutils-ping (already available) or fping (modulo #555398 available). It will help to kfreebsd-i386, kfreebsd-amd64 and hurd architectures. Thanks for considering it. You can track the bugreport via http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=555532 check_ping could maybe rewritten/patched to use liboping [1]? Thanks and kind regards, Jan. [1] http://verplant.org/liboping/ ---------------------------------------------------------------------- >Comment By: Thomas Guyot-Sionnest (dermoth) Date: 2009-12-05 00:02 Message: [ Proxying response from Jan... ] When autodetecting with inetutils-ping installed on buildtime all works fine Defining the commands (like the once when autodetected) and inetutils-ping having not installed when building gives me a segfault on runtime inetutils-ping installed on buildtime/autodetect: waja at packaging:~/debian-builds/nagios-plugins/trunk$ grep "ping syntax" ../build-area/nagios-plugins_1.4.14-1~pc4_i386.build checking for ICMP ping syntax... /bin/ping -n -c %d %s checking for ICMPv6 ping syntax... /bin/ping6 -n -c %d %s checking for ICMP ping syntax... /bin/ping -n -c %d %s checking for ICMPv6 ping syntax... /bin/ping6 -n -c %d %s Exectution works fine. inetutils-ping removed on buildtime/command defined: waja at packaging:~/debian-builds/nagios-plugins/trunk$ grep "ping syntax" ../build-area/nagios-plugins_1.4.14-1_i386.build checking for ICMP ping syntax... (command-line) /bin/ping -n -c %d %s checking for ICMPv6 ping syntax... (command-line) /bin/ping6 -n -c %d %s checking for ICMP ping syntax... (command-line) /bin/ping -n -c %d %s checking for ICMPv6 ping syntax... (command-line) /bin/ping6 -n -c %d %s packaging:~# LANG=C /usr/lib/nagios/plugins/check_ping 127.0.0.1 -w 2,20% -c 5,30% Segmentation fault ---------------------------------------------------------------------- Comment By: Thomas Guyot-Sionnest (dermoth) Date: 2009-12-04 15:48 Message: Gotchya. --with-ping[6]-command expected three arguments - two numeric and one string. I try to detect it now (attached patch) - will go upstream it it works for you... ---------------------------------------------------------------------- Comment By: Jan Wagner (cyco_dd) Date: 2009-11-23 10:47 Message: Unfortunately I have. :( Maybe you can have a look: normal debian package - using iputils-ping and compile following flags: --with-ping-command="/bin/ping -n -U -w %d -c %d %s" \ --with-ping6-command="/bin/ping6 -n -U -w %d -c %d %s" \ sid:~# /usr/lib/nagios/plugins/check_ping 127.0.0.1 -w 2,20% -c 5,30% PING OK - Packet loss = 0%, RTA = 0.00 ms| rta=0.000000ms;2.000000;5.000000;0.000000 pl=0%;20;30;0 Okay ... thats fine, like always. ---- pc1 - using iputils-ping and following compile flags: --with-ping-command="/bin/ping -n -c %d %s" \ --with-ping6-command="/bin/ping6 -n -c %d %s" \ sid:/tmp# LANG=C /usr/lib/nagios/plugins/check_ping 127.0.0.1 -w 2,20% -c 5,30% Speicherzugriffsfehler Okay ... here are just the ping commands wrong ---- pc2 - using iputils-ping and without specific compile flags (iputils-ping installed at compile time), but: checking for ICMP ping syntax... /bin/ping -n -U -w %d -c %d %s checking for ICMPv6 ping syntax... /bin/ping6 -n -U -w %d -c %d %s sid:/tmp# LANG=C /usr/lib/nagios/plugins/check_ping 127.0.0.1 -w 2,20% -c 5,30% PING OK - Packet loss = 0%, RTA = 0.00 ms| rta=0.000000ms;2.000000;5.000000;0.000000 pl=0%;20;30;0 Thats also fine, the commands are autodetected. ---- pc3 - using inetutils-ping and without specific compile flags (inetutils-ping installed at compile time), but: checking for ICMP ping syntax... /bin/ping -n -c %d %s checking for ICMPv6 ping syntax... /bin/ping6 -n -c %d %s sid:/tmp# LANG=C /usr/lib/nagios/plugins/check_ping 127.0.0.1 -w 2,20% -c 5,30% PING OK - Packet loss = 0%, RTA = 0.00 ms| rta=0.000000ms;2.000000;5.000000;0.000000 pl=0%;20;30;0 Looks great, command are autodetected and inetutils-ping works ---- pc4 - using inetutils-ping and the following compile flags (inetutils-ping NOT installed at compile time): --with-ping6-command="/bin/ping6 -n -c %d %s" \ --with-ping-command="/bin/ping -n -c %d %s" \ sid:/tmp# LANG=C /usr/lib/nagios/plugins/check_ping 127.0.0.1 -w 2,20% -c 5,30% Speicherzugriffsfehler This is the point I don't get. I'm using the same commands like the once when they where autodetected, but check_ping segfaults .... I'm missing something? Thanks for your help, Jan. ---------------------------------------------------------------------- Comment By: Thomas Guyot-Sionnest (dermoth) Date: 2009-11-11 17:29 Message: Normally configure decides which ping command and syntax to use, so it really depend on which packages you have installed. You can force the command to use with --with-ping-command=SYNTAX and --with-ping6-command=SYNTAX. An easy way to find the syntax it to look at a generated config.h when only the wanted ping commands are available. Search for #define PING_COMMAND and #define PING6_COMMAND. Let me know if you have any problem with specific ping variants. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=397597&aid=2896201&group_id=29880 From noreply at sourceforge.net Sat Dec 5 06:03:12 2009 From: noreply at sourceforge.net (SourceForge.net) Date: Sat, 05 Dec 2009 05:03:12 +0000 Subject: [Nagiosplug-devel] [ nagiosplug-Bugs-2896201 ] check_ping depends on iputils-ping Message-ID: Bugs item #2896201, was opened at 2009-11-11 15:37 Message generated for change (Comment added) made by dermoth You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=397597&aid=2896201&group_id=29880 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: General plugin execution Group: release-1.4.15 Status: Open Resolution: None Priority: 5 Private: No Submitted By: Jan Wagner (cyco_dd) Assigned to: Thomas Guyot-Sionnest (dermoth) Summary: check_ping depends on iputils-ping Initial Comment: The following Bugreport we got against our debian package: Hi, it seems that the nagios related packages need an ping command available. They choose iputils-ping, which is rather linux specific. Could be possible to switch (at least on non-linux) to inetutils-ping (already available) or fping (modulo #555398 available). It will help to kfreebsd-i386, kfreebsd-amd64 and hurd architectures. Thanks for considering it. You can track the bugreport via http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=555532 check_ping could maybe rewritten/patched to use liboping [1]? Thanks and kind regards, Jan. [1] http://verplant.org/liboping/ ---------------------------------------------------------------------- >Comment By: Thomas Guyot-Sionnest (dermoth) Date: 2009-12-05 00:03 Message: I'll double check... So what are the configure arguments in both cases? ---------------------------------------------------------------------- Comment By: Thomas Guyot-Sionnest (dermoth) Date: 2009-12-05 00:02 Message: [ Proxying response from Jan... ] When autodetecting with inetutils-ping installed on buildtime all works fine Defining the commands (like the once when autodetected) and inetutils-ping having not installed when building gives me a segfault on runtime inetutils-ping installed on buildtime/autodetect: waja at packaging:~/debian-builds/nagios-plugins/trunk$ grep "ping syntax" ../build-area/nagios-plugins_1.4.14-1~pc4_i386.build checking for ICMP ping syntax... /bin/ping -n -c %d %s checking for ICMPv6 ping syntax... /bin/ping6 -n -c %d %s checking for ICMP ping syntax... /bin/ping -n -c %d %s checking for ICMPv6 ping syntax... /bin/ping6 -n -c %d %s Exectution works fine. inetutils-ping removed on buildtime/command defined: waja at packaging:~/debian-builds/nagios-plugins/trunk$ grep "ping syntax" ../build-area/nagios-plugins_1.4.14-1_i386.build checking for ICMP ping syntax... (command-line) /bin/ping -n -c %d %s checking for ICMPv6 ping syntax... (command-line) /bin/ping6 -n -c %d %s checking for ICMP ping syntax... (command-line) /bin/ping -n -c %d %s checking for ICMPv6 ping syntax... (command-line) /bin/ping6 -n -c %d %s packaging:~# LANG=C /usr/lib/nagios/plugins/check_ping 127.0.0.1 -w 2,20% -c 5,30% Segmentation fault ---------------------------------------------------------------------- Comment By: Thomas Guyot-Sionnest (dermoth) Date: 2009-12-04 15:48 Message: Gotchya. --with-ping[6]-command expected three arguments - two numeric and one string. I try to detect it now (attached patch) - will go upstream it it works for you... ---------------------------------------------------------------------- Comment By: Jan Wagner (cyco_dd) Date: 2009-11-23 10:47 Message: Unfortunately I have. :( Maybe you can have a look: normal debian package - using iputils-ping and compile following flags: --with-ping-command="/bin/ping -n -U -w %d -c %d %s" \ --with-ping6-command="/bin/ping6 -n -U -w %d -c %d %s" \ sid:~# /usr/lib/nagios/plugins/check_ping 127.0.0.1 -w 2,20% -c 5,30% PING OK - Packet loss = 0%, RTA = 0.00 ms| rta=0.000000ms;2.000000;5.000000;0.000000 pl=0%;20;30;0 Okay ... thats fine, like always. ---- pc1 - using iputils-ping and following compile flags: --with-ping-command="/bin/ping -n -c %d %s" \ --with-ping6-command="/bin/ping6 -n -c %d %s" \ sid:/tmp# LANG=C /usr/lib/nagios/plugins/check_ping 127.0.0.1 -w 2,20% -c 5,30% Speicherzugriffsfehler Okay ... here are just the ping commands wrong ---- pc2 - using iputils-ping and without specific compile flags (iputils-ping installed at compile time), but: checking for ICMP ping syntax... /bin/ping -n -U -w %d -c %d %s checking for ICMPv6 ping syntax... /bin/ping6 -n -U -w %d -c %d %s sid:/tmp# LANG=C /usr/lib/nagios/plugins/check_ping 127.0.0.1 -w 2,20% -c 5,30% PING OK - Packet loss = 0%, RTA = 0.00 ms| rta=0.000000ms;2.000000;5.000000;0.000000 pl=0%;20;30;0 Thats also fine, the commands are autodetected. ---- pc3 - using inetutils-ping and without specific compile flags (inetutils-ping installed at compile time), but: checking for ICMP ping syntax... /bin/ping -n -c %d %s checking for ICMPv6 ping syntax... /bin/ping6 -n -c %d %s sid:/tmp# LANG=C /usr/lib/nagios/plugins/check_ping 127.0.0.1 -w 2,20% -c 5,30% PING OK - Packet loss = 0%, RTA = 0.00 ms| rta=0.000000ms;2.000000;5.000000;0.000000 pl=0%;20;30;0 Looks great, command are autodetected and inetutils-ping works ---- pc4 - using inetutils-ping and the following compile flags (inetutils-ping NOT installed at compile time): --with-ping6-command="/bin/ping6 -n -c %d %s" \ --with-ping-command="/bin/ping -n -c %d %s" \ sid:/tmp# LANG=C /usr/lib/nagios/plugins/check_ping 127.0.0.1 -w 2,20% -c 5,30% Speicherzugriffsfehler This is the point I don't get. I'm using the same commands like the once when they where autodetected, but check_ping segfaults .... I'm missing something? Thanks for your help, Jan. ---------------------------------------------------------------------- Comment By: Thomas Guyot-Sionnest (dermoth) Date: 2009-11-11 17:29 Message: Normally configure decides which ping command and syntax to use, so it really depend on which packages you have installed. You can force the command to use with --with-ping-command=SYNTAX and --with-ping6-command=SYNTAX. An easy way to find the syntax it to look at a generated config.h when only the wanted ping commands are available. Search for #define PING_COMMAND and #define PING6_COMMAND. Let me know if you have any problem with specific ping variants. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=397597&aid=2896201&group_id=29880 From noreply at sourceforge.net Sat Dec 5 06:44:41 2009 From: noreply at sourceforge.net (SourceForge.net) Date: Sat, 05 Dec 2009 05:44:41 +0000 Subject: [Nagiosplug-devel] [ nagiosplug-Patches-2908236 ] Support for larger numbers in the perfdata utility function Message-ID: Patches item #2908236, was opened at 2009-12-03 11:00 Message generated for change (Comment added) made by dermoth You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=397599&aid=2908236&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: Perf data Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Henrik Nilsson (rakhun) Assigned to: Nobody/Anonymous (nobody) Summary: Support for larger numbers in the perfdata utility function Initial Comment: Hi, this patch enables the perfdata utility function to work with larger numbers, such as check_disk with bytes as output unit, which would otherwise return large, negative numbers ---------------------------------------------------------------------- >Comment By: Thomas Guyot-Sionnest (dermoth) Date: 2009-12-05 00:44 Message: Thanks for the patch, although I'm wondering how useful it would be. There's no question about the need to graph large values, but this code will likely change a lot before we may think of changing check_disk's output format. Also I'm wondering it it wouldn't be wiser to use double for big values. AFAIK long long is not even supported natively by Perl, and RRD files use doubles. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=397599&aid=2908236&group_id=29880 From noreply at sourceforge.net Sat Dec 5 07:36:43 2009 From: noreply at sourceforge.net (SourceForge.net) Date: Sat, 05 Dec 2009 06:36:43 +0000 Subject: [Nagiosplug-devel] [ nagiosplug-Bugs-2896201 ] check_ping depends on iputils-ping Message-ID: Bugs item #2896201, was opened at 2009-11-11 15:37 Message generated for change (Comment added) made by dermoth You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=397597&aid=2896201&group_id=29880 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: General plugin execution Group: release-1.4.15 Status: Open Resolution: None Priority: 5 Private: No Submitted By: Jan Wagner (cyco_dd) Assigned to: Thomas Guyot-Sionnest (dermoth) Summary: check_ping depends on iputils-ping Initial Comment: The following Bugreport we got against our debian package: Hi, it seems that the nagios related packages need an ping command available. They choose iputils-ping, which is rather linux specific. Could be possible to switch (at least on non-linux) to inetutils-ping (already available) or fping (modulo #555398 available). It will help to kfreebsd-i386, kfreebsd-amd64 and hurd architectures. Thanks for considering it. You can track the bugreport via http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=555532 check_ping could maybe rewritten/patched to use liboping [1]? Thanks and kind regards, Jan. [1] http://verplant.org/liboping/ ---------------------------------------------------------------------- >Comment By: Thomas Guyot-Sionnest (dermoth) Date: 2009-12-05 01:36 Message: Nevermind - the output you sent is ok... So are you really getting this twice (I don't, wondering if it may be related to your issue)? checking for ICMP ping syntax... (command-line) /bin/ping6 -n -c %d %s checking for ICMPv6 ping syntax... (command-line) /bin/ping -n -c %d %s Please check config.h and tell me what you have defined for: - PING6_COMMAND - PING6_PACKETS_FIRST - PING_COMMAND - PING_HAS_TIMEOUT - PING_PACKETS_FIRST Also I figured I should also change it for ping6, I'll attach an updated patch. ---------------------------------------------------------------------- Comment By: Thomas Guyot-Sionnest (dermoth) Date: 2009-12-05 00:03 Message: I'll double check... So what are the configure arguments in both cases? ---------------------------------------------------------------------- Comment By: Thomas Guyot-Sionnest (dermoth) Date: 2009-12-05 00:02 Message: [ Proxying response from Jan... ] When autodetecting with inetutils-ping installed on buildtime all works fine Defining the commands (like the once when autodetected) and inetutils-ping having not installed when building gives me a segfault on runtime inetutils-ping installed on buildtime/autodetect: waja at packaging:~/debian-builds/nagios-plugins/trunk$ grep "ping syntax" ../build-area/nagios-plugins_1.4.14-1~pc4_i386.build checking for ICMP ping syntax... /bin/ping -n -c %d %s checking for ICMPv6 ping syntax... /bin/ping6 -n -c %d %s checking for ICMP ping syntax... /bin/ping -n -c %d %s checking for ICMPv6 ping syntax... /bin/ping6 -n -c %d %s Exectution works fine. inetutils-ping removed on buildtime/command defined: waja at packaging:~/debian-builds/nagios-plugins/trunk$ grep "ping syntax" ../build-area/nagios-plugins_1.4.14-1_i386.build checking for ICMP ping syntax... (command-line) /bin/ping -n -c %d %s checking for ICMPv6 ping syntax... (command-line) /bin/ping6 -n -c %d %s checking for ICMP ping syntax... (command-line) /bin/ping -n -c %d %s checking for ICMPv6 ping syntax... (command-line) /bin/ping6 -n -c %d %s packaging:~# LANG=C /usr/lib/nagios/plugins/check_ping 127.0.0.1 -w 2,20% -c 5,30% Segmentation fault ---------------------------------------------------------------------- Comment By: Thomas Guyot-Sionnest (dermoth) Date: 2009-12-04 15:48 Message: Gotchya. --with-ping[6]-command expected three arguments - two numeric and one string. I try to detect it now (attached patch) - will go upstream it it works for you... ---------------------------------------------------------------------- Comment By: Jan Wagner (cyco_dd) Date: 2009-11-23 10:47 Message: Unfortunately I have. :( Maybe you can have a look: normal debian package - using iputils-ping and compile following flags: --with-ping-command="/bin/ping -n -U -w %d -c %d %s" \ --with-ping6-command="/bin/ping6 -n -U -w %d -c %d %s" \ sid:~# /usr/lib/nagios/plugins/check_ping 127.0.0.1 -w 2,20% -c 5,30% PING OK - Packet loss = 0%, RTA = 0.00 ms| rta=0.000000ms;2.000000;5.000000;0.000000 pl=0%;20;30;0 Okay ... thats fine, like always. ---- pc1 - using iputils-ping and following compile flags: --with-ping-command="/bin/ping -n -c %d %s" \ --with-ping6-command="/bin/ping6 -n -c %d %s" \ sid:/tmp# LANG=C /usr/lib/nagios/plugins/check_ping 127.0.0.1 -w 2,20% -c 5,30% Speicherzugriffsfehler Okay ... here are just the ping commands wrong ---- pc2 - using iputils-ping and without specific compile flags (iputils-ping installed at compile time), but: checking for ICMP ping syntax... /bin/ping -n -U -w %d -c %d %s checking for ICMPv6 ping syntax... /bin/ping6 -n -U -w %d -c %d %s sid:/tmp# LANG=C /usr/lib/nagios/plugins/check_ping 127.0.0.1 -w 2,20% -c 5,30% PING OK - Packet loss = 0%, RTA = 0.00 ms| rta=0.000000ms;2.000000;5.000000;0.000000 pl=0%;20;30;0 Thats also fine, the commands are autodetected. ---- pc3 - using inetutils-ping and without specific compile flags (inetutils-ping installed at compile time), but: checking for ICMP ping syntax... /bin/ping -n -c %d %s checking for ICMPv6 ping syntax... /bin/ping6 -n -c %d %s sid:/tmp# LANG=C /usr/lib/nagios/plugins/check_ping 127.0.0.1 -w 2,20% -c 5,30% PING OK - Packet loss = 0%, RTA = 0.00 ms| rta=0.000000ms;2.000000;5.000000;0.000000 pl=0%;20;30;0 Looks great, command are autodetected and inetutils-ping works ---- pc4 - using inetutils-ping and the following compile flags (inetutils-ping NOT installed at compile time): --with-ping6-command="/bin/ping6 -n -c %d %s" \ --with-ping-command="/bin/ping -n -c %d %s" \ sid:/tmp# LANG=C /usr/lib/nagios/plugins/check_ping 127.0.0.1 -w 2,20% -c 5,30% Speicherzugriffsfehler This is the point I don't get. I'm using the same commands like the once when they where autodetected, but check_ping segfaults .... I'm missing something? Thanks for your help, Jan. ---------------------------------------------------------------------- Comment By: Thomas Guyot-Sionnest (dermoth) Date: 2009-11-11 17:29 Message: Normally configure decides which ping command and syntax to use, so it really depend on which packages you have installed. You can force the command to use with --with-ping-command=SYNTAX and --with-ping6-command=SYNTAX. An easy way to find the syntax it to look at a generated config.h when only the wanted ping commands are available. Search for #define PING_COMMAND and #define PING6_COMMAND. Let me know if you have any problem with specific ping variants. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=397597&aid=2896201&group_id=29880 From noreply at sourceforge.net Sat Dec 5 15:36:00 2009 From: noreply at sourceforge.net (SourceForge.net) Date: Sat, 05 Dec 2009 14:36:00 +0000 Subject: [Nagiosplug-devel] [ nagiosplug-Bugs-2896201 ] check_ping depends on iputils-ping Message-ID: Bugs item #2896201, was opened at 2009-11-11 21:37 Message generated for change (Comment added) made by cyco_dd You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=397597&aid=2896201&group_id=29880 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: General plugin execution Group: release-1.4.15 Status: Open Resolution: None Priority: 5 Private: No Submitted By: Jan Wagner (cyco_dd) Assigned to: Thomas Guyot-Sionnest (dermoth) Summary: check_ping depends on iputils-ping Initial Comment: The following Bugreport we got against our debian package: Hi, it seems that the nagios related packages need an ping command available. They choose iputils-ping, which is rather linux specific. Could be possible to switch (at least on non-linux) to inetutils-ping (already available) or fping (modulo #555398 available). It will help to kfreebsd-i386, kfreebsd-amd64 and hurd architectures. Thanks for considering it. You can track the bugreport via http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=555532 check_ping could maybe rewritten/patched to use liboping [1]? Thanks and kind regards, Jan. [1] http://verplant.org/liboping/ ---------------------------------------------------------------------- Comment By: Jan Wagner (cyco_dd) Date: 2009-12-05 15:36 Message: I'm getting this twice, since configure is issueing "/bin/sh ./config.status --recheck". That should be unrelated to the issue. The configure arguments are: NP_LIBEXEC:=/usr/lib/nagios/plugins ./configure \ --host=$(DEB_HOST_GNU_TYPE) \ --build=$(DEB_BUILD_GNU_TYPE) \ --prefix=/usr \ --mandir=/usr/share/man \ --infodir=/usr/share/info \ --libexecdir=${NP_LIBEXEC} \ --with-perl=/usr/bin/perl \ --with-openssl=/usr \ --with-pgsql=/usr \ --with-mysql=/usr \ --with-proc-loadavg=/proc/loadavg \ --with-ps-command="/bin/ps axwo 'stat uid pid ppid vsz rss pcpu etime comm args'" \ --with-ps-format="%s %d %d %d %d %d %f %s %s %n" \ --with-ps-cols=10 \ --with-ps-varlist="procstat,&procuid,&procpid,&procppid,&procvsz,&procrss,&procpcpu,procetime,procprog,&pos" \ --with-ping-command="/bin/ping -n -c %d %s" \ --with-ping6-command="/bin/ping6 -n -c %d %s" \ --with-nslookup-command="/usr/bin/nslookup -sil" \ --with-uptime-command="/usr/bin/uptime" \ --with-rpcinfo-command="/usr/bin/rpcinfo" \ --with-smbclient-command="/usr/bin/smbclient" \ --with-snmpget-command="/usr/bin/snmpget" \ --with-snmpgetnext-command="/usr/bin/snmpgetnext" \ --with-qstat-command="/usr/bin/quakestat" \ --with-fping-command="/usr/bin/fping" \ --with-ssh-command="/usr/bin/ssh" \ --with-mailq-command="/usr/bin/mailq" \ --with-proc-meminfo="/proc/meminfo" \ --with-dig-command="/usr/bin/dig" \ --with-apt-get-command="/usr/bin/apt-get" \ --disable-rpath Which fails with this at runtime. Working is installing inetutils-ping at build time and dropping --with-ping* from configure. With defined ping commands, in config.h I have: #define PING6_COMMAND "/bin/ping6 -n -c %d %s" #define PING6_PACKETS_FIRST 1 #define PING_COMMAND "/bin/ping -n -c %d %s" #define PING_HAS_TIMEOUT 1 #define PING_PACKETS_FIRST 1 Anyways ... I get also with your latest patch: # LANG=C /usr/lib/nagios/plugins/check_ping 127.0.0.1 -w 2,20% -c 5,30% Segmentation fault Without defining the ping commands and inetutils-ping installed, I get: #define PING6_COMMAND "/bin/ping6 -n -c %d %s" #define PING6_PACKETS_FIRST 1 #define PING_COMMAND "/bin/ping -n -c %d %s" /* #undef PING_HAS_TIMEOUT */ #define PING_PACKETS_FIRST 1 # LANG=C /usr/lib/nagios/plugins/check_ping 127.0.0.1 -w 2,20% -c 5,30% PING OK - Packet loss = 0%, RTA = 0.00 ms|rta=0.000000ms;2.000000;5.000000;0.000000 pl=0%;20;30;0 ---------------------------------------------------------------------- Comment By: Thomas Guyot-Sionnest (dermoth) Date: 2009-12-05 07:36 Message: Nevermind - the output you sent is ok... So are you really getting this twice (I don't, wondering if it may be related to your issue)? checking for ICMP ping syntax... (command-line) /bin/ping6 -n -c %d %s checking for ICMPv6 ping syntax... (command-line) /bin/ping -n -c %d %s Please check config.h and tell me what you have defined for: - PING6_COMMAND - PING6_PACKETS_FIRST - PING_COMMAND - PING_HAS_TIMEOUT - PING_PACKETS_FIRST Also I figured I should also change it for ping6, I'll attach an updated patch. ---------------------------------------------------------------------- Comment By: Thomas Guyot-Sionnest (dermoth) Date: 2009-12-05 06:03 Message: I'll double check... So what are the configure arguments in both cases? ---------------------------------------------------------------------- Comment By: Thomas Guyot-Sionnest (dermoth) Date: 2009-12-05 06:02 Message: [ Proxying response from Jan... ] When autodetecting with inetutils-ping installed on buildtime all works fine Defining the commands (like the once when autodetected) and inetutils-ping having not installed when building gives me a segfault on runtime inetutils-ping installed on buildtime/autodetect: waja at packaging:~/debian-builds/nagios-plugins/trunk$ grep "ping syntax" ../build-area/nagios-plugins_1.4.14-1~pc4_i386.build checking for ICMP ping syntax... /bin/ping -n -c %d %s checking for ICMPv6 ping syntax... /bin/ping6 -n -c %d %s checking for ICMP ping syntax... /bin/ping -n -c %d %s checking for ICMPv6 ping syntax... /bin/ping6 -n -c %d %s Exectution works fine. inetutils-ping removed on buildtime/command defined: waja at packaging:~/debian-builds/nagios-plugins/trunk$ grep "ping syntax" ../build-area/nagios-plugins_1.4.14-1_i386.build checking for ICMP ping syntax... (command-line) /bin/ping -n -c %d %s checking for ICMPv6 ping syntax... (command-line) /bin/ping6 -n -c %d %s checking for ICMP ping syntax... (command-line) /bin/ping -n -c %d %s checking for ICMPv6 ping syntax... (command-line) /bin/ping6 -n -c %d %s packaging:~# LANG=C /usr/lib/nagios/plugins/check_ping 127.0.0.1 -w 2,20% -c 5,30% Segmentation fault ---------------------------------------------------------------------- Comment By: Thomas Guyot-Sionnest (dermoth) Date: 2009-12-04 21:48 Message: Gotchya. --with-ping[6]-command expected three arguments - two numeric and one string. I try to detect it now (attached patch) - will go upstream it it works for you... ---------------------------------------------------------------------- Comment By: Jan Wagner (cyco_dd) Date: 2009-11-23 16:47 Message: Unfortunately I have. :( Maybe you can have a look: normal debian package - using iputils-ping and compile following flags: --with-ping-command="/bin/ping -n -U -w %d -c %d %s" \ --with-ping6-command="/bin/ping6 -n -U -w %d -c %d %s" \ sid:~# /usr/lib/nagios/plugins/check_ping 127.0.0.1 -w 2,20% -c 5,30% PING OK - Packet loss = 0%, RTA = 0.00 ms| rta=0.000000ms;2.000000;5.000000;0.000000 pl=0%;20;30;0 Okay ... thats fine, like always. ---- pc1 - using iputils-ping and following compile flags: --with-ping-command="/bin/ping -n -c %d %s" \ --with-ping6-command="/bin/ping6 -n -c %d %s" \ sid:/tmp# LANG=C /usr/lib/nagios/plugins/check_ping 127.0.0.1 -w 2,20% -c 5,30% Speicherzugriffsfehler Okay ... here are just the ping commands wrong ---- pc2 - using iputils-ping and without specific compile flags (iputils-ping installed at compile time), but: checking for ICMP ping syntax... /bin/ping -n -U -w %d -c %d %s checking for ICMPv6 ping syntax... /bin/ping6 -n -U -w %d -c %d %s sid:/tmp# LANG=C /usr/lib/nagios/plugins/check_ping 127.0.0.1 -w 2,20% -c 5,30% PING OK - Packet loss = 0%, RTA = 0.00 ms| rta=0.000000ms;2.000000;5.000000;0.000000 pl=0%;20;30;0 Thats also fine, the commands are autodetected. ---- pc3 - using inetutils-ping and without specific compile flags (inetutils-ping installed at compile time), but: checking for ICMP ping syntax... /bin/ping -n -c %d %s checking for ICMPv6 ping syntax... /bin/ping6 -n -c %d %s sid:/tmp# LANG=C /usr/lib/nagios/plugins/check_ping 127.0.0.1 -w 2,20% -c 5,30% PING OK - Packet loss = 0%, RTA = 0.00 ms| rta=0.000000ms;2.000000;5.000000;0.000000 pl=0%;20;30;0 Looks great, command are autodetected and inetutils-ping works ---- pc4 - using inetutils-ping and the following compile flags (inetutils-ping NOT installed at compile time): --with-ping6-command="/bin/ping6 -n -c %d %s" \ --with-ping-command="/bin/ping -n -c %d %s" \ sid:/tmp# LANG=C /usr/lib/nagios/plugins/check_ping 127.0.0.1 -w 2,20% -c 5,30% Speicherzugriffsfehler This is the point I don't get. I'm using the same commands like the once when they where autodetected, but check_ping segfaults .... I'm missing something? Thanks for your help, Jan. ---------------------------------------------------------------------- Comment By: Thomas Guyot-Sionnest (dermoth) Date: 2009-11-11 23:29 Message: Normally configure decides which ping command and syntax to use, so it really depend on which packages you have installed. You can force the command to use with --with-ping-command=SYNTAX and --with-ping6-command=SYNTAX. An easy way to find the syntax it to look at a generated config.h when only the wanted ping commands are available. Search for #define PING_COMMAND and #define PING6_COMMAND. Let me know if you have any problem with specific ping variants. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=397597&aid=2896201&group_id=29880 From noreply at sourceforge.net Sat Dec 5 21:17:50 2009 From: noreply at sourceforge.net (SourceForge.net) Date: Sat, 05 Dec 2009 20:17:50 +0000 Subject: [Nagiosplug-devel] [ nagiosplug-Bugs-2896201 ] check_ping depends on iputils-ping Message-ID: Bugs item #2896201, was opened at 2009-11-11 15:37 Message generated for change (Comment added) made by dermoth You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=397597&aid=2896201&group_id=29880 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: General plugin execution Group: release-1.4.15 Status: Open Resolution: None Priority: 5 Private: No Submitted By: Jan Wagner (cyco_dd) Assigned to: Thomas Guyot-Sionnest (dermoth) Summary: check_ping depends on iputils-ping Initial Comment: The following Bugreport we got against our debian package: Hi, it seems that the nagios related packages need an ping command available. They choose iputils-ping, which is rather linux specific. Could be possible to switch (at least on non-linux) to inetutils-ping (already available) or fping (modulo #555398 available). It will help to kfreebsd-i386, kfreebsd-amd64 and hurd architectures. Thanks for considering it. You can track the bugreport via http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=555532 check_ping could maybe rewritten/patched to use liboping [1]? Thanks and kind regards, Jan. [1] http://verplant.org/liboping/ ---------------------------------------------------------------------- >Comment By: Thomas Guyot-Sionnest (dermoth) Date: 2009-12-05 15:17 Message: So as discusson on IRC your build process do not re-generate autoconf. This is done automatically if you have the rigth software installed, but it may be simpler to use the attached patches Since I fixed a bunch of whitespaces the first patch may apply only if you ignore whitespace mismatches - the 2nd may apply correctly ---------------------------------------------------------------------- Comment By: Jan Wagner (cyco_dd) Date: 2009-12-05 09:36 Message: I'm getting this twice, since configure is issueing "/bin/sh ./config.status --recheck". That should be unrelated to the issue. The configure arguments are: NP_LIBEXEC:=/usr/lib/nagios/plugins ./configure \ --host=$(DEB_HOST_GNU_TYPE) \ --build=$(DEB_BUILD_GNU_TYPE) \ --prefix=/usr \ --mandir=/usr/share/man \ --infodir=/usr/share/info \ --libexecdir=${NP_LIBEXEC} \ --with-perl=/usr/bin/perl \ --with-openssl=/usr \ --with-pgsql=/usr \ --with-mysql=/usr \ --with-proc-loadavg=/proc/loadavg \ --with-ps-command="/bin/ps axwo 'stat uid pid ppid vsz rss pcpu etime comm args'" \ --with-ps-format="%s %d %d %d %d %d %f %s %s %n" \ --with-ps-cols=10 \ --with-ps-varlist="procstat,&procuid,&procpid,&procppid,&procvsz,&procrss,&procpcpu,procetime,procprog,&pos" \ --with-ping-command="/bin/ping -n -c %d %s" \ --with-ping6-command="/bin/ping6 -n -c %d %s" \ --with-nslookup-command="/usr/bin/nslookup -sil" \ --with-uptime-command="/usr/bin/uptime" \ --with-rpcinfo-command="/usr/bin/rpcinfo" \ --with-smbclient-command="/usr/bin/smbclient" \ --with-snmpget-command="/usr/bin/snmpget" \ --with-snmpgetnext-command="/usr/bin/snmpgetnext" \ --with-qstat-command="/usr/bin/quakestat" \ --with-fping-command="/usr/bin/fping" \ --with-ssh-command="/usr/bin/ssh" \ --with-mailq-command="/usr/bin/mailq" \ --with-proc-meminfo="/proc/meminfo" \ --with-dig-command="/usr/bin/dig" \ --with-apt-get-command="/usr/bin/apt-get" \ --disable-rpath Which fails with this at runtime. Working is installing inetutils-ping at build time and dropping --with-ping* from configure. With defined ping commands, in config.h I have: #define PING6_COMMAND "/bin/ping6 -n -c %d %s" #define PING6_PACKETS_FIRST 1 #define PING_COMMAND "/bin/ping -n -c %d %s" #define PING_HAS_TIMEOUT 1 #define PING_PACKETS_FIRST 1 Anyways ... I get also with your latest patch: # LANG=C /usr/lib/nagios/plugins/check_ping 127.0.0.1 -w 2,20% -c 5,30% Segmentation fault Without defining the ping commands and inetutils-ping installed, I get: #define PING6_COMMAND "/bin/ping6 -n -c %d %s" #define PING6_PACKETS_FIRST 1 #define PING_COMMAND "/bin/ping -n -c %d %s" /* #undef PING_HAS_TIMEOUT */ #define PING_PACKETS_FIRST 1 # LANG=C /usr/lib/nagios/plugins/check_ping 127.0.0.1 -w 2,20% -c 5,30% PING OK - Packet loss = 0%, RTA = 0.00 ms|rta=0.000000ms;2.000000;5.000000;0.000000 pl=0%;20;30;0 ---------------------------------------------------------------------- Comment By: Thomas Guyot-Sionnest (dermoth) Date: 2009-12-05 01:36 Message: Nevermind - the output you sent is ok... So are you really getting this twice (I don't, wondering if it may be related to your issue)? checking for ICMP ping syntax... (command-line) /bin/ping6 -n -c %d %s checking for ICMPv6 ping syntax... (command-line) /bin/ping -n -c %d %s Please check config.h and tell me what you have defined for: - PING6_COMMAND - PING6_PACKETS_FIRST - PING_COMMAND - PING_HAS_TIMEOUT - PING_PACKETS_FIRST Also I figured I should also change it for ping6, I'll attach an updated patch. ---------------------------------------------------------------------- Comment By: Thomas Guyot-Sionnest (dermoth) Date: 2009-12-05 00:03 Message: I'll double check... So what are the configure arguments in both cases? ---------------------------------------------------------------------- Comment By: Thomas Guyot-Sionnest (dermoth) Date: 2009-12-05 00:02 Message: [ Proxying response from Jan... ] When autodetecting with inetutils-ping installed on buildtime all works fine Defining the commands (like the once when autodetected) and inetutils-ping having not installed when building gives me a segfault on runtime inetutils-ping installed on buildtime/autodetect: waja at packaging:~/debian-builds/nagios-plugins/trunk$ grep "ping syntax" ../build-area/nagios-plugins_1.4.14-1~pc4_i386.build checking for ICMP ping syntax... /bin/ping -n -c %d %s checking for ICMPv6 ping syntax... /bin/ping6 -n -c %d %s checking for ICMP ping syntax... /bin/ping -n -c %d %s checking for ICMPv6 ping syntax... /bin/ping6 -n -c %d %s Exectution works fine. inetutils-ping removed on buildtime/command defined: waja at packaging:~/debian-builds/nagios-plugins/trunk$ grep "ping syntax" ../build-area/nagios-plugins_1.4.14-1_i386.build checking for ICMP ping syntax... (command-line) /bin/ping -n -c %d %s checking for ICMPv6 ping syntax... (command-line) /bin/ping6 -n -c %d %s checking for ICMP ping syntax... (command-line) /bin/ping -n -c %d %s checking for ICMPv6 ping syntax... (command-line) /bin/ping6 -n -c %d %s packaging:~# LANG=C /usr/lib/nagios/plugins/check_ping 127.0.0.1 -w 2,20% -c 5,30% Segmentation fault ---------------------------------------------------------------------- Comment By: Thomas Guyot-Sionnest (dermoth) Date: 2009-12-04 15:48 Message: Gotchya. --with-ping[6]-command expected three arguments - two numeric and one string. I try to detect it now (attached patch) - will go upstream it it works for you... ---------------------------------------------------------------------- Comment By: Jan Wagner (cyco_dd) Date: 2009-11-23 10:47 Message: Unfortunately I have. :( Maybe you can have a look: normal debian package - using iputils-ping and compile following flags: --with-ping-command="/bin/ping -n -U -w %d -c %d %s" \ --with-ping6-command="/bin/ping6 -n -U -w %d -c %d %s" \ sid:~# /usr/lib/nagios/plugins/check_ping 127.0.0.1 -w 2,20% -c 5,30% PING OK - Packet loss = 0%, RTA = 0.00 ms| rta=0.000000ms;2.000000;5.000000;0.000000 pl=0%;20;30;0 Okay ... thats fine, like always. ---- pc1 - using iputils-ping and following compile flags: --with-ping-command="/bin/ping -n -c %d %s" \ --with-ping6-command="/bin/ping6 -n -c %d %s" \ sid:/tmp# LANG=C /usr/lib/nagios/plugins/check_ping 127.0.0.1 -w 2,20% -c 5,30% Speicherzugriffsfehler Okay ... here are just the ping commands wrong ---- pc2 - using iputils-ping and without specific compile flags (iputils-ping installed at compile time), but: checking for ICMP ping syntax... /bin/ping -n -U -w %d -c %d %s checking for ICMPv6 ping syntax... /bin/ping6 -n -U -w %d -c %d %s sid:/tmp# LANG=C /usr/lib/nagios/plugins/check_ping 127.0.0.1 -w 2,20% -c 5,30% PING OK - Packet loss = 0%, RTA = 0.00 ms| rta=0.000000ms;2.000000;5.000000;0.000000 pl=0%;20;30;0 Thats also fine, the commands are autodetected. ---- pc3 - using inetutils-ping and without specific compile flags (inetutils-ping installed at compile time), but: checking for ICMP ping syntax... /bin/ping -n -c %d %s checking for ICMPv6 ping syntax... /bin/ping6 -n -c %d %s sid:/tmp# LANG=C /usr/lib/nagios/plugins/check_ping 127.0.0.1 -w 2,20% -c 5,30% PING OK - Packet loss = 0%, RTA = 0.00 ms| rta=0.000000ms;2.000000;5.000000;0.000000 pl=0%;20;30;0 Looks great, command are autodetected and inetutils-ping works ---- pc4 - using inetutils-ping and the following compile flags (inetutils-ping NOT installed at compile time): --with-ping6-command="/bin/ping6 -n -c %d %s" \ --with-ping-command="/bin/ping -n -c %d %s" \ sid:/tmp# LANG=C /usr/lib/nagios/plugins/check_ping 127.0.0.1 -w 2,20% -c 5,30% Speicherzugriffsfehler This is the point I don't get. I'm using the same commands like the once when they where autodetected, but check_ping segfaults .... I'm missing something? Thanks for your help, Jan. ---------------------------------------------------------------------- Comment By: Thomas Guyot-Sionnest (dermoth) Date: 2009-11-11 17:29 Message: Normally configure decides which ping command and syntax to use, so it really depend on which packages you have installed. You can force the command to use with --with-ping-command=SYNTAX and --with-ping6-command=SYNTAX. An easy way to find the syntax it to look at a generated config.h when only the wanted ping commands are available. Search for #define PING_COMMAND and #define PING6_COMMAND. Let me know if you have any problem with specific ping variants. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=397597&aid=2896201&group_id=29880 From noreply at sourceforge.net Sat Dec 5 21:48:47 2009 From: noreply at sourceforge.net (SourceForge.net) Date: Sat, 05 Dec 2009 20:48:47 +0000 Subject: [Nagiosplug-devel] [ nagiosplug-Bugs-2896201 ] check_ping depends on iputils-ping Message-ID: Bugs item #2896201, was opened at 2009-11-11 21:37 Message generated for change (Comment added) made by cyco_dd You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=397597&aid=2896201&group_id=29880 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: General plugin execution Group: release-1.4.15 Status: Open Resolution: None Priority: 5 Private: No Submitted By: Jan Wagner (cyco_dd) Assigned to: Thomas Guyot-Sionnest (dermoth) Summary: check_ping depends on iputils-ping Initial Comment: The following Bugreport we got against our debian package: Hi, it seems that the nagios related packages need an ping command available. They choose iputils-ping, which is rather linux specific. Could be possible to switch (at least on non-linux) to inetutils-ping (already available) or fping (modulo #555398 available). It will help to kfreebsd-i386, kfreebsd-amd64 and hurd architectures. Thanks for considering it. You can track the bugreport via http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=555532 check_ping could maybe rewritten/patched to use liboping [1]? Thanks and kind regards, Jan. [1] http://verplant.org/liboping/ ---------------------------------------------------------------------- >Comment By: Jan Wagner (cyco_dd) Date: 2009-12-05 21:48 Message: 41_check_ping_detect_args.dpatch worked for me, thanks ---------------------------------------------------------------------- Comment By: Thomas Guyot-Sionnest (dermoth) Date: 2009-12-05 21:17 Message: So as discusson on IRC your build process do not re-generate autoconf. This is done automatically if you have the rigth software installed, but it may be simpler to use the attached patches Since I fixed a bunch of whitespaces the first patch may apply only if you ignore whitespace mismatches - the 2nd may apply correctly ---------------------------------------------------------------------- Comment By: Jan Wagner (cyco_dd) Date: 2009-12-05 15:36 Message: I'm getting this twice, since configure is issueing "/bin/sh ./config.status --recheck". That should be unrelated to the issue. The configure arguments are: NP_LIBEXEC:=/usr/lib/nagios/plugins ./configure \ --host=$(DEB_HOST_GNU_TYPE) \ --build=$(DEB_BUILD_GNU_TYPE) \ --prefix=/usr \ --mandir=/usr/share/man \ --infodir=/usr/share/info \ --libexecdir=${NP_LIBEXEC} \ --with-perl=/usr/bin/perl \ --with-openssl=/usr \ --with-pgsql=/usr \ --with-mysql=/usr \ --with-proc-loadavg=/proc/loadavg \ --with-ps-command="/bin/ps axwo 'stat uid pid ppid vsz rss pcpu etime comm args'" \ --with-ps-format="%s %d %d %d %d %d %f %s %s %n" \ --with-ps-cols=10 \ --with-ps-varlist="procstat,&procuid,&procpid,&procppid,&procvsz,&procrss,&procpcpu,procetime,procprog,&pos" \ --with-ping-command="/bin/ping -n -c %d %s" \ --with-ping6-command="/bin/ping6 -n -c %d %s" \ --with-nslookup-command="/usr/bin/nslookup -sil" \ --with-uptime-command="/usr/bin/uptime" \ --with-rpcinfo-command="/usr/bin/rpcinfo" \ --with-smbclient-command="/usr/bin/smbclient" \ --with-snmpget-command="/usr/bin/snmpget" \ --with-snmpgetnext-command="/usr/bin/snmpgetnext" \ --with-qstat-command="/usr/bin/quakestat" \ --with-fping-command="/usr/bin/fping" \ --with-ssh-command="/usr/bin/ssh" \ --with-mailq-command="/usr/bin/mailq" \ --with-proc-meminfo="/proc/meminfo" \ --with-dig-command="/usr/bin/dig" \ --with-apt-get-command="/usr/bin/apt-get" \ --disable-rpath Which fails with this at runtime. Working is installing inetutils-ping at build time and dropping --with-ping* from configure. With defined ping commands, in config.h I have: #define PING6_COMMAND "/bin/ping6 -n -c %d %s" #define PING6_PACKETS_FIRST 1 #define PING_COMMAND "/bin/ping -n -c %d %s" #define PING_HAS_TIMEOUT 1 #define PING_PACKETS_FIRST 1 Anyways ... I get also with your latest patch: # LANG=C /usr/lib/nagios/plugins/check_ping 127.0.0.1 -w 2,20% -c 5,30% Segmentation fault Without defining the ping commands and inetutils-ping installed, I get: #define PING6_COMMAND "/bin/ping6 -n -c %d %s" #define PING6_PACKETS_FIRST 1 #define PING_COMMAND "/bin/ping -n -c %d %s" /* #undef PING_HAS_TIMEOUT */ #define PING_PACKETS_FIRST 1 # LANG=C /usr/lib/nagios/plugins/check_ping 127.0.0.1 -w 2,20% -c 5,30% PING OK - Packet loss = 0%, RTA = 0.00 ms|rta=0.000000ms;2.000000;5.000000;0.000000 pl=0%;20;30;0 ---------------------------------------------------------------------- Comment By: Thomas Guyot-Sionnest (dermoth) Date: 2009-12-05 07:36 Message: Nevermind - the output you sent is ok... So are you really getting this twice (I don't, wondering if it may be related to your issue)? checking for ICMP ping syntax... (command-line) /bin/ping6 -n -c %d %s checking for ICMPv6 ping syntax... (command-line) /bin/ping -n -c %d %s Please check config.h and tell me what you have defined for: - PING6_COMMAND - PING6_PACKETS_FIRST - PING_COMMAND - PING_HAS_TIMEOUT - PING_PACKETS_FIRST Also I figured I should also change it for ping6, I'll attach an updated patch. ---------------------------------------------------------------------- Comment By: Thomas Guyot-Sionnest (dermoth) Date: 2009-12-05 06:03 Message: I'll double check... So what are the configure arguments in both cases? ---------------------------------------------------------------------- Comment By: Thomas Guyot-Sionnest (dermoth) Date: 2009-12-05 06:02 Message: [ Proxying response from Jan... ] When autodetecting with inetutils-ping installed on buildtime all works fine Defining the commands (like the once when autodetected) and inetutils-ping having not installed when building gives me a segfault on runtime inetutils-ping installed on buildtime/autodetect: waja at packaging:~/debian-builds/nagios-plugins/trunk$ grep "ping syntax" ../build-area/nagios-plugins_1.4.14-1~pc4_i386.build checking for ICMP ping syntax... /bin/ping -n -c %d %s checking for ICMPv6 ping syntax... /bin/ping6 -n -c %d %s checking for ICMP ping syntax... /bin/ping -n -c %d %s checking for ICMPv6 ping syntax... /bin/ping6 -n -c %d %s Exectution works fine. inetutils-ping removed on buildtime/command defined: waja at packaging:~/debian-builds/nagios-plugins/trunk$ grep "ping syntax" ../build-area/nagios-plugins_1.4.14-1_i386.build checking for ICMP ping syntax... (command-line) /bin/ping -n -c %d %s checking for ICMPv6 ping syntax... (command-line) /bin/ping6 -n -c %d %s checking for ICMP ping syntax... (command-line) /bin/ping -n -c %d %s checking for ICMPv6 ping syntax... (command-line) /bin/ping6 -n -c %d %s packaging:~# LANG=C /usr/lib/nagios/plugins/check_ping 127.0.0.1 -w 2,20% -c 5,30% Segmentation fault ---------------------------------------------------------------------- Comment By: Thomas Guyot-Sionnest (dermoth) Date: 2009-12-04 21:48 Message: Gotchya. --with-ping[6]-command expected three arguments - two numeric and one string. I try to detect it now (attached patch) - will go upstream it it works for you... ---------------------------------------------------------------------- Comment By: Jan Wagner (cyco_dd) Date: 2009-11-23 16:47 Message: Unfortunately I have. :( Maybe you can have a look: normal debian package - using iputils-ping and compile following flags: --with-ping-command="/bin/ping -n -U -w %d -c %d %s" \ --with-ping6-command="/bin/ping6 -n -U -w %d -c %d %s" \ sid:~# /usr/lib/nagios/plugins/check_ping 127.0.0.1 -w 2,20% -c 5,30% PING OK - Packet loss = 0%, RTA = 0.00 ms| rta=0.000000ms;2.000000;5.000000;0.000000 pl=0%;20;30;0 Okay ... thats fine, like always. ---- pc1 - using iputils-ping and following compile flags: --with-ping-command="/bin/ping -n -c %d %s" \ --with-ping6-command="/bin/ping6 -n -c %d %s" \ sid:/tmp# LANG=C /usr/lib/nagios/plugins/check_ping 127.0.0.1 -w 2,20% -c 5,30% Speicherzugriffsfehler Okay ... here are just the ping commands wrong ---- pc2 - using iputils-ping and without specific compile flags (iputils-ping installed at compile time), but: checking for ICMP ping syntax... /bin/ping -n -U -w %d -c %d %s checking for ICMPv6 ping syntax... /bin/ping6 -n -U -w %d -c %d %s sid:/tmp# LANG=C /usr/lib/nagios/plugins/check_ping 127.0.0.1 -w 2,20% -c 5,30% PING OK - Packet loss = 0%, RTA = 0.00 ms| rta=0.000000ms;2.000000;5.000000;0.000000 pl=0%;20;30;0 Thats also fine, the commands are autodetected. ---- pc3 - using inetutils-ping and without specific compile flags (inetutils-ping installed at compile time), but: checking for ICMP ping syntax... /bin/ping -n -c %d %s checking for ICMPv6 ping syntax... /bin/ping6 -n -c %d %s sid:/tmp# LANG=C /usr/lib/nagios/plugins/check_ping 127.0.0.1 -w 2,20% -c 5,30% PING OK - Packet loss = 0%, RTA = 0.00 ms| rta=0.000000ms;2.000000;5.000000;0.000000 pl=0%;20;30;0 Looks great, command are autodetected and inetutils-ping works ---- pc4 - using inetutils-ping and the following compile flags (inetutils-ping NOT installed at compile time): --with-ping6-command="/bin/ping6 -n -c %d %s" \ --with-ping-command="/bin/ping -n -c %d %s" \ sid:/tmp# LANG=C /usr/lib/nagios/plugins/check_ping 127.0.0.1 -w 2,20% -c 5,30% Speicherzugriffsfehler This is the point I don't get. I'm using the same commands like the once when they where autodetected, but check_ping segfaults .... I'm missing something? Thanks for your help, Jan. ---------------------------------------------------------------------- Comment By: Thomas Guyot-Sionnest (dermoth) Date: 2009-11-11 23:29 Message: Normally configure decides which ping command and syntax to use, so it really depend on which packages you have installed. You can force the command to use with --with-ping-command=SYNTAX and --with-ping6-command=SYNTAX. An easy way to find the syntax it to look at a generated config.h when only the wanted ping commands are available. Search for #define PING_COMMAND and #define PING6_COMMAND. Let me know if you have any problem with specific ping variants. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=397597&aid=2896201&group_id=29880 From noreply at sourceforge.net Sun Dec 6 15:53:56 2009 From: noreply at sourceforge.net (SourceForge.net) Date: Sun, 06 Dec 2009 14:53:56 +0000 Subject: [Nagiosplug-devel] [ nagiosplug-Bugs-2896201 ] check_ping depends on iputils-ping Message-ID: Bugs item #2896201, was opened at 2009-11-11 15:37 Message generated for change (Comment added) made by dermoth You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=397597&aid=2896201&group_id=29880 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: General plugin execution Group: release-1.4.15 >Status: Closed >Resolution: Fixed Priority: 5 Private: No Submitted By: Jan Wagner (cyco_dd) Assigned to: Thomas Guyot-Sionnest (dermoth) Summary: check_ping depends on iputils-ping Initial Comment: The following Bugreport we got against our debian package: Hi, it seems that the nagios related packages need an ping command available. They choose iputils-ping, which is rather linux specific. Could be possible to switch (at least on non-linux) to inetutils-ping (already available) or fping (modulo #555398 available). It will help to kfreebsd-i386, kfreebsd-amd64 and hurd architectures. Thanks for considering it. You can track the bugreport via http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=555532 check_ping could maybe rewritten/patched to use liboping [1]? Thanks and kind regards, Jan. [1] http://verplant.org/liboping/ ---------------------------------------------------------------------- Comment By: Thomas Guyot-Sionnest (dermoth) Date: 2009-12-06 09:53 Message: This problem is now fixed in Git. Thank you for your report. ---------------------------------------------------------------------- Comment By: Jan Wagner (cyco_dd) Date: 2009-12-05 15:48 Message: 41_check_ping_detect_args.dpatch worked for me, thanks ---------------------------------------------------------------------- Comment By: Thomas Guyot-Sionnest (dermoth) Date: 2009-12-05 15:17 Message: So as discusson on IRC your build process do not re-generate autoconf. This is done automatically if you have the rigth software installed, but it may be simpler to use the attached patches Since I fixed a bunch of whitespaces the first patch may apply only if you ignore whitespace mismatches - the 2nd may apply correctly ---------------------------------------------------------------------- Comment By: Jan Wagner (cyco_dd) Date: 2009-12-05 09:36 Message: I'm getting this twice, since configure is issueing "/bin/sh ./config.status --recheck". That should be unrelated to the issue. The configure arguments are: NP_LIBEXEC:=/usr/lib/nagios/plugins ./configure \ --host=$(DEB_HOST_GNU_TYPE) \ --build=$(DEB_BUILD_GNU_TYPE) \ --prefix=/usr \ --mandir=/usr/share/man \ --infodir=/usr/share/info \ --libexecdir=${NP_LIBEXEC} \ --with-perl=/usr/bin/perl \ --with-openssl=/usr \ --with-pgsql=/usr \ --with-mysql=/usr \ --with-proc-loadavg=/proc/loadavg \ --with-ps-command="/bin/ps axwo 'stat uid pid ppid vsz rss pcpu etime comm args'" \ --with-ps-format="%s %d %d %d %d %d %f %s %s %n" \ --with-ps-cols=10 \ --with-ps-varlist="procstat,&procuid,&procpid,&procppid,&procvsz,&procrss,&procpcpu,procetime,procprog,&pos" \ --with-ping-command="/bin/ping -n -c %d %s" \ --with-ping6-command="/bin/ping6 -n -c %d %s" \ --with-nslookup-command="/usr/bin/nslookup -sil" \ --with-uptime-command="/usr/bin/uptime" \ --with-rpcinfo-command="/usr/bin/rpcinfo" \ --with-smbclient-command="/usr/bin/smbclient" \ --with-snmpget-command="/usr/bin/snmpget" \ --with-snmpgetnext-command="/usr/bin/snmpgetnext" \ --with-qstat-command="/usr/bin/quakestat" \ --with-fping-command="/usr/bin/fping" \ --with-ssh-command="/usr/bin/ssh" \ --with-mailq-command="/usr/bin/mailq" \ --with-proc-meminfo="/proc/meminfo" \ --with-dig-command="/usr/bin/dig" \ --with-apt-get-command="/usr/bin/apt-get" \ --disable-rpath Which fails with this at runtime. Working is installing inetutils-ping at build time and dropping --with-ping* from configure. With defined ping commands, in config.h I have: #define PING6_COMMAND "/bin/ping6 -n -c %d %s" #define PING6_PACKETS_FIRST 1 #define PING_COMMAND "/bin/ping -n -c %d %s" #define PING_HAS_TIMEOUT 1 #define PING_PACKETS_FIRST 1 Anyways ... I get also with your latest patch: # LANG=C /usr/lib/nagios/plugins/check_ping 127.0.0.1 -w 2,20% -c 5,30% Segmentation fault Without defining the ping commands and inetutils-ping installed, I get: #define PING6_COMMAND "/bin/ping6 -n -c %d %s" #define PING6_PACKETS_FIRST 1 #define PING_COMMAND "/bin/ping -n -c %d %s" /* #undef PING_HAS_TIMEOUT */ #define PING_PACKETS_FIRST 1 # LANG=C /usr/lib/nagios/plugins/check_ping 127.0.0.1 -w 2,20% -c 5,30% PING OK - Packet loss = 0%, RTA = 0.00 ms|rta=0.000000ms;2.000000;5.000000;0.000000 pl=0%;20;30;0 ---------------------------------------------------------------------- Comment By: Thomas Guyot-Sionnest (dermoth) Date: 2009-12-05 01:36 Message: Nevermind - the output you sent is ok... So are you really getting this twice (I don't, wondering if it may be related to your issue)? checking for ICMP ping syntax... (command-line) /bin/ping6 -n -c %d %s checking for ICMPv6 ping syntax... (command-line) /bin/ping -n -c %d %s Please check config.h and tell me what you have defined for: - PING6_COMMAND - PING6_PACKETS_FIRST - PING_COMMAND - PING_HAS_TIMEOUT - PING_PACKETS_FIRST Also I figured I should also change it for ping6, I'll attach an updated patch. ---------------------------------------------------------------------- Comment By: Thomas Guyot-Sionnest (dermoth) Date: 2009-12-05 00:03 Message: I'll double check... So what are the configure arguments in both cases? ---------------------------------------------------------------------- Comment By: Thomas Guyot-Sionnest (dermoth) Date: 2009-12-05 00:02 Message: [ Proxying response from Jan... ] When autodetecting with inetutils-ping installed on buildtime all works fine Defining the commands (like the once when autodetected) and inetutils-ping having not installed when building gives me a segfault on runtime inetutils-ping installed on buildtime/autodetect: waja at packaging:~/debian-builds/nagios-plugins/trunk$ grep "ping syntax" ../build-area/nagios-plugins_1.4.14-1~pc4_i386.build checking for ICMP ping syntax... /bin/ping -n -c %d %s checking for ICMPv6 ping syntax... /bin/ping6 -n -c %d %s checking for ICMP ping syntax... /bin/ping -n -c %d %s checking for ICMPv6 ping syntax... /bin/ping6 -n -c %d %s Exectution works fine. inetutils-ping removed on buildtime/command defined: waja at packaging:~/debian-builds/nagios-plugins/trunk$ grep "ping syntax" ../build-area/nagios-plugins_1.4.14-1_i386.build checking for ICMP ping syntax... (command-line) /bin/ping -n -c %d %s checking for ICMPv6 ping syntax... (command-line) /bin/ping6 -n -c %d %s checking for ICMP ping syntax... (command-line) /bin/ping -n -c %d %s checking for ICMPv6 ping syntax... (command-line) /bin/ping6 -n -c %d %s packaging:~# LANG=C /usr/lib/nagios/plugins/check_ping 127.0.0.1 -w 2,20% -c 5,30% Segmentation fault ---------------------------------------------------------------------- Comment By: Thomas Guyot-Sionnest (dermoth) Date: 2009-12-04 15:48 Message: Gotchya. --with-ping[6]-command expected three arguments - two numeric and one string. I try to detect it now (attached patch) - will go upstream it it works for you... ---------------------------------------------------------------------- Comment By: Jan Wagner (cyco_dd) Date: 2009-11-23 10:47 Message: Unfortunately I have. :( Maybe you can have a look: normal debian package - using iputils-ping and compile following flags: --with-ping-command="/bin/ping -n -U -w %d -c %d %s" \ --with-ping6-command="/bin/ping6 -n -U -w %d -c %d %s" \ sid:~# /usr/lib/nagios/plugins/check_ping 127.0.0.1 -w 2,20% -c 5,30% PING OK - Packet loss = 0%, RTA = 0.00 ms| rta=0.000000ms;2.000000;5.000000;0.000000 pl=0%;20;30;0 Okay ... thats fine, like always. ---- pc1 - using iputils-ping and following compile flags: --with-ping-command="/bin/ping -n -c %d %s" \ --with-ping6-command="/bin/ping6 -n -c %d %s" \ sid:/tmp# LANG=C /usr/lib/nagios/plugins/check_ping 127.0.0.1 -w 2,20% -c 5,30% Speicherzugriffsfehler Okay ... here are just the ping commands wrong ---- pc2 - using iputils-ping and without specific compile flags (iputils-ping installed at compile time), but: checking for ICMP ping syntax... /bin/ping -n -U -w %d -c %d %s checking for ICMPv6 ping syntax... /bin/ping6 -n -U -w %d -c %d %s sid:/tmp# LANG=C /usr/lib/nagios/plugins/check_ping 127.0.0.1 -w 2,20% -c 5,30% PING OK - Packet loss = 0%, RTA = 0.00 ms| rta=0.000000ms;2.000000;5.000000;0.000000 pl=0%;20;30;0 Thats also fine, the commands are autodetected. ---- pc3 - using inetutils-ping and without specific compile flags (inetutils-ping installed at compile time), but: checking for ICMP ping syntax... /bin/ping -n -c %d %s checking for ICMPv6 ping syntax... /bin/ping6 -n -c %d %s sid:/tmp# LANG=C /usr/lib/nagios/plugins/check_ping 127.0.0.1 -w 2,20% -c 5,30% PING OK - Packet loss = 0%, RTA = 0.00 ms| rta=0.000000ms;2.000000;5.000000;0.000000 pl=0%;20;30;0 Looks great, command are autodetected and inetutils-ping works ---- pc4 - using inetutils-ping and the following compile flags (inetutils-ping NOT installed at compile time): --with-ping6-command="/bin/ping6 -n -c %d %s" \ --with-ping-command="/bin/ping -n -c %d %s" \ sid:/tmp# LANG=C /usr/lib/nagios/plugins/check_ping 127.0.0.1 -w 2,20% -c 5,30% Speicherzugriffsfehler This is the point I don't get. I'm using the same commands like the once when they where autodetected, but check_ping segfaults .... I'm missing something? Thanks for your help, Jan. ---------------------------------------------------------------------- Comment By: Thomas Guyot-Sionnest (dermoth) Date: 2009-11-11 17:29 Message: Normally configure decides which ping command and syntax to use, so it really depend on which packages you have installed. You can force the command to use with --with-ping-command=SYNTAX and --with-ping6-command=SYNTAX. An easy way to find the syntax it to look at a generated config.h when only the wanted ping commands are available. Search for #define PING_COMMAND and #define PING6_COMMAND. Let me know if you have any problem with specific ping variants. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=397597&aid=2896201&group_id=29880 From noreply at sourceforge.net Thu Dec 10 03:47:44 2009 From: noreply at sourceforge.net (SourceForge.net) Date: Thu, 10 Dec 2009 02:47:44 +0000 Subject: [Nagiosplug-devel] [ nagiosplug-Bugs-2911752 ] check_radius doesn't detect or report authentication errors Message-ID: Bugs item #2911752, was opened at 2009-12-09 18:47 Message generated for change (Tracker Item Submitted) made by leres You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=397597&aid=2911752&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: Craig Leres (leres) Assigned to: Nobody/Anonymous (nobody) Summary: check_radius doesn't detect or report authentication errors Initial Comment: The check_radius plugin exits with status 0 and no messages if it gets a "result" it isn't expecting. This issue is tickled when you use an incorrect password. In that case, radiusclient returns REJECT_RC (2). The attached patch (against 1.4.13) adds a case to handle REJECT_RC and also complains if an unexpected result is returned. Although I did not actually test the snapshot version, examination of the code indicates that 1.4.14-61-g45e2 still has these issues. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=397597&aid=2911752&group_id=29880 From noreply at sourceforge.net Thu Dec 10 05:05:01 2009 From: noreply at sourceforge.net (SourceForge.net) Date: Thu, 10 Dec 2009 04:05:01 +0000 Subject: [Nagiosplug-devel] [ nagiosplug-Bugs-2911752 ] check_radius doesn't detect or report authentication errors Message-ID: Bugs item #2911752, was opened at 2009-12-09 21:47 Message generated for change (Comment added) made by dermoth You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=397597&aid=2911752&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: release-1.4.15 Status: Open >Resolution: Accepted Priority: 5 Private: No Submitted By: Craig Leres (leres) >Assigned to: Thomas Guyot-Sionnest (dermoth) Summary: check_radius doesn't detect or report authentication errors Initial Comment: The check_radius plugin exits with status 0 and no messages if it gets a "result" it isn't expecting. This issue is tickled when you use an incorrect password. In that case, radiusclient returns REJECT_RC (2). The attached patch (against 1.4.13) adds a case to handle REJECT_RC and also complains if an unexpected result is returned. Although I did not actually test the snapshot version, examination of the code indicates that 1.4.14-61-g45e2 still has these issues. ---------------------------------------------------------------------- >Comment By: Thomas Guyot-Sionnest (dermoth) Date: 2009-12-09 23:05 Message: Which library/version are you using for radius? We currently support the original radiusclient and radiusclient-ng, and none of them provide the REJECT_RC macro. I'll apply the last hunk anyway, but for the rest i'd like to know where it's from at the very least. Thanks ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=397597&aid=2911752&group_id=29880 From noreply at sourceforge.net Thu Dec 10 05:24:26 2009 From: noreply at sourceforge.net (SourceForge.net) Date: Thu, 10 Dec 2009 04:24:26 +0000 Subject: [Nagiosplug-devel] [ nagiosplug-Bugs-2911752 ] check_radius doesn't detect or report authentication errors Message-ID: Bugs item #2911752, was opened at 2009-12-09 18:47 Message generated for change (Comment added) made by leres You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=397597&aid=2911752&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: release-1.4.15 Status: Open Resolution: Accepted Priority: 5 Private: No Submitted By: Craig Leres (leres) Assigned to: Thomas Guyot-Sionnest (dermoth) Summary: check_radius doesn't detect or report authentication errors Initial Comment: The check_radius plugin exits with status 0 and no messages if it gets a "result" it isn't expecting. This issue is tickled when you use an incorrect password. In that case, radiusclient returns REJECT_RC (2). The attached patch (against 1.4.13) adds a case to handle REJECT_RC and also complains if an unexpected result is returned. Although I did not actually test the snapshot version, examination of the code indicates that 1.4.14-61-g45e2 still has these issues. ---------------------------------------------------------------------- Comment By: Craig Leres (leres) Date: 2009-12-09 20:24 Message: I'm using radiusclient-ng 0.5.6 (which although is a few years old also appears to be the current release) on a FreeBSD 7.2-RELEASE system. I build radiusclient-ng and nagios-plugins using ports. % find . -name '*.[ch]' | xargs egrep REJECT_RC ./radiusclient-ng-0.5.6/include/radiusclient-ng.h:#define REJECT_RC 2 ./radiusclient-ng-0.5.6/lib/sendserver.c: result = REJECT_RC; ---------------------------------------------------------------------- Comment By: Thomas Guyot-Sionnest (dermoth) Date: 2009-12-09 20:05 Message: Which library/version are you using for radius? We currently support the original radiusclient and radiusclient-ng, and none of them provide the REJECT_RC macro. I'll apply the last hunk anyway, but for the rest i'd like to know where it's from at the very least. Thanks ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=397597&aid=2911752&group_id=29880 From noreply at sourceforge.net Thu Dec 17 13:56:05 2009 From: noreply at sourceforge.net (SourceForge.net) Date: Thu, 17 Dec 2009 12:56:05 +0000 Subject: [Nagiosplug-devel] [ nagiosplug-Bugs-2916226 ] check_http -S fails with some servers Message-ID: Bugs item #2916226, was opened at 2009-12-17 13:56 Message generated for change (Tracker Item Submitted) made by patricia_jung You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=397597&aid=2916226&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: Patricia Jung (patricia_jung) Assigned to: Nobody/Anonymous (nobody) Summary: check_http -S fails with some servers Initial Comment: Hello Ton and all, while updating from v 1.4.13 to v. 1.4.14 I observe check_http behaving rather strangely when performing HTTPS checks. Same platform (openSUSE 11.2), both plugin versions were compiled without any deviating configure options: nagios-plugins-1.4.13> ./plugins/check_http -S -H -p 8443 HTTP OK HTTP/1.1 200 OK - 2328 bytes in 0.205 seconds |time=0.205096s;;;0.000000 size=2328B;;;0 nagios-plugins-1.4.14> /plugins/check_http -S -H -p 8443 CRITICAL - Cannot make SSL connection HTTP CRITICAL - Error on receive With other servers, however, the same test (same port) succeeds even with version 1.4.14. Any advice on how to proceed? Best Patricia ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=397597&aid=2916226&group_id=29880 From giuseppe.furlan at hotmail.com Thu Dec 17 14:43:37 2009 From: giuseppe.furlan at hotmail.com (giuseppe furlan) Date: Thu, 17 Dec 2009 13:43:37 +0000 Subject: [Nagiosplug-devel] =?windows-1256?q?change_default_=22check=5Fby?= =?windows-1256?q?=5Fssh=22_output_unit=FE?= Message-ID: hello all, I'm using Nagios with "check_by_ssh" plugin to monitor threads and jdbc connections on my linux machines. Apparently this plug-in catches my integer values (threads count, db connections etc) and convert them to percent values. The result is a Nagios' graph with % unit instead of decimal unit. I've checked the plugin's options but unit option is not implemented. I'm wondering if there is a patch to change the default graph % unit with a decimal unit. Regards Giuseppe Furlan _________________________________________________________________ Have more than one Hotmail account? Link them together to easily access both http://clk.atdmt.com/UKM/go/186394591/direct/01/ -------------- next part -------------- An HTML attachment was scrubbed... URL: From marc at ena.com Thu Dec 17 16:08:29 2009 From: marc at ena.com (Marc Powell) Date: Thu, 17 Dec 2009 09:08:29 -0600 Subject: [Nagiosplug-devel] =?utf-8?q?change_default_=22check=5Fby=5Fssh?= =?utf-8?q?=22_output_unit=E2=80=8F?= In-Reply-To: References: Message-ID: <52D01E60-F3FC-43E5-8028-1788873F9821@ena.com> On Dec 17, 2009, at 7:43 AM, giuseppe furlan wrote: > hello all, > I'm using Nagios with "check_by_ssh" plugin to monitor threads and jdbc connections on my linux machines. > Apparently this plug-in catches my integer values (threads count, db connections etc) and convert them to percent values. > The result is a Nagios' graph with % unit instead of decimal unit. > I've checked the plugin's options but unit option is not implemented. > > I'm wondering if there is a patch to change the default graph % unit with a decimal unit. check_by_ssh doesn't do any of this. It has no understanding of units or % or anything. It simply passes the output of the plugin it executes back to nagios as it was received. You either need to look at the output of the plugin that check_by_ssh is executing or the options for whatever you have that's doing the graphing. -- Marc From noreply at sourceforge.net Thu Dec 17 16:30:15 2009 From: noreply at sourceforge.net (SourceForge.net) Date: Thu, 17 Dec 2009 15:30:15 +0000 Subject: [Nagiosplug-devel] [ nagiosplug-Bugs-2916307 ] check_http -S fails with some servers Message-ID: Bugs item #2916307, was opened at 2009-12-17 16:30 Message generated for change (Tracker Item Submitted) made by patricia_jung You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=397597&aid=2916307&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: Patricia Jung (patricia_jung) Assigned to: Nobody/Anonymous (nobody) Summary: check_http -S fails with some servers Initial Comment: Hello Ton and all, while updating from v 1.4.13 to v. 1.4.14 I observe check_http behaving rather strangely when performing HTTPS checks. Same platform (openSUSE 11.2), both plugin versions were compiled without any deviating configure options: nagios-plugins-1.4.13> ./plugins/check_http -S -H -p 8443 HTTP OK HTTP/1.1 200 OK - 2328 bytes in 0.205 seconds |time=0.205096s;;;0.000000 size=2328B;;;0 nagios-plugins-1.4.14> /plugins/check_http -S -H -p 8443 CRITICAL - Cannot make SSL connection HTTP CRITICAL - Error on receive With other servers, however, the same test (same port) succeeds even with version 1.4.14. Any advice on how to proceed? Best Patricia ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=397597&aid=2916307&group_id=29880 From noreply at sourceforge.net Fri Dec 18 04:41:34 2009 From: noreply at sourceforge.net (SourceForge.net) Date: Fri, 18 Dec 2009 03:41:34 +0000 Subject: [Nagiosplug-devel] [ nagiosplug-Bugs-2916226 ] check_http -S fails with some servers Message-ID: Bugs item #2916226, was opened at 2009-12-17 07:56 Message generated for change (Comment added) made by dermoth You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=397597&aid=2916226&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: Closed >Resolution: Duplicate Priority: 5 Private: No Submitted By: Patricia Jung (patricia_jung) Assigned to: Nobody/Anonymous (nobody) Summary: check_http -S fails with some servers Initial Comment: Hello Ton and all, while updating from v 1.4.13 to v. 1.4.14 I observe check_http behaving rather strangely when performing HTTPS checks. Same platform (openSUSE 11.2), both plugin versions were compiled without any deviating configure options: nagios-plugins-1.4.13> ./plugins/check_http -S -H -p 8443 HTTP OK HTTP/1.1 200 OK - 2328 bytes in 0.205 seconds |time=0.205096s;;;0.000000 size=2328B;;;0 nagios-plugins-1.4.14> /plugins/check_http -S -H -p 8443 CRITICAL - Cannot make SSL connection HTTP CRITICAL - Error on receive With other servers, however, the same test (same port) succeeds even with version 1.4.14. Any advice on how to proceed? Best Patricia ---------------------------------------------------------------------- >Comment By: Thomas Guyot-Sionnest (dermoth) Date: 2009-12-17 22:41 Message: verbatim duplicate of #2916307 ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=397597&aid=2916226&group_id=29880 From noreply at sourceforge.net Fri Dec 18 04:42:15 2009 From: noreply at sourceforge.net (SourceForge.net) Date: Fri, 18 Dec 2009 03:42:15 +0000 Subject: [Nagiosplug-devel] [ nagiosplug-Bugs-2916226 ] check_http -S fails with some servers Message-ID: Bugs item #2916226, was opened at 2009-12-17 07:56 Message generated for change (Comment added) made by dermoth You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=397597&aid=2916226&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: Closed Resolution: Duplicate Priority: 5 Private: No Submitted By: Patricia Jung (patricia_jung) Assigned to: Nobody/Anonymous (nobody) Summary: check_http -S fails with some servers Initial Comment: Hello Ton and all, while updating from v 1.4.13 to v. 1.4.14 I observe check_http behaving rather strangely when performing HTTPS checks. Same platform (openSUSE 11.2), both plugin versions were compiled without any deviating configure options: nagios-plugins-1.4.13> ./plugins/check_http -S -H -p 8443 HTTP OK HTTP/1.1 200 OK - 2328 bytes in 0.205 seconds |time=0.205096s;;;0.000000 size=2328B;;;0 nagios-plugins-1.4.14> /plugins/check_http -S -H -p 8443 CRITICAL - Cannot make SSL connection HTTP CRITICAL - Error on receive With other servers, however, the same test (same port) succeeds even with version 1.4.14. Any advice on how to proceed? Best Patricia ---------------------------------------------------------------------- Comment By: Thomas Guyot-Sionnest (dermoth) Date: 2009-12-17 22:42 Message: This artifact has been marked as a duplicate of artifact 2916307 with reason: No explanation provided. ---------------------------------------------------------------------- Comment By: Thomas Guyot-Sionnest (dermoth) Date: 2009-12-17 22:41 Message: verbatim duplicate of #2916307 ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=397597&aid=2916226&group_id=29880 From noreply at sourceforge.net Fri Dec 18 04:55:55 2009 From: noreply at sourceforge.net (SourceForge.net) Date: Fri, 18 Dec 2009 03:55:55 +0000 Subject: [Nagiosplug-devel] [ nagiosplug-Bugs-2916307 ] check_http -S fails with some servers Message-ID: Bugs item #2916307, was opened at 2009-12-17 10:30 Message generated for change (Comment added) made by dermoth You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=397597&aid=2916307&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: release-1.4.15 Status: Open Resolution: None Priority: 5 Private: No Submitted By: Patricia Jung (patricia_jung) >Assigned to: Thomas Guyot-Sionnest (dermoth) Summary: check_http -S fails with some servers Initial Comment: Hello Ton and all, while updating from v 1.4.13 to v. 1.4.14 I observe check_http behaving rather strangely when performing HTTPS checks. Same platform (openSUSE 11.2), both plugin versions were compiled without any deviating configure options: nagios-plugins-1.4.13> ./plugins/check_http -S -H -p 8443 HTTP OK HTTP/1.1 200 OK - 2328 bytes in 0.205 seconds |time=0.205096s;;;0.000000 size=2328B;;;0 nagios-plugins-1.4.14> /plugins/check_http -S -H -p 8443 CRITICAL - Cannot make SSL connection HTTP CRITICAL - Error on receive With other servers, however, the same test (same port) succeeds even with version 1.4.14. Any advice on how to proceed? Best Patricia ---------------------------------------------------------------------- >Comment By: Thomas Guyot-Sionnest (dermoth) Date: 2009-12-17 22:55 Message: Thanks for your report. I've seen this bug previously (in debian trackers, I don't remember if there's a NP trackers counterpart).... So far it seemed to be a compatibility problem with OpenSSL, and last time I checked I could not find a single change in nagios-pugins that could explain this. So the most important question is did you freshly compile both plugins version at the same time (i.e. with the same OS patches/underlying libraries)?. Ideally I would like that you start from fresh tarballs in an empty directory, extract them, configure, compile and test both versions. If you can still reproduce this regression from fresh builds I will further investigate. It would be nice if you could include the full verbose output (-vvv) of the plugins, the exact version of OpenSSL you're using (i.e. installed OS packages) and the output of "pkg-config --modversion openssl". It would be even better if you can also provide an externally accessible URL I could test with (using private mail if you wish). Thank you ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=397597&aid=2916307&group_id=29880 From noreply at sourceforge.net Fri Dec 18 09:56:33 2009 From: noreply at sourceforge.net (SourceForge.net) Date: Fri, 18 Dec 2009 08:56:33 +0000 Subject: [Nagiosplug-devel] [ nagiosplug-Bugs-2916307 ] check_http -S fails with some servers Message-ID: Bugs item #2916307, was opened at 2009-12-17 16:30 Message generated for change (Comment added) made by patricia_jung You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=397597&aid=2916307&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: release-1.4.15 Status: Open Resolution: None Priority: 5 Private: No Submitted By: Patricia Jung (patricia_jung) Assigned to: Thomas Guyot-Sionnest (dermoth) Summary: check_http -S fails with some servers Initial Comment: Hello Ton and all, while updating from v 1.4.13 to v. 1.4.14 I observe check_http behaving rather strangely when performing HTTPS checks. Same platform (openSUSE 11.2), both plugin versions were compiled without any deviating configure options: nagios-plugins-1.4.13> ./plugins/check_http -S -H -p 8443 HTTP OK HTTP/1.1 200 OK - 2328 bytes in 0.205 seconds |time=0.205096s;;;0.000000 size=2328B;;;0 nagios-plugins-1.4.14> /plugins/check_http -S -H -p 8443 CRITICAL - Cannot make SSL connection HTTP CRITICAL - Error on receive With other servers, however, the same test (same port) succeeds even with version 1.4.14. Any advice on how to proceed? Best Patricia ---------------------------------------------------------------------- Comment By: Patricia Jung (patricia_jung) Date: 2009-12-18 09:56 Message: Hello Thomas, thanks for taking this up quickly! Yes, both plugin versions I compiled freshly from scratch yesterday. Unfortunately the host in question is only accessible via VPN, but I'm happy to help out with tests. > openssl version OpenSSL 0.9.8k 25 Mar 2009 (64-Bit-version from openssl-0.9.8k-3.5.3.x86_64/OpenSuse 11.2) > pkg-config --modversion openssl 0.9.8k > libexec/check_http_1.4.14 -vvv -S -H -p 8443 CRITICAL - Cannot make SSL connection GET / HTTP/1.1 User-Agent: check_http/v1.4.14 (nagios-plugins 1.4.14) Connection: close Host: :8443 HTTP CRITICAL - Error on receive > libexec/check_http_1.4.13 -vvv -S -H -p 8443 GET / HTTP/1.0 User-Agent: check_http/v2053 (nagios-plugins 1.4.13) Connection: close Host: :8443 https://:8443/ is 2328 characters STATUS: HTTP/1.1 200 OK **** HEADER **** Server: Apache-Coyote/1.1 ETag: W/"2103-1258744786000" Last-Modified: Fri, 20 Nov 2009 19:19:46 GMT Content-Type: text/html Content-Length: 2103 Date: Fri, 18 Dec 2009 08:09:54 GMT Connection: close **** CONTENT **** censhare WebClient
Configuring...
Loading Application...
Bild
HTTP OK HTTP/1.1 200 OK - 2328 bytes in 0.473 seconds |time=0.473123s;;;0.000000 size=2328B;;;0 Best Patricia ---------------------------------------------------------------------- Comment By: Thomas Guyot-Sionnest (dermoth) Date: 2009-12-18 04:55 Message: Thanks for your report. I've seen this bug previously (in debian trackers, I don't remember if there's a NP trackers counterpart).... So far it seemed to be a compatibility problem with OpenSSL, and last time I checked I could not find a single change in nagios-pugins that could explain this. So the most important question is did you freshly compile both plugins version at the same time (i.e. with the same OS patches/underlying libraries)?. Ideally I would like that you start from fresh tarballs in an empty directory, extract them, configure, compile and test both versions. If you can still reproduce this regression from fresh builds I will further investigate. It would be nice if you could include the full verbose output (-vvv) of the plugins, the exact version of OpenSSL you're using (i.e. installed OS packages) and the output of "pkg-config --modversion openssl". It would be even better if you can also provide an externally accessible URL I could test with (using private mail if you wish). Thank you ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=397597&aid=2916307&group_id=29880 From giuseppe.furlan at hotmail.com Fri Dec 18 13:48:13 2009 From: giuseppe.furlan at hotmail.com (giuseppe furlan) Date: Fri, 18 Dec 2009 12:48:13 +0000 Subject: [Nagiosplug-devel] =?windows-1256?q?change_default_=22check=5Fby?= =?windows-1256?q?=5Fssh=22_output_unit=FE?= In-Reply-To: <52D01E60-F3FC-43E5-8028-1788873F9821@ena.com> References: , <52D01E60-F3FC-43E5-8028-1788873F9821@ena.com> Message-ID: Thanks for your explanation. I'm using this plugin to retrieve 2 values (PendingRequest;HoggingThreadsCount) but the plugin's output consists of 3 values : time;PendingRequest;HoggingThreadsCount 1261047110;0;0 1261046810;0;0 1261047710;0;0 1261047410;0;0 1261048310;0;0 1261048010;0;0 1261048910;0;0 1261048610;0;0 1261049510;0;0 1261049210;0;0 1261050111;0;0 1261049810;0;0 1261050712;0;0 1261050412;0;0 1261051312;0;0 1261051012;0;0 1261051912;0;0 1261051612;0;0 Is the time column provided by "check_by_ssh" plugin ? If so, can I customize this timestamp value ? Thanks in advance Giuseppe > From: marc at ena.com > Date: Thu, 17 Dec 2009 09:08:29 -0600 > To: nagiosplug-devel at lists.sourceforge.net > Subject: Re: [Nagiosplug-devel] change default "check_by_ssh" output unit? > > > On Dec 17, 2009, at 7:43 AM, giuseppe furlan wrote: > > > hello all, > > I'm using Nagios with "check_by_ssh" plugin to monitor threads and jdbc connections on my linux machines. > > Apparently this plug-in catches my integer values (threads count, db connections etc) and convert them to percent values. > > The result is a Nagios' graph with % unit instead of decimal unit. > > I've checked the plugin's options but unit option is not implemented. > > > > I'm wondering if there is a patch to change the default graph % unit with a decimal unit. > > check_by_ssh doesn't do any of this. It has no understanding of units or % or anything. It simply passes the output of the plugin it executes back to nagios as it was received. You either need to look at the output of the plugin that check_by_ssh is executing or the options for whatever you have that's doing the graphing. > > -- > Marc > > > ------------------------------------------------------------------------------ > This SF.Net email is sponsored by the Verizon Developer Community > Take advantage of Verizon's best-in-class app development support > A streamlined, 14 day to market process makes app distribution fast and easy > Join now and get one step closer to millions of Verizon customers > http://p.sf.net/sfu/verizon-dev2dev > _______________________________________________________ > 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 _________________________________________________________________ View your other email accounts from your Hotmail inbox. Add them now. http://clk.atdmt.com/UKM/go/186394592/direct/01/ -------------- next part -------------- An HTML attachment was scrubbed... URL: From marc at ena.com Fri Dec 18 14:24:31 2009 From: marc at ena.com (Marc Powell) Date: Fri, 18 Dec 2009 07:24:31 -0600 Subject: [Nagiosplug-devel] =?utf-8?q?change_default_=22check=5Fby=5Fssh?= =?utf-8?q?=22_output_unit=E2=80=8F?= In-Reply-To: References: , <52D01E60-F3FC-43E5-8028-1788873F9821@ena.com> Message-ID: <60DA8D79-D5B3-406E-88AF-ECE7DCE815EE@ena.com> On Dec 18, 2009, at 6:48 AM, giuseppe furlan wrote: > Thanks for your explanation. > > I'm using this plugin to retrieve 2 values (PendingRequest;HoggingThreadsCount) but the plugin's output consists of 3 values : > time;PendingRequest;HoggingThreadsCount > 1261051612;0;0 > > Is the time column provided by "check_by_ssh" plugin ? No. The only output that check_by_ssh contributes is error and help information. Everything else comes from the other plugin being executed. -- Marc From lowbotskie at gmail.com Mon Dec 21 07:24:20 2009 From: lowbotskie at gmail.com (shoks) Date: Mon, 21 Dec 2009 14:24:20 +0800 Subject: [Nagiosplug-devel] plug-in license Message-ID: <725c97180912202224k19c08cecvdab82aef71ab09ac@mail.gmail.com> Hi, Is it accepted to release a plug-in under a non-GPL license? What is the license requirement of such? Thanks, shoks -------------- next part -------------- An HTML attachment was scrubbed... URL: From william at leibzon.org Mon Dec 21 08:10:18 2009 From: william at leibzon.org (William Leibzon) Date: Sun, 20 Dec 2009 23:10:18 -0800 Subject: [Nagiosplug-devel] plug-in license In-Reply-To: <725c97180912202224k19c08cecvdab82aef71ab09ac@mail.gmail.com> References: <725c97180912202224k19c08cecvdab82aef71ab09ac@mail.gmail.com> Message-ID: Release under any license you like if its not based on any other plugin code. P.S. What license are you planning on using and why? On Sun, Dec 20, 2009 at 10:24 PM, shoks wrote: > Hi, > > Is it accepted to release a plug-in under a non-GPL license? What is > the license requirement of such? > > Thanks, > shoks > > > ------------------------------------------------------------------------------ > This SF.Net email is sponsored by the Verizon Developer Community > Take advantage of Verizon's best-in-class app development support > A streamlined, 14 day to market process makes app distribution fast and > easy > Join now and get one step closer to millions of Verizon customers > http://p.sf.net/sfu/verizon-dev2dev > _______________________________________________________ > Nagios Plugin Development Mailing List > Nagiosplug-devel at lists.sourceforge.net > Unsubscribe at > https://lists.sourceforge.net/lists/listinfo/nagiosplug-devel > ::: Please include plugins version (-v) and OS when reporting any issue. > ::: Messages without supporting info will risk being sent to /dev/null > -------------- next part -------------- An HTML attachment was scrubbed... URL: From lowbotskie at gmail.com Mon Dec 21 09:42:11 2009 From: lowbotskie at gmail.com (shoks) Date: Mon, 21 Dec 2009 16:42:11 +0800 Subject: [Nagiosplug-devel] plug-in license In-Reply-To: References: <725c97180912202224k19c08cecvdab82aef71ab09ac@mail.gmail.com> Message-ID: <725c97180912210042o6f03889em81f0fa73bb5cb5d7@mail.gmail.com> On Mon, Dec 21, 2009 at 3:10 PM, William Leibzon wrote: > Release under any license you like if its not based on any other plugin > code. > It will be developed from scratch and will not use or invoke any plugin code. Will it not be infected if being called upon, that being the framework is under GPL? > > P.S. What license are you planning on using and why? > Similar to the BSD license. The goal is not to impose any restriction on the application and use of the plugin, for commercial, proprietary or any purpose. Thanks > > On Sun, Dec 20, 2009 at 10:24 PM, shoks wrote: > >> Hi, >> >> Is it accepted to release a plug-in under a non-GPL license? What is >> the license requirement of such? >> >> Thanks, >> shoks >> >> >> ------------------------------------------------------------------------------ >> This SF.Net email is sponsored by the Verizon Developer Community >> Take advantage of Verizon's best-in-class app development support >> A streamlined, 14 day to market process makes app distribution fast and >> easy >> Join now and get one step closer to millions of Verizon customers >> http://p.sf.net/sfu/verizon-dev2dev >> _______________________________________________________ >> 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 >> > > > > ------------------------------------------------------------------------------ > This SF.Net email is sponsored by the Verizon Developer Community > Take advantage of Verizon's best-in-class app development support > A streamlined, 14 day to market process makes app distribution fast and > easy > Join now and get one step closer to millions of Verizon customers > http://p.sf.net/sfu/verizon-dev2dev > _______________________________________________________ > Nagios Plugin Development Mailing List > Nagiosplug-devel at lists.sourceforge.net > Unsubscribe at > https://lists.sourceforge.net/lists/listinfo/nagiosplug-devel > ::: Please include plugins version (-v) and OS when reporting any issue. > ::: Messages without supporting info will risk being sent to /dev/null > -------------- next part -------------- An HTML attachment was scrubbed... URL: From noreply at sourceforge.net Mon Dec 21 10:17:10 2009 From: noreply at sourceforge.net (SourceForge.net) Date: Mon, 21 Dec 2009 09:17:10 +0000 Subject: [Nagiosplug-devel] [ nagiosplug-Bugs-2832884 ] translation of --help broken Message-ID: Bugs item #2832884, was opened at 2009-08-05 18:48 Message generated for change (Comment added) made by dermoth You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=397597&aid=2832884&group_id=29880 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Interface (example) >Group: release-1.4.15 Status: Open >Resolution: Accepted Priority: 5 Private: No Submitted By: Jan Wagner (cyco_dd) >Assigned to: Thomas Guyot-Sionnest (dermoth) Summary: translation of --help broken Initial Comment: Hi there, looks like the translation of the help is somewhat broken in general. At least for LANG=de_DE.UTF-8, LANG=fr_FR.UTF-8 and check_dhcp, check_disk, where I can confirm the problem. The following Bugreport we got against our debian package: On my french system : ====================================== [root at kayak]:~ # /usr/lib/nagios/plugins/check_dhcp --help check_dhcp v1991 (nagios-plugins 1.4.12) Copyright (c) 2001-2004 Ethan Galstad (nagios at nagios.org) Copyright (c) 2001-2007 Nagios Plugin Development Team Ce plugin teste la disponibilit? de serveurs DHCP dans un r?seau. Utilisation: check_dhcp [-v] [-u] [-s serverip] [-r requestedip] [-t timeout] [-i interface] [-m mac] Options: -h, --help Print detailed help screen -V, --version Print version information Project-Id-Version: fr Report-Msgid-Bugs-To: nagiosplug-devel at lists.sourceforge.net POT-Creation-Date: 2008-05-27 23:06+0100 PO-Revision-Date: 2007-12-10 02:10-0500 Last-Translator: Thomas Guyot-Sionnest Language-Team: MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Plural-Forms: nplurals=2; plural=(n != 1); X-Generator: KBabel 1.11.4 -v, --verbose Show details for command-line debugging (Nagios may truncate output) -s, --serverip=IPADDRESS IP address of DHCP server that we must hear from -r, --requestedip=IPADDRESS IP address that should be offered by at least one DHCP server -t, --timeout=INTEGER Seconds to wait for DHCPOFFER before timeout occurs -i, --interface=STRING Interface to to use for listening (i.e. eth0) -m, --mac=STRING MAC address to use in the DHCP request -u, --unicast Unicast testing: mimic a DHCP relay, requires -s Send email to nagios-users at lists.sourceforge.net if you have questions regarding use of this software. To submit patches or suggest improvements, send email to nagiosplug-devel at lists.sourceforge.net ======================================= There is the translator info into the translation... You can track the bugreport via http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=522631 Thanks and kind regards, Jan. ---------------------------------------------------------------------- >Comment By: Thomas Guyot-Sionnest (dermoth) Date: 2009-12-21 04:17 Message: This is caused by "" matching the header of the translation files. I'll have to see if I can remove the part that matches in the po files, but it seems this can be fixed by setting UT_EXTRA_OPTS and UT_EXTRA_OPTS_NOTES to NULL instead of "" in plugins/utils.h I'm not sure if this solution will work on all systems though as gettext(3) doesn't mention anything about the string being set to null... I'll have to check that. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=397597&aid=2832884&group_id=29880 From noreply at sourceforge.net Mon Dec 21 10:19:51 2009 From: noreply at sourceforge.net (SourceForge.net) Date: Mon, 21 Dec 2009 09:19:51 +0000 Subject: [Nagiosplug-devel] [ nagiosplug-Patches-2908236 ] Support for larger numbers in the perfdata utility function Message-ID: Patches item #2908236, was opened at 2009-12-03 11:00 Message generated for change (Comment added) made by dermoth You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=397599&aid=2908236&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: Perf data Group: None >Status: Pending Resolution: None Priority: 5 Private: No Submitted By: Henrik Nilsson (rakhun) Assigned to: Nobody/Anonymous (nobody) Summary: Support for larger numbers in the perfdata utility function Initial Comment: Hi, this patch enables the perfdata utility function to work with larger numbers, such as check_disk with bytes as output unit, which would otherwise return large, negative numbers ---------------------------------------------------------------------- >Comment By: Thomas Guyot-Sionnest (dermoth) Date: 2009-12-21 04:19 Message: Setting status to pending, this item will close if there's no further activity on it ---------------------------------------------------------------------- Comment By: Thomas Guyot-Sionnest (dermoth) Date: 2009-12-05 00:44 Message: Thanks for the patch, although I'm wondering how useful it would be. There's no question about the need to graph large values, but this code will likely change a lot before we may think of changing check_disk's output format. Also I'm wondering it it wouldn't be wiser to use double for big values. AFAIK long long is not even supported natively by Perl, and RRD files use doubles. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=397599&aid=2908236&group_id=29880 From noreply at sourceforge.net Mon Dec 21 14:32:48 2009 From: noreply at sourceforge.net (SourceForge.net) Date: Mon, 21 Dec 2009 13:32:48 +0000 Subject: [Nagiosplug-devel] [ nagiosplug-Patches-2918676 ] This patch adds performance data to check_procs program. Message-ID: Patches item #2918676, was opened at 2009-12-21 13:32 Message generated for change (Tracker Item Submitted) made by You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=397599&aid=2918676&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: Perf data Group: release-1.4.14 Status: Open Resolution: None Priority: 5 Private: No Submitted By: tayfun () Assigned to: Nobody/Anonymous (nobody) Summary: This patch adds performance data to check_procs program. Initial Comment: I have simply added some print statements to the end so that number of processes are seen according to the performance data format. It also makes sure that it uses a dash, and not a colon while printing these. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=397599&aid=2918676&group_id=29880 From noreply at sourceforge.net Mon Dec 21 14:55:43 2009 From: noreply at sourceforge.net (SourceForge.net) Date: Mon, 21 Dec 2009 13:55:43 +0000 Subject: [Nagiosplug-devel] [ nagiosplug-Patches-2918676 ] This patch adds performance data to check_procs program. Message-ID: Patches item #2918676, was opened at 2009-12-21 13:32 Message generated for change (Comment added) made by You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=397599&aid=2918676&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: Perf data Group: release-1.4.14 Status: Open Resolution: None Priority: 5 Private: No Submitted By: tayfun () Assigned to: Nobody/Anonymous (nobody) Summary: This patch adds performance data to check_procs program. Initial Comment: I have simply added some print statements to the end so that number of processes are seen according to the performance data format. It also makes sure that it uses a dash, and not a colon while printing these. ---------------------------------------------------------------------- >Comment By: tayfun () Date: 2009-12-21 13:55 Message: Apparently I created a reverse patch. I just added the correct direction now. Just do a $ patch plugins/check_procs.c plugins/check_procs.c.patch --verbose for the patch to work, from the nagios-plugins directory. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=397599&aid=2918676&group_id=29880 From noreply at sourceforge.net Mon Dec 21 15:59:18 2009 From: noreply at sourceforge.net (SourceForge.net) Date: Mon, 21 Dec 2009 14:59:18 +0000 Subject: [Nagiosplug-devel] [ nagiosplug-Bugs-2918714 ] check_disk shows 0MB on large (32 Terra Byte) filesystem Message-ID: Bugs item #2918714, was opened at 2009-12-21 14:59 Message generated for change (Tracker Item Submitted) made by lixuz You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=397597&aid=2918714&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: lixuz (lixuz) Assigned to: Nobody/Anonymous (nobody) Summary: check_disk shows 0MB on large (32 Terra Byte) filesystem Initial Comment: root at tsm2:/tmp# ./check_disk -w 80% -c 90% /tsmstg DISK CRITICAL - free space: /tsmstg 0 MB (0% inode=99%);| /tsmstg=5683186MB;3352063;1676031;0;16760320 root at tsm2:/tmp# df -h /tsmstg Filesystem Size Used Avail Use% Mounted on /dev/tsmstglv 32T 22T 11T 67% /tsmstg root at tsm2:/tmp# ./check_disk -V check_disk v1.4.14-61-g45e2 (nagios-plugins 1.4.14) Operating system is AIX 5.3, gcc version 4.0.0 ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=397597&aid=2918714&group_id=29880 From noreply at sourceforge.net Mon Dec 21 16:01:05 2009 From: noreply at sourceforge.net (SourceForge.net) Date: Mon, 21 Dec 2009 15:01:05 +0000 Subject: [Nagiosplug-devel] [ nagiosplug-Bugs-2918714 ] check_disk shows 0MB on large (32 Terra Byte) filesystem Message-ID: Bugs item #2918714, was opened at 2009-12-21 14:59 Message generated for change (Comment added) made by lixuz You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=397597&aid=2918714&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: lixuz (lixuz) Assigned to: Nobody/Anonymous (nobody) Summary: check_disk shows 0MB on large (32 Terra Byte) filesystem Initial Comment: root at tsm2:/tmp# ./check_disk -w 80% -c 90% /tsmstg DISK CRITICAL - free space: /tsmstg 0 MB (0% inode=99%);| /tsmstg=5683186MB;3352063;1676031;0;16760320 root at tsm2:/tmp# df -h /tsmstg Filesystem Size Used Avail Use% Mounted on /dev/tsmstglv 32T 22T 11T 67% /tsmstg root at tsm2:/tmp# ./check_disk -V check_disk v1.4.14-61-g45e2 (nagios-plugins 1.4.14) Operating system is AIX 5.3, gcc version 4.0.0 ---------------------------------------------------------------------- >Comment By: lixuz (lixuz) Date: 2009-12-21 15:01 Message: Out put of truss # truss ./check_disk -w 80% -c 90% /tsmstg execve("./check_disk", 0x2FF22884, 0x2000E538) argc: 6 __loadx(0x03000000, 0x2FF22660, 0x00000140, 0x10000000, 0x20000C3F) = 0x00000000 __loadx(0x0C000000, 0xF038FA14, 0x0000000B, 0xF034A004, 0xF038F430) = 0x00000000 thread_init(0x0000000000000000, 0x00000000D0117D74) = sbrk(0x00000000) = 0x20002300 vmgetinfo(0x2FF22568, 7, 16) = 0 sbrk(0x00000000) = 0x20002300 vmgetinfo(0x2FF22030, 7, 16) = 0 sbrk(0x00000000) = 0x20002300 __libc_sbrk(0x00000000) = 0x20002300 getrpid(-1, -1, -264978308) = 663612 _getpid() = 663612 getprocs(0x20002DC8, 920, 0x00000000, 0, 0xF034A3B0, 1) = 1 appulimit(1005, 0) = 0x2DF23000 _thread_self() = 1122369 thread_setmystate(0x00000000, 0x2FF221C0) = 0 thread_setmystate(0x2FF21EB0, 0x2FF221B8) = 0 _sigaction(3, 0x2FF224E8, 0x2FF224F8) = 0 _sigaction(4, 0x2FF224E8, 0x2FF224F8) = 0 _sigaction(5, 0x2FF224E8, 0x2FF224F8) = 0 _sigaction(6, 0x2FF224E8, 0x2FF224F8) = 0 _sigaction(7, 0x2FF224E8, 0x2FF224F8) = 0 _sigaction(8, 0x2FF224E8, 0x2FF224F8) = 0 _sigaction(10, 0x2FF224E8, 0x2FF224F8) = 0 _sigaction(11, 0x2FF224E8, 0x2FF224F8) = 0 _sigaction(12, 0x2FF224E8, 0x2FF224F8) = 0 _sigaction(36, 0x2FF224E8, 0x2FF224F8) = 0 _sigaction(39, 0x2FF224E8, 0x2FF224F8) = 0 open("/unix", O_RDONLY|O_LARGEFILE) = 3 kioctl(3, 22528, 0x00000000, 0x00000000) Err#25 ENOTTY kioctl(3, 22528, 0x00000000, 0x00000000) Err#25 ENOTTY kread(3, "01F7\005 H181413\0\0\0\0".., 4096) = 4096 klseek(3, 0, 0, 0x00000001) = 0 klseek(3, 0, 13594638, 0x00000000) = 0 kread(3, "\0\0\0\0\0\0 1\0\0\0\004".., 4096) = 4096 klseek(3, 0, 0, 0x00000001) = 0 klseek(3, 0, 0, 0x00000001) = 0 klseek(3, 0, 14685640, 0x00000000) = 0 kread(3, " _ _ m u l h\0 _ _ m u l".., 4096) = 4096 klseek(3, 0, 0, 0x00000001) = 0 klseek(3, 0, 13594674, 0x00000000) = 0 kread(3, "\0\0\0\0\0\0 180\0\0\0\v".., 4096) = 4096 klseek(3, 0, 8, 0x00000001) = 0 kread(3, "\0\0\0\001 TA1B8\0\0028E".., 4096) = 4096 klseek(3, 0, 8, 0x00000001) = 0 kread(3, "\0\0\0\001 TA5 H\0\0\tCA".., 4096) = 4096 klseek(3, 0, 8, 0x00000001) = 0 kread(3, "\0\0\0\001 TA8D8\0\0028E".., 4096) = 4096 klseek(3, 0, 8, 0x00000001) = 0 kread(3, "\0\0\0\001 TAC h\0\0028E".., 4096) = 4096 klseek(3, 0, 8, 0x00000001) = 0 kread(3, "\0\0\0\001 TAFF8\0\0028E".., 4096) = 4096 klseek(3, 0, 8, 0x00000001) = 0 kread(3, "\0\0\0\001 TB388\0\0028E".., 4096) = 4096 klseek(3, 0, 8, 0x00000001) = 0 kread(3, "\0\0\0\001 TB718\0\003 s".., 4096) = 4096 klseek(3, 0, 8, 0x00000001) = 0 kread(3, "\0\0\0\001 TBAA8\0\003 s".., 4096) = 4096 klseek(3, 0, 8, 0x00000001) = 0 kread(3, "\0\0\0\001 TBE 8\0\003 s".., 4096) = 4096 klseek(3, 0, 8, 0x00000001) = 0 kread(3, "\0\0\0\001 TC1C8\0\0028E".., 4096) = 4096 klseek(3, 0, 8, 0x00000001) = 0 kread(3, "\0\0\0\001 TC5 X\0\0 " c".., 4096) = 4096 klseek(3, 0, 8, 0x00000001) = 0 kread(3, "\0\0\0\001 TC8E8\0\0 'AB".., 4096) = 4096 klseek(3, 0, 8, 0x00000001) = 0 kread(3, "\0\0\0\001 TCC x\0\0 - v".., 4096) = 4096 klseek(3, 0, 8, 0x00000001) = 0 kread(3, "\0\0\0\001 TD0\b\0\0 194".., 4096) = 4096 klseek(3, 0, 8, 0x00000001) = 0 kread(3, "\0\0\0\001 TD398\0\0 8\0".., 4096) = 4096 klseek(3, 0, 8, 0x00000001) = 0 kread(3, "\0\0\0\001 TD7 (\0\0 ? .".., 4096) = 4096 klseek(3, 0, 8, 0x00000001) = 0 kread(3, "\0\0\0\001 TDAB8\0\0028E".., 4096) = 4096 klseek(3, 0, 8, 0x00000001) = 0 kread(3, "\0\0\0\001 TDE H\0\003 s".., 4096) = 4096 klseek(3, 0, 8, 0x00000001) = 0 kread(3, "\0\0\0\001 TE1D8\0\0 EB2".., 4096) = 4096 klseek(3, 0, 8, 0x00000001) = 0 kread(3, "\0\0\0\001 U C 8\0\0 J U".., 4096) = 4096 klseek(3, 0, 8, 0x00000001) = 0 kread(3, "\0\0\0\001 U FF0\0\0 LD6".., 4096) = 4096 klseek(3, 0, 8, 0x00000001) = 0 kread(3, "\0\0\0\001 U J80\0\003 s".., 4096) = 4096 klseek(3, 0, 8, 0x00000001) = 0 kread(3, "\0\0\0\001 U N10\0\0028E".., 4096) = 4096 klseek(3, 0, 8, 0x00000001) = 0 kread(3, "\0\0\0\001 U QA0\0\0 T9F".., 4096) = 4096 klseek(3, 0, 8, 0x00000001) = 0 kread(3, "\0\0\0\001 U U 0\0\003 s".., 4096) = 4096 klseek(3, 0, 8, 0x00000001) = 0 kread(3, "\0\0\0\001 U XC0\0\0 \05".., 4096) = 4096 klseek(3, 0, 8, 0x00000001) = 0 kread(3, "\0\0\0\001 U \ P\0\0 b 7".., 4096) = 4096 klseek(3, 0, 8, 0x00000001) = 0 kread(3, "\0\0\0\001 U _E0\0\0 e Q".., 4096) = 4096 klseek(3, 0, 8, 0x00000001) = 0 kread(3, "\0\0\0\001 U c p\0\0 iF8".., 4096) = 4096 klseek(3, 0, 0, 0x00000001) = 0 klseek(3, 0, 0, 0x00000001) = 0 klseek(3, 0, 14710193, 0x00000000) = 0 kread(3, " p i n n e d _ p r _ s t".., 4096) = 4096 klseek(3, 0, 0, 0x00000001) = 0 klseek(3, 0, 13713798, 0x00000000) = 0 kread(3, "\0\0\0\0\0 U10\0\0\0 `\v".., 4096) = 4096 klseek(3, 0, 0, 0x00000001) = 0 klseek(3, 0, 0, 0x00000001) = 0 klseek(3, 0, 14705293, 0x00000000) = 0 kread(3, " n o n p r i v _ p a g e".., 4096) = 4096 klseek(3, 0, 0, 0x00000001) = 0 klseek(3, 0, 13714068, 0x00000000) = 0 kread(3, "\0\0\0\0\0\0 0\0\0\0 j 0".., 4096) = 4096 klseek(3, 0, 0, 0x00000001) = 0 klseek(3, 0, 0, 0x00000001) = 0 klseek(3, 0, 14712820, 0x00000000) = 0 kread(3, " g _ c o p y r\0 . m u l".., 4096) = 4096 klseek(3, 0, 0, 0x00000001) = 0 klseek(3, 0, 13714104, 0x00000000) = 0 kread(3, "\0\0\0\0\0\0 1\0\0\0 j 8".., 4096) = 4096 klseek(3, 0, 0, 0x00000001) = 0 klseek(3, 0, 0, 0x00000001) = 0 klseek(3, 0, 14688688, 0x00000000) = 0 kread(3, " c m p _ s w a p _ i n d".., 4096) = 4096 klseek(3, 0, 0, 0x00000001) = 0 klseek(3, 0, 13714608, 0x00000000) = 0 kread(3, "\0\0\0\0\0\0 4C0\0\004 w".., 4096) = 4096 klseek(3, 0, 0, 0x00000001) = 0 klseek(3, 0, 0, 0x00000001) = 0 klseek(3, 0, 14686779, 0x00000000) = 0 kread(3, " g _ k s r v a l\0 d s i".., 4096) = 4096 klseek(3, 0, 0, 0x00000001) = 0 klseek(3, 0, 13714644, 0x00000000) = 0 kread(3, "\0\0\0\0\0\0 4C8\0\0 I f".., 4096) = 4096 klseek(3, 0, 0, 0x00000001) = 0 klseek(3, 0, 0, 0x00000001) = 0 klseek(3, 0, 14704426, 0x00000000) = 0 kread(3, " T r c o n f l a g\0 h _".., 4096) = 4096 klseek(3, 0, 0, 0x00000001) = 0 klseek(3, 0, 13714680, 0x00000000) = 0 kread(3, "\0\0\0\0\0\0 4E0\0\0\fC2".., 4096) = 4096 klseek(3, 0, 0, 0x00000001) = 0 klseek(3, 0, 0, 0x00000001) = 0 klseek(3, 0, 14688902, 0x00000000) = 0 kread(3, " _ s y s t e m _ c o n f".., 4096) = 4096 klseek(3, 0, 0, 0x00000001) = 0 klseek(3, 0, 13714716, 0x00000000) = 0 kread(3, "\0\0\0\0\0\0 5DC\0\0\f\v".., 4096) = 4096 klseek(3, 0, 0, 0x00000001) = 0 klseek(3, 0, 0, 0x00000001) = 0 klseek(3, 0, 14688719, 0x00000000) = 0 kread(3, " u t r c h o o k _ s c _".., 4096) = 4096 klseek(3, 0, 0, 0x00000001) = 0 klseek(3, 0, 13714752, 0x00000000) = 0 kread(3, "\0\0\0\0\0\0 5E0\0\0189B".., 4096) = 4096 klseek(3, 0, 0, 0x00000001) = 0 klseek(3, 0, 0, 0x00000001) = 0 klseek(3, 0, 14705342, 0x00000000) = 0 kread(3, " _ s y s t e m _ T B _ c".., 4096) = 4096 klseek(3, 0, 0, 0x00000001) = 0 klseek(3, 0, 13714824, 0x00000000) = 0 kread(3, "\0\0\0\0\0\0 6\b\0\01897".., 4096) = 4096 klseek(3, 0, 0, 0x00000001) = 0 klseek(3, 0, 0, 0x00000001) = 0 klseek(3, 0, 14691931, 0x00000000) = 0 kread(3, " t o d\0 _ _ e x t e n s".., 4096) = 4096 klseek(3, 0, 0, 0x00000001) = 0 klseek(3, 0, 13714860, 0x00000000) = 0 kread(3, "\0\0\0\0\0\0 618\0\0 R15".., 4096) = 4096 klseek(3, 0, 0, 0x00000001) = 0 klseek(3, 0, 0, 0x00000001) = 0 klseek(3, 0, 14706649, 0x00000000) = 0 kread(3, " t b _ t i c s _ p e r _".., 4096) = 4096 klseek(3, 0, 0, 0x00000001) = 0 klseek(3, 0, 13714896, 0x00000000) = 0 kread(3, "\0\0\0\0\0\0 6 \0\0 R %".., 4096) = 4096 klseek(3, 0, 0, 0x00000001) = 0 klseek(3, 0, 0, 0x00000001) = 0 klseek(3, 0, 14712882, 0x00000000) = 0 kread(3, " _ c l e a r _ l o c k _".., 4096) = 4096 klseek(3, 0, 0, 0x00000001) = 0 klseek(3, 0, 13714968, 0x00000000) = 0 kread(3, "\0\0\0\0\0\0 6 H\0\00E8F".., 4096) = 4096 klseek(3, 0, 0, 0x00000001) = 0 klseek(3, 0, 0, 0x00000001) = 0 klseek(3, 0, 14689363, 0x00000000) = 0 kread(3, " A R M _ T r c o n f l a".., 4096) = 4096 klseek(3, 0, 0, 0x00000001) = 0 klseek(3, 0, 13715004, 0x00000000) = 0 kread(3, "\0\0\0\0\0\0 6 P\0\0\r15".., 4096) = 4096 klseek(3, 0, 0, 0x00000001) = 0 klseek(3, 0, 0, 0x00000001) = 0 klseek(3, 0, 14688985, 0x00000000) = 0 kread(3, " s v c _ i n s t r u c t".., 4096) = 4096 klseek(3, 0, 0, 0x00000001) = 0 klseek(3, 0, 13715040, 0x00000000) = 0 kread(3, "\0\0\0\0\0\0 6 P\0\013FE".., 4096) = 4096 klseek(3, 0, 0, 0x00000001) = 0 klseek(3, 0, 0, 0x00000001) = 0 klseek(3, 0, 14712915, 0x00000000) = 0 kread(3, " . s v c _ i n s t r\0 s".., 4096) = 4096 klseek(3, 0, 0, 0x00000001) = 0 klseek(3, 0, 13715112, 0x00000000) = 0 kread(3, "\0\0\0\0\0\0 71C\0\0 j9A".., 4096) = 4096 klseek(3, 0, 0, 0x00000001) = 0 klseek(3, 0, 0, 0x00000001) = 0 klseek(3, 0, 14705131, 0x00000000) = 0 kread(3, " . s y s _ c a l l _ r e".., 4096) = 4096 klseek(3, 0, 0, 0x00000001) = 0 klseek(3, 0, 13715364, 0x00000000) = 0 kread(3, "\0\0\0\0\0\0 8 0\0\0 k\r".., 4096) = 4096 klseek(3, 0, 0, 0x00000001) = 0 klseek(3, 0, 0, 0x00000001) = 0 klseek(3, 0, 14713041, 0x00000000) = 0 kread(3, " s c _ t r a c e _ e n d".., 4096) = 4096 klseek(3, 0, 0, 0x00000001) = 0 klseek(3, 0, 13715400, 0x00000000) = 0 kread(3, "\0\0\0\0\0\0 8 P\0\0 k ".., 4096) = 4096 klseek(3, 0, 0, 0x00000001) = 0 klseek(3, 0, 0, 0x00000001) = 0 klseek(3, 0, 14687143, 0x00000000) = 0 kread(3, " v r s a v e _ p a t c h".., 4096) = 4096 klseek(3, 0, 0, 0x00000001) = 0 klseek(3, 0, 13715760, 0x00000000) = 0 kread(3, "\0\0\0\0\0\0 =A0\0\0 kC5".., 4096) = 4096 klseek(3, 0, 0, 0x00000001) = 0 klseek(3, 0, 0, 0x00000001) = 0 klseek(3, 0, 14713225, 0x00000000) = 0 kread(3, " c s c _ r e t _ h _ p u".., 4096) = 4096 klseek(3, 0, 0, 0x00000001) = 0 klseek(3, 0, 13715796, 0x00000000) = 0 kread(3, "\0\0\0\0\0\0 > (\0\0 kDA".., 4096) = 4096 close(3) = 0 getuidx(4) = 0 getuidx(2) = 0 getuidx(1) = 0 getgidx(4) = 0 getgidx(2) = 0 getgidx(1) = 0 __loadx(0x01000080, 0x2FF213E8, 0x00000960, 0x2FF21E68, 0x2FF22F4A) = 0x00000000 mntctl(2, 4, " ") = 0 mntctl(2, 1768, "") = 15 open("/etc/vfs", O_RDONLY|O_NDELAY) = 3 kfcntl(3, F_SETLK, 0x2FF22590) = 0 kfcntl(3, F_GETFL, 0x20003FE4) = 32768 kioctl(3, 22528, 0x00000000, 0x00000000) Err#25 ENOTTY kioctl(3, 22528, 0x00000000, 0x00000000) Err#25 ENOTTY kread(3, " # @ ( # ) v f s @".., 4096) = 1617 close(3) = 0 open("/etc/vfs", O_RDONLY|O_NDELAY) = 3 kfcntl(3, F_SETLK, 0x2FF22590) = 0 kfcntl(3, F_GETFL, 0x20003FE4) = 32768 kioctl(3, 22528, 0x00000000, 0x00000000) Err#25 ENOTTY kioctl(3, 22528, 0x00000000, 0x00000000) Err#25 ENOTTY kread(3, " # @ ( # ) v f s @".., 4096) = 1617 close(3) = 0 open("/etc/vfs", O_RDONLY|O_NDELAY) = 3 kfcntl(3, F_SETLK, 0x2FF22590) = 0 kfcntl(3, F_GETFL, 0x20003FE4) = 32768 kioctl(3, 22528, 0x00000000, 0x00000000) Err#25 ENOTTY kioctl(3, 22528, 0x00000000, 0x00000000) Err#25 ENOTTY kread(3, " # @ ( # ) v f s @".., 4096) = 1617 close(3) = 0 open("/etc/vfs", O_RDONLY|O_NDELAY) = 3 kfcntl(3, F_SETLK, 0x2FF22590) = 0 kfcntl(3, F_GETFL, 0x20003FE4) = 32768 kioctl(3, 22528, 0x00000000, 0x00000000) Err#25 ENOTTY kioctl(3, 22528, 0x00000000, 0x00000000) Err#25 ENOTTY kread(3, " # @ ( # ) v f s @".., 4096) = 1617 close(3) = 0 open("/etc/vfs", O_RDONLY|O_NDELAY) = 3 kfcntl(3, F_SETLK, 0x2FF22590) = 0 kfcntl(3, F_GETFL, 0x20003FE4) = 32768 kioctl(3, 22528, 0x00000000, 0x00000000) Err#25 ENOTTY kioctl(3, 22528, 0x00000000, 0x00000000) Err#25 ENOTTY kread(3, " # @ ( # ) v f s @".., 4096) = 1617 close(3) = 0 open("/etc/vfs", O_RDONLY|O_NDELAY) = 3 kfcntl(3, F_SETLK, 0x2FF22590) = 0 kfcntl(3, F_GETFL, 0x20003FE4) = 32768 kioctl(3, 22528, 0x00000000, 0x00000000) Err#25 ENOTTY kioctl(3, 22528, 0x00000000, 0x00000000) Err#25 ENOTTY kread(3, " # @ ( # ) v f s @".., 4096) = 1617 close(3) = 0 open("/etc/vfs", O_RDONLY|O_NDELAY) = 3 kfcntl(3, F_SETLK, 0x2FF22590) = 0 kfcntl(3, F_GETFL, 0x20003FE4) = 32768 kioctl(3, 22528, 0x00000000, 0x00000000) Err#25 ENOTTY kioctl(3, 22528, 0x00000000, 0x00000000) Err#25 ENOTTY kread(3, " # @ ( # ) v f s @".., 4096) = 1617 close(3) = 0 open("/etc/vfs", O_RDONLY|O_NDELAY) = 3 kfcntl(3, F_SETLK, 0x2FF22590) = 0 kfcntl(3, F_GETFL, 0x20003FE4) = 32768 kioctl(3, 22528, 0x00000000, 0x00000000) Err#25 ENOTTY kioctl(3, 22528, 0x00000000, 0x00000000) Err#25 ENOTTY kread(3, " # @ ( # ) v f s @".., 4096) = 1617 close(3) = 0 open("/etc/vfs", O_RDONLY|O_NDELAY) = 3 kfcntl(3, F_SETLK, 0x2FF22590) = 0 kfcntl(3, F_GETFL, 0x20003FE4) = 32768 kioctl(3, 22528, 0x00000000, 0x00000000) Err#25 ENOTTY kioctl(3, 22528, 0x00000000, 0x00000000) Err#25 ENOTTY kread(3, " # @ ( # ) v f s @".., 4096) = 1617 close(3) = 0 open("/etc/vfs", O_RDONLY|O_NDELAY) = 3 kfcntl(3, F_SETLK, 0x2FF22590) = 0 kfcntl(3, F_GETFL, 0x20003FE4) = 32768 kioctl(3, 22528, 0x00000000, 0x00000000) Err#25 ENOTTY kioctl(3, 22528, 0x00000000, 0x00000000) Err#25 ENOTTY kread(3, " # @ ( # ) v f s @".., 4096) = 1617 close(3) = 0 open("/etc/vfs", O_RDONLY|O_NDELAY) = 3 kfcntl(3, F_SETLK, 0x2FF22590) = 0 kfcntl(3, F_GETFL, 0x20003FE4) = 32768 kioctl(3, 22528, 0x00000000, 0x00000000) Err#25 ENOTTY kioctl(3, 22528, 0x00000000, 0x00000000) Err#25 ENOTTY kread(3, " # @ ( # ) v f s @".., 4096) = 1617 close(3) = 0 open("/etc/vfs", O_RDONLY|O_NDELAY) = 3 kfcntl(3, F_SETLK, 0x2FF22590) = 0 kfcntl(3, F_GETFL, 0x20003FE4) = 32768 kioctl(3, 22528, 0x00000000, 0x00000000) Err#25 ENOTTY kioctl(3, 22528, 0x00000000, 0x00000000) Err#25 ENOTTY kread(3, " # @ ( # ) v f s @".., 4096) = 1617 close(3) = 0 open("/etc/vfs", O_RDONLY|O_NDELAY) = 3 kfcntl(3, F_SETLK, 0x2FF22590) = 0 kfcntl(3, F_GETFL, 0x20003FE4) = 32768 kioctl(3, 22528, 0x00000000, 0x00000000) Err#25 ENOTTY kioctl(3, 22528, 0x00000000, 0x00000000) Err#25 ENOTTY kread(3, " # @ ( # ) v f s @".., 4096) = 1617 close(3) = 0 open("/etc/vfs", O_RDONLY|O_NDELAY) = 3 kfcntl(3, F_SETLK, 0x2FF22590) = 0 kfcntl(3, F_GETFL, 0x20003FE4) = 32768 kioctl(3, 22528, 0x00000000, 0x00000000) Err#25 ENOTTY kioctl(3, 22528, 0x00000000, 0x00000000) Err#25 ENOTTY kread(3, " # @ ( # ) v f s @".., 4096) = 1617 close(3) = 0 open("/etc/vfs", O_RDONLY|O_NDELAY) = 3 kfcntl(3, F_SETLK, 0x2FF22590) = 0 kfcntl(3, F_GETFL, 0x20003FE4) = 32768 kioctl(3, 22528, 0x00000000, 0x00000000) Err#25 ENOTTY kioctl(3, 22528, 0x00000000, 0x00000000) Err#25 ENOTTY kread(3, " # @ ( # ) v f s @".., 4096) = 1617 close(3) = 0 statx("/tsmstg", 0x20009C48, 128, 010) = 0 statfs("/tsmstg", 0x2FF224E8) = 0 mntctl(2, 512, "") = 0 mntctl(2, 1768, "") = 15 open("/etc/vfs", O_RDONLY) = 3 kioctl(3, 22528, 0x00000000, 0x00000000) Err#25 ENOTTY kioctl(3, 22528, 0x00000000, 0x00000000) Err#25 ENOTTY kread(3, " # @ ( # ) v f s @".., 4096) = 1617 close(3) = 0 kioctl(1, 22528, 0x00000000, 0x00000000) = 0 DISK CRITICAL - free space: /tsmstg 0 MB (0% inode=99%);| /tsmstg=5724916MB;3352063;1676031;0;16760320 kwrite(1, " D I S K C R I T I C A".., 103) = 103 __loadx(0x04000000, 0x2FF21F20, 0x00000800, 0x0000D0B2, 0x00000000) = 0x00000000 kfcntl(1, F_GETFL, 0x10112041) = 67108866 kfcntl(2, F_GETFL, 0x10112041) = 67108866 _exit(2) ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=397597&aid=2918714&group_id=29880 From william at leibzon.org Mon Dec 21 19:23:24 2009 From: william at leibzon.org (William Leibzon) Date: Mon, 21 Dec 2009 10:23:24 -0800 Subject: [Nagiosplug-devel] plug-in license In-Reply-To: <725c97180912210042o6f03889em81f0fa73bb5cb5d7@mail.gmail.com> References: <725c97180912202224k19c08cecvdab82aef71ab09ac@mail.gmail.com> <725c97180912210042o6f03889em81f0fa73bb5cb5d7@mail.gmail.com> Message-ID: Since no new plugins are being added to standard nagos-plugins distribution (which is under GPL) you should release new plugin on your own put it on exchange.nagios.org. You can use libraries available but you don't have to and I think no matter if you do or not you can release your plugin under any license including entirely commercial one. As far as BSD vs GPL it makes a difference only when some commercial company is going to integrate it into their own distribution with only binary being there (i.e. if plugin is written in C and only compiled version is released). If plugin is written in interpreted language (Perl) then even if they include it in their own distribution, the code is available for anyone and they can't put it under different license. Similarly they can include GPL plugin in their own distribution too (Redhat is commercial distro but obviously includes mostly GPL code) and because of what plugins really are, I can't see where the above would ever make a difference so I think releasing all plugins under GPL is fine even if you envision commercial use and distribution. Some of my own plugins are included in commercial (or semi-commercial since they make most code available as open-source) distributions - Groundwork and Zenoss. Nobody ever told me or asked for my permission but I don't see any issue either. On Mon, Dec 21, 2009 at 12:42 AM, shoks wrote: > > > On Mon, Dec 21, 2009 at 3:10 PM, William Leibzon wrote: > >> Release under any license you like if its not based on any other plugin >> code. >> > It will be developed from scratch and will not use or invoke any plugin > code. Will it not > be infected if being called upon, that being the framework is under GPL? > > >> >> P.S. What license are you planning on using and why? >> > Similar to the BSD license. The goal is not to impose any restriction on > the application > and use of the plugin, for commercial, proprietary or any purpose. > > Thanks > >> >> On Sun, Dec 20, 2009 at 10:24 PM, shoks wrote: >> >>> Hi, >>> >>> Is it accepted to release a plug-in under a non-GPL license? What is >>> the license requirement of such? >>> >>> Thanks, >>> shoks >>> >>> >>> ------------------------------------------------------------------------------ >>> This SF.Net email is sponsored by the Verizon Developer Community >>> Take advantage of Verizon's best-in-class app development support >>> A streamlined, 14 day to market process makes app distribution fast and >>> easy >>> Join now and get one step closer to millions of Verizon customers >>> http://p.sf.net/sfu/verizon-dev2dev >>> _______________________________________________________ >>> 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 >>> >> >> >> >> ------------------------------------------------------------------------------ >> This SF.Net email is sponsored by the Verizon Developer Community >> Take advantage of Verizon's best-in-class app development support >> A streamlined, 14 day to market process makes app distribution fast and >> easy >> Join now and get one step closer to millions of Verizon customers >> http://p.sf.net/sfu/verizon-dev2dev >> _______________________________________________________ >> 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 >> > > > > ------------------------------------------------------------------------------ > This SF.Net email is sponsored by the Verizon Developer Community > Take advantage of Verizon's best-in-class app development support > A streamlined, 14 day to market process makes app distribution fast and > easy > Join now and get one step closer to millions of Verizon customers > http://p.sf.net/sfu/verizon-dev2dev > _______________________________________________________ > Nagios Plugin Development Mailing List > Nagiosplug-devel at lists.sourceforge.net > Unsubscribe at > https://lists.sourceforge.net/lists/listinfo/nagiosplug-devel > ::: Please include plugins version (-v) and OS when reporting any issue. > ::: Messages without supporting info will risk being sent to /dev/null > -------------- next part -------------- An HTML attachment was scrubbed... URL: From lowbotskie at gmail.com Tue Dec 22 03:23:52 2009 From: lowbotskie at gmail.com (shoks) Date: Tue, 22 Dec 2009 10:23:52 +0800 Subject: [Nagiosplug-devel] plug-in license In-Reply-To: References: <725c97180912202224k19c08cecvdab82aef71ab09ac@mail.gmail.com> <725c97180912210042o6f03889em81f0fa73bb5cb5d7@mail.gmail.com> Message-ID: <725c97180912211823v3f7142d6hcff54d57069eff58@mail.gmail.com> That would work for me. Thanks for the guidance! On Tue, Dec 22, 2009 at 2:23 AM, William Leibzon wrote: > Since no new plugins are being added to standard nagos-plugins distribution > (which is under GPL) you should release new plugin on your own put it on > exchange.nagios.org. You can use libraries available but you don't have to > and I think no matter if you do or not you can release your plugin under any > license including entirely commercial one. > > As far as BSD vs GPL it makes a difference only when some commercial > company is going to integrate it into their own distribution with only > binary being there (i.e. if plugin is written in C and only compiled version > is released). If plugin is written in interpreted language (Perl) then even > if they include it in their own distribution, the code is available for > anyone and they can't put it under different license. Similarly they can > include GPL plugin in their own distribution too (Redhat is commercial > distro but obviously includes mostly GPL code) and because of what plugins > really are, I can't see where the above would ever make a difference so I > think releasing all plugins under GPL is fine even if you envision > commercial use and distribution. > > Some of my own plugins are included in commercial (or semi-commercial since > they make most code available as open-source) distributions - Groundwork and > Zenoss. Nobody ever told me or asked for my permission but I don't see any > issue either. > > > On Mon, Dec 21, 2009 at 12:42 AM, shoks wrote: > >> >> >> On Mon, Dec 21, 2009 at 3:10 PM, William Leibzon wrote: >> >>> Release under any license you like if its not based on any other plugin >>> code. >>> >> It will be developed from scratch and will not use or invoke any plugin >> code. Will it not >> be infected if being called upon, that being the framework is under GPL? >> >> >>> >>> P.S. What license are you planning on using and why? >>> >> Similar to the BSD license. The goal is not to impose any restriction on >> the application >> and use of the plugin, for commercial, proprietary or any purpose. >> >> Thanks >> >>> >>> On Sun, Dec 20, 2009 at 10:24 PM, shoks wrote: >>> >>>> Hi, >>>> >>>> Is it accepted to release a plug-in under a non-GPL license? What is >>>> the license requirement of such? >>>> >>>> Thanks, >>>> shoks >>>> >>>> >>>> ------------------------------------------------------------------------------ >>>> This SF.Net email is sponsored by the Verizon Developer Community >>>> Take advantage of Verizon's best-in-class app development support >>>> A streamlined, 14 day to market process makes app distribution fast and >>>> easy >>>> Join now and get one step closer to millions of Verizon customers >>>> http://p.sf.net/sfu/verizon-dev2dev >>>> _______________________________________________________ >>>> 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 >>>> >>> >>> >>> >>> ------------------------------------------------------------------------------ >>> This SF.Net email is sponsored by the Verizon Developer Community >>> Take advantage of Verizon's best-in-class app development support >>> A streamlined, 14 day to market process makes app distribution fast and >>> easy >>> Join now and get one step closer to millions of Verizon customers >>> http://p.sf.net/sfu/verizon-dev2dev >>> _______________________________________________________ >>> 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 >>> >> >> >> >> ------------------------------------------------------------------------------ >> This SF.Net email is sponsored by the Verizon Developer Community >> Take advantage of Verizon's best-in-class app development support >> A streamlined, 14 day to market process makes app distribution fast and >> easy >> Join now and get one step closer to millions of Verizon customers >> http://p.sf.net/sfu/verizon-dev2dev >> _______________________________________________________ >> 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 >> > > > > ------------------------------------------------------------------------------ > This SF.Net email is sponsored by the Verizon Developer Community > Take advantage of Verizon's best-in-class app development support > A streamlined, 14 day to market process makes app distribution fast and > easy > Join now and get one step closer to millions of Verizon customers > http://p.sf.net/sfu/verizon-dev2dev > _______________________________________________________ > Nagios Plugin Development Mailing List > Nagiosplug-devel at lists.sourceforge.net > Unsubscribe at > https://lists.sourceforge.net/lists/listinfo/nagiosplug-devel > ::: Please include plugins version (-v) and OS when reporting any issue. > ::: Messages without supporting info will risk being sent to /dev/null > -------------- next part -------------- An HTML attachment was scrubbed... URL: From mlitwin at stubhub.com Mon Dec 28 20:34:09 2009 From: mlitwin at stubhub.com (Litwin, Matthew) Date: Mon, 28 Dec 2009 12:34:09 -0700 Subject: [Nagiosplug-devel] check_disk can't handle very large partitions Message-ID: <745DC7D8-C939-4ACD-A4A6-7E1DCFB6C759@stubhub.com> Hi, I am finding that the check_disk plugin (compiled for Solaris 10) does not handle large partitions and will invariably report 0% for them. I am not sure what the cutoff for this is, but it is the case for a 7.1TB partition. I have been looking for a revision history for this plugin to see if this has been fixed since this version, but I am unable to find it. Is there a revision -bash-3.00$ ./check_disk -V check_disk v1848 (nagios-plugins 1.4.11) -bash-3.00$ df -mh | grep /mnt 7.1T 4.5T 2.6T 64% /mnt/oracle_stage01 1.5T 847G 672G 56% /mnt/oracle_stage02 -bash-3.00$ ./check_disk -w 90 -c 95 -R /mnt/oracle_stage02 DISK OK - free space: /mnt/oracle_stage02 687264 MB (44% inode=100%);| /mnt/oracle_stage02=866399MB;1553574;1553569;0;1553664 -bash-3.00$ ./check_disk -w 90 -c 95 -R /mnt/oracle_stage01 DISK CRITICAL - free space: /mnt/oracle_stage01 0 MB (0% inode=-107400410755%);| /mnt/oracle_stage01=2147483647MB;2147483647;2147483647;0;2147483647 Thanks, Matthew Litwin mlitwin at stubhub.com 415.222.8475 From dermoth at aei.ca Tue Dec 29 02:03:07 2009 From: dermoth at aei.ca (Thomas Guyot-Sionnest) Date: Mon, 28 Dec 2009 20:03:07 -0500 Subject: [Nagiosplug-devel] check_disk can't handle very large partitions In-Reply-To: <745DC7D8-C939-4ACD-A4A6-7E1DCFB6C759@stubhub.com> References: <745DC7D8-C939-4ACD-A4A6-7E1DCFB6C759@stubhub.com> Message-ID: <4B39554B.3070906@aei.ca> On 28/12/09 02:34 PM, Litwin, Matthew wrote: > Hi, I am finding that the check_disk plugin (compiled for Solaris 10) does not handle large partitions and will invariably report 0% for them. I am not sure what the cutoff for this is, but it is the case for a 7.1TB partition. > > I have been looking for a revision history for this plugin to see if this has been fixed since this version, but I am unable to find it. > > Is there a revision This is in the 1.4.12 release notes (NEWS file): >> check_disk should now work with large file systems (2TB+) on all archs that supports it > -bash-3.00$ ./check_disk -V > check_disk v1848 (nagios-plugins 1.4.11) You will have to upgrade then. -- Thomas From noreply at sourceforge.net Thu Dec 31 18:27:55 2009 From: noreply at sourceforge.net (SourceForge.net) Date: Thu, 31 Dec 2009 17:27:55 +0000 Subject: [Nagiosplug-devel] [ nagiosplug-Patches-1150826 ] Performance data added to check_mysql Message-ID: Patches item #1150826, was opened at 2005-02-24 03:11 Message generated for change (Comment added) made by lnxus You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=397599&aid=1150826&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: Perf data Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Ben Clewett (benclewett) Assigned to: Ton Voon (tonvoon) Summary: Performance data added to check_mysql Initial Comment: Performance data added to check_mysql by inteperating data returned by MySQL. If this format remains the same, should always work. Tested MySQL v 4.0.11 -> 4.1.9 Ben. -- bclewett at perfparse.org ---------------------------------------------------------------------- Comment By: Dale Blount (lnxus) Date: 2009-12-31 12:27 Message: Status update? I applied this (with fuzz) to nagiosplug 1.4.12 and it seems to work for me. ---------------------------------------------------------------------- Comment By: Ben Clewett (benclewett) Date: 2005-02-28 10:16 Message: Logged In: YES user_id=157178 Thanks for finding the patch, I know a lot of users will be interested in this. Regards, Ben ---------------------------------------------------------------------- Comment By: Matthew Kent (mattkent) Date: 2005-02-28 10:11 Message: Logged In: YES user_id=983566 Yeah I took it from your email. Will look at applying this week when I have some time. ---------------------------------------------------------------------- Comment By: Ben Clewett (benclewett) Date: 2005-02-28 03:30 Message: Logged In: YES user_id=157178 Did I forget? I can see it attached. Or did you copy this fromn my email? So is this ok now? ---------------------------------------------------------------------- Comment By: Matthew Kent (mattkent) Date: 2005-02-25 14:39 Message: Logged In: YES user_id=983566 Another tiny patch for replication data to apply ---------------------------------------------------------------------- Comment By: Matthew Kent (mattkent) Date: 2005-02-25 14:38 Message: Logged In: YES user_id=983566 Think you forgot the file :) ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=397599&aid=1150826&group_id=29880