Nagios Check_http Error

Contents Nagios Check_http Download Nagios Check Url Nagios Check_http String

(c) 1999-2013 Monitoring Plugins Development Team This plugin tests the HTTP service on the specified host. It can test normal (http) and secure (https) servers, follow redirects, search for strings and regular expressions, check connection times, and report on certificate expiration nagios check_http service example times. Usage: check_http -H | -I [-u ] [-p ] [-J

Nagios Check_http Download

] [-K ] [-w ] [-c ] [-t ] [-L] [-E] [-a auth] [-b proxy_auth] nagios check_http post example [-f ] [-e ] [-d string] [-s string] [-l] [-r | -R ] [-P string] [-m :] [-4|-6] [-N] [-M ] [-A string] [-k string] [-S ] [--sni] [-C [,]] [-T ] nagios check http authentication example [-j method] NOTE: One or both of -H and -I must be specified Options: -h, --help Print detailed help screen -V, --version Print version information --extra-opts=[section][@file] Read options from an ini file. See https://www.monitoring-plugins.org/doc/extra-opts.html for usage and examples. -H, --hostname=ADDRESS Host name argument for servers using host headers (virtual host) Append a port to include it in the header (eg: example.com:5000) -I, --IP-address=ADDRESS IP address or name (use

Nagios Check Url

numeric address if possible to bypass DNS lookup). -p, --port=INTEGER Port number (default: 80) -4, --use-ipv4 Use IPv4 connection -6, --use-ipv6 Use IPv6 connection -S, --ssl=VERSION[+] Connect via SSL. Port defaults to 443. VERSION is optional, and prevents auto-negotiation (2 = SSLv2, 3 = SSLv3, 1 = TLSv1, 1.1 = TLSv1.1, 1.2 = TLSv1.2). With a '+' suffix, newer versions are also accepted. --sni Enable SSL/TLS hostname extension support (SNI) -C, --certificate=INTEGER[,INTEGER] Minimum number of days a certificate has to be valid. Port defaults to 443 (when this option is used the URL is not checked.) -J, --client-cert=FILE Name of file that contains the client certificate (PEM format) to be used in establishing the SSL session -K, --private-key=FILE Name of file containing the private key (PEM format) matching the client certificate -e, --expect=STRING Comma-delimited list of strings, at least one of them is expected in the first (status) line of the server response (default: HTTP/1.) If specified skips all other status line logic (ex: 3xx, 4xx, 5xx processing) -d, --header-string=STRING String to expect in the response headers -s, --string=STRING String to expect in the content -u, --url=PATH URL to GET or POST (default: /) -P, --post=STRING URL encoded http POST d

[ date ] [ thread ] [ subject ] [ author ] Thank you Thomas, I actually tried that already (I think I tried every single option with check_http) What I can't figure out is why would nagios report an http 500 and running exactly the same nagios check_http different port command from a shell it works perfectly fine: This is the HTTP Check Service CGI nagios check http url for myhost.mydomain.net: Status Information:HTTP CRITICAL: HTTP/1.1 500 Internal Server Error - 720 bytes in 0.201 second response time Performance Data:time=0.201368s;3.000000;5.000000;0.000000 size=720B;;;0 This is

Nagios Check_http String

from a shell: ./check_http -H myhost.mydomain.net HTTP OK: HTTP/1.1 200 OK - 279 bytes in 0.002 second response time |time=0.001871s;;;0.000000 size=279B;;;0 I tried with Curl and that works (I get a 200). Does anyone know about any kind https://www.monitoring-plugins.org/doc/man/check_http.html of debug I can do? I'm not sure where to start as everything looks fine from a command line. Regards. Javier. On Mon, Jan 24, 2011 at 11:32 PM, Thomas Guyot-Sionnest wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > On 11-01-21 10:46 AM, Javier D'Ovidio wrote: >> Hello All: >> This is my first post to this mailing list so be nice with me :P I'm >> facing a few https://www.monitoring-plugins.org/archive/help/2011-January/006078.html issues with the check_http plugin. I'm checking an apache >> on a host using check_http. Looking at the Nagios CGI I can see the >> service in a CRITICAL state with the following information: >> >> Status Information:HTTP CRITICAL: HTTP/1.1 500 Internal Server Error - >> 720 bytes in 0.201 second response time >> Performance Data:time=0.201368s;3.000000;5.000000;0.000000 size=720B;;;0 >> >> >> Now, when I run the check_http on the command line, I get a different answer: >> >> ./check_http -H myhost.mydomain.net >> HTTP OK: HTTP/1.1 200 OK - 279 bytes in 0.002 second response time >> |time=0.001871s;;;0.000000 size=279B;;;0 >> >> This is my command definition: >> >> define command{ >> command_name check_site_http >> command_line $USER1$/check_http -H $HOSTADDRESS$ -w 5 -c 7 -t 8 >> } >> >> >> As you can see, its very simple. Did anyone seen something like this >> in the past? I have no idea why this might be happening > > $HOSTADDRESS$ is usually the IP-address of the server in Nagios. The > general ways of using check_http are: > > 1. -H -I > > where vhost is the hostname generally used to access the server and -I > is the server's IP, This is one way one can test an individual server in > a pool of load-balancer servers. > > 2. -H > > Where hostname

• All times are UTC - 6 hours [ DST ] Powered by phpBB © 2000, 2002, 2005, 2007 phpBB Group

just setting up Nagios for the first time.  I have an IIS server that is set to require HTTPS. The check_http command gives the following as expected: HTTP WARNING: HTTP/1.1 403 Forbidden - 1609 bytes in 0.041 second response time. So i created a new command definition called check_https and added the -S parameter (found here: http://nagiosplugins.org/man/check_http) ; to the command. Now i am getting an error check_http: Invalid option - SSL is not available

This is my command definition: # 'check_http' with SSL command switch define command{         command_name    check_https         command_line    $USER1$/check_http -I $HOSTADDRESS$ -S $ARG1$         } This is my service definition: define service{     use        generic-service        ; Inherit default values from a template     host_name        reg.ymcasv.org     service_description    HTTP     check_command    check_https     } OpenSSL is installed and i re-installed the plugins to make sure ssl was installed before they were. Any ideas? is there some openSSL config that i might be missing? Thanks. Reply Subscribe View Best Answer RELATED TOPICS: Nagios Check_ldap & check_ldaps Nagios "conditional results" Your most useful Nagios checks, I want to know!   9 Replies Thai Pepper OP Best Answer Opie7423 May 23, 2011 at 3:02 UTC Does your check_https look like this? http://pastebin.com/xaGJY1GF This is my command definition: define command{ # 'check_https' command definition         command_name    check_https         command_line    $USER1$/check_https $ARG1$         } 0 Chipotle OP quickliketurtle May 23, 2011 at 3:14 UTC I just add the -S parameter to the check_http command. I don't have a separate file like the one you linked.  I'm guessing that is my problem. So i will create a check_https file... What is the extension? and where do i put it. Then i will update the command definition to match yours.