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:
While the current /usr/lib/pcsd/pcsd launch script in RHEL7 is based on a standard iniscript skeleton it doesn't work that way.
When the start() is issued, instead of sending the ruby process into the background the script is kept running and ruby is spawned as a child of this script. As soon as systemd sends the TERM signal to the script to stop pcsd, it tries to terminate the child process tree as well. This often leads to the TERM signal being caugth twice in ruby resulting in a traceback:
Shutting down (TERM)
Shutting down (TERM)
/usr/lib/pcsd/vendor/bundle/ruby/gems/rack-1.6.4/lib/rack/handler/webrick.rb:48:in `shutdown': undefined method `shutdown' for nil:NilClass (NoMethodError)
from /usr/lib/pcsd/ssl.rb:56:in `block in <main>'
from /usr/share/ruby/webrick/log.rb:150:in `call'
from /usr/share/ruby/webrick/log.rb:150:in `strftime'
from /usr/share/ruby/webrick/log.rb:150:in `log'
from /usr/share/ruby/webrick/log.rb:94:in `info'
from /usr/share/ruby/webrick/server.rb:197:in `block in start'
from /usr/share/ruby/webrick/server.rb:32:in `start'
from /usr/share/ruby/webrick/server.rb:160:in `start'
from /usr/lib/pcsd/vendor/bundle/ruby/gems/rack-1.6.4/lib/rack/handler/webrick.rb:34:in `run'
from /usr/lib/pcsd/ssl.rb:62:in `<main>
I've tried disabling the termination of children processes in systemd, but it introduces a different issue with the ruby process getting stuck when the stop is issued shortly after startup.
Also, there's a stop() function in the startup script which doesn't seem to be doing anything at all and therefore cannot be used by systemd to shutdown pcsd correctly.
> Version-Release number of selected component (if applicable):
pcs-0.9.142-2.el7.x86_64
> Expected results:
We need either to rewrite the script so it can work a fully-feature iniscript or call pcsd daemon directly from systemd.
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/RHSA-2016-2596.html