From noreply at sourceforge.net Fri Feb 17 02:50:38 2012 From: noreply at sourceforge.net (SourceForge.net) Date: Thu, 16 Feb 2012 17:50:38 -0800 Subject: [Nagiosplug-devel] [ nagiosplug-Bugs-3008084 ] check_dhcp Microsoft Server Options 66 and 67 CRITICAL Message-ID: Bugs item #3008084, was opened at 2010-05-27 10:43 Message generated for change (Comment added) made by martinkonrad You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=397597&aid=3008084&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: arch nemesis (mstng67) Assigned to: Nobody/Anonymous (nobody) Summary: check_dhcp Microsoft Server Options 66 and 67 CRITICAL Initial Comment: Plugin Version (-V output): check_dhcp v1.4.14 (nagios-plugins 1.4.14) Plugin Name: check_dhcp Plugin Commandline showing issues: /usr/lib/nagios/plugins/check_dhcp -s 192.168.0.16 Output from above command: CRITICAL: Received 1 DHCPOFFER(s), 0 of 1 requested servers responded, max lease time = 0 sec. Operating System: Linux Mint 8 Helena - Main Edition Architecture: x86 Compiler: ??? The plugins were installed using APT. The change that prompted the CRITICAL output: Added Microsoft DHCP server options 66 and 67 to DHCP server configuration. These options are Boot Server Host Name and Bootfile Name, respectively. Restart the DHCP service. The next check of the DHCP server yielded the above output. Number of DHCP servers on the network: 1. The above mentioned MS DHCP server is the only DHCP server on the network. My guess is that the plugin is incorrectly parsing the options returned in the DHCPOFFER. I have no proof to back up this theory except that if the DHCP server is re-configured back to the known good (without options 66 and 67) then the plugin returns OK. If options 66 and 67 are configured the plugin returns CRITICAL for the specified server. Until a fix is released, I have simply removed the -s 192.168.0.16 portion of the command config file for the dhcp plugin to ensure that the plugin responds OK as long as it receives a DHCPOFFER. I know that it's a temporary fix, but it's what I know to do for now. If you need additional information, please email me. ---------------------------------------------------------------------- Comment By: Martin Konrad (martinkonrad) Date: 2012-02-16 17:50 Message: I can confirm the described behavior. But as it seems there is no fix: Microsoft delivers the data from the DHCP option 66 field as "next server ip address" to work around some buggy PXE devices (http://www.symantec.com/business/support/index?page=content&id=TECH40756). That's why check_dhcp thinks the DHCP server is behind a DHCP proxy which of course is not the case. I confirmed that looking at the DHCP offer with Wireshark. There are two ways around that: 1. Do not check the IP of the DHCP server. 2. Check against your TFTP boot-server's IP. Hope that helps... ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=397597&aid=3008084&group_id=29880 From noreply at sourceforge.net Wed Feb 22 08:56:18 2012 From: noreply at sourceforge.net (SourceForge.net) Date: Tue, 21 Feb 2012 23:56:18 -0800 Subject: [Nagiosplug-devel] [ nagiosplug-Patches-3490731 ] check_fping: IPv6 support Message-ID: Patches item #3490731, was opened at 2012-02-21 23:56 Message generated for change (Tracker Item Submitted) made by You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=397599&aid=3490731&group_id=29880 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Enhancement Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: http://vmattila.myopenid.com/ () Assigned to: Nobody/Anonymous (nobody) Summary: check_fping: IPv6 support Initial Comment: Add IPv6 support to check_fping This patch adds command line options -4 and -6 (--use-ipv4 and --use-ipv6) to check_fping. IPv4 is used by default, maintaining backwards compatibilty with older check_fping versions. IPv6 support requires the fping6 program. The implementation is really an imitation of check_ping IPv6 support: Plugin command line option -4/-6 designates whether to run fping/fping6. Please note that especially the changes to configure.in might be all wrong - I don't know what's the proper autoconf way, patching configure.in just seemed to work for me. Patch against Plugin Version (-V output): Git master on 2012-02-21 Plugin Name: check_fping Example Plugin Commandline: check_fping -6 -H ping.funet.fi Tested on operating system: Ubuntu 11.10 Oneiric Tested on architecture: x86_64 Tested with compiler: gcc version 4.6.1 (Ubuntu/Linaro 4.6.1-9ubuntu3) ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=397599&aid=3490731&group_id=29880 From frnkblk at iname.com Fri Feb 24 05:28:19 2012 From: frnkblk at iname.com (Frank Bulk) Date: Thu, 23 Feb 2012 22:28:19 -0600 Subject: [Nagiosplug-devel] check_http fails to redirect to secure sites Message-ID: <050101ccf2ac$bca74fc0$35f5ef40$@iname.com> Starting this morning two of the sites I monitor failed, www.sprint.net and www.sprintv6.net. After some testing it?s become clear to me that check_http doesn?t currently redirect to secure sites, even with the use of the '-f follow' command. I guess Sprint turned on redirection to the secure version this morning. Not sure whether to call this a bug or working-as-designed, but I?m request the follow feature be enhanced to allow redirection to the secure version of host. I'm running check_http version 1.4.15. Here's a copy of my tests: ============================================================================ == nagios:/etc/nagios3# nagios:/etc/nagios3# /usr/lib/nagios/plugins/check_http -H www.sprint.net -4 CRITICAL - Socket timeout after 10 seconds nagios:/etc/nagios3# nagios:/etc/nagios3# wget -4 www.sprint.net --2012-02-23 17:52:06-- http://www.sprint.net/ Resolving www.sprint.net... 208.24.22.50 Connecting to www.sprint.net|208.24.22.50|:80... connected. HTTP request sent, awaiting response... 302 Moved Temporarily Location: https://www.sprint.net/ [following] --2012-02-23 17:52:06-- https://www.sprint.net/ Connecting to www.sprint.net|208.24.22.50|:443... connected. HTTP request sent, awaiting response... 200 OK Length: unspecified [text/html] Saving to: ?index.html.4? [ <=> ] 16,997 --.-K/s in 0.05s 2012-02-23 17:52:06 (348 KB/s) - ?index.html.4? nagios:/etc/nagios3# ============================================================================ == nagios:/etc/nagios3# /usr/lib/nagios/plugins/check_http -H www.sprint.net -6 CRITICAL - Socket timeout after 10 seconds nagios:/etc/nagios3# nagios:/etc/nagios3# wget -6 www.sprint.net --2012-02-23 17:54:49-- http://www.sprint.net/ Resolving www.sprint.net... 2600:: Connecting to www.sprint.net|2600::|:80... connected. HTTP request sent, awaiting response... 302 Moved Temporarily Location: https://www.sprint.net/ [following] --2012-02-23 17:54:49-- https://www.sprint.net/ Connecting to www.sprint.net|2600::|:443... connected. HTTP request sent, awaiting response... 200 OK Length: unspecified [text/html] Saving to: ?index.html.5? [ <=> ] 17,739 --.-K/s in 0s 2012-02-23 17:54:49 (174 MB/s) - ?index.html.5? nagios:/etc/nagios3# ============================================================================ == -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 6517 bytes Desc: not available URL: From wkhunzai at yahoo.com Fri Feb 24 05:53:22 2012 From: wkhunzai at yahoo.com (wali hunzai) Date: Thu, 23 Feb 2012 20:53:22 -0800 (PST) Subject: [Nagiosplug-devel] email alert notification Message-ID: <1330059202.20008.YahooMailClassic@web125503.mail.ne1.yahoo.com> hi,? I am getting hundreds of emails on daily basis and it is a hacktik for me to view and delete them on daily basis. therefore, I want to limit the email alerts in such a way that It could send alerts only about the entries that are available in the switch.cfg or entries of printer.cfg or windows.cfg. I want specific email alerts from?specific systesms/switches/printer. ? any help please ? regards ? wkhan ? -------------- next part -------------- An HTML attachment was scrubbed... URL: From waja at cyconet.org Wed Feb 29 19:12:29 2012 From: waja at cyconet.org (Jan Wagner) Date: Wed, 29 Feb 2012 19:12:29 +0100 Subject: [Nagiosplug-devel] email alert notification In-Reply-To: <1330059202.20008.YahooMailClassic@web125503.mail.ne1.yahoo.com> References: <1330059202.20008.YahooMailClassic@web125503.mail.ne1.yahoo.com> Message-ID: <201202291912.33597.waja@cyconet.org> Hi Wali, On Friday, 24. February 2012, wali hunzai wrote: > to view and delete them on daily basis. therefore, I want to limit the > email alerts in such a way that It could send alerts only about the > entries that are available in the switch.cfg or entries of printer.cfg or > windows.cfg. I want specific email alerts from specific > systesms/switches/printer. this is related to your monitoring system (nagios/icinga/whatever) and not plugin specific. Cheers, Jan. -- Never write mail to , you have been warned! -----BEGIN GEEK CODE BLOCK----- Version: 3.12 GIT d-- s+: a C+++ UL++++ P+ L+++ E--- W+++ N+++ o++ K++ w--- O M V- PS PE Y++ PGP++ t-- 5 X R tv- b+ DI D+ G++ e++ h---- r+++ y++++ ------END GEEK CODE BLOCK------ -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 190 bytes Desc: This is a digitally signed message part. URL: