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.
Description of problem:
The commands specified in ExecStopPost of a forking systemd-servicefile are not executed even though the documentation states otherwise:
"ExecStopPost=
Additional commands that are executed after the service was stopped. This includes cases where the commands configured in ExecStop= were used, where the service does not have any
ExecStop= defined, or where the service exited unexpectedly. This argument takes multiple command lines, following the same scheme as described for ExecStart. Use of these settings is
optional. Specifier and environment variable substitution is supported."
Version-Release number of selected component (if applicable):
systemd 219-62.el7_6.6
How reproducible:
Create service of type forking, stop it with failed state, ExecStopPost-command is not executed.
Steps to Reproduce:
1.
2.
3.
Actual results:
ExecStopPost-command is not executed.
Expected results:
ExecStopPost-command should be executed.
Additional info:
Severall prior complaints, nothing ever materialized:
https://bugzilla.redhat.com/show_bug.cgi?id=1353039https://bugs.freedesktop.org/show_bug.cgi?id=78240https://bbs.archlinux.org/viewtopic.php?id=181006
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://access.redhat.com/errata/RHBA-2020:1117
Description of problem: The commands specified in ExecStopPost of a forking systemd-servicefile are not executed even though the documentation states otherwise: "ExecStopPost= Additional commands that are executed after the service was stopped. This includes cases where the commands configured in ExecStop= were used, where the service does not have any ExecStop= defined, or where the service exited unexpectedly. This argument takes multiple command lines, following the same scheme as described for ExecStart. Use of these settings is optional. Specifier and environment variable substitution is supported." Version-Release number of selected component (if applicable): systemd 219-62.el7_6.6 How reproducible: Create service of type forking, stop it with failed state, ExecStopPost-command is not executed. Steps to Reproduce: 1. 2. 3. Actual results: ExecStopPost-command is not executed. Expected results: ExecStopPost-command should be executed. Additional info: Severall prior complaints, nothing ever materialized: https://bugzilla.redhat.com/show_bug.cgi?id=1353039 https://bugs.freedesktop.org/show_bug.cgi?id=78240 https://bbs.archlinux.org/viewtopic.php?id=181006