Red Hat Bugzilla – Bug 168722
Cluster Manager hangs on stopping in 2 node cluster.
Last modified: 2009-04-16 16:18:08 EDT
From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.2; SV1; .NET CLR 1.1.4322)
Description of problem:
service clumanager hangs on
Shutting down Red Hat Cluster Manager...
Initiating shutdown of Quorum Services: [ OK ]
Waiting for User Services to stop: [ OK ]
Waiting for Quorum Services to stop: [ OK ]
Waiting for Membership Services to stop:
ps -ef |grep clumanager shows the following
root 8072 29795 0 16:26 pts/3 00:00:00 /bin/sh /sbin/service clumanager stop
root 8079 8072 1 16:26 pts/3 00:00:00 /bin/sh /etc/init.d/clumanager stop
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1.service clumanager stop
Actual Results: Nothing. The command hangs.
Expected Results: The cluster service should have stopped.
Please retry with the U5 version, 188.8.131.52, or the U6 beta version, 1.2.28.
This works for me.
I upgraded to clumanager-184.108.40.206-1.
Problem still happens but not everytime now.
First of all, it works for me, which is why I'm puzzled.
Can I look at your configuration? You can block out IPs/hostnames if you need
to, but the rest needs to be intact.
I can't give you access to the machines as it is behing firewall and it is
against company policy.
Let me know how else I can send you the information you need.
I meant /etc/cluster.xml ...
I hid the configuration from public view.
The configuration looks good, it looks like it's waiting for membership to stop
(which is odd, actually).
So this is prioritized correctly, can you please file a request here?
I still can't reproduce this. Is there anything special I need to know to make
Is the cluster formed (are both nodes up)? Is there only one up but at the
point we try to stop, the node is quorate? Do I need to run "service clumanager
start ; service clumanager stop" in a tight loop?
Cluster is formed. Both nodes are up. I just run service clumanager stop.
The command works sometimes but sometimes it hangs. I do have a couple of
services defined and they failover between the nodes correctly.
Well, it's hanging in this loop (obviously):
if [ -n "`pidof $MEMBD`" ]; then
echo -n $"Waiting for Membership Services to stop: "
while [ -n "`pidof $MEMBD`" ]; do
echo $"Membership Services are stopped."
so, it didn't exit for some reason. Can you run "service clumanager stop", and
while it's 'hung', run "service clumanager status" from another terminal? That
should correctly indicate which daemon(s) are stuck.