RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1214401 - apachectl graceful does not ignore sysconfig HTTPD
Summary: apachectl graceful does not ignore sysconfig HTTPD
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: httpd
Version: 7.1
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Luboš Uhliarik
QA Contact: Martin Frodl
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-04-22 16:05 UTC by Martin Frodl
Modified: 2021-01-14 09:33 UTC (History)
2 users (show)

Fixed In Version: httpd-2.4.6-32.el7
Doc Type: Bug Fix
Doc Text:
Cause: The legacy HTTPD variable defined in /etc/sysconfig/httpd, which should be ignored according to the documentation, is actually taken into account when doing a graceful restart. Consequence: When using /etc/sysconfig/httpd from older httpd version with HTTPD variable defined, the httpd can fail to start. Fix: HTTPD variable is now ignored as documented. Result: httpd starts properly even in the mentioned case.
Clone Of:
: 1221681 (view as bug list)
Environment:
Last Closed: 2015-11-19 04:37:35 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2015:2194 0 normal SHIPPED_LIVE httpd bug fix and enhancement update 2015-11-19 08:05:27 UTC

Description Martin Frodl 2015-04-22 16:05:33 UTC
Description of problem:

The legacy HTTPD variable defined in /etc/sysconfig/httpd, which should be ignored according to the documentation, is actually taken into account when doing a graceful restart. When adding the following line to /etc/sysconfig/httpd...

HTTPD=/usr/sbin/httpd.event

...graceful restart fails because of being unable to locate the binary:

# systemctl start httpd
# apachectl reload
/usr/sbin/apachectl: line 137: /usr/sbin/httpd.event: No such file or directory

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

Comment 2 Martin Frodl 2015-04-22 16:49:15 UTC
My apologies, now I see that 'reload' is not a valid apachectl command, so I am not quite sure whether to consider this behaviour a bug or a feature. Strictly speaking, the HTTPD variable should be ignored under any circumstances. Also, the output could surely be more informative when a nonexistent apachectl command is run. On the other hand, whoever enters meaningless commands can hardly expect a meaningful answer.

Devel, the decision upon this bug's fate is yours.

Comment 7 errata-xmlrpc 2015-11-19 04:37:35 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


Note You need to log in before you can comment on or make changes to this bug.