Beginer questions about check_http

Assaf Flatto nagios at flatto.net
Thu Jan 14 17:54:01 CET 2010


Cosmin Neagu wrote:
> Hello everybody,
>
> I'm using check_http to monitor a wab server where we have more than 3 
> web address. Like:
> www.example1.com
> www.example2.com
> www.example3.com...are all on the same server.
>
>
> Is there a way to check the status for each site? I'm a little 
> confused from reding the help of check_http, i have tried like:
> libexec/check_http -H 194.81.149.12 -p 80 --url=/www.example1.com
> libexec/check_http -H 194.81.149.12 -p 80 -P www.example1.com
> libexec/check_http -H 194.81.149.12 -p 80 -s www.example1.com
> But the output is not what i'm expecting.
>
> Can someone tell me if this is even posible?
>
> I think it should be something like this:
> cosmin at cacti-1:/usr/local/nagios> libexec/check_http -H 194.81.149.12 
> -p 80 *-u www.example1.com*
> HTTP WARNING: HTTP/1.1 400 Bad Request
>
> But it gives me bad request, and i don't know why.
> PS: of course that all the testing is done with the real web site and 
> the correct ip address, not exemple1.com.
>
The best way to do that is to query the websites with the FQDN in the 
host address :

libexec/check_http -H www.example.com -p 80

that will resolve and send the query to the server with the URL and will 
trigger the vhost reply on the target host .

Assaf




------------------------------------------------------------------------------
Throughout its 18-year history, RSA Conference consistently attracts the
world's best and brightest in the field, creating opportunities for Conference
attendees to learn about information security's most important issues through
interactions with peers, luminaries and emerging and established companies.
http://p.sf.net/sfu/rsaconf-dev2dev
_______________________________________________
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





More information about the Users mailing list