Bug 1214398

Summary: apachectl graceful does not start httpd when not running
Product: Red Hat Enterprise Linux 7 Reporter: Martin Frodl <mfrodl>
Component: httpdAssignee: Luboš Uhliarik <luhliari>
Status: CLOSED ERRATA QA Contact: Martin Frodl <mfrodl>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 7.1CC: jkaluza, jorton
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: httpd-2.4.6-32.el7 Doc Type: Bug Fix
Doc Text:
Cause: Man page for "apachectl graceful" mentioned that httpd should be started as a result of graceful restart when it was not running before. Consequence: The man page was not right - the httpd is not started in that case. Fix: Man page has been fixed. Result: The man page is right now.
Story Points: ---
Clone Of:
: 1221702 (view as bug list) Environment:
Last Closed: 2015-11-19 04:37:31 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1221702    

Description Martin Frodl 2015-04-22 15:53:36 UTC
Description of problem:

A snippet from apachectl man page:

       graceful
              Gracefully  restarts  the Apache httpd daemon. If the daemon is
              not running, it is started.

Contrary to this, httpd does not in fact start when it is not running. I assume this was caused by the replacement of 'systemctl restart' with 'systemctl reload' in bug 917565. If this is an expected behaviour, the documentation should be updated. If it is not expected, the apachectl script should be modified so as to call 'systemctl [re]start' when the service is stopped.

Version-Release number of selected component (if applicable):
httpd-2.4.6-31.el7.x86_64

Comment 6 errata-xmlrpc 2015-11-19 04:37:31 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHBA-2015-2194.html