Dear All, I am using CentOS4 Update 3 Cluster Suite for i386 Architecture and my linux kernel version is 2.6.9-34.EL I have configured two node cluster My nodes are primary and secondary and I am using cluster to monitoring scripts During reboot or poweroff i am getting the problem is cman stop failed and I have verified the "/var/log/messages" log file and i getting the following messages Jun 12 18:34:13 primary cman: Stopping cman: Jun 12 18:34:16 primary cman: failed to stop cman failed Jun 12 18:34:16 primary cman: Jun 12 18:34:16 primary cman: Jun 12 18:34:16 primary rc: Stopping cman: failed We are not sure why this is happening. Can some one throw light on this. Regards -S.Balaji
The log info that you have provided is not enough to decide on the problem that you are facing. Could you please post the entire log and the cluster.conf file along with it. Thanks GS R Balaji wrote:> Dear All, > > I am using CentOS4 Update 3 Cluster Suite for i386 Architecture and > my linux kernel version is 2.6.9-34.EL > I have configured two node cluster > My nodes are primary and secondary and I am using cluster to > monitoring scripts > During reboot or poweroff i am getting the problem is cman stop failed > and I have verified the "/var/log/messages" log file and i getting the > following > messages > Jun 12 18:34:13 primary cman: Stopping cman: > Jun 12 18:34:16 primary cman: failed to stop cman failed > Jun 12 18:34:16 primary cman: > Jun 12 18:34:16 primary cman: > Jun 12 18:34:16 primary rc: Stopping cman: failed > > We are not sure why this is happening. Can some one throw light on this. > > Regards > -S.Balaji > _______________________________________________ > CentOS mailing list > CentOS at centos.org > http://lists.centos.org/mailman/listinfo/centos >-------------- next part -------------- A non-text attachment was scrubbed... Name: gsrlinux.vcf Type: text/x-vcard Size: 156 bytes Desc: not available URL: <http://lists.centos.org/pipermail/centos/attachments/20080613/fd47e7fe/attachment-0002.vcf>
HI, For ur cluster issue do md5sum check of cluster.conf on all the nodes and also use clean_start=1 in cluster.conf and check . REgards lingu On Fri, Jun 13, 2008 at 12:39 PM, Balaji <balajisundar at midascomm.com> wrote:> Dear All, > > I am using CentOS4 Update 3 Cluster Suite for i386 Architecture and > my linux kernel version is 2.6.9-34.EL > I have configured two node cluster > My nodes are primary and secondary and I am using cluster to monitoring > scripts > During reboot or poweroff i am getting the problem is cman stop failed > and I have verified the "/var/log/messages" log file and i getting the > following > messages > Jun 12 18:34:13 primary cman: Stopping cman: > Jun 12 18:34:16 primary cman: failed to stop cman failed > Jun 12 18:34:16 primary cman: > Jun 12 18:34:16 primary cman: > Jun 12 18:34:16 primary rc: Stopping cman: failed > > We are not sure why this is happening. Can some one throw light on this. > > Regards > -S.Balaji > _______________________________________________ > CentOS mailing list > CentOS at centos.org > http://lists.centos.org/mailman/listinfo/centos >-------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.centos.org/pipermail/centos/attachments/20080615/c658b648/attachment-0002.html>
Maybe Matching Threads
- CTDB+GFS2+CMAN. clean_start="0" or clean_start="1"?
- Clustersuite package installation failed in Itanium server
- Dependency problem between cman and openais with last cman update
- cluster.conf validating, but cman not starting
- DRBD,GFS2 and GNBD without all clustered cman stuff