On Fri, 11 Dec 2009 10:24:49 +0000, Christine Caulfield wrote > On 11/12/09 10:21, Kaloyan Kovachev wrote: > > On Fri, 11 Dec 2009 09:58:38 +0000, Christine Caulfield wrote > >> On 11/12/09 09:48, Kaloyan Kovachev wrote: > >>> On Thu, 10 Dec 2009 16:12:33 +0000, Christine Caulfield wrote > >>>> On 10/12/09 15:27, Kaloyan Kovachev wrote: > >>>>> Hello, > >>>>> after upgrading to 3.0.6 i get: > >>>>> > >>>>> Starting cman... Relax-NG validity error : Extra element cman in interleave > >>>>> > >>>>> but cluster.conf should be correct and was working so far without problems. > >>>>> The coresponding section in<cluster> is: > >>>>> > >>>>> <cman expected_votes="7"> > >>>>> <multicast addr="239.192.11.81" keyfile="/etc/cluster/cman_authkey"/> > >>>>> </cman> > >>>>> > >>>>> how should i change it to pass the validity check? > >>>> > >>>> Remove the keyfile="" attribute. cman ignores it anyway :-) > >>>> > >>> > >>> I am sure it was working with RHCM v2, so it seems i will need to rewrite the > >>> config for V3, as i get another error now about specifying multicast interface > >>> for clusternode and there will be others for sure > >> > >> Yes, it would work fine under v2. In fact it's working now - you're just > >> getting a warning message (I hope!). We have added a lot more checks to > >> the configuration to try and help invalid configurations from being run > >> and causing trouble. > > > > when starting the cluster i get just warnings, but updating the config and > > using cman_tool version -r cman doesn't reload it, so i am forced to fix my > > errors :) > > > >> > >>>> If you need to specify an encrpytion key it should go into the<totem> > >>>> part of cluster.conf. > >>>> > >>> > >>> looking at cluster.rng keyfile is valid for the cman block. May i just move it > >>> there or i should create<totem> > >> > >> I would just remove it. It's not doing anything, so if you move it to > >> <totem> you will change the encryption key used by the cluster and have > >> to reboot all your nodes to get them communicating again. > >> > > > > The cluster is not a production one, so it is OK and am looking for the > > correct end result. My question was actually 'Is encription key valid/used > > only from<totem> section or in<cman> too as described in cluster.rng > > file'. > > > > Multicast and keyfile are present in both<cman> and<totem> ... i guess > > <totem> is the preferred one for future compatibility? > > > > Confusingly, multicast must be part of <cman> and keyfile should be part > of <totem>. > > That's just how it is, sorry ;-) >
Thanks. The validation schema should be updated then, as it allows keyfile in cman too (fixed in my copy and could provide a patch). I still can't find how do i specify per node interface. There is interface allowed only in <totem> section while most of the nodes have (and use) bond0, for one of them i need to specify different interface for cluster communication. Is per node interface attribute missed from the validation schema or is removed completely? > Chrissie > > -- > 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
