[BlueOnyx:14339] Re: SL-6.5 updates break Apache if SSL is enabled

[Michael Stauber]

Hi all,

Dan wrote:
> Scientific Linux released version 6.5 last night with 184 updates!!

On a Friday? <sigh> What's worse is trying to make sense of the new
glitches with just 3 hours of sleep.

The number of updates you get depends on what's installed. I'm getting
207 due to having some devel RPMs installed, but that's minus the MySQL
RPMs, as I'm running a newer MySQL PKG.

My 5108R testbox managed to "yum upgrade" partially last night. But for
half of the SL repositories the checksums didn't match, so some stuff is
missing. A "yum clean all" and another "yum update" fixed that.

Afterwards Apache failed to restart with an error message that I've
never seen before:

Syntax error on line 10 of /etc/httpd/conf.d/ssl_perl.conf:
$parms->add_config() has failed: mod_perl:1: <VirtualHost> was not
closed. at /usr/lib64/perl5/Apache2/PerlSections.pm line 215.\n

There is one Vsite with SSL enabled (self signed cert - not that it
matters). ssl_perl.conf uses Apache::PerlSections to read CODB to see
which Vsites have SSL enabled and then dynamically generates the
<VirtualHost> container needed for SSL and inserts that into the Apache
configuration at runtime.

On my testbox it fails to create any output. Updated a second test box
and then got the very same results: Dead Apache as soon as one Vsite has
SSL enabled.

That's not looking good. I'm combing through ssl_perl.pl now to see why
our SSL implementation is suddenly broken. After all, neither Apache nor
the direct dependencies of ssl_perl.pl seem to have been updated this
time around.

-- 
With best regards

Michael Stauber