If you can post you config, that would go a long way towards helping you out. otherwise you are asking people to guess at your problem as there could be many, or just something small.
-C On Tue, Mar 27, 2012 at 5:09 PM, Chen, Ming Ming <ming-ming.c...@hp.com>wrote: > Hi,**** > > IN RHEL 6 release, it says that :**** > > • If you are using a clustered system for failover where only a single > node that accesses the storage**** > > is active at any one time, you should use High Availability Logical Volume > Management agents (HALVM).**** > > ** ** > > That is exactly what I want to do, but could not find any information > about HALVM, and if it is included in the RHEL 6.**** > > Any information will be appreciated.**** > > Regards**** > > Ming**** > > ** ** > > ** ** > > *From:* linux-cluster-boun...@redhat.com [mailto: > linux-cluster-boun...@redhat.com] *On Behalf Of *Parvez Shaikh > *Sent:* Monday, March 26, 2012 5:10 AM > *To:* linux clustering > *Subject:* [Linux-cluster] [TOTEM] The consensus timeout expired.**** > > ** ** > > Hi all, > > I have a cluster with two blades in IBM BladeCenter. Following error is > appearing when I start cman service and it keep repeating the message > /var/log/messages -**** > > openais[10770]: [TOTEM] The consensus timeout expired. > openais[10770]: [TOTEM] entering GATHER state from 3.**** > > > Heart beating IP is available on the blade and link to blade2 is also > fine. Cluster on blade2 is not running. > > Services like iptables and portmap are also down. > > Has anyone encountered such error and resolved it? > > I am using RHEL 5.5**** > > cman_tool version > 6.2.0 config 1**** > > > > > Thanks, > Parvez**** > > -- > Linux-cluster mailing list > Linux-cluster@redhat.com > https://www.redhat.com/mailman/listinfo/linux-cluster >
-- Linux-cluster mailing list Linux-cluster@redhat.com https://www.redhat.com/mailman/listinfo/linux-cluster
