Apache 2.2.2/SSL startup problem
Chris Lilley
Hi
I have a problem with a new installation of httpd 2.2.2 on RedHat EL 3
and SSL. I've just done a vanilla installation with mod_ssl compiled in
statically, and created a new test certificate using OpenSSL, as in the
docs on the web site.
Whenever I try to start the server, it fails, with the error message
[Fri...] [error] Init: Multiple RSA server certificates not allowed
in the error log. As far as I can tell, I only have a single
SSLCertificateFile specified and a single SSLCertificateKeyFile too.
From reading the code, it appears that the configuration must believe
that the certificate has been specified more than once, but I can't see
where that's happening.
Anyone seen this before? A quick google reveals very few hits. Oh, and
the previous 2.0.46 installation works fine.
Cheers,
-Chrisl
Chris Lilley
>
> Hi
>
> I have a problem with a new installation of httpd 2.2.2 on RedHat EL 3
> and SSL. I've just done a vanilla installation with mod_ssl compiled in
> statically, and created a new test certificate using OpenSSL, as in the
> docs on the web site.
>
> Whenever I try to start the server, it fails, with the error message
>
> [Fri...] [error] Init: Multiple RSA server certificates not allowed
>
> in the error log. As far as I can tell, I only have a single
> SSLCertificateFile specified and a single SSLCertificateKeyFile too.
> From reading the code, it appears that the configuration must believe
> that the certificate has been specified more than once, but I can't see
> where that's happening.
In case anyone's interested, I recompiled 2.2.2 with mod_ssl as a DSO
rather than including it statically, and the problem disappeared (a
little worrying).
Since then, I had problems getting the SSL config to start up reliably -
it would work one time out of six and fail the other five times, around
the time it was doing digest initialisation for SSL.
I've given up and gone back to 2.0.58, which works just fine. If
anything, I suspect that I haven't invested the necessary time to
migrate the configuration properly from 2.0.x to 2.2.x and have taken a
bad short cut somewhere. I'm happy with 2.0.58, anyhow. Hey ho.
-Chrisl