Um, you appear to have cman and corosync as cloned resources. Thats really not a good idea.
Have you seen the "clusters from scratch" document? That would be a good place to start. On Thu, Jun 14, 2012 at 8:16 AM, Yount, William D <[email protected]> wrote: > I have two servers, 10.89.99.31(KNTCLFS001) and 10.89.99.32(KNTCLFS002). I am > trying to use 10.89.99.30 to float between them in an Active/Active cluster. > > > > I have several services which should be running simultaneously on both > servers. I am trying to set up an Active/Active cluster. I am using the > cluster solely for NFS and am using GFS2 for clustered storage. > > > > What I would like is for either one of the nodes to go out, and the storage > to still be available. Right now, everything works fine if KNTCLFS002 goes > out. If KNTCLFS001 goes out instead, then nothing > > works, which probably means that everything was attaching to KNTCFLS001 to > begin with. I am not sure if I should adjust my stickiness settings. > > > > One specific issue is that after a reboot, the node will start corosync but > not cman. So I have to manually stop corosync and then start cman up. > > > > I am trying to use this as storage for VMs and I would like the storage to > always be available. Can someone look over the attached configuration and let > me know if any changes are warranted in order to achieve 'an always' up NFS > share? Is there a better solution? > > > > > Thanks, > William > > > _______________________________________________ > Linux-HA mailing list > [email protected] > http://lists.linux-ha.org/mailman/listinfo/linux-ha > See also: http://linux-ha.org/ReportingProblems _______________________________________________ Linux-HA mailing list [email protected] http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
