Bug 190392 - cman init scripts seem to always fail when stopping
cman init scripts seem to always fail when stopping
Status: CLOSED ERRATA
Product: Red Hat Cluster Suite
Classification: Red Hat
Component: cman (Show other bugs)
4
All Linux
medium Severity medium
: ---
: ---
Assigned To: Abhijith Das
Cluster QE
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2006-05-01 17:32 EDT by Corey Marthaler
Modified: 2009-04-16 15:55 EDT (History)
2 users (show)

See Also:
Fixed In Version: RHBA-2006-0556
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2006-08-10 17:32:59 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
fix for bz (703 bytes, patch)
2006-05-02 15:28 EDT, Abhijith Das
no flags Details | Diff

  None (edit)
Description Corey Marthaler 2006-05-01 17:32:53 EDT
Description of problem:
I've been seeing this a lot lately and it's annoying me. :)

I'll try and debug this a bit more later but here's what I've been seeing:

[root@taft-01 ~]# cat /proc/cluster/services
Service          Name                              GID LID State     Code
[root@taft-01 ~]# service cman stop
Stopping cman:                                             [FAILED]
[root@taft-01 ~]# cat /proc/cluster/nodes
Node  Votes Exp Sts  Name

from syslog:
May  1 10:30:42 taft-01 kernel: CMAN: we are leaving the cluster.
May  1 10:30:42 taft-01 ccsd[8725]: Cluster manager shutdown.  Attemping to
reconnect...
May  1 10:30:45 taft-01 cman: failed to stop cman failed

Version-Release number of selected component (if applicable):
[root@taft-01 ~]# rpm -q cman
cman-1.0.4-0

How reproducible:
almost every time
Comment 1 Christine Caulfield 2006-05-02 03:04:06 EDT
Needs passing to whever manages the init scripts. All the subsystems need to be
shut down. This includes ccsd which polls cman to see if it is active.
Comment 2 Corey Marthaler 2006-05-02 10:55:44 EDT
First, when did that change? Ccsd must be started before cman can be started and
we've always (since the begining of rhel4) stopped cman before stopping ccsd and
it worked just fine.

Second, stopping ccsd first still doen't help:
[root@taft-02 ~]# service ccsd stop
Stopping ccsd:                                             [  OK  ]
[root@taft-02 ~]# service cman stop
Stopping cman:                                             [FAILED]

In both cases (before and after ccsd is stopped), a leave by hand shows that the
stop did infact work:
[root@taft-02 ~]# cman_tool leave
cman_tool: Error leaving cluster: Cluster software not started
 
Comment 4 Abhijith Das 2006-05-02 15:28:53 EDT
Created attachment 128512 [details]
fix for bz

The cman init script ties the success of 'service cman stop' to successfully
completing a 'modprobe -r cman'. The 'modprobe -r' doesn't always succeed
because other modules (gfs, lock_dlm) may still be using it. This patch ties
the success of 'service cman stop' to 'cman_tool leave' which makes more sense
to me. Let me know if this works for you and I'll commit the patch.
Comment 5 Corey Marthaler 2006-05-08 17:46:57 EDT
Having the success tied to cluster membership removal does make more sense. The
patch works for me. 

Comment 6 Abhijith Das 2006-05-08 18:32:09 EDT
Checked in fix to RHEL4, HEAD and STABLE.
Comment 7 Corey Marthaler 2006-08-04 12:09:28 EDT
fix verified.
Comment 9 Red Hat Bugzilla 2006-08-10 17:32:59 EDT
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.

http://rhn.redhat.com/errata/RHBA-2006-0556.html

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