<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=iso-8859-1">
<META content="MSHTML 6.00.2800.1126" name=GENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=#f1f0ed>
<DIV><FONT face=Arial size=2>> -----Original Message-----<BR>> From: Karl
DeBisschop [mailto:karl@debisschop.net]<BR>> Sent: Sunday, February 02, 2003
10:23 AM<BR>> To: DM<BR>> Cc: <A
href="mailto:nagios-users@lists.sourceforge.net">nagios-users@lists.sourceforge.net</A><BR>>
Subject: Re: [Nagios-users] Stange problem checking https<BR>> <BR>>
<BR>> On Sat, 2003-02-01 at 20:09, DM wrote:<BR>> > Hi Karl,<BR>>
> <BR>> > Unfortunately the app in question is on an intranet and
not publicly<BR>> > available.<BR>> ><BR>> > With your
direction, I'll be happy to perform additional diagnostics<BR>> > and send
you the output.<BR>> <BR>> I was hoping to save you the compile etc. But,
alas, I cannot.<BR>> <BR>> My first step would be to download the current
CVS tree, build the<BR>> plugins, and try that. As I had noted, the http
plugin has <BR>> been revised<BR>> several times, and some possibly
relevent code was fixed.<BR></FONT></DIV>
<DIV><FONT face=Arial size=2>OK, I downloaded the current CVS tree and built the
plugins. Unfortunately, I think the new check_http module ((nagios-plugins
1.3.0-beta2) 1.19 )has a bug in it which prevents the SSL option from working at
all:</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>$ ./check_http -w 5 -c 10 <A
href="http://www.verisign.com">www.verisign.com</A><BR>HTTP ok: HTTP/1.1 200 OK
- 0.354 second response time |time= 0.354</FONT></DIV><FONT
face=Arial size=2>
<DIV><BR>$ ./check_http -w 5 -c 10 --ssl <A
href="http://www.verisign.com">www.verisign.com</A><BR>Segmentation Fault</DIV>
<DIV> </DIV>
<DIV>gdb ./check_http<BR>(gdb) run -w 5 -c 10 --ssl <A
href="http://www.verisign.com">www.verisign.com</A><BR>Starting program:
/temp/nagios/libexec/./check_http -w 5 -c 10<BR>--ssl <A
href="http://www.verisign.com">www.verisign.com</A></DIV>
<DIV> </DIV>
<DIV>Program received signal SIGSEGV, Segmentation fault.<BR>asprintf (ptr=0x0,
format=0x17290 "%s") at
snprintf.c:836<BR>836
*ptr = NULL;<BR>(gdb) backtrace<BR>#0 asprintf (ptr=0x0, format=0x17290
"%s") at snprintf.c:836<BR>#1 0x13d80 in connect_SSL () at
check_http.c:923<BR>#2 0x13aa0 in check_http () at
check_http.c:552<BR>#3 0x1218c in main (argc=168960, argv=0x0) at
check_http.c:271<BR>(gdb) <BR></FONT></DIV>
<DIV><FONT face=Arial size=2>Looks like the connect_SSL function is sending a
null pointer to asprintf, making it segfault.</DIV>
<DIV> </DIV>
<DIV>Since I've verified earlier on that check_http is indeed returning the
correct value to Nagios,</DIV>
<DIV>I don't think the issue here is specifically with the check_http plugin,
but rather something</DIV>
<DIV>with how Nagios deals with this particular host/service.</DIV>
<DIV> </DIV></FONT></BODY></HTML>