Stange problem checking https
DM
nagios.dm at wrhambrecht.com
Tue Feb 4 23:33:59 CET 2003
Subhendu,
Here's the output you requested:
$/apps/nagios/libexec> ./check_http -V
check_http (nagios-plugins 1.3.0-beta2) 1.12
$/apps/nagios/libexec> /apps/nagios/libexec/check_http -v -S -I hosta.mydomain.com -H intranet.mydomain.com -u '/eqo/auction?act=login&cusip=45673456' -t 40 -e 200
Page is 5882 characters
STATUS: HTTP/1.0 200 OK
**** HEADER ****
Server: Resin/2.1.s021217
Pragma: no-cache
Expires: -1
Cache-Control: no-cache
P3P: CP="NON DSP COR CURa ADMa IVAa IVDa CONa OUR NOR UNI PUR COM NAV STA"
Set-Cookie: JSESSIONID=aKepta_IHR-4; Path=/
Content-Type: text/html
Date: Tue, 04 Feb 2003 21:58:21 GMT
**** CONTENT ****
<html>
<head>
<script src="/eqo/web-content/jscript/eqo.js"></script>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<title>OpenFollowOn 45673456: Login</title>
</head>
<body bgcolor="#ffffff" link="#0000ff" vlink="#0000ff" alink="#0000ff"
marginwidth="0" marginheight="0" topmargin="0" leftmargin="0"
onLoad="javascript:assertTopFrame();">
<map name="Map">
<area shape="rect" coords="111,2,164,21"
href="javascript:SpawnWindow('/eqo/terms?cusip=45673456','termsWin','102014252910118172714');">
<area shape="rect" coords="169,2,217,22"
href="javascript:SpawnWindow('/eqo/static?class=perDeal&cusip=45673456&content=rules','contentWin','1020142529
10118172714');">
<area shape="rect" coords="222,2,308,21"
href="javascript:SpawnWindow('/eqo/static?class=perProduct&cusip=45673456&content=hiw/overview','contentWin','
102014252910118172714');">
<area shape="rect" coords="313,2,351,21"
href="javascript:SpawnWindow('/eqo/static?class=perProduct&cusip=45673456&content=hiw/faq','contentWin','10201
4252910118172714');">
<area shape="rect" coords="356,2,433,21"
href="javascript:SpawnWindow('/eqo/static?class=perDeal&cusip=45673456&content=contacts','contentWin','1020142
52910118172714')">
</map>
<table border="0" cellspacing="0" cellpadding="0" width="100%"
background="/eqo/web-content/images/horiz_bg_pat.gif">
<tr>
<td align="left" valign="middle"><img src="/eqo/web-content/images/logo_nav_02.gif" vspace="4"></td>
<td> </td>
<td align="right" valign="middle"><img src="/eqo/web-content/images/openfollowon_logo.gif" vspace="4"></td>
</tr>
</table>
<table border="0" cellspacing="0" cellpadding="0" width="100%">
<tr>
<td align="center" valign="bottom" colspan="3"><img src="/eqo/web-content/images/navbar_deal.gif"
usemap="#Map" border="0"></td>
</tr>
</table>
<table border="0" cellpadding="1" cellspacing="0" width="100%" bordercolor="#cccccc">
<tr>
<td bgcolor="#b5bcd6">
<font size="3" face="Verdana, Arial, Helvetica, sans-serif"><b>Login to the OpenFollowOn
Auction for:<br>
4,000,000 shares of Acme Inc.
(NASDAQ:ACME)</b></font></td>
<td align="right" bgcolor="#b5bcd6">
<font size="2" face="Verdana, Arial, Helvetica, sans-serif"><b>Current Time:
02/04/03, 04:58PM EST</b></font><br>
<font color="#cc0000" size="2" face="Verdana, Arial, Helvetica, sans-serif"><b>Auction open time:
02/04/03 at 05:00PM EST</b></font></td>
</tr>
<tr>
<td align="left" bgcolor="#b5bcd6">
<font color="#CC0000" size="2" face="Verdana, Arial, Helvetica, sans-serif"><b>
</b></font>
</td>
<td align="right" bgcolor="#b5bcd6">
<font size="2" face="Verdana, Arial, Helvetica, sans-serif">The auction is <b>
Not Open</b></font>
</td>
</tr>
</table>
<form method="POST" action="/eqo/auction" name="loginForm">
<table border="0" cellpadding="4" cellspacing="0" width="100%">
<tr>
<td bgcolor="#ffffff" width="20%" align="right">
<font size="2" face="Verdana, Arial, Helvetica, sans-serif"><b>User ID</b></font>
</td>
<td bgcolor="#ffffff">
<input type="text" size="30" maxlength="30" name="acct" value="">
</td>
</tr>
<tr>
<td bgcolor="#ffffff" width="20%" align="right">
<font size="2" face="Verdana, Arial, Helvetica, sans-serif"><b>Password</b></font>
</td>
<td bgcolor="#ffffff">
<input type="password" size="30" maxlength="30" name="securityKey" value="">
</td>
</tr>
<tr>
<td bgcolor="#ffffff" width="20%" align="right"> </td>
<td>
<input type="hidden" name="act" value="login">
<input type="hidden" name="cmd" value="exec">
<input type="hidden" name="cusip" value="45673456">
<input type="submit" name="goButton" value="Login">
</td>
</tr>
</table>
</form>
<table width="75%" border="0">
<tr>
<td>
<font color="#000000" size="2" face="Verdana, Arial, Helvetica, sans-serif"><a
href="javascript:SpawnWindow('/eqo/terms?cusip=45673456','termsWin','102014252910118172714');">
Click here to view Auction Terms</a>
</font><br><br>
</td>
<tr>
<td>
<font color="#cc0000" size="2" face="Verdana, Arial, Helvetica, sans-serif"><b>Very Important:</b>
After
submitting or changing a bid in the auction, you will always be asked for
<b>confirmation. </b>If you do not indicate confirmation by clicking a<b> confirmation button</b>,
your
bidding action will <b>not</b> be recorded by the system.</font><br><br>
</td>
</tr>
<tr>
<td>
<font color="#000000" size="2" face="Verdana, Arial, Helvetica, sans-serif"><b>Reminder:</b> Your
browser must
have "cookies" enabled in order to access the auction. If you have trouble accessing the system,
please contact
your local technical support personnel or <a
href="javascript:SpawnWindow('/eqo/static?class=perDeal&cusip=45673456&content=contacts','contentWin','1020142
52910118172714');">contact
us</a>.</font>
</td>
</tr>
</table>
<script>
document.loginForm.goButton.focus();
document.loginForm.acct.select();
</script>
</body>
</html>
HTTP OK: Status line output matched "200"
HTTP ok: HTTP/1.0 200 OK - 0.293 second response time |time= 0.293
$/apps/nagios/libexec> echo $?
0
> -----Original Message-----
> From: Subhendu Ghosh [mailto:sghosh at sghosh.org]
> Sent: Tuesday, February 04, 2003 1:18 PM
> To: nagios-users at lists.sourceforge.net
> Subject: Re: [Nagios-users] Stange problem checking https
>
>
>
> Can you post the command (add the verbose option) and the output...
>
> -sg
>
> On Fri, 31 Jan 2003, DM wrote:
>
> >
> > Following Subhendu's suggestion, I've installed the latest
> check_http plugin,
> > but unfortunately, Nagios is still issuing a "warning"
> status for a seemingly fine
> > reponse from the web server.
> >
> > check_http (nagios-plugins 1.3.0-beta2) 1.12
> >
> > Current Status: WARNING (Has been acknowledged)
> > Status Information: HTTP ok: HTTP/1.0 200 OK - 0.240 second
> response time
> > Current Attempt: 3/3
> > State Type: HARD
> > Last Check Type: ACTIVE
> > Last Check Time: 01-31-2003 10:55:22
> > Status Data Age: 0d 0h 2m 6s
> > Next Scheduled Active Check: 01-31-2003 11:00:22
> > Latency: < 1 second
> > Check Duration: < 1 second
> > Last State Change: 01-27-2003 10:27:32
> > Current State Duration: 4d 0h 29m 56s
> > Last Service Notification: 01-27-2003 12:27:32
> > Current Notification Number: 3
> > Is This Service Flapping? N/A
> > Percent State Change: N/A
> > In Scheduled Downtime? NO
> > Last Update: 01-31-2003 10:57:20
> >
> >
> > All details from below are still the same, with the
> exception that I now have the latest version of the
> > check_http plugin.
> >
> > Any ideas?
> >
> > -David
> >
> >
> > > -----Original Message-----
> > > From: Subhendu Ghosh [mailto:sghosh at sghosh.org]
> > > Sent: Monday, January 27, 2003 2:01 PM
> > > To: nagios-users at lists.sourceforge.net
> > > Subject: Re: [Nagios-users] Stange problem checking https
> > >
> > >
> > > On Mon, 27 Jan 2003, DM wrote:
> > >
> > > > Hi All,
> > > >
> > > > I've got a problem with Nagios returning a "warning status" when
> > > > checking https on a Resin http server. Resin is a
> servlet/JSP engine
> > > > which can also serve up static pages as well as dynamic.
> > > (details can be
> > > > had at http://www.caucho.com/resin/)
> > > >
> > > > The problem is that Nagios keeps generating a "warning"
> > > status for the
> > > > http service, even though the service is up. Nagios doesn't
> > > even seem to
> > > > indicate a problem, other than indicating a warning
> status. (i.e.
> > > > response time is good, etc.)
> > > >
> > > > The Resin server is serving up the https pages just
> fine. Hitting it
> > > > with different browsers (IE6, Konqueror) works fine.
> Also Nagios is
> > > > working fine with other web servers (Zeus, IIS). I've
> > > checked the syntax
> > > > and run the check_http manually with the command line and
> > > it works fine
> > > > too. The response from the plugin is always "HTTP ok:
> > > HTTP/1.0 200 OK -
> > > > 0 second response time"
> > > >
> > > > The only difference I can come up with is that the http
> > > response from
> > > > the Resin server comes back as "HTTP/1.0" as opposed to all
> > > the other
> > > > web servers which return a "HTTP/1.1" Could this be causing
> > > a problem
> > > > for Nagios?
> > > >
> > > > Below are full details about platforms, versions, relevant
> > > lines from
> > > > config files, etc. As mentioned above, this Nagios
> config works just
> > > > fine with my other servers.
> > > >
> > > > Any ideas are appreciated.
> > > >
> > > > -David
> > > >
> > > >
> > > > Nagios version:
> > > >
> > > > Nagios 1.0
> > > > Copyright (c) 1999-2002 Ethan Galstad (nagios at nagios.org)
> > > > Last Modified: 11-24-2002
> > > > License: GPL
> > > >
> > > > Nagios server is running on Solaris 8.0 with latest
> > > Maintenance Updates/ patch
> > > > clusters.
> > > >
> > > > check_http plugin version:
> > > >
> > > > admin at nagios:>check_http -V
> > > > check_http (netsaint-plugins 1.2.9-4) 1.32.2.6
> > > >
> > > > services.cfg:
> > > >
> > > > check_command
> > > >
> check_https!hosta.mydomain.com!/test/test?act=login&id=45673456
> > > >
> > > > commands.cfg:
> > > >
> > > > # 'check_https' command definition
> > > > define command{
> > > > command_name check_https
> > > > command_line /apps/nagios/libexec/check_http -S
> > > -I $HOSTADDRESS$ -H $
> > > > ARG1$ -u $ARG2$ -t 40 -e 200
> > > > }
> > > >
> > > > hosts.cfg:
> > > >
> > > > # 'hosta' host definition
> > > > define host{
> > > > use generic-host ;
> > > Name of host template
> > > > to use
> > > >
> > > > host_name hosta
> > > > alias AliasA
> > > > address 2.3.4.5
> > > > parents parenta
> > > > check_command check-host-alive
> > > > max_check_attempts 10
> > > > notification_interval 120
> > > > notification_period normal
> > > > notification_options d,u,r
> > > > }
> > > >
> > > >
> > > > Running the check_http command manually using the
> > > > same parameters that Nagios uses, works fine:
> > > >
> > > > check_http \
> > > > -S -I hosta.mydomain.com \
> > > > -H web.mydomain.com \
> > > > -u '/test/test?act=login&id=45673456' -t 40 -e 200
> > > >
> > > > It returns a normal status:
> > > >
> > > > "HTTP ok: HTTP/1.0 200 OK - 0 second response time"
> > > >
> > > > >From the "Service State Information" page on Nagios:
> > > >
> > > > Current Status: WARNING
> > > > Status Information: HTTP ok: HTTP/1.0 200 OK - 0 second
> > > response time
> > > > Current Attempt: 3/3
> > > > State Type: HARD
> > > > Last Check Type: ACTIVE
> > > > Last Check Time: 01-27-2003 12:07:23
> > > > Status Data Age: 0d 0h 2m 11s
> > > > Next Scheduled Active Check: 01-27-2003 12:12:23
> > > > Latency: 1 second
> > > > Check Duration: < 1 second
> > > > Last State Change: 01-27-2003 10:27:32
> > > > Current State Duration: 0d 1h 42m 2s
> > > > Last Service Notification: 01-27-2003 11:27:32
> > > > Current Notification Number: 2
> > > > Is This Service Flapping? N/A
> > > > Percent State Change: N/A
> > > > In Scheduled Downtime? NO
> > > > Last Update: 01-27-2003 12:09:22
> > > >
> > > > >From the "Alert History" on Nagios:
> > > >
> > > > [01-27-2003 10:27:32] SERVICE ALERT:
> > > hosta;HTTPS;WARNING;HARD;3;HTTP ok: HTTP/1.0 200 OK - 0
> > > second response time
> > > > [01-27-2003 10:26:32] SERVICE ALERT:
> > > hosta;HTTPS;WARNING;SOFT;2;HTTP ok: HTTP/1.0 200 OK - 0
> > > second response time
> > > > [01-27-2003 10:25:33] SERVICE ALERT:
> > > hosta;HTTPS;WARNING;SOFT;1;HTTP ok: HTTP/1.0 200 OK - 1
> > > second response time
> > > >
> > > >
> > >
> > >
> > >
> > > On the command line - do n "echo $?" after the plugin to
> see what the
> > > return code is.
> > >
> > > Also may want to try a newer check_http - lots of changes
> > > since 1.2.9-4
> > > release.
> > >
> > > --
> > > -sg
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://www.monitoring-lists.org/archive/users/attachments/20030204/32231b2b/attachment.html>
More information about the Users
mailing list