Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
Created attachment 736323[details]
proposed changes
Description of problem:
ocf:heartbeat:apache script should try first send WINCH signal before sending
TERM signal. According to apache manual page
https://httpd.apache.org/docs/2.2/stopping.html it is the way of graceful
killing of children and that is what I think should be done.
Version-Release number of selected component (if applicable):
resource-agents-3.9.5-4.el7.x86_64
How reproducible: n/a
Steps to Reproduce: n/a
Actual results: Immediate stop
https://httpd.apache.org/docs/2.2/stopping.html#term
Apache is being killed with TERM signal which "...causes it to immediately
attempt to kill off all of its children. It may take it several seconds to
complete killing off its children. Then the parent itself exits. Any requests
in progress are terminated, and no further requests are served." [2]
Expected results: Graceful stop
https://httpd.apache.org/docs/2.2/stopping.html#gracefulstop
"...causes the parent process to advise the children to exit after their
current request (or to exit immediately if they're not serving anything). The
parent will then remove its PidFile and cease listening on all ports. The
parent will continue to run, and monitor children which are handling requests.
Once all children have finalised and exited or the timeout specified by the
GracefulShutdownTimeout has been reached, the parent will also exit. If the
timeout is reached, any remaining children will be sent the TERM signal to
force them to exit."
This request was resolved in Red Hat Enterprise Linux 7.0.
Contact your manager or support representative in case you have further questions about the request.