Apache 2.0.48 gives core on startssl

[Gagan Puri <ga...@infosys.com>]

> Hi,
> 
> I have installed Apache 2.0.48 with enable-ssl option on Solaris 8.
> The server starts and works fine in non-ssl mode however on starting in ssl mode it gives the following exception:
> # ../bin/apachectl startssl
> [Thu Dec 04 16:27:04 2003] [crit] [Thu Dec 04 16:27:04 2003] file vhost.c, line 232, assertion "rv == APR_SUCCESS" failed
> Abort - core dumped
> 
> On analysing the core file using gdb(gdb httpd core), the following backtrace is shown:
> #0  0xfefa9780 in __sigprocmask () from /usr/lib/libthread.so.1
> (gdb) bt
> #0  0xfefa9780 in __sigprocmask () from /usr/lib/libthread.so.1
> #1  0xfef9e978 in _resetsig () from /usr/lib/libthread.so.1
> #2  0xfef9e118 in _sigon () from /usr/lib/libthread.so.1
> #3  0xfefa1158 in _thrp_kill () from /usr/lib/libthread.so.1
> #4  0xff04ba7c in raise () from /usr/lib/libc.so.1
> #5  0xff035964 in abort () from /usr/lib/libc.so.1
> #6  0x7fe74 in piped_log_spawn (pl=0x130af8) at log.c:728
> 
> The issue doesn't seems to be in my application. If not what could be the issue???????
> 
> 
> regards,
Gagan 

Re: Apache 2.0.48 gives core on startssl

[Jeff Trawick <tr...@attglobal.net>]

Gagan Puri wrote:
>>I have installed Apache 2.0.48 with enable-ssl option on Solaris 8.
>>The server starts and works fine in non-ssl mode however on starting in ssl mode it gives the following exception:
>># ../bin/apachectl startssl
>>[Thu Dec 04 16:27:04 2003] [crit] [Thu Dec 04 16:27:04 2003] file vhost.c, line 232, assertion "rv == APR_SUCCESS" failed
>>Abort - core dumped

Here is the code that blew:

else if (strcasecmp(host, "_default_") == 0
          || strcmp(host, "255.255.255.255") == 0) {
  rv = apr_sockaddr_info_get(&my_addr, "255.255.255.255", APR_INET, port, 0, p);
  ap_assert(rv == APR_SUCCESS); /* must be bug or out of storage */

The expected cause is a resolver bug.  If you're on a real old level of Solaris 
(w.r.t. patches), upgrading to the current recommended patch set will hopefully 
fix this.

Alternatively, try to avoid coding _default_ or "255.255.255.255".

Another idea: convince APR that it has no working getaddrinfo.  Perhaps you can 
try this patch and run buildconf, configure, make and see if it gets better?

Index: srclib/apr/build/apr_network.m4
===================================================================
RCS file: /home/cvs/apr/build/apr_network.m4,v
retrieving revision 1.23
diff -u -r1.23 apr_network.m4
--- srclib/apr/build/apr_network.m4     2 Sep 2003 08:42:56 -0000       1.23
+++ srclib/apr/build/apr_network.m4     4 Dec 2003 11:45:12 -0000
@@ -39,6 +39,10 @@
      if (ai->ai_addr->sa_family != AF_INET) {
          exit(1);
      }
+    error = getaddrinfo("255.255.255.255", NULL, &hints, &ai);
+    if (error) {
+        exit(1);
+    }
      exit(0);
  }
  ],[


>>#5  0xff035964 in abort () from /usr/lib/libc.so.1
>>#6  0x7fe74 in piped_log_spawn (pl=0x130af8) at log.c:728

I don't know why piped_log_spawn() was displayed.