Red Hat Bugzilla – Bug 195591
The init scripts for the cluster components are broken
Last modified: 2009-04-16 18:26:34 EDT
Description of problem:
The current init scripts in the source base have not been updated to reflect the
changes in the infrastructure. The cman script still trys to load kernel
modules that no longer exist. There are no startup references to the new dlm
modules, no references for configfs, and nothing starts up groupd.
Need to replace all of the current core infrastructure startup scripts with
probably a single one that does the following:
Loads the appropriate kernel modules
mount -t configfs none /sys/kernel/config
Also, need the appropriate stop command and status commands for the init scripts.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
*** Bug 196020 has been marked as a duplicate of this bug. ***
Committed single init script to start up cluster called cman: Covers loading of
modules, starting ccsd, cman and fencing, and starting daemons(gfs_controld,
dlm_controld, fenced and groupd). Replaces ccsd, cman and fenced init scripts.
The gfs script has a problem with its loop to unmount all gfs
mounts. If you have a gfs2 file system mounted, it will loop
repeatedly, mistaking it for a gfs file system.
changed awk regexp string to fix the problem in comment#3. Fix committed for gfs
and gfs2 init scripts in cvs HEAD.
Fixing Product Name. Cluster Suite was merged into Red Hat Enterpise Linux for
5.0. In addition dlm, fence and ccs were merged into the cman package, so
bugzilla should reflect package name where those utilities are located.
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux maintenance release. Product Management has requested
further review of this request by Red Hat Engineering, for potential
inclusion in a Red Hat Enterprise Linux Update release for currently deployed
products. This request is not yet committed for inclusion in an Update
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.