httpd-bugs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject DO NOT REPLY [Bug 52395] New: reload results in different end environment to restart
Date Thu, 29 Dec 2011 01:14:09 GMT

             Bug #: 52395
           Summary: reload results in different end environment to restart
           Product: Apache httpd-2
           Version: 2.2.21
          Platform: PC
        OS/Version: FreeBSD
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Runtime Config
    Classification: Unclassified

Server is FreeBSD based, running Apache HTTPd version 2.2.21:

[notice] Apache/2.2.21 (FreeBSD) mod_ssl/2.2.21 OpenSSL/0.9.8q

We had a vhost file that was updated a week ago. Previous vhost was of form:

<VirtualHost *:80>

    ProxyPreserveHost On
    ProxyPass /
    ProxyPassReverse /

It just contained a ":80" entry.
A "*:443" entry was added of identical form, but by mistake without the line:

Include conf/ssl.conf

which is in all our *:443 entries and does the usual standard settings for SSL
(encryption format, certificate etc.)

configtest passed it okay as it still doesn't check SSL stuff (see  Reload brought the
changes in without any complaint.  Despite several reloads that have occurred
since the mistake was made last week, not once has httpd complained about lack
of SSL configuration until today when a restart, rather than a reload, was

On restart it threw up the expected, an error it should have been hitting ever
since the mistake was made:

[error] Server should be SSL-aware but has no certificate configured [Hint:
SSLCertificateFile] ((null):0)

To my possibly crazy mind the same config files should result in the same end
environment, regardless of whether httpd was passed a reload or a restart.  The
config files should be describing an exact operating environment.  Sadly this
shows it isn't the case.

It would be nice if configtest had failed, but given it's 6 years after that
bug was submitted I figure that's never going to happen; but it's very
disturbing that reload and restart can end up so differently.

I've since tested with a working environment, setting up a vhost with a working
SSL setup, commenting out the include ssl.conf entry and reloading, after which
it stays running.  Restart fails.  Uncommenting the line and restarting results
in it working fine.

Configure bugmail:
------- You are receiving this mail because: -------
You are the assignee for the bug.

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message