Problem with check_http

[Morris, Patrick]

Tata, Joseph wrote:
> I am in the process of deploying a new Nagios installation running 
> version 3.2.  I currently have v2.7 running on another machine and 
> have imported my config to the 3.2 server using NagiosQL.  So far 
> almost everything works, but I'm having a problem with any commands 
> which use the "check_http" option.
> We have a number of web applications which I'm checking with various 
> custom commands.  These commands usually check a specific javascript 
> page on the target server which queries the site's database back end 
> and returns "OK" if everything is working (this lets me ensure that 
> the webserver is able to access the database as well as serve web 
> requests).
>  
> My command syntax is:
>  
>  ./check_http -H <hostname or IP> -S -u '<name of the javascript 
> page>' -s OK -w 20 -c 30 -t 40
> This works completely fine on my 2.7 server, but always returns 
> "Connection refused HTTP CRITICAL - Unable to open TCP socket" when 
> run from the 3.2 server against the same target.
>  
> Any idea what could be going on here?

The most likely cause I can think of would be a routing misconfiguration 
on the new box.

Can you telnet to the application port (from that check definition, 
apparently 443) at the target host's address from that host?

------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day 
trial. Simplify your report design, integration and deployment - and focus on 
what you do best, core application coding. Discover what's new with
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
_______________________________________________
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