Red Hat Bugzilla – Bug 172893
clulockd hang causes infinite timeout loop from connecting clients
Last modified: 2009-04-16 16:18:35 EDT
Description of problem:
If signals occur quickly in sequence, it's possible for clulockd to deadlock
during a reconfiguration.
Version-Release number of selected component (if applicable):
How reproducible: 100%
Steps to Reproduce:
1. service clumanager start
2. while [ 0 ]; do killall -HUP clulockd; done
clulockd hangs, and causes timeout errors for connecting
Under high load conditions, an occasional timeout warning may occur; this is not
a cause for alarm.
Created attachment 120908 [details]
Fixes signal handling
Setting to modified
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.
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.