apache2 won"t start

As this rookie creeps ever closer to getting it to run, I keep coming up with problems that I am sure someone has seen before. Thanks for the help.

Apache 2036
ssl 096c
on solaris 8




./bin/apachectl startssl
[Mon Jun 10 10:19:51 2002] [crit] [Mon Jun 10 10:19:51 2002] file vhost.c, line 232, assertion "rv == APR_SUCCESS" failed
Abort - core dumped
../bin/apachectl startssl: httpd could not be started


____________________________________________________________ __________
Apache Interface to OpenSSL (mod_ssl) www.modssl.org
User Support Mailing List modssl-users@modssl.org
Automated List Manager majordomo@modssl.org

Re: apache2 won"t start

On Mon, 10 Jun 2002, Jeff Landers wrote:

> ./bin/apachectl startssl [Mon Jun 10 10:19:51 2002] [crit] [Mon Jun 10
> 10:19:51 2002] file vhost.c, line 232, assertion "rv == APR_SUCCESS"
> failed Abort - core dumped ./bin/apachectl startssl: httpd could not be
> started


That means the call to apr_sockaddr_info_get() on the address
"255.255.255.255" failed (the call is made because you're using
"_default_" in one of your vhosts). So then the question is: why did it
fail? Well, to know that, I need to know (a) what the actual return code
was, (b) what OS you're running, and it would be helpful to also have (c)
a backtrace.

See http://httpd.apache.org/dev/debugging.html for help on fetching b and
c. :)

Thanks,
Cliff


____________________________________________________________ __________
Apache Interface to OpenSSL (mod_ssl) www.modssl.org
User Support Mailing List modssl-users@modssl.org
Automated List Manager majordomo@modssl.org

Re: apache2 won"t start

Thank you for the info. I will work on debugging but here is another question. Why, when ssl and apache are under /usr/local, is vhosts.c still under the source code directory? This seems more like a compilation problem although I have compiled it a couple of times.

>>> jwoolley@apache.org 06/10/02 09:56AM >>>
On Mon, 10 Jun 2002, Jeff Landers wrote:

> ./bin/apachectl startssl [Mon Jun 10 10:19:51 2002] [crit] [Mon Jun 10
> 10:19:51 2002] file vhost.c, line 232, assertion "rv == APR_SUCCESS"
> failed Abort - core dumped ./bin/apachectl startssl: httpd could not be
> started


That means the call to apr_sockaddr_info_get() on the address
"255.255.255.255" failed (the call is made because you're using
"_default_" in one of your vhosts). So then the question is: why did it
fail? Well, to know that, I need to know (a) what the actual return code
was, (b) what OS you're running, and it would be helpful to also have (c)
a backtrace.

See http://httpd.apache.org/dev/debugging.html for help on fetching b and
c. :)

Thanks,
Cliff


____________________________________________________________ __________
Apache Interface to OpenSSL (mod_ssl) www.modssl.org
User Support Mailing List modssl-users@modssl.org
Automated List Manager majordomo@modssl.org

____________________________________________________________ __________
Apache Interface to OpenSSL (mod_ssl) www.modssl.org
User Support Mailing List modssl-users@modssl.org
Automated List Manager majordomo@modssl.org

Re: apache2 won"t start

On Tue, 11 Jun 2002, Jeff Landers wrote:

> Thank you for the info. I will work on debugging but here is another
> question. Why, when ssl and apache are under /usr/local, is vhosts.c
> still under the source code directory? This seems more like a
> compilation problem although I have compiled it a couple of times.

Um, because vhosts.c is one of the source files? I guess I don't
understand the question. It's not a compilation problem -- it compiles
just fine. It's a runtime problem. It just so happens that the runtime
error occurred in code that was compiled from vhosts.c, and the debugger
is telling you which source file to look in for the line that faulted.

--Cliff

____________________________________________________________ __________
Apache Interface to OpenSSL (mod_ssl) www.modssl.org
User Support Mailing List modssl-users@modssl.org
Automated List Manager majordomo@modssl.org

Re: apache2 won"t start

The question is, and maybe I am just totally in left field, if I compile it and install in /usr/local/apache shouldn't all of the necessary code be located there instead of in the original tarball directory located under /tmp which I am going to blow away once the thing works. I didn't see the non-ssl version going back to the source directory after it was compiled because I blew the souce directory (tarball extraction) away. Can you get this newbie on the right track. The non-ssl version works but once I compile it with the ssl module it won't work either way.

Jeff Landers
UNIX System Administrator
City of Henderson, NV
702-566-2761
jl1@gty.ci.henderson.nv.us

>>> jwoolley@apache.org 06/11/02 10:23AM >>>
On Tue, 11 Jun 2002, Jeff Landers wrote:

> Thank you for the info. I will work on debugging but here is another
> question. Why, when ssl and apache are under /usr/local, is vhosts.c
> still under the source code directory? This seems more like a
> compilation problem although I have compiled it a couple of times.

Um, because vhosts.c is one of the source files? I guess I don't
understand the question. It's not a compilation problem -- it compiles
just fine. It's a runtime problem. It just so happens that the runtime
error occurred in code that was compiled from vhosts.c, and the debugger
is telling you which source file to look in for the line that faulted.

--Cliff

____________________________________________________________ __________
Apache Interface to OpenSSL (mod_ssl) www.modssl.org
User Support Mailing List modssl-users@modssl.org
Automated List Manager majordomo@modssl.org

____________________________________________________________ __________
Apache Interface to OpenSSL (mod_ssl) www.modssl.org
User Support Mailing List modssl-users@modssl.org
Automated List Manager majordomo@modssl.org