On Mon, Sep 18, 2000 at 07:03:13PM +0100, Clive Hughes wrote:
> I believe I have now built it with static modules. When I start Apache I
> see
>
> Apache/1.3.12 (Unix) PHP/4.0.2 mod_ssl/2.6.6 OpenSSL/0.9.5 ....
What OS was this? This might be an openssl issue - your openssl should
be at least up to 0.9.5a (unless your system has /dev/urandom). You may
even have better results with openssl 0.9.6 (should be out in a week).
>
> in the Apache error_log
>
> and a httpd -l shows me mod_ssl.c and mod_php4.c as compiled-in modules. I
> assume the OpenSSL part is statically linked, too, although I don't know how
> to prove that.
It is.
> I still get these sort of messages in my error_log, however
>
> [Mon Sep 18 18:40:47 2000] [notice] child pid 18628 exit signal Bus Error
> (10)
> [Mon Sep 18 18:40:48 2000] [notice] child pid 18629 exit signal Bus Error
> (10)
>
> and this stops the application behaving correctly. In fact they seem to
> come along 2 at a time!
>
It could be because it is killing the whole server instead of just the
current child.
> My build must be wrong somewhere; although Apache+PHP4 only behaves
> correctly.
>
How did you configure?
> I just can't seem to to find out what's going wrong here and I have spent
> days looking at this. Any pointers would be helpful.
>
Throwing a core through gdb would probably give us some pointers. If you
have a chance to run the process through strace (linux) or truss (solaris)
that might give us some ekstra pointers.
vh
Mads Toftum
--
`Darn it, who spiked my coffee with water?!' - lwall
______________________________________________________________________
Apache Interface to OpenSSL (mod_ssl) www.modssl.org
User Support Mailing List [EMAIL PROTECTED]
Automated List Manager [EMAIL PROTECTED]
