From noreply at sourceforge.net Mon Sep 1 09:02:20 2008 From: noreply at sourceforge.net (SourceForge.net) Date: Mon, 01 Sep 2008 07:02:20 +0000 Subject: [Nagiosplug-devel] [ nagiosplug-Bugs-2081810 ] check_rpc return code on false libpath Message-ID: Bugs item #2081810, was opened at 2008-08-29 05:45 Message generated for change (Comment added) made by neuntoeter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=397597&aid=2081810&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: Wont Fix Priority: 5 Private: No Submitted By: Volker (neuntoeter) Assigned to: Nobody/Anonymous (nobody) Summary: check_rpc return code on false libpath Initial Comment: Hi, I noticed a problem with check_rpc. If check_rpc can't find the utils.pm package in the given libpath (e.g. the utils.pm is not in lib "/usr/local/nagios/libexec";) and check_rpc is executed in nagios, the return code in Nagios is 2 -> Critical and the Plugin Output shown in Nagios only shows (null). The correct behaviour should be: Status: Unknown (3) Output: Can't find utils.pm in lib path. I spent nearly a whole day finding the reason why check_rpc did not work. It took so long to find out, because I didn't get any error when executing it manually in the shell (the utils.pm was in the working directory). A perl error message an a status Unknown could have saved me a lot of time. PS: I used version from 1.4.9 regards, Volker ---------------------------------------------------------------------- >Comment By: Volker (neuntoeter) Date: 2008-09-01 07:02 Message: Logged In: YES user_id=1055795 Originator: YES Yes, I executed the plugin by hands. Unfortunately I executed it in the /usr/local/nagios/plugins directory where also the utils.pm exists. So I didn't get any error and the plugin works fine. The working directory is different when the plugin is executed by nagios and the utils.pm isn't found then, because the lib path in the script is /usr/local/nagios/libexec. Is there a way to change the behaviour of the script to send the plugins STDERR to STDOUT, so that at least some error messages shows up in Nagios? ---------------------------------------------------------------------- Comment By: Thomas Guyot (dermoth) Date: 2008-08-29 16:25 Message: Logged In: YES user_id=375623 Originator: NO Did you try running the plugin by hands? It should print a clear error about missing utils.pm. This is Perl's error code and message, not the plugin's. IMO it make absolutely no sense to add an eval in there to catch this error, especially since it shouldn't happen under normal circumstances and the error message is clear from the command line. It's also the job of utils.pm to define Nagios error codes, so handling that would also require duplicate "fallback" definitions. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=397597&aid=2081810&group_id=29880 From noreply at sourceforge.net Mon Sep 1 09:21:45 2008 From: noreply at sourceforge.net (SourceForge.net) Date: Mon, 01 Sep 2008 07:21:45 +0000 Subject: [Nagiosplug-devel] [ nagiosplug-Bugs-2082501 ] check_http redirects sporadically endless in version 1.4.12 Message-ID: Bugs item #2082501, was opened at 2008-08-29 16:10 Message generated for change (Comment added) made by ewasser You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=397597&aid=2082501&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 (specify) Status: Open Resolution: None Priority: 5 Private: No Submitted By: Erik Wasser (ewasser) Assigned to: Nobody/Anonymous (nobody) Summary: check_http redirects sporadically endless in version 1.4.12 Initial Comment: The check_http plugin in version 1.4.12 is brocken. Version 1.4.11 works fine. The plugin messes up the redirection url. The redirection doesn't end and it will result in a "WARNING". Here's the sample output, the binarys were taken from DAG http://apt.sw.be/redhat/el5/en/i386/RPMS.dag/ but I also recompiled the version 1.4.12 from the official sources. Plugin Version (-V output): check_http v1991 (nagios-plugins 1.4.12) Plugin Name: check_http Plugin Commandline showing issues: see down below Operating System: Linux Architecture: i386, x86_64 Compiler: gcc WORKING VERSION 1.4.11: % ./check_http-1.4.11-1 --onredirect=follow -H www.taxi-blog.de -u /wordpress/ -s Impressum -t 30 HTTP OK HTTP/1.1 200 OK - 0.552 second response time |time=0.551658s;;;0.000000 size=61131B;;;0 This is working everytime. DEFECT VERSION 1.4.12: The error itself is not consistent: B-( % ./plugins/check_http --onredirect=follow -H www.taxi-blog.de -u /wordpress/ -s Impressum -t 30 HTTP OK HTTP/1.1 200 OK - 1.525 second response time |time=1.525200s;;;0.000000 size=61216B;;;0 % ./plugins/check_http --onredirect=follow -H www.taxi-blog.de -u /wordpress/ -s Impressum -t 30 HTTP WARNING - maximum redirection depth 15 exceeded - http://www.taxi-blog.de:80wordpress/ % ./plugins/check_http --onredirect=follow -H www.taxi-blog.de -u /wordpress/ -s Impressum -t 30 HTTP OK HTTP/1.1 200 OK - 0.173 second response time |time=0.172721s;;;0.000000 size=61216B;;;0 % ./plugins/check_http --onredirect=follow -H www.taxi-blog.de -u /wordpress/ -s Impressum -t 30 HTTP OK HTTP/1.1 200 OK - 2.788 second response time |time=2.788378s;;;0.000000 size=61217B;;;0 % ./plugins/check_http --onredirect=follow -H www.taxi-blog.de -u /wordpress/ -s Impressum -t 30 HTTP OK HTTP/1.1 200 OK - 0.169 second response time |time=0.168843s;;;0.000000 size=61216B;;;0 % ./plugins/check_http --onredirect=follow -H www.taxi-blog.de -u /wordpress/ -s Impressum -t 30 HTTP WARNING - maximum redirection depth 15 exceeded - http://www.taxi-blog.de:80wordpress/ % ./plugins/check_http --onredirect=follow -H www.taxi-blog.de -u /wordpress/ -s Impressum -t 30 HTTP WARNING - maximum redirection depth 15 exceeded - http://www.taxi-blog.de:80wordpress/ As you can see the error messages shows a messed up error message (a missing '/'). I think it depends on the header structure/size/order of the HTTP response message. Others URLs are failing too with the version 1.4.12 so I think it's not an apache problem on the other side. Greetings and thanks for the good work. ---------------------------------------------------------------------- >Comment By: Erik Wasser (ewasser) Date: 2008-09-01 09:21 Message: Logged In: YES user_id=80027 Originator: YES Thanks for the feedback, that's no problem at all. I've used the .tar.gz from SourceForge. % cd /tmp/nagios-plugins-1.4.12 % ./configure % make % plugins/check_http --verbose -H www.taxi-blog.de --onredirect=follow -H www.taxi-blog.de -u /wordpress/ -s Impressum -t 30 option f:4 GET /wordpress/ HTTP/1.0 User-Agent: check_http/v1991 (nagios-plugins 1.4.12) Connection: close Host: www.taxi-blog.de:80 http://www.taxi-blog.de:80/wordpress/ is 294 characters STATUS: HTTP/1.1 301 Moved Permanently **** HEADER **** Date: Mon, 01 Sep 2008 07:12:39 GMT Server: Apache X-Powered-By: PHP/5.1.6 X-Pingback: http://www.taxi-blog.de/wordpress/xmlrpc.php Location: http://www.taxi-blog.de/wordpress/ Content-Length: 0 Content-Type: text/html; charset=UTF-8 Connection: close **** CONTENT **** Redirection to http://www.taxi-blog.de:80/wordpress/ GET /wordpress/ HTTP/1.0 User-Agent: check_http/v1991 (nagios-plugins 1.4.12) Connection: close Host: www.taxi-blog.de:80 http://www.taxi-blog.de:80/wordpress/ is 294 characters STATUS: HTTP/1.1 301 Moved Permanently **** HEADER **** Date: Mon, 01 Sep 2008 07:12:39 GMT Server: Apache X-Powered-By: PHP/5.1.6 X-Pingback: http://www.taxi-blog.de/wordpress/xmlrpc.php Location: http://www.taxi-blog.de/wordpress/ Content-Length: 0 Content-Type: text/html; charset=UTF-8 Connection: close **** CONTENT **** Redirection to http://www.taxi-blog.de:80/wordpress/ GET /wordpress/ HTTP/1.0 User-Agent: check_http/v1991 (nagios-plugins 1.4.12) Connection: close Host: www.taxi-blog.de:80 [...snipped the repeating output...] http://www.taxi-blog.de:80/wordpress/ is 294 characters STATUS: HTTP/1.1 301 Moved Permanently **** HEADER **** Date: Mon, 01 Sep 2008 07:12:42 GMT Server: Apache X-Powered-By: PHP/5.1.6 X-Pingback: http://www.taxi-blog.de/wordpress/xmlrpc.php Location: http://www.taxi-blog.de/wordpress/ Content-Length: 0 Content-Type: text/html; charset=UTF-8 Connection: close **** CONTENT **** HTTP WARNING - maximum redirection depth 15 exceeded - http://www.taxi-blog.de:80wordpress/ % I hope that will help. ---------------------------------------------------------------------- Comment By: Holger Weiss (hweiss) Date: 2008-08-29 17:43 Message: Logged In: YES user_id=759506 Originator: NO There's no obvious change in the code between 1.4.11 and 1.4.12 which could cause this, and so far, I can't reproduce the problem: % check_http --onredirect=critical -H www.taxi-blog.de -u /wordpress/ -s Impressum -t 30 HTTP OK HTTP/1.1 200 OK - 0.591 second response time |time=0.590834s;;;0.000000 size=61229B;;;0 That is, the server doesn't actually redirect this URL. Using "-u /wordpress" without a trailing slash redirects to /wordpress/, though. I tried the following call 100 times in a loop and always got an OK: % check_http -H www.taxi-blog.de --onredirect=follow -H www.taxi-blog.de -u /wordpress/ -s Impressum -t 30 HTTP OK HTTP/1.1 200 OK - 0.761 second response time |time=0.760912s;;;0.000000 size=61229B;;;0 So, could you please try to reproduce the problem using "--verbose" and post the output (up to the **** CONTENT **** part)? (It would be nice if you could use the version compiled from the official sources for this.) Thank you! ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=397597&aid=2082501&group_id=29880 From dermoth at aei.ca Mon Sep 1 16:18:59 2008 From: dermoth at aei.ca (Thomas Guyot-Sionnest) Date: Mon, 01 Sep 2008 10:18:59 -0400 Subject: [Nagiosplug-devel] check_dns issue In-Reply-To: <001401c8fbf1$4e51e860$0a00a8c0@inishdalla> References: <001401c8fbf1$4e51e860$0a00a8c0@inishdalla> Message-ID: <48BBF9D3.1090501@aei.ca> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 11/08/08 04:31 PM, James Mernin wrote: > > 135c135 > > < if ((temp_buffer = strstr (chld_out.line[i], "name = "))) > > --- > >> if ((temp_buffer = strstr (chld_out.line[i], "name = ")) && (NULL == > strstr (chld_out.line[i], "canonical name = "))) > Seems like a problem, but to fix it I'd rather get only lines with "name = ", i.e. check from the beginning of the line instead of removing known strings. I'll have a look at it. - -- Thomas -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFIu/nT6dZ+Kt5BchYRAjp0AJ9Sc/OK6Lq7r5IrLMVJ61gtLK5Z5gCgmFZr LkLuoSREygpLDzReRK/MHXk= =R8GF -----END PGP SIGNATURE----- From dermoth at aei.ca Mon Sep 1 16:29:38 2008 From: dermoth at aei.ca (Thomas Guyot-Sionnest) Date: Mon, 01 Sep 2008 10:29:38 -0400 Subject: [Nagiosplug-devel] check_http patch In-Reply-To: <489B9CFD.2080900@aei.ca> References: <21856.128.123.16.247.1218121184.squirrel@www.jeffharris.net> <489B9CFD.2080900@aei.ca> Message-ID: <48BBFC52.5030301@aei.ca> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 07/08/08 09:10 PM, Thomas Guyot-Sionnest wrote: > On 07/08/08 10:59 AM, Michael Harris wrote: >> Hi all, >> Here's a patch I wrote for the check_http plugin. We were having >> problems getting 301s back instead of 200s from our VMware servers. This >> patch re-structures the HTTP 1.1 headers, which fixed the problem. > > Thanks for the patch; I'll commit it... I backed out your patch as someone pointed out that it removed the :port from the host header (I missed it). Can you try the attached patch instead? Thanks - -- Thomas -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFIu/xS6dZ+Kt5BchYRAvhdAJ9Ktep9Oew34u5U5suocj841MXOFQCg5PTs Zj6aw/+yddufP5R2yv8UQa4= =ZJ7r -----END PGP SIGNATURE----- -------------- next part -------------- A non-text attachment was scrubbed... Name: check_http1.1_v2.patch Type: text/x-diff Size: 925 bytes Desc: not available URL: From noreply at sourceforge.net Mon Sep 1 16:58:27 2008 From: noreply at sourceforge.net (SourceForge.net) Date: Mon, 01 Sep 2008 14:58:27 +0000 Subject: [Nagiosplug-devel] [ nagiosplug-Bugs-2082501 ] check_http redirects sporadically endless in version 1.4.12 Message-ID: Bugs item #2082501, was opened at 2008-08-29 16:10 Message generated for change (Comment added) made by hweiss You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=397597&aid=2082501&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 (specify) >Status: Pending >Resolution: Invalid Priority: 5 Private: No Submitted By: Erik Wasser (ewasser) Assigned to: Nobody/Anonymous (nobody) Summary: check_http redirects sporadically endless in version 1.4.12 Initial Comment: The check_http plugin in version 1.4.12 is brocken. Version 1.4.11 works fine. The plugin messes up the redirection url. The redirection doesn't end and it will result in a "WARNING". Here's the sample output, the binarys were taken from DAG http://apt.sw.be/redhat/el5/en/i386/RPMS.dag/ but I also recompiled the version 1.4.12 from the official sources. Plugin Version (-V output): check_http v1991 (nagios-plugins 1.4.12) Plugin Name: check_http Plugin Commandline showing issues: see down below Operating System: Linux Architecture: i386, x86_64 Compiler: gcc WORKING VERSION 1.4.11: % ./check_http-1.4.11-1 --onredirect=follow -H www.taxi-blog.de -u /wordpress/ -s Impressum -t 30 HTTP OK HTTP/1.1 200 OK - 0.552 second response time |time=0.551658s;;;0.000000 size=61131B;;;0 This is working everytime. DEFECT VERSION 1.4.12: The error itself is not consistent: B-( % ./plugins/check_http --onredirect=follow -H www.taxi-blog.de -u /wordpress/ -s Impressum -t 30 HTTP OK HTTP/1.1 200 OK - 1.525 second response time |time=1.525200s;;;0.000000 size=61216B;;;0 % ./plugins/check_http --onredirect=follow -H www.taxi-blog.de -u /wordpress/ -s Impressum -t 30 HTTP WARNING - maximum redirection depth 15 exceeded - http://www.taxi-blog.de:80wordpress/ % ./plugins/check_http --onredirect=follow -H www.taxi-blog.de -u /wordpress/ -s Impressum -t 30 HTTP OK HTTP/1.1 200 OK - 0.173 second response time |time=0.172721s;;;0.000000 size=61216B;;;0 % ./plugins/check_http --onredirect=follow -H www.taxi-blog.de -u /wordpress/ -s Impressum -t 30 HTTP OK HTTP/1.1 200 OK - 2.788 second response time |time=2.788378s;;;0.000000 size=61217B;;;0 % ./plugins/check_http --onredirect=follow -H www.taxi-blog.de -u /wordpress/ -s Impressum -t 30 HTTP OK HTTP/1.1 200 OK - 0.169 second response time |time=0.168843s;;;0.000000 size=61216B;;;0 % ./plugins/check_http --onredirect=follow -H www.taxi-blog.de -u /wordpress/ -s Impressum -t 30 HTTP WARNING - maximum redirection depth 15 exceeded - http://www.taxi-blog.de:80wordpress/ % ./plugins/check_http --onredirect=follow -H www.taxi-blog.de -u /wordpress/ -s Impressum -t 30 HTTP WARNING - maximum redirection depth 15 exceeded - http://www.taxi-blog.de:80wordpress/ As you can see the error messages shows a messed up error message (a missing '/'). I think it depends on the header structure/size/order of the HTTP response message. Others URLs are failing too with the version 1.4.12 so I think it's not an apache problem on the other side. Greetings and thanks for the good work. ---------------------------------------------------------------------- >Comment By: Holger Weiss (hweiss) Date: 2008-09-01 16:58 Message: Logged In: YES user_id=759506 Originator: NO Thank you very much. Now I can reproduce the problem: last time, I simply grabbed the wrong SVN revision of check_http.c. Sorry about that! However, as far as I can tell the only bug here is the missing '/' in the error message. The URL which the plugin uses for the request includes the '/', so the error message is misleading and has nothing to do with your problem. I now fixed the error message in SVN. Thanks for the hint! Regarding your actual problem: With HTTP/1.1, the server extracts the virtual host name to use from the "Host:" header provided by the client. check_http generates the header line "Host: www.taxi-blog.de:80". Now, the problem is that the server seems to treat this as a request for a virtual host different from the host which would be requested using "Host: www.taxi-blog.de" (without the explicit port) and that the server therefore redirects the client to "www.taxi-blog.de". Since the plugin then re-adds the port number to the "Host:" header for the new (redirected) request, there's an infinite redirection loop. The standard clearly states that "Host: foo" and "Host: foo:80" are equivalent for HTTP requests (see: http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html#sec14.23). So, IMO it's a server issue (or a configuration problem or an issue of PHP or Wordpress or whoever generates the response). So I'll set this item's status to "pending", but I'll put removing the port number from the "Host:" header if the default port is used on my TODO list (since that shouldn't hurt). As to why the server only _sometimes_ behaves like this, I have no idea. In any case, this has nothing to do with the plugin. Try netcat(1): ----------- 8< ------------------------------ 8< ----------- % printf "GET /wordpress/ HTTP/1.0\r\n" > /tmp/request % printf "Host: www.taxi-blog.de:80\r\n\r\n" >> /tmp/request % nc www.taxi-blog.de 80 < /tmp/request | head HTTP/1.1 301 Moved Permanently Date: Mon, 01 Sep 2008 13:01:27 GMT Server: Apache X-Powered-By: PHP/5.1.6 X-Pingback: http://www.taxi-blog.de/wordpress/xmlrpc.php Location: http://www.taxi-blog.de/wordpress/ Content-Type: text/html; charset=UTF-8 Content-Length: 0 Connection: close % nc www.taxi-blog.de 80 < /tmp/request | head HTTP/1.1 200 OK Date: Mon, 01 Sep 2008 13:01:25 GMT Server: Apache X-Powered-By: PHP/5.1.6 X-Pingback: http://www.taxi-blog.de/wordpress/xmlrpc.php Last-Modified: Mon, 01 Sep 2008 13:01:21 GMT Content-Type: text/html; charset=UTF-8 Connection: close ---------------------------------------------------------------------- Comment By: Erik Wasser (ewasser) Date: 2008-09-01 09:21 Message: Logged In: YES user_id=80027 Originator: YES Thanks for the feedback, that's no problem at all. I've used the .tar.gz from SourceForge. % cd /tmp/nagios-plugins-1.4.12 % ./configure % make % plugins/check_http --verbose -H www.taxi-blog.de --onredirect=follow -H www.taxi-blog.de -u /wordpress/ -s Impressum -t 30 option f:4 GET /wordpress/ HTTP/1.0 User-Agent: check_http/v1991 (nagios-plugins 1.4.12) Connection: close Host: www.taxi-blog.de:80 http://www.taxi-blog.de:80/wordpress/ is 294 characters STATUS: HTTP/1.1 301 Moved Permanently **** HEADER **** Date: Mon, 01 Sep 2008 07:12:39 GMT Server: Apache X-Powered-By: PHP/5.1.6 X-Pingback: http://www.taxi-blog.de/wordpress/xmlrpc.php Location: http://www.taxi-blog.de/wordpress/ Content-Length: 0 Content-Type: text/html; charset=UTF-8 Connection: close **** CONTENT **** Redirection to http://www.taxi-blog.de:80/wordpress/ GET /wordpress/ HTTP/1.0 User-Agent: check_http/v1991 (nagios-plugins 1.4.12) Connection: close Host: www.taxi-blog.de:80 http://www.taxi-blog.de:80/wordpress/ is 294 characters STATUS: HTTP/1.1 301 Moved Permanently **** HEADER **** Date: Mon, 01 Sep 2008 07:12:39 GMT Server: Apache X-Powered-By: PHP/5.1.6 X-Pingback: http://www.taxi-blog.de/wordpress/xmlrpc.php Location: http://www.taxi-blog.de/wordpress/ Content-Length: 0 Content-Type: text/html; charset=UTF-8 Connection: close **** CONTENT **** Redirection to http://www.taxi-blog.de:80/wordpress/ GET /wordpress/ HTTP/1.0 User-Agent: check_http/v1991 (nagios-plugins 1.4.12) Connection: close Host: www.taxi-blog.de:80 [...snipped the repeating output...] http://www.taxi-blog.de:80/wordpress/ is 294 characters STATUS: HTTP/1.1 301 Moved Permanently **** HEADER **** Date: Mon, 01 Sep 2008 07:12:42 GMT Server: Apache X-Powered-By: PHP/5.1.6 X-Pingback: http://www.taxi-blog.de/wordpress/xmlrpc.php Location: http://www.taxi-blog.de/wordpress/ Content-Length: 0 Content-Type: text/html; charset=UTF-8 Connection: close **** CONTENT **** HTTP WARNING - maximum redirection depth 15 exceeded - http://www.taxi-blog.de:80wordpress/ % I hope that will help. ---------------------------------------------------------------------- Comment By: Holger Weiss (hweiss) Date: 2008-08-29 17:43 Message: Logged In: YES user_id=759506 Originator: NO There's no obvious change in the code between 1.4.11 and 1.4.12 which could cause this, and so far, I can't reproduce the problem: % check_http --onredirect=critical -H www.taxi-blog.de -u /wordpress/ -s Impressum -t 30 HTTP OK HTTP/1.1 200 OK - 0.591 second response time |time=0.590834s;;;0.000000 size=61229B;;;0 That is, the server doesn't actually redirect this URL. Using "-u /wordpress" without a trailing slash redirects to /wordpress/, though. I tried the following call 100 times in a loop and always got an OK: % check_http -H www.taxi-blog.de --onredirect=follow -H www.taxi-blog.de -u /wordpress/ -s Impressum -t 30 HTTP OK HTTP/1.1 200 OK - 0.761 second response time |time=0.760912s;;;0.000000 size=61229B;;;0 So, could you please try to reproduce the problem using "--verbose" and post the output (up to the **** CONTENT **** part)? (It would be nice if you could use the version compiled from the official sources for this.) Thank you! ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=397597&aid=2082501&group_id=29880 From noreply at sourceforge.net Tue Sep 2 10:13:02 2008 From: noreply at sourceforge.net (SourceForge.net) Date: Tue, 02 Sep 2008 08:13:02 +0000 Subject: [Nagiosplug-devel] [ nagiosplug-Bugs-2082501 ] check_http redirects sporadically endless in version 1.4.12 Message-ID: Bugs item #2082501, was opened at 2008-08-29 16:10 Message generated for change (Comment added) made by ewasser You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=397597&aid=2082501&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 (specify) >Status: Open Resolution: Invalid Priority: 5 Private: No Submitted By: Erik Wasser (ewasser) Assigned to: Nobody/Anonymous (nobody) Summary: check_http redirects sporadically endless in version 1.4.12 Initial Comment: The check_http plugin in version 1.4.12 is brocken. Version 1.4.11 works fine. The plugin messes up the redirection url. The redirection doesn't end and it will result in a "WARNING". Here's the sample output, the binarys were taken from DAG http://apt.sw.be/redhat/el5/en/i386/RPMS.dag/ but I also recompiled the version 1.4.12 from the official sources. Plugin Version (-V output): check_http v1991 (nagios-plugins 1.4.12) Plugin Name: check_http Plugin Commandline showing issues: see down below Operating System: Linux Architecture: i386, x86_64 Compiler: gcc WORKING VERSION 1.4.11: % ./check_http-1.4.11-1 --onredirect=follow -H www.taxi-blog.de -u /wordpress/ -s Impressum -t 30 HTTP OK HTTP/1.1 200 OK - 0.552 second response time |time=0.551658s;;;0.000000 size=61131B;;;0 This is working everytime. DEFECT VERSION 1.4.12: The error itself is not consistent: B-( % ./plugins/check_http --onredirect=follow -H www.taxi-blog.de -u /wordpress/ -s Impressum -t 30 HTTP OK HTTP/1.1 200 OK - 1.525 second response time |time=1.525200s;;;0.000000 size=61216B;;;0 % ./plugins/check_http --onredirect=follow -H www.taxi-blog.de -u /wordpress/ -s Impressum -t 30 HTTP WARNING - maximum redirection depth 15 exceeded - http://www.taxi-blog.de:80wordpress/ % ./plugins/check_http --onredirect=follow -H www.taxi-blog.de -u /wordpress/ -s Impressum -t 30 HTTP OK HTTP/1.1 200 OK - 0.173 second response time |time=0.172721s;;;0.000000 size=61216B;;;0 % ./plugins/check_http --onredirect=follow -H www.taxi-blog.de -u /wordpress/ -s Impressum -t 30 HTTP OK HTTP/1.1 200 OK - 2.788 second response time |time=2.788378s;;;0.000000 size=61217B;;;0 % ./plugins/check_http --onredirect=follow -H www.taxi-blog.de -u /wordpress/ -s Impressum -t 30 HTTP OK HTTP/1.1 200 OK - 0.169 second response time |time=0.168843s;;;0.000000 size=61216B;;;0 % ./plugins/check_http --onredirect=follow -H www.taxi-blog.de -u /wordpress/ -s Impressum -t 30 HTTP WARNING - maximum redirection depth 15 exceeded - http://www.taxi-blog.de:80wordpress/ % ./plugins/check_http --onredirect=follow -H www.taxi-blog.de -u /wordpress/ -s Impressum -t 30 HTTP WARNING - maximum redirection depth 15 exceeded - http://www.taxi-blog.de:80wordpress/ As you can see the error messages shows a messed up error message (a missing '/'). I think it depends on the header structure/size/order of the HTTP response message. Others URLs are failing too with the version 1.4.12 so I think it's not an apache problem on the other side. Greetings and thanks for the good work. ---------------------------------------------------------------------- >Comment By: Erik Wasser (ewasser) Date: 2008-09-02 10:13 Message: Logged In: YES user_id=80027 Originator: YES Thanks for verbose answer. I think you are right it's a wordpress issue but I found a least one other (customer) application that has the same problem. And I think there were will be more. B-((( The symptoms are always the same. You speak to the applikation with www.foo.invalid:80 and it returns a redirect to www.foo.invalid (without the port number). check_http add the :80 again and the game begins again. That makes the plugin pretty incompatible with "my" world. Currently we can't upgrade to 1.4.12 because of this issue so I would like do to the patch for myself because we need this feature. Would that be okay for you? ---------------------------------------------------------------------- Comment By: Holger Weiss (hweiss) Date: 2008-09-01 16:58 Message: Logged In: YES user_id=759506 Originator: NO Thank you very much. Now I can reproduce the problem: last time, I simply grabbed the wrong SVN revision of check_http.c. Sorry about that! However, as far as I can tell the only bug here is the missing '/' in the error message. The URL which the plugin uses for the request includes the '/', so the error message is misleading and has nothing to do with your problem. I now fixed the error message in SVN. Thanks for the hint! Regarding your actual problem: With HTTP/1.1, the server extracts the virtual host name to use from the "Host:" header provided by the client. check_http generates the header line "Host: www.taxi-blog.de:80". Now, the problem is that the server seems to treat this as a request for a virtual host different from the host which would be requested using "Host: www.taxi-blog.de" (without the explicit port) and that the server therefore redirects the client to "www.taxi-blog.de". Since the plugin then re-adds the port number to the "Host:" header for the new (redirected) request, there's an infinite redirection loop. The standard clearly states that "Host: foo" and "Host: foo:80" are equivalent for HTTP requests (see: http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html#sec14.23). So, IMO it's a server issue (or a configuration problem or an issue of PHP or Wordpress or whoever generates the response). So I'll set this item's status to "pending", but I'll put removing the port number from the "Host:" header if the default port is used on my TODO list (since that shouldn't hurt). As to why the server only _sometimes_ behaves like this, I have no idea. In any case, this has nothing to do with the plugin. Try netcat(1): ----------- 8< ------------------------------ 8< ----------- % printf "GET /wordpress/ HTTP/1.0\r\n" > /tmp/request % printf "Host: www.taxi-blog.de:80\r\n\r\n" >> /tmp/request % nc www.taxi-blog.de 80 < /tmp/request | head HTTP/1.1 301 Moved Permanently Date: Mon, 01 Sep 2008 13:01:27 GMT Server: Apache X-Powered-By: PHP/5.1.6 X-Pingback: http://www.taxi-blog.de/wordpress/xmlrpc.php Location: http://www.taxi-blog.de/wordpress/ Content-Type: text/html; charset=UTF-8 Content-Length: 0 Connection: close % nc www.taxi-blog.de 80 < /tmp/request | head HTTP/1.1 200 OK Date: Mon, 01 Sep 2008 13:01:25 GMT Server: Apache X-Powered-By: PHP/5.1.6 X-Pingback: http://www.taxi-blog.de/wordpress/xmlrpc.php Last-Modified: Mon, 01 Sep 2008 13:01:21 GMT Content-Type: text/html; charset=UTF-8 Connection: close ---------------------------------------------------------------------- Comment By: Erik Wasser (ewasser) Date: 2008-09-01 09:21 Message: Logged In: YES user_id=80027 Originator: YES Thanks for the feedback, that's no problem at all. I've used the .tar.gz from SourceForge. % cd /tmp/nagios-plugins-1.4.12 % ./configure % make % plugins/check_http --verbose -H www.taxi-blog.de --onredirect=follow -H www.taxi-blog.de -u /wordpress/ -s Impressum -t 30 option f:4 GET /wordpress/ HTTP/1.0 User-Agent: check_http/v1991 (nagios-plugins 1.4.12) Connection: close Host: www.taxi-blog.de:80 http://www.taxi-blog.de:80/wordpress/ is 294 characters STATUS: HTTP/1.1 301 Moved Permanently **** HEADER **** Date: Mon, 01 Sep 2008 07:12:39 GMT Server: Apache X-Powered-By: PHP/5.1.6 X-Pingback: http://www.taxi-blog.de/wordpress/xmlrpc.php Location: http://www.taxi-blog.de/wordpress/ Content-Length: 0 Content-Type: text/html; charset=UTF-8 Connection: close **** CONTENT **** Redirection to http://www.taxi-blog.de:80/wordpress/ GET /wordpress/ HTTP/1.0 User-Agent: check_http/v1991 (nagios-plugins 1.4.12) Connection: close Host: www.taxi-blog.de:80 http://www.taxi-blog.de:80/wordpress/ is 294 characters STATUS: HTTP/1.1 301 Moved Permanently **** HEADER **** Date: Mon, 01 Sep 2008 07:12:39 GMT Server: Apache X-Powered-By: PHP/5.1.6 X-Pingback: http://www.taxi-blog.de/wordpress/xmlrpc.php Location: http://www.taxi-blog.de/wordpress/ Content-Length: 0 Content-Type: text/html; charset=UTF-8 Connection: close **** CONTENT **** Redirection to http://www.taxi-blog.de:80/wordpress/ GET /wordpress/ HTTP/1.0 User-Agent: check_http/v1991 (nagios-plugins 1.4.12) Connection: close Host: www.taxi-blog.de:80 [...snipped the repeating output...] http://www.taxi-blog.de:80/wordpress/ is 294 characters STATUS: HTTP/1.1 301 Moved Permanently **** HEADER **** Date: Mon, 01 Sep 2008 07:12:42 GMT Server: Apache X-Powered-By: PHP/5.1.6 X-Pingback: http://www.taxi-blog.de/wordpress/xmlrpc.php Location: http://www.taxi-blog.de/wordpress/ Content-Length: 0 Content-Type: text/html; charset=UTF-8 Connection: close **** CONTENT **** HTTP WARNING - maximum redirection depth 15 exceeded - http://www.taxi-blog.de:80wordpress/ % I hope that will help. ---------------------------------------------------------------------- Comment By: Holger Weiss (hweiss) Date: 2008-08-29 17:43 Message: Logged In: YES user_id=759506 Originator: NO There's no obvious change in the code between 1.4.11 and 1.4.12 which could cause this, and so far, I can't reproduce the problem: % check_http --onredirect=critical -H www.taxi-blog.de -u /wordpress/ -s Impressum -t 30 HTTP OK HTTP/1.1 200 OK - 0.591 second response time |time=0.590834s;;;0.000000 size=61229B;;;0 That is, the server doesn't actually redirect this URL. Using "-u /wordpress" without a trailing slash redirects to /wordpress/, though. I tried the following call 100 times in a loop and always got an OK: % check_http -H www.taxi-blog.de --onredirect=follow -H www.taxi-blog.de -u /wordpress/ -s Impressum -t 30 HTTP OK HTTP/1.1 200 OK - 0.761 second response time |time=0.760912s;;;0.000000 size=61229B;;;0 So, could you please try to reproduce the problem using "--verbose" and post the output (up to the **** CONTENT **** part)? (It would be nice if you could use the version compiled from the official sources for this.) Thank you! ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=397597&aid=2082501&group_id=29880 From noreply at sourceforge.net Tue Sep 2 10:28:11 2008 From: noreply at sourceforge.net (SourceForge.net) Date: Tue, 02 Sep 2008 08:28:11 +0000 Subject: [Nagiosplug-devel] [ nagiosplug-Bugs-2082501 ] check_http redirects sporadically endless in version 1.4.12 Message-ID: Bugs item #2082501, was opened at 2008-08-29 16:10 Message generated for change (Comment added) made by hweiss You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=397597&aid=2082501&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 (specify) Status: Open Resolution: Invalid Priority: 5 Private: No Submitted By: Erik Wasser (ewasser) Assigned to: Nobody/Anonymous (nobody) Summary: check_http redirects sporadically endless in version 1.4.12 Initial Comment: The check_http plugin in version 1.4.12 is brocken. Version 1.4.11 works fine. The plugin messes up the redirection url. The redirection doesn't end and it will result in a "WARNING". Here's the sample output, the binarys were taken from DAG http://apt.sw.be/redhat/el5/en/i386/RPMS.dag/ but I also recompiled the version 1.4.12 from the official sources. Plugin Version (-V output): check_http v1991 (nagios-plugins 1.4.12) Plugin Name: check_http Plugin Commandline showing issues: see down below Operating System: Linux Architecture: i386, x86_64 Compiler: gcc WORKING VERSION 1.4.11: % ./check_http-1.4.11-1 --onredirect=follow -H www.taxi-blog.de -u /wordpress/ -s Impressum -t 30 HTTP OK HTTP/1.1 200 OK - 0.552 second response time |time=0.551658s;;;0.000000 size=61131B;;;0 This is working everytime. DEFECT VERSION 1.4.12: The error itself is not consistent: B-( % ./plugins/check_http --onredirect=follow -H www.taxi-blog.de -u /wordpress/ -s Impressum -t 30 HTTP OK HTTP/1.1 200 OK - 1.525 second response time |time=1.525200s;;;0.000000 size=61216B;;;0 % ./plugins/check_http --onredirect=follow -H www.taxi-blog.de -u /wordpress/ -s Impressum -t 30 HTTP WARNING - maximum redirection depth 15 exceeded - http://www.taxi-blog.de:80wordpress/ % ./plugins/check_http --onredirect=follow -H www.taxi-blog.de -u /wordpress/ -s Impressum -t 30 HTTP OK HTTP/1.1 200 OK - 0.173 second response time |time=0.172721s;;;0.000000 size=61216B;;;0 % ./plugins/check_http --onredirect=follow -H www.taxi-blog.de -u /wordpress/ -s Impressum -t 30 HTTP OK HTTP/1.1 200 OK - 2.788 second response time |time=2.788378s;;;0.000000 size=61217B;;;0 % ./plugins/check_http --onredirect=follow -H www.taxi-blog.de -u /wordpress/ -s Impressum -t 30 HTTP OK HTTP/1.1 200 OK - 0.169 second response time |time=0.168843s;;;0.000000 size=61216B;;;0 % ./plugins/check_http --onredirect=follow -H www.taxi-blog.de -u /wordpress/ -s Impressum -t 30 HTTP WARNING - maximum redirection depth 15 exceeded - http://www.taxi-blog.de:80wordpress/ % ./plugins/check_http --onredirect=follow -H www.taxi-blog.de -u /wordpress/ -s Impressum -t 30 HTTP WARNING - maximum redirection depth 15 exceeded - http://www.taxi-blog.de:80wordpress/ As you can see the error messages shows a messed up error message (a missing '/'). I think it depends on the header structure/size/order of the HTTP response message. Others URLs are failing too with the version 1.4.12 so I think it's not an apache problem on the other side. Greetings and thanks for the good work. ---------------------------------------------------------------------- >Comment By: Holger Weiss (hweiss) Date: 2008-09-02 10:28 Message: Logged In: YES user_id=759506 Originator: NO Sure! Just attach your patch to this tracker item and I'll look into it. Should be mostly trivial, just keep the different default ports for HTTP and HTTPS in mind. Thank you! ---------------------------------------------------------------------- Comment By: Erik Wasser (ewasser) Date: 2008-09-02 10:13 Message: Logged In: YES user_id=80027 Originator: YES Thanks for verbose answer. I think you are right it's a wordpress issue but I found a least one other (customer) application that has the same problem. And I think there were will be more. B-((( The symptoms are always the same. You speak to the applikation with www.foo.invalid:80 and it returns a redirect to www.foo.invalid (without the port number). check_http add the :80 again and the game begins again. That makes the plugin pretty incompatible with "my" world. Currently we can't upgrade to 1.4.12 because of this issue so I would like do to the patch for myself because we need this feature. Would that be okay for you? ---------------------------------------------------------------------- Comment By: Holger Weiss (hweiss) Date: 2008-09-01 16:58 Message: Logged In: YES user_id=759506 Originator: NO Thank you very much. Now I can reproduce the problem: last time, I simply grabbed the wrong SVN revision of check_http.c. Sorry about that! However, as far as I can tell the only bug here is the missing '/' in the error message. The URL which the plugin uses for the request includes the '/', so the error message is misleading and has nothing to do with your problem. I now fixed the error message in SVN. Thanks for the hint! Regarding your actual problem: With HTTP/1.1, the server extracts the virtual host name to use from the "Host:" header provided by the client. check_http generates the header line "Host: www.taxi-blog.de:80". Now, the problem is that the server seems to treat this as a request for a virtual host different from the host which would be requested using "Host: www.taxi-blog.de" (without the explicit port) and that the server therefore redirects the client to "www.taxi-blog.de". Since the plugin then re-adds the port number to the "Host:" header for the new (redirected) request, there's an infinite redirection loop. The standard clearly states that "Host: foo" and "Host: foo:80" are equivalent for HTTP requests (see: http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html#sec14.23). So, IMO it's a server issue (or a configuration problem or an issue of PHP or Wordpress or whoever generates the response). So I'll set this item's status to "pending", but I'll put removing the port number from the "Host:" header if the default port is used on my TODO list (since that shouldn't hurt). As to why the server only _sometimes_ behaves like this, I have no idea. In any case, this has nothing to do with the plugin. Try netcat(1): ----------- 8< ------------------------------ 8< ----------- % printf "GET /wordpress/ HTTP/1.0\r\n" > /tmp/request % printf "Host: www.taxi-blog.de:80\r\n\r\n" >> /tmp/request % nc www.taxi-blog.de 80 < /tmp/request | head HTTP/1.1 301 Moved Permanently Date: Mon, 01 Sep 2008 13:01:27 GMT Server: Apache X-Powered-By: PHP/5.1.6 X-Pingback: http://www.taxi-blog.de/wordpress/xmlrpc.php Location: http://www.taxi-blog.de/wordpress/ Content-Type: text/html; charset=UTF-8 Content-Length: 0 Connection: close % nc www.taxi-blog.de 80 < /tmp/request | head HTTP/1.1 200 OK Date: Mon, 01 Sep 2008 13:01:25 GMT Server: Apache X-Powered-By: PHP/5.1.6 X-Pingback: http://www.taxi-blog.de/wordpress/xmlrpc.php Last-Modified: Mon, 01 Sep 2008 13:01:21 GMT Content-Type: text/html; charset=UTF-8 Connection: close ---------------------------------------------------------------------- Comment By: Erik Wasser (ewasser) Date: 2008-09-01 09:21 Message: Logged In: YES user_id=80027 Originator: YES Thanks for the feedback, that's no problem at all. I've used the .tar.gz from SourceForge. % cd /tmp/nagios-plugins-1.4.12 % ./configure % make % plugins/check_http --verbose -H www.taxi-blog.de --onredirect=follow -H www.taxi-blog.de -u /wordpress/ -s Impressum -t 30 option f:4 GET /wordpress/ HTTP/1.0 User-Agent: check_http/v1991 (nagios-plugins 1.4.12) Connection: close Host: www.taxi-blog.de:80 http://www.taxi-blog.de:80/wordpress/ is 294 characters STATUS: HTTP/1.1 301 Moved Permanently **** HEADER **** Date: Mon, 01 Sep 2008 07:12:39 GMT Server: Apache X-Powered-By: PHP/5.1.6 X-Pingback: http://www.taxi-blog.de/wordpress/xmlrpc.php Location: http://www.taxi-blog.de/wordpress/ Content-Length: 0 Content-Type: text/html; charset=UTF-8 Connection: close **** CONTENT **** Redirection to http://www.taxi-blog.de:80/wordpress/ GET /wordpress/ HTTP/1.0 User-Agent: check_http/v1991 (nagios-plugins 1.4.12) Connection: close Host: www.taxi-blog.de:80 http://www.taxi-blog.de:80/wordpress/ is 294 characters STATUS: HTTP/1.1 301 Moved Permanently **** HEADER **** Date: Mon, 01 Sep 2008 07:12:39 GMT Server: Apache X-Powered-By: PHP/5.1.6 X-Pingback: http://www.taxi-blog.de/wordpress/xmlrpc.php Location: http://www.taxi-blog.de/wordpress/ Content-Length: 0 Content-Type: text/html; charset=UTF-8 Connection: close **** CONTENT **** Redirection to http://www.taxi-blog.de:80/wordpress/ GET /wordpress/ HTTP/1.0 User-Agent: check_http/v1991 (nagios-plugins 1.4.12) Connection: close Host: www.taxi-blog.de:80 [...snipped the repeating output...] http://www.taxi-blog.de:80/wordpress/ is 294 characters STATUS: HTTP/1.1 301 Moved Permanently **** HEADER **** Date: Mon, 01 Sep 2008 07:12:42 GMT Server: Apache X-Powered-By: PHP/5.1.6 X-Pingback: http://www.taxi-blog.de/wordpress/xmlrpc.php Location: http://www.taxi-blog.de/wordpress/ Content-Length: 0 Content-Type: text/html; charset=UTF-8 Connection: close **** CONTENT **** HTTP WARNING - maximum redirection depth 15 exceeded - http://www.taxi-blog.de:80wordpress/ % I hope that will help. ---------------------------------------------------------------------- Comment By: Holger Weiss (hweiss) Date: 2008-08-29 17:43 Message: Logged In: YES user_id=759506 Originator: NO There's no obvious change in the code between 1.4.11 and 1.4.12 which could cause this, and so far, I can't reproduce the problem: % check_http --onredirect=critical -H www.taxi-blog.de -u /wordpress/ -s Impressum -t 30 HTTP OK HTTP/1.1 200 OK - 0.591 second response time |time=0.590834s;;;0.000000 size=61229B;;;0 That is, the server doesn't actually redirect this URL. Using "-u /wordpress" without a trailing slash redirects to /wordpress/, though. I tried the following call 100 times in a loop and always got an OK: % check_http -H www.taxi-blog.de --onredirect=follow -H www.taxi-blog.de -u /wordpress/ -s Impressum -t 30 HTTP OK HTTP/1.1 200 OK - 0.761 second response time |time=0.760912s;;;0.000000 size=61229B;;;0 So, could you please try to reproduce the problem using "--verbose" and post the output (up to the **** CONTENT **** part)? (It would be nice if you could use the version compiled from the official sources for this.) Thank you! ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=397597&aid=2082501&group_id=29880 From noreply at sourceforge.net Tue Sep 2 10:37:42 2008 From: noreply at sourceforge.net (SourceForge.net) Date: Tue, 02 Sep 2008 08:37:42 +0000 Subject: [Nagiosplug-devel] [ nagiosplug-Bugs-2082501 ] check_http redirects sporadically endless in version 1.4.12 Message-ID: Bugs item #2082501, was opened at 2008-08-29 16:10 Message generated for change (Comment added) made by ewasser You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=397597&aid=2082501&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 (specify) Status: Open Resolution: Invalid Priority: 5 Private: No Submitted By: Erik Wasser (ewasser) Assigned to: Nobody/Anonymous (nobody) Summary: check_http redirects sporadically endless in version 1.4.12 Initial Comment: The check_http plugin in version 1.4.12 is brocken. Version 1.4.11 works fine. The plugin messes up the redirection url. The redirection doesn't end and it will result in a "WARNING". Here's the sample output, the binarys were taken from DAG http://apt.sw.be/redhat/el5/en/i386/RPMS.dag/ but I also recompiled the version 1.4.12 from the official sources. Plugin Version (-V output): check_http v1991 (nagios-plugins 1.4.12) Plugin Name: check_http Plugin Commandline showing issues: see down below Operating System: Linux Architecture: i386, x86_64 Compiler: gcc WORKING VERSION 1.4.11: % ./check_http-1.4.11-1 --onredirect=follow -H www.taxi-blog.de -u /wordpress/ -s Impressum -t 30 HTTP OK HTTP/1.1 200 OK - 0.552 second response time |time=0.551658s;;;0.000000 size=61131B;;;0 This is working everytime. DEFECT VERSION 1.4.12: The error itself is not consistent: B-( % ./plugins/check_http --onredirect=follow -H www.taxi-blog.de -u /wordpress/ -s Impressum -t 30 HTTP OK HTTP/1.1 200 OK - 1.525 second response time |time=1.525200s;;;0.000000 size=61216B;;;0 % ./plugins/check_http --onredirect=follow -H www.taxi-blog.de -u /wordpress/ -s Impressum -t 30 HTTP WARNING - maximum redirection depth 15 exceeded - http://www.taxi-blog.de:80wordpress/ % ./plugins/check_http --onredirect=follow -H www.taxi-blog.de -u /wordpress/ -s Impressum -t 30 HTTP OK HTTP/1.1 200 OK - 0.173 second response time |time=0.172721s;;;0.000000 size=61216B;;;0 % ./plugins/check_http --onredirect=follow -H www.taxi-blog.de -u /wordpress/ -s Impressum -t 30 HTTP OK HTTP/1.1 200 OK - 2.788 second response time |time=2.788378s;;;0.000000 size=61217B;;;0 % ./plugins/check_http --onredirect=follow -H www.taxi-blog.de -u /wordpress/ -s Impressum -t 30 HTTP OK HTTP/1.1 200 OK - 0.169 second response time |time=0.168843s;;;0.000000 size=61216B;;;0 % ./plugins/check_http --onredirect=follow -H www.taxi-blog.de -u /wordpress/ -s Impressum -t 30 HTTP WARNING - maximum redirection depth 15 exceeded - http://www.taxi-blog.de:80wordpress/ % ./plugins/check_http --onredirect=follow -H www.taxi-blog.de -u /wordpress/ -s Impressum -t 30 HTTP WARNING - maximum redirection depth 15 exceeded - http://www.taxi-blog.de:80wordpress/ As you can see the error messages shows a messed up error message (a missing '/'). I think it depends on the header structure/size/order of the HTTP response message. Others URLs are failing too with the version 1.4.12 so I think it's not an apache problem on the other side. Greetings and thanks for the good work. ---------------------------------------------------------------------- >Comment By: Erik Wasser (ewasser) Date: 2008-09-02 10:37 Message: Logged In: YES user_id=80027 Originator: YES Here's the patch. The comments are longer than the source itself to so please feel free to cut something. B-) % check_http --onredirect=follow -H www.taxi-blog.de -u /wordpress/ -s Impressum -t 30 is now working everytime. File Added: nagios-plugins-1.4.12-ommit-default-port.patch ---------------------------------------------------------------------- Comment By: Holger Weiss (hweiss) Date: 2008-09-02 10:28 Message: Logged In: YES user_id=759506 Originator: NO Sure! Just attach your patch to this tracker item and I'll look into it. Should be mostly trivial, just keep the different default ports for HTTP and HTTPS in mind. Thank you! ---------------------------------------------------------------------- Comment By: Erik Wasser (ewasser) Date: 2008-09-02 10:13 Message: Logged In: YES user_id=80027 Originator: YES Thanks for verbose answer. I think you are right it's a wordpress issue but I found a least one other (customer) application that has the same problem. And I think there were will be more. B-((( The symptoms are always the same. You speak to the applikation with www.foo.invalid:80 and it returns a redirect to www.foo.invalid (without the port number). check_http add the :80 again and the game begins again. That makes the plugin pretty incompatible with "my" world. Currently we can't upgrade to 1.4.12 because of this issue so I would like do to the patch for myself because we need this feature. Would that be okay for you? ---------------------------------------------------------------------- Comment By: Holger Weiss (hweiss) Date: 2008-09-01 16:58 Message: Logged In: YES user_id=759506 Originator: NO Thank you very much. Now I can reproduce the problem: last time, I simply grabbed the wrong SVN revision of check_http.c. Sorry about that! However, as far as I can tell the only bug here is the missing '/' in the error message. The URL which the plugin uses for the request includes the '/', so the error message is misleading and has nothing to do with your problem. I now fixed the error message in SVN. Thanks for the hint! Regarding your actual problem: With HTTP/1.1, the server extracts the virtual host name to use from the "Host:" header provided by the client. check_http generates the header line "Host: www.taxi-blog.de:80". Now, the problem is that the server seems to treat this as a request for a virtual host different from the host which would be requested using "Host: www.taxi-blog.de" (without the explicit port) and that the server therefore redirects the client to "www.taxi-blog.de". Since the plugin then re-adds the port number to the "Host:" header for the new (redirected) request, there's an infinite redirection loop. The standard clearly states that "Host: foo" and "Host: foo:80" are equivalent for HTTP requests (see: http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html#sec14.23). So, IMO it's a server issue (or a configuration problem or an issue of PHP or Wordpress or whoever generates the response). So I'll set this item's status to "pending", but I'll put removing the port number from the "Host:" header if the default port is used on my TODO list (since that shouldn't hurt). As to why the server only _sometimes_ behaves like this, I have no idea. In any case, this has nothing to do with the plugin. Try netcat(1): ----------- 8< ------------------------------ 8< ----------- % printf "GET /wordpress/ HTTP/1.0\r\n" > /tmp/request % printf "Host: www.taxi-blog.de:80\r\n\r\n" >> /tmp/request % nc www.taxi-blog.de 80 < /tmp/request | head HTTP/1.1 301 Moved Permanently Date: Mon, 01 Sep 2008 13:01:27 GMT Server: Apache X-Powered-By: PHP/5.1.6 X-Pingback: http://www.taxi-blog.de/wordpress/xmlrpc.php Location: http://www.taxi-blog.de/wordpress/ Content-Type: text/html; charset=UTF-8 Content-Length: 0 Connection: close % nc www.taxi-blog.de 80 < /tmp/request | head HTTP/1.1 200 OK Date: Mon, 01 Sep 2008 13:01:25 GMT Server: Apache X-Powered-By: PHP/5.1.6 X-Pingback: http://www.taxi-blog.de/wordpress/xmlrpc.php Last-Modified: Mon, 01 Sep 2008 13:01:21 GMT Content-Type: text/html; charset=UTF-8 Connection: close ---------------------------------------------------------------------- Comment By: Erik Wasser (ewasser) Date: 2008-09-01 09:21 Message: Logged In: YES user_id=80027 Originator: YES Thanks for the feedback, that's no problem at all. I've used the .tar.gz from SourceForge. % cd /tmp/nagios-plugins-1.4.12 % ./configure % make % plugins/check_http --verbose -H www.taxi-blog.de --onredirect=follow -H www.taxi-blog.de -u /wordpress/ -s Impressum -t 30 option f:4 GET /wordpress/ HTTP/1.0 User-Agent: check_http/v1991 (nagios-plugins 1.4.12) Connection: close Host: www.taxi-blog.de:80 http://www.taxi-blog.de:80/wordpress/ is 294 characters STATUS: HTTP/1.1 301 Moved Permanently **** HEADER **** Date: Mon, 01 Sep 2008 07:12:39 GMT Server: Apache X-Powered-By: PHP/5.1.6 X-Pingback: http://www.taxi-blog.de/wordpress/xmlrpc.php Location: http://www.taxi-blog.de/wordpress/ Content-Length: 0 Content-Type: text/html; charset=UTF-8 Connection: close **** CONTENT **** Redirection to http://www.taxi-blog.de:80/wordpress/ GET /wordpress/ HTTP/1.0 User-Agent: check_http/v1991 (nagios-plugins 1.4.12) Connection: close Host: www.taxi-blog.de:80 http://www.taxi-blog.de:80/wordpress/ is 294 characters STATUS: HTTP/1.1 301 Moved Permanently **** HEADER **** Date: Mon, 01 Sep 2008 07:12:39 GMT Server: Apache X-Powered-By: PHP/5.1.6 X-Pingback: http://www.taxi-blog.de/wordpress/xmlrpc.php Location: http://www.taxi-blog.de/wordpress/ Content-Length: 0 Content-Type: text/html; charset=UTF-8 Connection: close **** CONTENT **** Redirection to http://www.taxi-blog.de:80/wordpress/ GET /wordpress/ HTTP/1.0 User-Agent: check_http/v1991 (nagios-plugins 1.4.12) Connection: close Host: www.taxi-blog.de:80 [...snipped the repeating output...] http://www.taxi-blog.de:80/wordpress/ is 294 characters STATUS: HTTP/1.1 301 Moved Permanently **** HEADER **** Date: Mon, 01 Sep 2008 07:12:42 GMT Server: Apache X-Powered-By: PHP/5.1.6 X-Pingback: http://www.taxi-blog.de/wordpress/xmlrpc.php Location: http://www.taxi-blog.de/wordpress/ Content-Length: 0 Content-Type: text/html; charset=UTF-8 Connection: close **** CONTENT **** HTTP WARNING - maximum redirection depth 15 exceeded - http://www.taxi-blog.de:80wordpress/ % I hope that will help. ---------------------------------------------------------------------- Comment By: Holger Weiss (hweiss) Date: 2008-08-29 17:43 Message: Logged In: YES user_id=759506 Originator: NO There's no obvious change in the code between 1.4.11 and 1.4.12 which could cause this, and so far, I can't reproduce the problem: % check_http --onredirect=critical -H www.taxi-blog.de -u /wordpress/ -s Impressum -t 30 HTTP OK HTTP/1.1 200 OK - 0.591 second response time |time=0.590834s;;;0.000000 size=61229B;;;0 That is, the server doesn't actually redirect this URL. Using "-u /wordpress" without a trailing slash redirects to /wordpress/, though. I tried the following call 100 times in a loop and always got an OK: % check_http -H www.taxi-blog.de --onredirect=follow -H www.taxi-blog.de -u /wordpress/ -s Impressum -t 30 HTTP OK HTTP/1.1 200 OK - 0.761 second response time |time=0.760912s;;;0.000000 size=61229B;;;0 So, could you please try to reproduce the problem using "--verbose" and post the output (up to the **** CONTENT **** part)? (It would be nice if you could use the version compiled from the official sources for this.) Thank you! ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=397597&aid=2082501&group_id=29880 From noreply at sourceforge.net Tue Sep 2 13:27:32 2008 From: noreply at sourceforge.net (SourceForge.net) Date: Tue, 02 Sep 2008 11:27:32 +0000 Subject: [Nagiosplug-devel] [ nagiosplug-Bugs-2082501 ] check_http redirects sporadically endless in version 1.4.12 Message-ID: Bugs item #2082501, was opened at 2008-08-29 16:10 Message generated for change (Comment added) made by hweiss You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=397597&aid=2082501&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 (specify) >Status: Closed >Resolution: Accepted Priority: 5 Private: No Submitted By: Erik Wasser (ewasser) Assigned to: Nobody/Anonymous (nobody) Summary: check_http redirects sporadically endless in version 1.4.12 Initial Comment: The check_http plugin in version 1.4.12 is brocken. Version 1.4.11 works fine. The plugin messes up the redirection url. The redirection doesn't end and it will result in a "WARNING". Here's the sample output, the binarys were taken from DAG http://apt.sw.be/redhat/el5/en/i386/RPMS.dag/ but I also recompiled the version 1.4.12 from the official sources. Plugin Version (-V output): check_http v1991 (nagios-plugins 1.4.12) Plugin Name: check_http Plugin Commandline showing issues: see down below Operating System: Linux Architecture: i386, x86_64 Compiler: gcc WORKING VERSION 1.4.11: % ./check_http-1.4.11-1 --onredirect=follow -H www.taxi-blog.de -u /wordpress/ -s Impressum -t 30 HTTP OK HTTP/1.1 200 OK - 0.552 second response time |time=0.551658s;;;0.000000 size=61131B;;;0 This is working everytime. DEFECT VERSION 1.4.12: The error itself is not consistent: B-( % ./plugins/check_http --onredirect=follow -H www.taxi-blog.de -u /wordpress/ -s Impressum -t 30 HTTP OK HTTP/1.1 200 OK - 1.525 second response time |time=1.525200s;;;0.000000 size=61216B;;;0 % ./plugins/check_http --onredirect=follow -H www.taxi-blog.de -u /wordpress/ -s Impressum -t 30 HTTP WARNING - maximum redirection depth 15 exceeded - http://www.taxi-blog.de:80wordpress/ % ./plugins/check_http --onredirect=follow -H www.taxi-blog.de -u /wordpress/ -s Impressum -t 30 HTTP OK HTTP/1.1 200 OK - 0.173 second response time |time=0.172721s;;;0.000000 size=61216B;;;0 % ./plugins/check_http --onredirect=follow -H www.taxi-blog.de -u /wordpress/ -s Impressum -t 30 HTTP OK HTTP/1.1 200 OK - 2.788 second response time |time=2.788378s;;;0.000000 size=61217B;;;0 % ./plugins/check_http --onredirect=follow -H www.taxi-blog.de -u /wordpress/ -s Impressum -t 30 HTTP OK HTTP/1.1 200 OK - 0.169 second response time |time=0.168843s;;;0.000000 size=61216B;;;0 % ./plugins/check_http --onredirect=follow -H www.taxi-blog.de -u /wordpress/ -s Impressum -t 30 HTTP WARNING - maximum redirection depth 15 exceeded - http://www.taxi-blog.de:80wordpress/ % ./plugins/check_http --onredirect=follow -H www.taxi-blog.de -u /wordpress/ -s Impressum -t 30 HTTP WARNING - maximum redirection depth 15 exceeded - http://www.taxi-blog.de:80wordpress/ As you can see the error messages shows a messed up error message (a missing '/'). I think it depends on the header structure/size/order of the HTTP response message. Others URLs are failing too with the version 1.4.12 so I think it's not an apache problem on the other side. Greetings and thanks for the good work. ---------------------------------------------------------------------- >Comment By: Holger Weiss (hweiss) Date: 2008-09-02 13:27 Message: Logged In: YES user_id=759506 Originator: NO I committed that change to SVN. Thank you. ---------------------------------------------------------------------- Comment By: Erik Wasser (ewasser) Date: 2008-09-02 10:37 Message: Logged In: YES user_id=80027 Originator: YES Here's the patch. The comments are longer than the source itself to so please feel free to cut something. B-) % check_http --onredirect=follow -H www.taxi-blog.de -u /wordpress/ -s Impressum -t 30 is now working everytime. File Added: nagios-plugins-1.4.12-ommit-default-port.patch ---------------------------------------------------------------------- Comment By: Holger Weiss (hweiss) Date: 2008-09-02 10:28 Message: Logged In: YES user_id=759506 Originator: NO Sure! Just attach your patch to this tracker item and I'll look into it. Should be mostly trivial, just keep the different default ports for HTTP and HTTPS in mind. Thank you! ---------------------------------------------------------------------- Comment By: Erik Wasser (ewasser) Date: 2008-09-02 10:13 Message: Logged In: YES user_id=80027 Originator: YES Thanks for verbose answer. I think you are right it's a wordpress issue but I found a least one other (customer) application that has the same problem. And I think there were will be more. B-((( The symptoms are always the same. You speak to the applikation with www.foo.invalid:80 and it returns a redirect to www.foo.invalid (without the port number). check_http add the :80 again and the game begins again. That makes the plugin pretty incompatible with "my" world. Currently we can't upgrade to 1.4.12 because of this issue so I would like do to the patch for myself because we need this feature. Would that be okay for you? ---------------------------------------------------------------------- Comment By: Holger Weiss (hweiss) Date: 2008-09-01 16:58 Message: Logged In: YES user_id=759506 Originator: NO Thank you very much. Now I can reproduce the problem: last time, I simply grabbed the wrong SVN revision of check_http.c. Sorry about that! However, as far as I can tell the only bug here is the missing '/' in the error message. The URL which the plugin uses for the request includes the '/', so the error message is misleading and has nothing to do with your problem. I now fixed the error message in SVN. Thanks for the hint! Regarding your actual problem: With HTTP/1.1, the server extracts the virtual host name to use from the "Host:" header provided by the client. check_http generates the header line "Host: www.taxi-blog.de:80". Now, the problem is that the server seems to treat this as a request for a virtual host different from the host which would be requested using "Host: www.taxi-blog.de" (without the explicit port) and that the server therefore redirects the client to "www.taxi-blog.de". Since the plugin then re-adds the port number to the "Host:" header for the new (redirected) request, there's an infinite redirection loop. The standard clearly states that "Host: foo" and "Host: foo:80" are equivalent for HTTP requests (see: http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html#sec14.23). So, IMO it's a server issue (or a configuration problem or an issue of PHP or Wordpress or whoever generates the response). So I'll set this item's status to "pending", but I'll put removing the port number from the "Host:" header if the default port is used on my TODO list (since that shouldn't hurt). As to why the server only _sometimes_ behaves like this, I have no idea. In any case, this has nothing to do with the plugin. Try netcat(1): ----------- 8< ------------------------------ 8< ----------- % printf "GET /wordpress/ HTTP/1.0\r\n" > /tmp/request % printf "Host: www.taxi-blog.de:80\r\n\r\n" >> /tmp/request % nc www.taxi-blog.de 80 < /tmp/request | head HTTP/1.1 301 Moved Permanently Date: Mon, 01 Sep 2008 13:01:27 GMT Server: Apache X-Powered-By: PHP/5.1.6 X-Pingback: http://www.taxi-blog.de/wordpress/xmlrpc.php Location: http://www.taxi-blog.de/wordpress/ Content-Type: text/html; charset=UTF-8 Content-Length: 0 Connection: close % nc www.taxi-blog.de 80 < /tmp/request | head HTTP/1.1 200 OK Date: Mon, 01 Sep 2008 13:01:25 GMT Server: Apache X-Powered-By: PHP/5.1.6 X-Pingback: http://www.taxi-blog.de/wordpress/xmlrpc.php Last-Modified: Mon, 01 Sep 2008 13:01:21 GMT Content-Type: text/html; charset=UTF-8 Connection: close ---------------------------------------------------------------------- Comment By: Erik Wasser (ewasser) Date: 2008-09-01 09:21 Message: Logged In: YES user_id=80027 Originator: YES Thanks for the feedback, that's no problem at all. I've used the .tar.gz from SourceForge. % cd /tmp/nagios-plugins-1.4.12 % ./configure % make % plugins/check_http --verbose -H www.taxi-blog.de --onredirect=follow -H www.taxi-blog.de -u /wordpress/ -s Impressum -t 30 option f:4 GET /wordpress/ HTTP/1.0 User-Agent: check_http/v1991 (nagios-plugins 1.4.12) Connection: close Host: www.taxi-blog.de:80 http://www.taxi-blog.de:80/wordpress/ is 294 characters STATUS: HTTP/1.1 301 Moved Permanently **** HEADER **** Date: Mon, 01 Sep 2008 07:12:39 GMT Server: Apache X-Powered-By: PHP/5.1.6 X-Pingback: http://www.taxi-blog.de/wordpress/xmlrpc.php Location: http://www.taxi-blog.de/wordpress/ Content-Length: 0 Content-Type: text/html; charset=UTF-8 Connection: close **** CONTENT **** Redirection to http://www.taxi-blog.de:80/wordpress/ GET /wordpress/ HTTP/1.0 User-Agent: check_http/v1991 (nagios-plugins 1.4.12) Connection: close Host: www.taxi-blog.de:80 http://www.taxi-blog.de:80/wordpress/ is 294 characters STATUS: HTTP/1.1 301 Moved Permanently **** HEADER **** Date: Mon, 01 Sep 2008 07:12:39 GMT Server: Apache X-Powered-By: PHP/5.1.6 X-Pingback: http://www.taxi-blog.de/wordpress/xmlrpc.php Location: http://www.taxi-blog.de/wordpress/ Content-Length: 0 Content-Type: text/html; charset=UTF-8 Connection: close **** CONTENT **** Redirection to http://www.taxi-blog.de:80/wordpress/ GET /wordpress/ HTTP/1.0 User-Agent: check_http/v1991 (nagios-plugins 1.4.12) Connection: close Host: www.taxi-blog.de:80 [...snipped the repeating output...] http://www.taxi-blog.de:80/wordpress/ is 294 characters STATUS: HTTP/1.1 301 Moved Permanently **** HEADER **** Date: Mon, 01 Sep 2008 07:12:42 GMT Server: Apache X-Powered-By: PHP/5.1.6 X-Pingback: http://www.taxi-blog.de/wordpress/xmlrpc.php Location: http://www.taxi-blog.de/wordpress/ Content-Length: 0 Content-Type: text/html; charset=UTF-8 Connection: close **** CONTENT **** HTTP WARNING - maximum redirection depth 15 exceeded - http://www.taxi-blog.de:80wordpress/ % I hope that will help. ---------------------------------------------------------------------- Comment By: Holger Weiss (hweiss) Date: 2008-08-29 17:43 Message: Logged In: YES user_id=759506 Originator: NO There's no obvious change in the code between 1.4.11 and 1.4.12 which could cause this, and so far, I can't reproduce the problem: % check_http --onredirect=critical -H www.taxi-blog.de -u /wordpress/ -s Impressum -t 30 HTTP OK HTTP/1.1 200 OK - 0.591 second response time |time=0.590834s;;;0.000000 size=61229B;;;0 That is, the server doesn't actually redirect this URL. Using "-u /wordpress" without a trailing slash redirects to /wordpress/, though. I tried the following call 100 times in a loop and always got an OK: % check_http -H www.taxi-blog.de --onredirect=follow -H www.taxi-blog.de -u /wordpress/ -s Impressum -t 30 HTTP OK HTTP/1.1 200 OK - 0.761 second response time |time=0.760912s;;;0.000000 size=61229B;;;0 So, could you please try to reproduce the problem using "--verbose" and post the output (up to the **** CONTENT **** part)? (It would be nice if you could use the version compiled from the official sources for this.) Thank you! ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=397597&aid=2082501&group_id=29880 From noreply at sourceforge.net Tue Sep 2 17:12:36 2008 From: noreply at sourceforge.net (SourceForge.net) Date: Tue, 02 Sep 2008 15:12:36 +0000 Subject: [Nagiosplug-devel] [ nagiosplug-Patches-2089159 ] No Message-ID: Patches item #2089159, was opened at 2008-09-02 17:12 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=397599&aid=2089159&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: Bugfix Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Dieter Van de Walle (dietervdw) Assigned to: Nobody/Anonymous (nobody) Summary: No Initial Comment: Patch against Plugin Version (-V output): check_http v1991 (nagios-plugins 1.4.12) Plugin Name: check_http Example Plugin Commandline: ./check_http -u "http://somewhere" -f follow -k "header: value" Tested on operating system: Ubuntu Tested on architecture: x86 Tested with compiler: gcc version 4.1.3 20080623 (prerelease) (Debian 4.1.2-23) When adding extra headers and doing a redirect, mayhem occurs. The extra headers are free'd in the first check_http() call, making the second check_http() call after the redir() create a faulty request. Drop the free(http_opt_headers) . ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=397599&aid=2089159&group_id=29880 From noreply at sourceforge.net Tue Sep 2 17:13:04 2008 From: noreply at sourceforge.net (SourceForge.net) Date: Tue, 02 Sep 2008 15:13:04 +0000 Subject: [Nagiosplug-devel] [ nagiosplug-Patches-2089159 ] check_http: extra headers and redirect doesn't work Message-ID: Patches item #2089159, was opened at 2008-09-02 17:12 Message generated for change (Settings changed) made by dietervdw You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=397599&aid=2089159&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: Bugfix Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Dieter Van de Walle (dietervdw) Assigned to: Nobody/Anonymous (nobody) >Summary: check_http: extra headers and redirect doesn't work Initial Comment: Patch against Plugin Version (-V output): check_http v1991 (nagios-plugins 1.4.12) Plugin Name: check_http Example Plugin Commandline: ./check_http -u "http://somewhere" -f follow -k "header: value" Tested on operating system: Ubuntu Tested on architecture: x86 Tested with compiler: gcc version 4.1.3 20080623 (prerelease) (Debian 4.1.2-23) When adding extra headers and doing a redirect, mayhem occurs. The extra headers are free'd in the first check_http() call, making the second check_http() call after the redir() create a faulty request. Drop the free(http_opt_headers) . ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=397599&aid=2089159&group_id=29880 From hrpoliveira at gmail.com Tue Sep 2 17:18:33 2008 From: hrpoliveira at gmail.com (Helder Oliveira) Date: Tue, 2 Sep 2008 16:18:33 +0100 Subject: [Nagiosplug-devel] NRPE security Message-ID: Hey all, i have read lots of stuff about nrpe, and i have one question. We configure the remote host iptables to accept our tcp request to the 5556 port, but shoudn't we configure from wich IP the request should be ? Aren't we at risk that someone point a nagios to our machine and get our data ? I got this question reading the NRPE tutorial, at this moment im reading a iptables tutorial to see if has any sense what im thinking, but you guys have more experience and may have a few words for me. Thanks for your time. -------------- next part -------------- An HTML attachment was scrubbed... URL: From jhmartin at toger.us Tue Sep 2 18:31:56 2008 From: jhmartin at toger.us (Jason Martin) Date: Tue, 2 Sep 2008 09:31:56 -0700 Subject: [Nagiosplug-devel] NRPE security In-Reply-To: References: Message-ID: <20080902163156.GE5898@mal.toger.us> On Tue, Sep 02, 2008 at 04:18:33PM +0100, Helder Oliveira wrote: > We configure the remote host iptables to accept our tcp request to the 5556 > port, but shoudn't we configure from wich IP the request should be ? > Aren't we at risk that someone point a nagios to our machine and get our > data ? If at all possible you should configure iptables to only allow your own nagios hosts access to NRPE. -Jason Martin -- A computer's attention span is as long as it's power cord. This message is PGP/MIME signed. -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 219 bytes Desc: not available URL: From duncan.ferguson at altinity.com Thu Sep 4 15:55:48 2008 From: duncan.ferguson at altinity.com (Duncan Ferguson) Date: Thu, 4 Sep 2008 14:55:48 +0100 Subject: [Nagiosplug-devel] [Nagios-users] check_procs from Nagios plugins 1.4.12 is veeery slow on Solaris 10 5/08 In-Reply-To: <48BFDC55.5060607@adnovum.ch> References: <48BFDC55.5060607@adnovum.ch> Message-ID: <52064DA7-9A86-41FA-8026-542DB793833D@altinity.com> Can you please try a recent snapshot? The I rewrote the pst3 binary to enable to work faster and be zone aware (to allow use in in the global and sub zones). Its been fine for me, but I don't think there has been a release since the code was committed. CC'ing in the nagiosplug-devel list (probably best place for this thread). Duncs On 4 Sep 2008, at 14:02, Bernd Nies wrote: > Hi, > > Something bad happened to the check_proc plugin between version 1.45 > and > v1991. For counting ca 1700 processes on a Sun Enterprise M4000 it > takes > 45 seconds and sometimes longer. An older version was much faster qirh > 0.3 seconds. > > I compiled Nagios plugins 1.4.12 on a Solaris 9 with GCC 3.4.6 to get > binaries that can run on Solaris 8, 9 and 10. > > > > [root at adnsoz05 ~]$ /opt/adnnagios/libexec/check_procs-1.45 -V > check_procs (nagios-plugins 1.4.1) 1.45 > > [root at adnsoz05 ~]$ /opt/adnnagios/libexec/check_procs -V > check_procs v1991 (nagios-plugins 1.4.12) > > > > [root at adnsoz05 ~]$ time /opt/adnnagios/libexec/check_procs-1.45 > PROCS OK: 1695 processes > > real 0m0.320s > user 0m0.051s > sys 0m0.296s > > [root at adnsoz05 ~]$ time /opt/adnnagios/libexec/check_procs -t 60 > PROCS OK: 1664 processes > > real 0m45.543s > user 0m2.851s > sys 0m41.231s > > > Any ideas what's going wrong? > > Bye > Bernd > > > ------------------------------------------------------------------------- > This SF.Net email is sponsored by the Moblin Your Move Developer's > challenge > Build the coolest Linux based applications with Moblin SDK & win > great prizes > Grand prize is a trip for two to an Open Source event anywhere in > the world > http://moblin-contest.org/redirect.php?banner_id=100&url=/ > _______________________________________________ > Nagios-users mailing list > Nagios-users at lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/nagios-users > ::: Please include Nagios version, plugin version (-v) and OS when > reporting any issue. > ::: Messages without supporting info will risk being sent to /dev/null -- Duncan Ferguson Senior Developer, Altinity Limited http://www.altinity.com Tel: +44 (0)870 787 9243 US: +1 866 879 9184 Fax: +44 (0)845 280 1725 Skype: duncan_j_ferguson MSN: duncan.ferguson at altinity.com The contents of this email and any files transmitted with it are confidential and intended solely for the use of the individuals to whom it is addressed. If you are not the intended recipient or have received this e-mail in error please notify the sender and delete this e-mail immediately. Any unauthorised copying, disclosure or distribution of the material in this e-mail is strictly prohibited. Altinity Limited | 404 Seven Sisters Road | London | N4 2LX | United Kingdom Registered in England and Wales under company number 4743767 From noreply at sourceforge.net Mon Sep 8 20:00:00 2008 From: noreply at sourceforge.net (SourceForge.net) Date: Mon, 08 Sep 2008 18:00:00 +0000 Subject: [Nagiosplug-devel] [ nagiosplug-Feature Requests-2100684 ] "Thresholds" syntax to support enumerated values as well Message-ID: Feature Requests item #2100684, was opened at 2008-09-08 18:00 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=397600&aid=2100684&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 Improvements (example) Group: None Status: Open Priority: 5 Private: No Submitted By: Mike Whittaker (mikewhit) Assigned to: Nobody/Anonymous (nobody) Summary: "Thresholds" syntax to support enumerated values as well Initial Comment: I have a case in which an SNMP operation retrieves a status value from a host. However, the value is not an 'ordered' value in which you can assign increasing or decreasing levels of problem. Instead the value is a value from an enumeration set. In this case, it would be useful if the 'thresholds' plugin command-line syntax was extended to allow a list of specific values, to allow this situation to be handled concisely. e.g. get_device_status $HOST -w 1,3,5,7 -c 2, This example is meant to indicate that the presence of a trailing comma introduces an enumeration set or single value in which the status (warning or critical) is returned if the enumeration value is met. Hence the example would return WARNING if the status code was 1,3,5 or 7; CRITICAL if the status code was 2 [equivalent to "Threshold" @2:2]; OK otherwise. It may be possible to combine comma-trailing enumerated values with additional existing threshold syntax parameters, but that would complicate decoding logic !! ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=397600&aid=2100684&group_id=29880 From noreply at sourceforge.net Mon Sep 8 21:52:03 2008 From: noreply at sourceforge.net (SourceForge.net) Date: Mon, 08 Sep 2008 19:52:03 +0000 Subject: [Nagiosplug-devel] [ nagiosplug-Bugs-1993363 ] check_procs times out on Solaris 10 Message-ID: Bugs item #1993363, was opened at 2008-06-13 21:58 Message generated for change (Comment added) made by tonvoon You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=397597&aid=1993363&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: snapshot tarball Status: Open Resolution: None Priority: 5 Private: No Submitted By: maemigh (maemigh) Assigned to: Ton Voon (tonvoon) Summary: check_procs times out on Solaris 10 Initial Comment: I'm having problems with the latest snapshot of check_procs timing out. The version is v1991 (nagios-plugins 1.4.12). This is using pst3 included with the plugins. ./check_procs CRITICAL - Plugin timed out after 10 seconds ./check_procs -w 2:2 -c 2:2 -C nagios CRITICAL - Plugin timed out after 10 seconds I've tried sparc and x86 builds, both timeout: Solaris 5.10 Generic_118833-36 sparc Solaris Generic_127112-11 i386 ---------------------------------------------------------------------- >Comment By: Ton Voon (tonvoon) Date: 2008-09-08 20:52 Message: maemigh, Can you try this with the latest snapshot. pst3 has been updated to avoid using /dev/kmem so it should now work for zones. Ton ---------------------------------------------------------------------- Comment By: maemigh (maemigh) Date: 2008-06-20 15:40 Message: Logged In: YES user_id=1520524 Originator: YES SVN from 6-19 is causing a segfault on one of our Solaris 9 servers: Here is some output from truss: stat("/usr/platform/SUNW,Sun-Fire-V240/lib/sparcv9/libkvm_psr.so.1", 0xFFFFFFFF7FFFE8D0) Err#2 ENOENT brk(0x100102520) = 0 brk(0x100106520) = 0 stat("/dev/kmem", 0xFFFFFFFF7FFFF2D0) = 0 stat("/dev/mem", 0xFFFFFFFF7FFFF250) = 0 stat("/dev/kmem", 0xFFFFFFFF7FFFF1D0) = 0 stat("/dev/allkmem", 0xFFFFFFFF7FFFF150) = 0 open("/dev/kmem", O_RDONLY) = 3 open("/dev/mem", O_RDONLY) = 4 open("/dev/ksyms", O_RDONLY) = 5 read(5, "7F E L F020201\0\0\0\0\0".., 16) = 16 lseek(5, 0, SEEK_SET) = 0 lseek(5, 0, SEEK_END) = 895494 mmap(0x00000000, 895494, PROT_READ, MAP_PRIVATE, 5, 0) = 0xFFFFFFFF7E300000 munmap(0xFFFFFFFF7E300000, 895494) = 0 close(5) = 0 pread(3, "\0\0030E92 " u p", 8, 0x0142C300) = 8 pread(3, "\0\0030E92 " u p", 8, 0x0142C300) = 8 ioctl(1, TCGETA, 0xFFFFFFFF7FFFE14C) = 0 fstat(1, 0xFFFFFFFF7FFFE0E0) = 0 S UID PID PPID VSZ RSS %CPU COMMAND ARGS write(1, " S U I D P I".., 52) = 52 pread(3, "\0\003\005F7 5 0\0\003\0".., 2584, 0x30E92227570) = 2584 pread(3, "\0\0 Z ?", 4, 0x30003070C4C) = 4 pread(3, "\0\0\0 R\0\0 Z ?\0\0\0\0".., 32, 0x30003070C48) = 32 open("/proc/23103/as", O_RDONLY) = 5 pread(5, "FFFFFFFF7FFFFD\0\0\0\0\0".., 1240, 0xFFFFFFFF7FFFFB28) = 1240 close(5) = 0 open("/proc/23103/psinfo", O_RDONLY) = 5 read(5, "\b\0C4 H\0\0\001\0\0 Z ?".., 416) = 416 close(5) = 0 O 0 23103 23102 2096 1160 0.1 pst3 ./pst3 write(1, " O 0 2 3 1 0".., 52) = 52 pread(3, "\0\003\01CE6D6 8\0\003\0".., 2584, 0x3000513A120) = 2584 pread(3, "\0\0 Z >", 4, 0x3000316EA84) = 4 pread(3, "\0\0\0 u\0\0 Z >\0\0\0\0".., 32, 0x3000316EA80) = 32 open("/proc/23102/as", O_RDONLY) = 5 pread(5, "FFFFFFFF7FFFFCE8FFFFFFFF".., 1272, 0xFFFFFFFF7FFFFB08) = 1272 close(5) = 0 open("/proc/23102/psinfo", O_RDONLY) = 5 read(5, "\b02 @\b\0\0\002\0\0 Z >".., 416) = 416 close(5) = 0 S 0 23102 22954 2800 1784 0.1 truss truss ./pst3 write(1, " S 0 2 3 1 0".., 59) = 59 pread(3, "\0\003\001 -A8 p\0\003\0".., 2584, 0x3000253B450) = 2584 pread(3, "\0\0 YAA", 4, 0x30002D0DF6C) = 4 pread(3, "\0\0\019\0\0 YAA\0\0030E".., 32, 0x30002D0DF68) = 32 open("/proc/22954/as", O_RDONLY) = 5 pread(5, "FFBFFF p\0\0\0\0FFBFFF t".., 188, 0xFFBFFF44) = 188 close(5) = 0 brk(0x100106520) = 0 brk(0x10091E520) = 0 Incurred fault #6, FLTBOUNDS %pc = 0xFFFFFFFF7F400648 siginfo: SIGSEGV SEGV_MAPERR addr=0x101131598 Received signal #11, SIGSEGV [default] siginfo: SIGSEGV SEGV_MAPERR addr=0x101131598 ---------------------------------------------------------------------- Comment By: maemigh (maemigh) Date: 2008-06-19 19:31 Message: Logged In: YES user_id=1520524 Originator: YES PS_COMMAND was set, but it was set to a location that didn't exist. I was running the check_procs command without first doing a make install. I'm thinking that the plugin should probably report that /usr/local/nagios/libexec/pst3 doesn't exist rather than timing out after 10 seconds. I ran into another problem with pst3 in that it will not run inside a Solaris zone (as /dev/kmem does not exist) -- are there plans to make changes to allow for use in zones? ---------------------------------------------------------------------- Comment By: Ton Voon (tonvoon) Date: 2008-06-17 10:23 Message: Logged In: YES user_id=664364 Originator: NO Sorry, misread your report. So are you saying that PS_COMMAND is not set? ---------------------------------------------------------------------- Comment By: Ton Voon (tonvoon) Date: 2008-06-17 10:22 Message: Logged In: YES user_id=664364 Originator: NO Hi maemigh, The issue is that pst3 times out as it is taking too long to query. We've found this on a master host with multiple zones. Please try the snapshot at http://nagiosplug.sf.net/snapshot as pst3 has been optimised to make less kvm calls. It would be useful if you could give us timings before and after the snapshot. Beware, we've recently found an issue where it can coredump if a process disappears as it is trying to access it - a fix is due soon. Ton ---------------------------------------------------------------------- Comment By: maemigh (maemigh) Date: 2008-06-16 21:32 Message: Logged In: YES user_id=1520524 Originator: YES Had time to do a little more digging. This happens if the file pointed to by PS_COMMAND does not exist. There do not appear to be any checks within spopen to handle a return code from execve in the event of an error. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=397597&aid=1993363&group_id=29880 From rkomorn at dofc.org Wed Sep 10 20:13:44 2008 From: rkomorn at dofc.org (Romain Komorn) Date: Wed, 10 Sep 2008 11:13:44 -0700 Subject: [Nagiosplug-devel] contrib/check_mssql.sh 2.0 not properly deleting $errorfile . Message-ID: <6288478a0809101113p3a753b2ev9621fb771d3e4285@mail.gmail.com> Folks, At the beginning of version 2.0 of the contrib/check_mssql.sh script, the following file gets created: Line 67: errorfile=`$mktempcmd /tmp/$hostname.XXXXXX` However, upon "successful" completion, the cleanup command issued is: Line 95: $rmcmd -f $tmpfile $resultfile; This means that the $errorfile created above isn't properly cleaned up, and quickly starts to clutter up /tmp . The other cleanup command, Line 102: $rmcmd -f $tmpfile $resultfile $errorfile never gets executed, due to the fact that the script exits at the end of the if/else block starting with: Line 88: if [ "$resultfileln" == "2" ]; then This appears to still be the case in the snapshot at http://nagiosplug.sourceforge.net/snapshot/nagios-plugins-trunk-200809101200.tar.gz Romain Komorn -------------- next part -------------- An HTML attachment was scrubbed... URL: From noreply at sourceforge.net Wed Sep 10 20:27:02 2008 From: noreply at sourceforge.net (SourceForge.net) Date: Wed, 10 Sep 2008 18:27:02 +0000 Subject: [Nagiosplug-devel] [ nagiosplug-Bugs-2104167 ] errorfile does not get delted upon succesfull completion Message-ID: Bugs item #2104167, was opened at 2008-09-10 11:27 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=397597&aid=2104167&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: snapshot tarball Status: Open Resolution: None Priority: 5 Private: No Submitted By: Romain Komorn (rkomorn) Assigned to: Nobody/Anonymous (nobody) Summary: errorfile does not get delted upon succesfull completion Initial Comment: At the beginning of version 2.0 of the contrib/check_mssql.sh script, the following file gets created: Line 67: errorfile=`$mktempcmd /tmp/$hostname.XXXXXX` However, upon "successful" completion, the cleanup command issued is: Line 95: $rmcmd -f $tmpfile $resultfile; This means that the $errorfile created above isn't properly cleaned up, and quickly starts to clutter up /tmp . The other cleanup command, Line 102: $rmcmd -f $tmpfile $resultfile $errorfile never gets executed, due to the fact that the script exits at the end of the if/else block starting with: Line 88: if [ "$resultfileln" == "2" ]; then This appears to still be the case in the snapshot at http://nagiosplug.sourceforge.net/snapshot/nagios-plugins-trunk-200809101200.tar.gz ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=397597&aid=2104167&group_id=29880 From noreply at sourceforge.net Wed Sep 10 20:35:13 2008 From: noreply at sourceforge.net (SourceForge.net) Date: Wed, 10 Sep 2008 18:35:13 +0000 Subject: [Nagiosplug-devel] [ nagiosplug-Bugs-2104167 ] errorfile does not get delted upon succesfull completion Message-ID: Bugs item #2104167, was opened at 2008-09-10 11:27 Message generated for change (Comment added) made by rkomorn You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=397597&aid=2104167&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: snapshot tarball Status: Open Resolution: None Priority: 5 Private: No Submitted By: Romain Komorn (rkomorn) Assigned to: Nobody/Anonymous (nobody) Summary: errorfile does not get delted upon succesfull completion Initial Comment: At the beginning of version 2.0 of the contrib/check_mssql.sh script, the following file gets created: Line 67: errorfile=`$mktempcmd /tmp/$hostname.XXXXXX` However, upon "successful" completion, the cleanup command issued is: Line 95: $rmcmd -f $tmpfile $resultfile; This means that the $errorfile created above isn't properly cleaned up, and quickly starts to clutter up /tmp . The other cleanup command, Line 102: $rmcmd -f $tmpfile $resultfile $errorfile never gets executed, due to the fact that the script exits at the end of the if/else block starting with: Line 88: if [ "$resultfileln" == "2" ]; then This appears to still be the case in the snapshot at http://nagiosplug.sourceforge.net/snapshot/nagios-plugins-trunk-200809101200.tar.gz ---------------------------------------------------------------------- >Comment By: Romain Komorn (rkomorn) Date: 2008-09-10 11:35 Message: File Added: check_mssql.sh-errorfile_deletion-patch.txt ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=397597&aid=2104167&group_id=29880 From noreply at sourceforge.net Wed Sep 10 20:37:00 2008 From: noreply at sourceforge.net (SourceForge.net) Date: Wed, 10 Sep 2008 18:37:00 +0000 Subject: [Nagiosplug-devel] [ nagiosplug-Bugs-2104167 ] errorfile does not get delted upon succesfull completion Message-ID: Bugs item #2104167, was opened at 2008-09-10 11:27 Message generated for change (Comment added) made by rkomorn You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=397597&aid=2104167&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: snapshot tarball Status: Open Resolution: None Priority: 5 Private: No Submitted By: Romain Komorn (rkomorn) Assigned to: Nobody/Anonymous (nobody) Summary: errorfile does not get delted upon succesfull completion Initial Comment: At the beginning of version 2.0 of the contrib/check_mssql.sh script, the following file gets created: Line 67: errorfile=`$mktempcmd /tmp/$hostname.XXXXXX` However, upon "successful" completion, the cleanup command issued is: Line 95: $rmcmd -f $tmpfile $resultfile; This means that the $errorfile created above isn't properly cleaned up, and quickly starts to clutter up /tmp . The other cleanup command, Line 102: $rmcmd -f $tmpfile $resultfile $errorfile never gets executed, due to the fact that the script exits at the end of the if/else block starting with: Line 88: if [ "$resultfileln" == "2" ]; then This appears to still be the case in the snapshot at http://nagiosplug.sourceforge.net/snapshot/nagios-plugins-trunk-200809101200.tar.gz ---------------------------------------------------------------------- >Comment By: Romain Komorn (rkomorn) Date: 2008-09-10 11:37 Message: File Added: check_mssql.sh-errorfile_deletion.patch ---------------------------------------------------------------------- Comment By: Romain Komorn (rkomorn) Date: 2008-09-10 11:35 Message: File Added: check_mssql.sh-errorfile_deletion-patch.txt ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=397597&aid=2104167&group_id=29880 From yin.yuanxing at tri-media.com Tue Sep 16 03:56:18 2008 From: yin.yuanxing at tri-media.com (Rik) Date: Tue, 16 Sep 2008 09:56:18 +0800 Subject: [Nagiosplug-devel] Question about NAGIOS Message-ID: <000001c9179f$6ed23a80$1402a8c0@rik> HI, We need to have a web interface for adding and removing check servers\services If I need to shutdown www3 - 1) I go to nagios for remove monitoring of that server 2) shutdown & restart www3 3) go to nagios and add monitoring .... Could you please tell me how to do it with pllugins? Many thanks Best Regards, -------------- next part -------------- An HTML attachment was scrubbed... URL: From ae at op5.se Tue Sep 16 08:42:25 2008 From: ae at op5.se (Andreas Ericsson) Date: Tue, 16 Sep 2008 08:42:25 +0200 Subject: [Nagiosplug-devel] Question about NAGIOS In-Reply-To: <000001c9179f$6ed23a80$1402a8c0@rik> References: <000001c9179f$6ed23a80$1402a8c0@rik> Message-ID: <48CF5551.3090900@op5.se> Rik wrote: > HI, > > We need to have a web interface for adding and removing check > servers\services > > > > If I need to shutdown www3 - > > 1) I go to nagios for remove monitoring of that server > > 2) shutdown & restart www3 > > 3) go to nagios and add monitoring .... > > > > Could you please tell me how to do it with pllugins? > Your best bet would be to turn to one of the many nagios consulting companies around, or googling for webconfiguration interfaces. I've heard Fruity is getting support for Nagios 3, but it probably uses the rest of the IT Groundworks opensource suit of tools, so it might not be pleasant to install. I haven't tried. YMMV. -- Andreas Ericsson andreas.ericsson at op5.se OP5 AB www.op5.se Tel: +46 8-230225 Fax: +46 8-230231 From noreply at sourceforge.net Tue Sep 16 13:52:33 2008 From: noreply at sourceforge.net (SourceForge.net) Date: Tue, 16 Sep 2008 11:52:33 +0000 Subject: [Nagiosplug-devel] [ nagiosplug-Patches-2114022 ] check_ircd: added ipv6 support and removed unneccessary bind Message-ID: Patches item #2114022, was opened at 2008-09-16 13:52 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=397599&aid=2114022&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: Robert S. (rj667) Assigned to: Nobody/Anonymous (nobody) Summary: check_ircd: added ipv6 support and removed unneccessary bind Initial Comment: Patch against Plugin Version: 1.3 Plugin Name: check_ircd Example Plugin Commandline: check_ircd -H 2001:888:0:2::6667 Tested on operating system: Linux Tested on architecture: x86_64 Tested with compiler: none (perl-script) - added IPv6 support - removed unneccessary bind() call ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=397599&aid=2114022&group_id=29880 From jhmartin at toger.us Tue Sep 16 15:00:59 2008 From: jhmartin at toger.us (Jason Martin) Date: Tue, 16 Sep 2008 06:00:59 -0700 Subject: [Nagiosplug-devel] Question about NAGIOS In-Reply-To: <000001c9179f$6ed23a80$1402a8c0@rik> References: <000001c9179f$6ed23a80$1402a8c0@rik> Message-ID: <20080916130059.GP5898@mal.toger.us> On Tue, Sep 16, 2008 at 09:56:18AM +0800, Rik wrote: > We need to have a web interface for adding and removing check > servers\services > > If I need to shutdown www3 - > 1) I go to nagios for remove monitoring of that server > 2) shutdown & restart www3 > 3) go to nagios and add monitoring .... > Could you please tell me how to do it with pllugins? Plugins aren't involved. The Nagios website already allows you to submit a 'maintenance window' whereby alarms are disabled for a particular service/host for a given amount of time. No need to remove monitoring for the server. -Jason Martin -- This message is PGP/MIME signed. -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 219 bytes Desc: not available URL: From ton.voon at altinity.com Wed Sep 17 11:44:48 2008 From: ton.voon at altinity.com (Ton Voon) Date: Wed, 17 Sep 2008 10:44:48 +0100 Subject: [Nagiosplug-devel] Notice for 1.4.13 Message-ID: Hi! Based on conversations at the Netways conference last week, I think we should do a release of 1.4.13. So this is notice that we'll aim for a cut next week. Anything that should be added in? Ton http://www.altinity.com UK: +44 (0)870 787 9243 US: +1 866 879 9184 Fax: +44 (0)845 280 1725 Skype: tonvoon From jason at newio.org Thu Sep 18 23:21:43 2008 From: jason at newio.org (Jason Reynolds) Date: Thu, 18 Sep 2008 16:21:43 -0500 Subject: [Nagiosplug-devel] Writing a new plugin, having a strange bug. Message-ID: <530aaeb70809181421q423b0fd0ieb248206c0e670f6@mail.gmail.com> Hello all, I'm relatively new to the nagios plugin development scene. I've been working on a health-check type plugin for some custom apps, mostly regarding the opensims project (www.opensims.org). The problem that I am having is very simply that when my plugin's return code is 1, 2, or 3, Nagios still shows the service as "OK". I have verified the plugin's return code by executing it myself, then using echo $? from the command line, showing the return code. I'd appreciate any help anyone is willing to give. Thanks in advance! Jason -------------- next part -------------- An HTML attachment was scrubbed... URL: From dermoth at aei.ca Fri Sep 19 04:30:50 2008 From: dermoth at aei.ca (Thomas Guyot-Sionnest) Date: Thu, 18 Sep 2008 22:30:50 -0400 Subject: [Nagiosplug-devel] Writing a new plugin, having a strange bug. In-Reply-To: <530aaeb70809181421q423b0fd0ieb248206c0e670f6@mail.gmail.com> References: <530aaeb70809181421q423b0fd0ieb248206c0e670f6@mail.gmail.com> Message-ID: <48D30EDA.3080905@aei.ca> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 18/09/08 05:21 PM, Jason Reynolds wrote: > Hello all, > > I'm relatively new to the nagios plugin development scene. I've > been working on a health-check type plugin for > some custom apps, mostly regarding the opensims project > (www.opensims.org ). The problem that I am > having is very > simply that when my plugin's return code is 1, 2, or 3, Nagios still > shows the service as "OK". I have verified the plugin's > return code by executing it myself, then using echo $? from the command > line, showing the return code. This is the first time I ever hear about such bug. It would definitely help if you can show us some code that cause it. If it's written in Perl, is it being executed trough the ePN? There's some specific things that you can't do under it (http://nagiosplug.sourceforge.net/developer-guidelines.html#PERLPLUGIN); if that's the case you should first try without ePN by specifying the perl executable in the command line (ex: command_line /usr/bin/perl $USER!$/check_stuff blah blah blah). - -- Thomas -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFI0w7Z6dZ+Kt5BchYRAqYcAKDuuQvjQDWwwiUqselZBpTCVGsWxQCg7eku ovj6hEz4LEzyMIpJmpzEkqQ= =fHNb -----END PGP SIGNATURE----- From jhmartin at toger.us Fri Sep 19 05:51:10 2008 From: jhmartin at toger.us (Jason Martin) Date: Thu, 18 Sep 2008 20:51:10 -0700 Subject: [Nagiosplug-devel] Writing a new plugin, having a strange bug. In-Reply-To: <530aaeb70809181421q423b0fd0ieb248206c0e670f6@mail.gmail.com> References: <530aaeb70809181421q423b0fd0ieb248206c0e670f6@mail.gmail.com> Message-ID: <20080919035110.GQ5898@mal.toger.us> On Thu, Sep 18, 2008 at 04:21:43PM -0500, Jason Reynolds wrote: > simply that when my plugin's return code is 1, 2, or 3, Nagios still shows > the service as "OK". I have verified the plugin's > return code by executing it myself, then using echo $? from the command > line, showing the return code. Please post your command definition, including NRPE configuratino for same. It sounds like you aren't executing the plugin you think you are, or there is a wrapper that is losing the return code somewhere along the way. Common example: #!/bin/sh check_http .... if [ $? -ne 0 ]; then echo oh no! fi The above always returns 0 since the script will end up returning the exit code of echo if $? is not 0. It is good that you are checking $? while testing the plugin, so it sounds like it is something upstream of it. -- This message is PGP/MIME signed. -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 219 bytes Desc: not available URL: From davediff at nbcs.rutgers.edu Mon Sep 22 17:32:36 2008 From: davediff at nbcs.rutgers.edu (David Diffenbaugh) Date: Mon, 22 Sep 2008 11:32:36 -0400 (EDT) Subject: [Nagiosplug-devel] proposal for new plugin check_byhttp Message-ID: I have a need for a plugin which would have the functionality proposed below. Before I start working on it does anyone have any suggestions or requests? Is anyone already working on something similar? check_byhttp will be a nagios plugin which retrieves content from a specified host using http. This file will contain a status state (OK,WARN,CRITICAL) and a status message. The plugin will return the state and status message that is listed in the retrieved content. It also will check the last modified time of the document, as reported by the Last-Modified field, to ensure the status is current. If the file is current it will report the status. If the file is not current it will return a state and status message reporting that the document is not up to date based on time thresh-hold arguments passed to the plugin. This plugin only will work when http is functioning correctly on the server the file is hosted on, and will assume this is always the case. The server you are connecting to should be monitored by check_http. I looked through the plugins to make sure this wasn't already possible. The check_http plugin has an -s option that allows you to search for a string in the returned content. This is almost what I want, but I would like the status message to match the returned content and the state to be determined from that message. Perhaps instead of writing a new plugin I could incorporate this to the check_http plugin. Any suggestions? Dave Diffenbaugh Office of Information Technology Rutgers University From dermoth at aei.ca Tue Sep 23 04:13:15 2008 From: dermoth at aei.ca (Thomas Guyot-Sionnest) Date: Mon, 22 Sep 2008 22:13:15 -0400 Subject: [Nagiosplug-devel] proposal for new plugin check_byhttp In-Reply-To: References: Message-ID: <48D850BB.9010603@aei.ca> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 22/09/08 11:32 AM, David Diffenbaugh wrote: > I have a need for a plugin which would have the functionality proposed > below. Before I start working on it does anyone have any suggestions or > requests? Is anyone already working on something similar? > > check_byhttp will be a nagios plugin which retrieves content from a > specified host using http. This file will contain a status state > (OK,WARN,CRITICAL) and a status message. The plugin will return the state > and status message that is listed in the retrieved content. It also will > check the last modified time of the document, as reported by the > Last-Modified field, to ensure the status is current. If the file is > current it will report the status. If the file is not current it will > return a state and status message reporting that the document is not up to > date based on time thresh-hold arguments passed to the plugin. I've been thinking about that lately (I probably even posted about it in this mailing list...) - you should be able to define the string match that cause ok, warn and crit, and possibly print the text returned. It should probably also be able to do SOAP and/or XMLRPC requests (I'm not very knowledgeful in this area so correct me if needed) using a published API so that any web-based plugin could be written to commutate to check_by_http using this standard API. The real problem lies in code duplication. The current check_httl should be made into functions that are callable by check_by_http too. Alternatively, it had been suggested we could use curl (and likely move check_http to use curl as well), which would let us forget about the details of the http protocol and concentrate on coding functionality instead. > This plugin only will work when http is functioning correctly on the > server the file is hosted on, and will assume this is always the case. > The server you are connecting to should be monitored by check_http. Obviously - connection problems should default to UNKNOWN, overridable by a switch (some people want to know if the http-based service fails too). I'd like to have this default behaviour for check_nrpe, check_nt, check_snmp and check_by_ssh too (it's likely the case already for some of these plugins), in a major release. - -- Thomas -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFI2FC76dZ+Kt5BchYRAsF0AKDjIyEHhkId76KWgxwsZlwMMEPjMQCgoxXD LHY61I8J4lxKYjeODiCiFbQ= =Rh2K -----END PGP SIGNATURE----- From dermoth at aei.ca Tue Sep 23 04:58:58 2008 From: dermoth at aei.ca (Thomas Guyot-Sionnest) Date: Mon, 22 Sep 2008 22:58:58 -0400 Subject: [Nagiosplug-devel] Duplicate email (Was: Re: proposal for new plugin check_byhttp) In-Reply-To: <48D850BB.9010603@aei.ca> References: <48D850BB.9010603@aei.ca> Message-ID: <48D85B72.30002@aei.ca> I received a duplicate of the email I posted. The path until sourceforge is the same as the correct email received from sourceforge, then move on to snecma.fr which in turn send it back to my mail server. It looks like a minsonfigured user's relay sending messages back to their source. Anyone noticed something similar? On 22/09/08 10:13 PM, Thomas Guyot-Sionnest wrote: > On 22/09/08 11:32 AM, David Diffenbaugh wrote: >> I have a need for a plugin which would have the functionality proposed >> below. Before I start working on it does anyone have any suggestions or >> requests? Is anyone already working on something similar? > >> check_byhttp will be a nagios plugin which retrieves content from a >> specified host using http. This file will contain a status state >> (OK,WARN,CRITICAL) and a status message. The plugin will return the state >> and status message that is listed in the retrieved content. It also will >> check the last modified time of the document, as reported by the >> Last-Modified field, to ensure the status is current. If the file is >> current it will report the status. If the file is not current it will >> return a state and status message reporting that the document is not up to >> date based on time thresh-hold arguments passed to the plugin. > > I've been thinking about that lately (I probably even posted about it in > this mailing list...) - you should be able to define the string match > that cause ok, warn and crit, and possibly print the text returned. > > It should probably also be able to do SOAP and/or XMLRPC requests (I'm > not very knowledgeful in this area so correct me if needed) using a > published API so that any web-based plugin could be written to commutate > to check_by_http using this standard API. > > The real problem lies in code duplication. The current check_httl should > be made into functions that are callable by check_by_http too. > Alternatively, it had been suggested we could use curl (and likely move > check_http to use curl as well), which would let us forget about the > details of the http protocol and concentrate on coding functionality > instead. > >> This plugin only will work when http is functioning correctly on the >> server the file is hosted on, and will assume this is always the case. >> The server you are connecting to should be monitored by check_http. > > Obviously - connection problems should default to UNKNOWN, overridable > by a switch (some people want to know if the http-based service fails > too). I'd like to have this default behaviour for check_nrpe, check_nt, > check_snmp and check_by_ssh too (it's likely the case already for some > of these plugins), in a major release. > ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________________ 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 e-mail and any attached documents may contain confidential or proprietary information. If you are not the intended recipient, please advise the sender immediately and delete this e-mail and all attached documents from your computer system. Any unauthorised disclosure, distribution or copying hereof is prohibited." " Ce courriel et les documents qui y sont attaches peuvent contenir des informations confidentielles. Si vous n'etes pas le destinataire escompte, merci d'en informer l'expediteur immediatement et de detruire ce courriel ainsi que tous les documents attaches de votre systeme informatique. Toute divulgation, distribution ou copie du present courriel et des documents attaches sans autorisation prealable de son emetteur est interdite." # -- Thomas I received a duplicate of the email I posted. The path until sourceforge is the same as the correct email received from sourceforge, then move on to snecma.fr which in turn send it back to my mail server. It looks like a minsonfigured user's relay sending messages back to their source. Anyone noticed something similar? On 22/09/08 10:13 PM, Thomas Guyot-Sionnest wrote: > On 22/09/08 11:32 AM, David Diffenbaugh wrote: >> I have a need for a plugin which would have the functionality proposed >> below. Before I start working on it does anyone have any suggestions or >> requests? Is anyone already working on something similar? > >> check_byhttp will be a nagios plugin which retrieves content from a >> specified host using http. This file will contain a status state >> (OK,WARN,CRITICAL) and a status message. The plugin will return the state >> and status message that is listed in the retrieved content. It also will >> check the last modified time of the document, as reported by the >> Last-Modified field, to ensure the status is current. If the file is >> current it will report the status. If the file is not current it will >> return a state and status message reporting that the document is not up to >> date based on time thresh-hold arguments passed to the plugin. > > I've been thinking about that lately (I probably even posted about it in > this mailing list...) - you should be able to define the string match > that cause ok, warn and crit, and possibly print the text returned. > > It should probably also be able to do SOAP and/or XMLRPC requests (I'm > not very knowledgeful in this area so correct me if needed) using a > published API so that any web-based plugin could be written to commutate > to check_by_http using this standard API. > > The real problem lies in code duplication. The current check_httl should > be made into functions that are callable by check_by_http too. > Alternatively, it had been suggested we could use curl (and likely move > check_http to use curl as well), which would let us forget about the > details of the http protocol and concentrate on coding functionality > instead. > >> This plugin only will work when http is functioning correctly on the >> server the file is hosted on, and will assume this is always the case. >> The server you are connecting to should be monitored by check_http. > > Obviously - connection problems should default to UNKNOWN, overridable > by a switch (some people want to know if the http-based service fails > too). I'd like to have this default behaviour for check_nrpe, check_nt, > check_snmp and check_by_ssh too (it's likely the case already for some > of these plugins), in a major release. > ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________________ 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 e-mail and any attached documents may contain confidential or proprietary information. If you are not the intended recipient, please advise the sender immediately and delete this e-mail and all attached documents from your computer system. Any unauthorised disclosure, distribution or copying hereof is prohibited." " Ce courriel et les documents qui y sont attaches peuvent contenir des informations confidentielles. Si vous n'etes pas le destinataire escompte, merci d'en informer l'expediteur immediatement et de detruire ce courriel ainsi que tous les documents attaches de votre systeme informatique. Toute divulgation, distribution ou copie du present courriel et des documents attaches sans autorisation prealable de son emetteur est interdite." # -- Thomas From duncan.ferguson at altinity.com Tue Sep 23 16:55:58 2008 From: duncan.ferguson at altinity.com (Duncan Ferguson) Date: Tue, 23 Sep 2008 15:55:58 +0100 Subject: [Nagiosplug-devel] check_icmp query Message-ID: <4029BCDE-2046-431C-B72C-03A0A1DB8276@altinity.com> Hiya, I am trying to use check_icmp as a host check for monitoring a server in a different continent over a network that has the occasional glitch, but I cannot get the options right. Basically, what I am trying to achieve is to get check_icmp to send say 5 packets, with a delay of a second between each packet and if it gets 1 packet back then the host is up and happy - 99% of the time there is 0% packet loss with an rta of 44ms or less, but 0.75% of the time there is 10% loss and 0.25% of the time there is 100% loss. When there is loss the next moment everything is ok again so i want the hsst check to be a little more resilient. What is the correct way of specifying this? Using the '-i' and '-I' switches doesnt seem to affect sending the packets (all the packets seem to be sent at once or with no delay between them rather that have a one second delay that i specify). check_icmp -H -n 10 -m 1 -w 1000.0,80% -c 5000.0,100% -i 1s -I 1s -l 128 I don't understand networking well enough to go through the code and work out whether what I am trying to do is unreasonable, its missing functionality or its a bug. Any pointers gratefully accepted. Duncs From ae at op5.se Tue Sep 23 23:23:05 2008 From: ae at op5.se (Andreas Ericsson) Date: Tue, 23 Sep 2008 23:23:05 +0200 Subject: [Nagiosplug-devel] check_icmp query In-Reply-To: <4029BCDE-2046-431C-B72C-03A0A1DB8276@altinity.com> References: <4029BCDE-2046-431C-B72C-03A0A1DB8276@altinity.com> Message-ID: <48D95E39.1070507@op5.se> Duncan Ferguson wrote: > Hiya, > > I am trying to use check_icmp as a host check for monitoring a server > in a different continent over a network that has the occasional > glitch, but I cannot get the options right. > > Basically, what I am trying to achieve is to get check_icmp to send > say 5 packets, with a delay of a second between each packet and if it > gets 1 packet back then the host is up and happy - 99% of the time > there is 0% packet loss with an rta of 44ms or less, but 0.75% of the > time there is 10% loss and 0.25% of the time there is 100% loss. > When there is loss the next moment everything is ok again so i want > the hsst check to be a little more resilient. > > What is the correct way of specifying this? Using the '-i' and '-I' > switches doesnt seem to affect sending the packets (all the packets > seem to be sent at once or with no delay between them rather that have > a one second delay that i specify). > > check_icmp -H -n 10 -m 1 -w 1000.0,80% -c 5000.0,100% -i 1s > -I 1s -l 128 > > I don't understand networking well enough to go through the code and > work out whether what I am trying to do is unreasonable, its missing > functionality or its a bug. > What you're trying is not unreasonable at all, and check_icmp has special support for it, if you call it as a program named "check_host" instead of check_icmp. cd /your/plugin/path ln -s check_icmp check_host ./check_host -n 5 -i 1s -H will do exactly what you want, and when you get a response within 44ms it will take roughly 47ms of runtime to complete. Note that the output is slightly different when it's running in host check mode, as it will stop sending ICMP packets (or even listening for them) after having received one, so there's no packet loss value, only an RTT (round trip time, as opposed to round trip average). Turning the above instructions into a nagios command and then utilizing that for host checks is left as an exercise to the reader ;-) -- Andreas Ericsson andreas.ericsson at op5.se OP5 AB www.op5.se Tel: +46 8-230225 Fax: +46 8-230231 From duncan.ferguson at altinity.com Wed Sep 24 11:13:11 2008 From: duncan.ferguson at altinity.com (Duncan Ferguson) Date: Wed, 24 Sep 2008 10:13:11 +0100 Subject: [Nagiosplug-devel] check_icmp query In-Reply-To: <48D95E39.1070507@op5.se> References: <4029BCDE-2046-431C-B72C-03A0A1DB8276@altinity.com> <48D95E39.1070507@op5.se> Message-ID: On 23 Sep 2008, at 22:23, Andreas Ericsson wrote: > Duncan Ferguson wrote: >> >> Basically, what I am trying to achieve is to get check_icmp to send >> say 5 packets, with a delay of a second between each packet and if it >> gets 1 packet back then the host is up and happy - 99% of the time >> there is 0% packet loss with an rta of 44ms or less, but 0.75% of the >> time there is 10% loss and 0.25% of the time there is 100% loss. >> When there is loss the next moment everything is ok again so i want >> the hsst check to be a little more resilient. >> > What you're trying is not unreasonable at all, and check_icmp has > special > support for it, if you call it as a program named "check_host" instead > of check_icmp. That seems absolutely perfect - thanks. I had seen the different names within the code but couldn't work out what each one did. Thanks for your help, Duncs From alvin.chang at openx.org Wed Sep 24 12:02:11 2008 From: alvin.chang at openx.org (Alvin Chang) Date: Wed, 24 Sep 2008 11:02:11 +0100 Subject: [Nagiosplug-devel] check_mysql_query with $SERVICEPERFDATA$ Message-ID: <7d60a8530809240302p4f9a4427h8f5c0a9dc871cbde@mail.gmail.com> Hi All: I know I can probably wrap this with NRPE or Perl, but wouldn't it be best if check_mysql_query returns results in a way that the returned value has $SERVICEPERFDATA$ in it? Thanks, -- Alvin Chang Linux Systems Administrator OpenX Limited Skype: alvin.chang_at_openx.org IRC: #openx on freenode.net -------------- next part -------------- An HTML attachment was scrubbed... URL: From noreply at sourceforge.net Mon Sep 29 16:20:32 2008 From: noreply at sourceforge.net (SourceForge.net) Date: Mon, 29 Sep 2008 14:20:32 +0000 Subject: [Nagiosplug-devel] [ nagiosplug-Bugs-2136116 ] make failure on solaris 9 Message-ID: Bugs item #2136116, was opened at 2008-09-29 16:20 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=397597&aid=2136116&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: Compilation Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: tao71 (tao71) Assigned to: Nobody/Anonymous (nobody) Summary: make failure on solaris 9 Initial Comment: I'm trying to compile nagios-plugins-1.4.13. configure is fine, but make fails: check_http.c:64: error: syntax error before '*' token check_http.c:64: warning: data definition has no type or storage class make[2]: *** [check_http.o] Error 1 make[2]: Leaving directory `/export/home/nagios/nagios-plugins-1.4.13/plugins' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/export/home/nagios/nagios-plugins-1.4.13' make: *** [all] Error 2 I read through all bug reports and found a lot of hints, but none of them worked for me. Even with the latest make (3.81), gcc (3.4.6) and libiconv (1.11) downloaded from sunfreeware didn't help. I also tried with different versions of plugins (1.4.12 and 1.4.13), but I get the same errors. And because I read in one of the closed bugs, to use solaris make, I tried it with /usr/local/bin at the beginning of PATH and in the end. But even this didn't make any change. As I don't have a lot of experience with compiling, I'm stuck and need help. (On Linux it all worked fine, but not on Solaris...) Please tell me if you need any additional information. Thanks in advance. Marc ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=397597&aid=2136116&group_id=29880 From noreply at sourceforge.net Tue Sep 30 06:43:20 2008 From: noreply at sourceforge.net (SourceForge.net) Date: Tue, 30 Sep 2008 04:43:20 +0000 Subject: [Nagiosplug-devel] [ nagiosplug-Bugs-2136116 ] make failure on solaris 9 Message-ID: Bugs item #2136116, was opened at 2008-09-29 10:20 Message generated for change (Comment added) made by dermoth You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=397597&aid=2136116&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: Compilation Group: None >Status: Pending Resolution: None Priority: 5 Private: No Submitted By: tao71 (tao71) Assigned to: Nobody/Anonymous (nobody) Summary: make failure on solaris 9 Initial Comment: I'm trying to compile nagios-plugins-1.4.13. configure is fine, but make fails: check_http.c:64: error: syntax error before '*' token check_http.c:64: warning: data definition has no type or storage class make[2]: *** [check_http.o] Error 1 make[2]: Leaving directory `/export/home/nagios/nagios-plugins-1.4.13/plugins' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/export/home/nagios/nagios-plugins-1.4.13' make: *** [all] Error 2 I read through all bug reports and found a lot of hints, but none of them worked for me. Even with the latest make (3.81), gcc (3.4.6) and libiconv (1.11) downloaded from sunfreeware didn't help. I also tried with different versions of plugins (1.4.12 and 1.4.13), but I get the same errors. And because I read in one of the closed bugs, to use solaris make, I tried it with /usr/local/bin at the beginning of PATH and in the end. But even this didn't make any change. As I don't have a lot of experience with compiling, I'm stuck and need help. (On Linux it all worked fine, but not on Solaris...) Please tell me if you need any additional information. Thanks in advance. Marc ---------------------------------------------------------------------- >Comment By: Thomas Guyot (dermoth) Date: 2008-09-30 00:43 Message: You seem to have a broken SSL installation (missing header files). You can either: 1. Configure without ssl support (no https, SSL, certificate or TLS checks): ./configure --without-openssl 2. Fix/install openssl. According to your config.log it looks like it's using /usr/local/ssl as your openssl installation. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=397597&aid=2136116&group_id=29880