Geting warning, but can't find reason

Karl DeBisschop karl at debisschop.net
Thu Nov 7 14:02:44 CET 2002


On Thu, 2002-11-07 at 08:29, msimon at adartis.de wrote:
> I'm using nagios to check if some HTTP-Pages are still up and reachable.
> At the moment I am monitoring two pages, on of them (A) is just a simple
> index.html without frames,etc.
> 
> The other one (B) has frames on it.
> 
> The checkcommands for that pages are:
> A:
> define command{
>         command_name    check_http_A
>         command_line            $USER1$/check_http -I 10.100.0.3 -s 
> entsteht }
> 
> 
> B:
> define command{
>         command_name    check_http_A
>         command_line            $USER1$/check_http -I 10.100.0.7 -u 
> home.html -s neugierig }


try:

$USER1$/check_http -I 10.100.0.7 -u /home.html -s neugierig

(note the forward slash)

> 
> While bothe pages are up and reachable by browser, 
> nagios tells me that page A is up and o.k.
> while page B gives back a warning-message and "HTTP WARNING: HTTP/1.1 400 Bad Request"
> 
> Any ideas what the reason might be ??
> 
>  
> 
> 
> 
> 
> Marco Simon 
> Consultant
> 
> adARTIS e.K.
> Im Hansengarten 9
> D-56412 Hübingen 
> Tel: 02602/10688-10 
> 
> www.adartis.de
> msimon at adartis.de 




-------------------------------------------------------
This sf.net email is sponsored by: See the NEW Palm 
Tungsten T handheld. Power & Color in a compact size!
http://ads.sourceforge.net/cgi-bin/redirect.pl?palm0001en




More information about the Users mailing list