On Fri, Nov 27, 1998, Bob Berman wrote:
> On my Solaris 2.6 box, I built mod_ssl OK (not as DSO!)
> along with mod_perl. I start up httpd (apachectl startssl)
> and it starts up. Sort of. The problem is that I have a
> persistent Sybase database connection configured via
> Apache::Sybase::CTLib. This module saves you the overhead
> of connecting and reconnecting to the database each time
> you make a query. But this apparently conflicts with mod_ssl,
> because I get in the Apache error_log:
>
> [Fri Nov 27 16:12:15 1998] [notice] Apache/1.3.3 (Unix) PHP/3.0.5
> mod_perl/1.16 mod_ssl/2.1.0 SSLeay /0.9.0b configured -- resuming normal
>operations
> [Fri Nov 27 16:12:15 1998] [notice] httpd: child pid 11516 exit signal Pollable
>Event (22)
> [Fri Nov 27 16:12:16 1998] [notice] httpd: child pid 11521 exit signal Pollable
>Event (22)
> [Fri Nov 27 16:12:16 1998] [notice] httpd: child pid 11519 exit signal Pollable
>Event (22)
> [Fri Nov 27 16:12:16 1998] [notice] httpd: child pid 11518 exit signal Pollable
>Event (22)
> [Fri Nov 27 16:12:16 1998] [notice] httpd: child pid 11517 exit signal Pollable
>Event (22)
> [Fri Nov 27 16:12:18 1998] [notice] httpd: child pid 11522 exit signal Pollable
>Event (22)
> [Fri Nov 27 16:12:19 1998] [notice] httpd: child pid 11525 exit signal Pollable
>Event (22)
> forever.....
>
> and I can't connect to the httpd process via ssl. If I disable the persistent
> connection (in my startup.pl file), everything is fine. And the persistent
> connection stuff has been working fine until I installed ssl. Do you have any
> idea what may be going on here and can I fix this?
Hmmmmm... I've no clue what's going on here (the errors don't make a lot of
sense for me). Perhaps it's some conflict between SSLeay and your Sybase
stuff. And you also have PHP compiled in: Puhhh... a lot of stuff which can
cause problems. Are you really sure it's caused by mod_ssl+SSLeay? I ask
because when you rebuild with mod_ssl+SSLeay you could be done some other
related errors. So the best advice I can give you is: Try to build
mod_ssl+SSLeay as a DSO libssl.so (this should work as expected also for you
with 2.1.1 in the next days) and try it out once without the LoadModule
command for libssl.so and once with the LoadModule command. Only this way you
can be sure that the problem is really caused by mod_ssl+SSLeay.
Ralf S. Engelschall
[EMAIL PROTECTED]
www.engelschall.com
______________________________________________________________________
Apache Interface to SSLeay (mod_ssl) www.engelschall.com/sw/mod_ssl/
Official Support Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
