Beginer questions about check_http

[Cosmin Neagu]

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.

-- 
Cosmin Neagu
NOC Team Leader
Str. I. G. Duca nr 36
Otopeni, Judetul Ilfov, 075100 Romania
Tel: 021 303 3159 / 0732 669 193
www.omnilogic.ro

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://www.monitoring-lists.org/archive/users/attachments/20100114/dd9b5e48/attachment.html>
-------------- next part --------------
------------------------------------------------------------------------------
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
-------------- next part --------------
_______________________________________________
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