On Fri, 2007-03-09 at 15:47 +0100, Fabien MALFOY wrote: > Hi > > I'm trying to build a two nodes cluster with Cluster Manager on Fedora > Core 6. As I dispose of only one machine and that my solution needs > three, I decided to create two XEN virtual Fedora Core 6 (M1 and M2). I > use the Dom0 (M0) host as the storage back-end. All used packages are > those of standard repositories of Fedora Core 6 (including Xen, Cman, > OpenAIS...). So, the cluster will be made of the two DomU. > > But i'm not able to start correctly the Cman service on M1 and M2. > Here's a part of the log : > > Mar 7 15:29:17 M1 openais[2220]: [CMAN ] CMAN 2.0.60 (built Jan 24 2007 > 15:30:39) started > Mar 7 15:29:17 M1 openais[2220]: [SYNC ] Not using a virtual synchrony > filter. > Mar 7 15:29:17 M1 openais[2220]: [MAIN ] AIS Executive Service: started > and ready to provide service. > Mar 7 15:29:18 M1 ccsd[2214]: Initial status:: Inquorate > *Mar 7 15:29:32 M1 openais[2220]: [TOTEM] The consensus timeout expired. > Mar 7 15:29:32 M1 openais[2220]: [TOTEM] entering GATHER state from 3. > Mar 7 15:29:47 M1 openais[2220]: [TOTEM] The consensus timeout expired. > Mar 7 15:29:47 M1 openais[2220]: [TOTEM] entering GATHER state from 3. > Mar 7 15:30:02 M1 openais[2220]: [TOTEM] The consensus timeout expired. > Mar 7 15:30:02 M1 openais[2220]: [TOTEM] entering GATHER state from 3. > > *This till the timeout and cman fails to start. To ensure that my > configuration was well formed, I adapted my cluster.conf to exclude M2, > replaced by M0. In this case, the cman service starts correctly on M0 > and warns about the absence of M1. On M1, the service fails to start > with the same log. Is there a matter between Xen and Cluster Manager ? > Thanks for your help. > Fabien, I believe the problem you have is that your default firewall rules setup by fedora core 6 are not allowing the openais protocol to reach consensus. To start off with, try turning off your firewall. Regards -steve -- Linux-cluster mailing list Linux-cluster@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/linux-cluster
