Hello,

I'm having a problem monitoring some services using check_http.  I'm
using the 1.4.16 release of the plugins as distributed from Repoforge.org.

I think it's related to the same issue that Janet Sullivan posted and
Holger Weiss responded to on the Nagios-users mailing list in June
2009:

http://www.mail-archive.com/nagios-users@lists.sourceforge.net/msg27053.html

Basically, the deal is that I'm looking at services that use keepalive
without being asked to and violate HTTP in all sorts of other interesting
ways.  For example, the embedded web server in an Areca hardware RAID
controller:

$ telnet areca 80
Trying IP.AD.DR.ESS...
Connected to areca.
Escape character is '^]'.
GET / HTTP/1.1 <-- followed by single carriage return
HTTP/1.1 401 Unauthorized
Content-Type: text/html
WWW-Authenticate: Digest realm="Raid Console", qop="auth", 
nonce="0c7598e0fd182f05acdef23442245789"
Content-Length: 0

The second carriage return produces a web page - with additional
HTTP headers...

A warning for the "unauthorized" state would be more useful information
in monitoring than the critical timeout.

Another oddity I've seen is that trying to monitor the availability
of an HP ILO results in a timeout - doing a basic GET such as by
check_http doesn't produce any response, even though the service is
responding all right if connected to with a web browser.

All ideas welcome...

------------------------------------------------------------------------------
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdyn_sfd2d_oct
_______________________________________________
icinga-users mailing list
icinga-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/icinga-users

Reply via email to