Thank you all.<div>The problem I have is that I don't seem to be able to get out of the cluster gracefully, even if I stop the services manually in the right order.</div><div>For example, I joined the cluster manually by starting cman, clvmd and gfs2 in the order and everything is working just fine.</div>
<div><br></div><div>Then I wanted to reboot. This time, I want to do it manually so I went to stop the services in order.</div><div><div>[root@test2 ~]# service gfs2 stop</div><div>Unmounting GFS2 filesystem (/vrstorm): [ OK ]</div>
<div>[root@test2 ~]# service clvmd stop</div><div>Signaling clvmd to exit [ OK ]</div><div>Waiting for clvmd to exit: [FAILED]</div><div>clvmd failed to exit [FAILED]</div>
<div><br></div><div>Somehow clvmd cannot be stopped. I still have the process running</div><div><div>root 2646 0.0 0.5 194476 45016 ? SLsl 02:18 0:00 clvmd -T30</div></div><div><br></div><div>How do I stop clvmd gracefully? I am running RHEL-6.</div>
<div><div>[root@test2 ~]# uname -a</div><div>Linux test2 2.6.32-71.18.2.el6.x86_64 #1 SMP Wed Mar 2 14:17:40 EST 2011 x86_64 x86_64 x86_64 GNU/Linux</div><div>[root@test2 ~]# cat /etc/redhat-release </div><div>Red Hat Enterprise Linux Server release 6.0 (Santiago)</div>
</div><div><br></div><div><br></div><div>Thank you very much.</div><div><br></div><div>Shi</div><div><br></div><div><br></div><br><div class="gmail_quote">On Thu, Mar 10, 2011 at 1:41 PM, Alvaro Jose Fernandez <span dir="ltr"><<a href="mailto:alvaro.fernandez@sivsa.com">alvaro.fernandez@sivsa.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div lang="ES" link="blue" vlink="purple">
<div>
<p class="MsoNormal"><font size="2" color="navy" face="Arial"><span lang="EN-GB" style="font-size:10.0pt;font-family:Arial;color:navy">Hi,</span></font></p>
<p class="MsoNormal"><font size="2" color="navy" face="Arial"><span lang="EN-GB" style="font-size:10.0pt;font-family:Arial;color:navy"> </span></font></p>
<p class="MsoNormal"><font size="2" color="navy" face="Arial"><span lang="EN-GB" style="font-size:10.0pt;font-family:Arial;color:navy">Given fencing is properly
configured, I think the default boot/sshutdown RHCS scripts should work. I too
use two_node (but no clvmd) in RHEL5.5 with latest updates to cman and
rgmanager, and a shutdown -r works well (and a shutdown -h too). The other node
cluster daemon should log this as a node shutdown in /var/log/messages, and it
should adjust quorum, and not trigger a fencing action over the other node.</span></font></p>
<p class="MsoNormal"><font size="2" color="navy" face="Arial"><span lang="EN-GB" style="font-size:10.0pt;font-family:Arial;color:navy"> </span></font></p>
<p class="MsoNormal"><font size="2" color="navy" face="Arial"><span lang="EN-GB" style="font-size:10.0pt;font-family:Arial;color:navy">If one halts and poweroff
via shutdown -h one of the two nodes, and then reboots (via shutdown -r) the
surviving node, the surviving node will fence the other. We have power switch
fencing, and it should simply suceed (making a power off then a power on on
the other node's outlets). Once this fencing suceeds, the boot sequence
continues and the node assumes quorum. </span></font></p>
<p class="MsoNormal"><font size="2" color="navy" face="Arial"><span lang="EN-GB" style="font-size:10.0pt;font-family:Arial;color:navy"> </span></font></p>
<p class="MsoNormal"><font size="2" color="navy" face="Arial"><span lang="EN-GB" style="font-size:10.0pt;font-family:Arial;color:navy">If later the other node
is powered on, it should join the cluster without problems.</span></font></p>
<p class="MsoNormal"><font size="2" color="navy" face="Arial"><span lang="EN-GB" style="font-size:10.0pt;font-family:Arial;color:navy"> </span></font></p><font color="#888888">
<p class="MsoNormal"><font size="2" color="navy" face="Arial"><span lang="EN-GB" style="font-size:10.0pt;font-family:Arial;color:navy">alvaro,</span></font></p></font><div><div></div><div class="h5">
<p class="MsoNormal"><font size="3" face="Times New Roman"><span lang="EN-GB" style="font-size:12.0pt"> </span></font></p>
<p class="MsoNormal"><font size="3" face="Times New Roman"><span style="font-size:12.0pt">Hi there,</span></font></p>
<div>
<p class="MsoNormal"><font size="3" face="Times New Roman"><span style="font-size:12.0pt"> </span></font></p>
</div>
<div>
<p class="MsoNormal"><font size="3" face="Times New Roman"><span style="font-size:12.0pt">I've setup a two-node cluster with cman, clvmd and gfs2. I don't use
qdisk but had</span></font></p>
</div>
<div>
<p class="MsoNormal"><font size="3" face="Times New Roman"><span style="font-size:12.0pt"><cman expected_votes="1" two_node="1"/></span></font></p>
</div>
<div>
<p class="MsoNormal"><font size="3" face="Times New Roman"><span style="font-size:12.0pt"> </span></font></p>
</div>
<div>
<p class="MsoNormal"><font size="3" face="Times New Roman"><span style="font-size:12.0pt">I would like to know what is the proper procedure to reboot a node in
the two-node cluster (maybe this applies for all size?) when both nodes are
functioning fine but I just want to reboot one for some reason (for example,
upgrade kernel). Is there a preferred/better way to reboot the machine rather
than just running the "reboot" command as root. I have been doing the
"reboot" command so far and it sometimes creates problems for us,
including making the other node to fail. </span></font></p>
</div>
<div>
<p class="MsoNormal"><font size="3" face="Times New Roman"><span style="font-size:12.0pt"> </span></font></p>
</div>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><font size="3" face="Times New Roman"><span style="font-size:12.0pt">Thank you very much.<br clear="all">
Shi<br>
-- <br>
Shi Jin, Ph.D.</span></font></p>
</div>
</div></div></div>
</div>
<br>--<br>
Linux-cluster mailing list<br>
<a href="mailto:Linux-cluster@redhat.com">Linux-cluster@redhat.com</a><br>
<a href="https://www.redhat.com/mailman/listinfo/linux-cluster" target="_blank">https://www.redhat.com/mailman/listinfo/linux-cluster</a><br></blockquote></div><br><br clear="all"><br>-- <br>Shi Jin, Ph.D.<br><br>
</div>