Tony Mizukami wrote:
>
> > > Thank your for your response.
> >
> > > Unfortunately, nothing is written (at all) to the error file, nor to the
> > > access_log. There is also no core file.
> >
> > But when you say nothing is written at all to the error log, this
> indicates
> > that perhaps the error log is not setup correctly.
>
> Aha... 'Twas my own fault, it seems. I had copied over the httpd.conf
> files from another server, and the ErrorLevel was set to error.
> Setting this to 'info' revealed the errors, which though fatal
> apparently were deemed of 'info' importance. (^-^)
Hmmm ... I may have some of the error levels wrong, so please do point
out problems like this. I'll fix this one for the next release.
>
> Properly setting the paths to my cert files got everything to start up.
> Thanks for the pointer, Ralf.
>
> Now of course, I have to figure out why I'm getting the infamous
>
> [error] SSL_Accept failed
> [error] error:14094412:SSL routines:SSL3_READ_BYTES:sslv3 alert bad certificate
>
> messages, even though I compiled with SSLCaching off. (T_T)
Caching now works!
> Since non-SSL ports seem to be working, perhaps this has something to do
> with a bad certificate?
I'd guess so, but it isn't immediately obvious why.
Cheers,
Ben.
--
Ben Laurie |Phone: +44 (181) 735 0686| Apache Group member
Freelance Consultant |Fax: +44 (181) 735 0689|http://www.apache.org/
and Technical Director|Email: ben@algroup.co.uk |
A.L. Digital Ltd, |Apache-SSL author http://www.apache-ssl.org/
London, England. |"Apache: TDG" http://www.ora.com/catalog/apache/
WE'RE RECRUITING! http://www.aldigital.co.uk/recruit/