[Nagiosplug-help] check_http - getting full response

[Harper Mann]

Sorry, but check_http doesn't work that way.  It returns an error message
but not the GET output:

./check_http -H www.itgroundwork.com -u /about/contact.html -s "FAIL" -w 8
-c 10 -L
<A HREF="http://www.itgroundwork.com:80/about/contact.html"
target="_blank">HTTP CRITICAL: string not found</A>|time=  0.072

Note that you can get the link to the problem page which can be clicked on
to see what is going on.

You could modify check_http to give the output, and it can be HTML, but the
Nagios GUI isn't really set up to display a page of output.  It's intended
to show a result string of < 400 (I forget the exact number) characters and
will truncate > than the set amount.

You can also use the plugin "urlize" to set your URL which is the newer way
to do it.

- Harper

Harper Mann
Groundwork Open Source Solutions
510-599-2075 (cell)


-----Original Message-----
From: nagiosplug-help-admin at lists.sourceforge.net
[mailto:nagiosplug-help-admin at lists.sourceforge.net] On Behalf Of Rajini
Sent: Tuesday, September 14, 2004 12:44 PM
To: nagiosplug-help at lists.sourceforge.net
Subject: [Nagiosplug-help] check_http - getting full response

I am new to nagios.
I want to use check_http to go after a service. 

/check_http -H $HOSTADDRESS$ -u $ARG1$ -s $ARG2$ -w $ARG3$ -c $ARG4$

I set $ARG2 = "SUCCESS".

If the check fails, I want the entire output ( the failure cases) to be sent

as part of notification.

How do I configure this?

- Thanks 
Rajini



-------------------------------------------------------
This SF.Net email is sponsored by: thawte's Crypto Challenge Vl
Crack the code and win a Sony DCRHC40 MiniDV Digital Handycam
Camcorder. More prizes in the weekly Lunch Hour Challenge.
Sign up NOW http://ad.doubleclick.net/clk;10740251;10262165;m
_______________________________________________
Nagiosplug-help mailing list
Nagiosplug-help at lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nagiosplug-help
::: Please include plugins version (-v) and OS when reporting any issue. 
::: Messages without supporting info will risk being sent to /dev/null