-
-
Notifications
You must be signed in to change notification settings - Fork 547
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
COOK-3898: apache_site definition issues a restart rather than a reload to apache #225
Comments
I think maybe this should be reworked... web_app does a |
This is what we got currently
It does seem like apache_config should do a restart. More details at http://httpd.apache.org/docs/2.4/stopping.html |
This commit 9680088 generate the same problem than #333, the apache is restarted just after a reload and failed.
As mentioned in #355, the problem can be solved with a wait between the reload and the restart. |
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
Migration of https://tickets.opscode.com/browse/COOK-3898 by Kimball Johnson
From reading the source code the apache_site definition issues a restart to apache rather than a reload. This is unnecessary and will cause an short outage to your webserver which is not wanted or required.
@juliandunn comment:
I think the reason is because any custom template can be specified in the web_app definition. That template might make non-reload-safe changes (e.g. Listen port) that would cause Apache to fail entirely if just a reload were attempted.
The text was updated successfully, but these errors were encountered: