Stange problem checking https

[DM]

-----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=123ABC123

> 

> 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=123ABC123' -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.

 

-yes, return code 0 (OK)

 

>Also may want to try a newer check_http - lots of changes since 1.2.9-4 

>release.

 

-yes, I've tried the latest release (check_http (nagios-plugins 1.3.0-beta2) 1.12), but that version seems to have a problem with SSL. The same exact syntax that works fine under version 1.2.9-4, returns this error under 1.3.0-beta2:

 

$./check_http \

>         -S -I hosta.mydomain.com \

>         -H www.mydomain.com \

>         -u '/test/test?act=login&id=123ABC123' -t 40 -e 200

check_http: invalid option - SSL is not available

 

any other thoughts?

 

-David
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://www.monitoring-lists.org/archive/users/attachments/20030128/ac434708/attachment.html>