Apache 2.0.54 with SSL goes haywire

[Olivier Masse]

For the last three days I've been getting nuts trying to make Apache 2.0.54 work with SSL. It compiles fine, but the first SSL request to the server makes a few httpds go in a loop using 100% CPU. If I click reload a few times, it makes matters worse. :)

I've tried a few Apache versions (2.0.46, 2.0.51), to no avail. Oh yes, I also tried to compile it with different OpenSSL versions (0.9.7c, 0.9.7g), then I settled on HP's own 0.9.7e distribution to save time. I also tried a different set of keys, just to be sure. I patched my lab server to a recent bundle, and really tried to narrow down what's causing this -- I can't find anything.

I'm using plain vanilla compilation and configuration settings for Apache, nothing specific, with gcc 3.4.3 as my compiler.

The HP Apache web server works fine with SSL. I'd be glad to use it, but our security guys insist on having a custom-compiled Apache. Currently I can't even make it work with the default compile options. I really need to find a way to make it work.

Anybody had the same problem recently?

Thanks

[Denver Osborn]

Can you post the steps used to build Apache on that box? Also the output of "httpd -l", "httpd -t -DSSL" and "httpd -V"

Does it otherwise work fine w/ out mod_ssl loaded?

It might also help to see the ssl config file's directives.

Have you also tried setting the log level to debug for more info?

-denver

[Olivier Masse]

The problem was the compiler. It was the last thing that that I didn't try changing versions. I tried a common denominator and switched to an old version of a 32-bit GCC 3.3.1 and it woks. There is probably something in the optimizer routines at 3.4.3.

Bottom line is, don't use GCC 3.4.3 to compiler Apache with mod_ssl. :)

Thanks

[Olivier Masse]

close thread