check_http problems

[Seth Hollist]

Actually it says Trying... forever.  I didn't realize a proxy server setting
could cause such a problem, but apparently that my very well may be the
problem.  I did try unsetting the proxy setting, but that didn't seem to
make a differance.  I guess I need to see if this machine is still allowed
to directly access the internet, or find some kind of work around for this
problem.

-----Original Message-----
From: Robert Nelson [mailto:rnelson at windchannel.com]
Sent: Tuesday, July 20, 2004 12:51 PM
To: Seth Hollist; nagios-users at lists.sourceforge.net
Subject: RE: [Nagios-users] check_http problems

> If I use lynx from the Nagios server that I run the check on 
> I'm able to access the site just fine.  I'm wondering if check_http 
> doesn't properly establish a connection with a sync packet, as the
> firewall on the web-server expects this.

As the other person said, it certainly does the proper TCP connection.
Try "telnet <hostip> 80" and see if that works - should bring up a blank
screen, as opposed to saying "Connecting..." forever.


This e-mail, including attachments, may include confidential and/or
proprietary information, and may be used only by the person or entity to
which it is addressed. If the reader of this e-mail is not the intended
recipient or his or her authorized agent, the reader is hereby notified that
any dissemination, distribution or copying of this e-mail is prohibited. If
you have received this e-mail in error, please notify the sender by replying
to this message and delete this e-mail immediately.


-------------------------------------------------------
This SF.Net email is sponsored by BEA Weblogic Workshop
FREE Java Enterprise J2EE developer tools!
Get your free copy of BEA WebLogic Workshop 8.1 today.
http://ads.osdn.com/?ad_id=4721&alloc_id=10040&op=click
_______________________________________________
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