Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 172886 - Poor signal handling in cluquorumd
Poor signal handling in cluquorumd
Product: Red Hat Cluster Suite
Classification: Red Hat
Component: clumanager (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Lon Hohberger
Cluster QE
Depends On:
Blocks: 172895
  Show dependency treegraph
Reported: 2005-11-10 16:00 EST by Lon Hohberger
Modified: 2009-04-16 16:18 EDT (History)
1 user (show)

See Also:
Fixed In Version: RHBA-2006-0196
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2006-03-27 13:06:26 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
Fixes quorumd signal handling (1.94 KB, patch)
2005-11-10 16:06 EST, Lon Hohberger
no flags Details | Diff

External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2006:0196 normal SHIPPED_LIVE clumanager bug fix update 2006-03-27 00:00:00 EST

  None (edit)
Description Lon Hohberger 2005-11-10 16:00:09 EST
Description of problem:

(a) SIGHUP isn't properly handled, and
(b) if two signals come in quickly, cluquorumd can deadlock because it call
syslog (and other unsafe things) in the signal handler for SIGHUP

Version-Release number of selected component (if applicable): 1.2.28

How reproducible: ?
Comment 1 Lon Hohberger 2005-11-10 16:06:24 EST
Created attachment 120904 [details]
Fixes quorumd signal handling
Comment 3 Lon Hohberger 2005-11-11 15:59:05 EST
A new *TEST* package build with several bugfixes (fixes bugzillas: 171637 172735
172893 172894 ) is available.  Gulm-bridge support has been disabled in this
release to prevent having to install with the "--nodeps" option:


Let us know if this works for you.
Comment 4 Lon Hohberger 2005-12-14 16:22:06 EST

This is a pre-emptive strike against a potential problem,
and needs no testing.  Verify that the cluster still operates under
normal constraints.
Comment 5 Lon Hohberger 2005-12-14 16:34:27 EST
Actually scratch that; writing a test case.
Comment 6 Lon Hohberger 2005-12-14 16:53:01 EST
1.  Set cluquorumd to debug log level.  Send cluquorumd SIGHUP
signals very quickly by running this for a few seconds (presss ^C to
stop it):

    while [ 0 ]; do killall -HUP cluquorumd; done

2.  Run clustat.  It should hang. 
3.  On 1.2.30, this behavior should not exist.
Comment 9 Red Hat Bugzilla 2006-03-27 13:06:27 EST
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.


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