Thanks for all your help Andrew and Thomas, I finally worked out what was going wrong. A separate cluster of 2 servers on the same network were configured to multicast over the same port numbers as those I was specifying in the corosync.confs of the cluster I was working on. So every time I tried to start my cluster is was failing because it was receiving conflicting communications from the other cluster. After changing the port numbers, corosync now starts up without a problem.
However, I do have one more question: If pacemaker is supposed to replace heartbeat as the crm, why is it that the pacemaker rpms that I am using from http://www.clusterlabs.org/rpm/epel-5/x86_64/ have a dependency on the heartbeat rpm? You cannot install the pacemaker rpms without the heartbeat rpm (unless of course you use --no-deps). The instructions on this page http://www.clusterlabs.org/wiki/Install#Binary_Packages specifically tell you to do the following in order to install the required software for a pacemaker cluster on Redhat Enterprise: yum install -y pacemaker corosync heartbeat Is it just that there are some shared scripts or binaries or libraries that pacemaker needs from heartbeat? Cheers, Tom On Mon, Mar 22, 2010 at 2:35 PM, Andrew Beekhof <[email protected]> wrote: > On Sat, Mar 20, 2010 at 1:06 AM, Thomas Guthmann <[email protected]> > wrote: > > Hi Tom, > > > >> heartbeat-libs-3.0.2-2.el5.x86_64.rpm > >> heartbeat-3.0.2-2.el5.x86_64.rpm > >> openais-1.1.0-1.el5.x86_64.rpm > >> openaislib-1.1.0-1.el5.x86_64.rpm > > > > I reckon it could be due to the presence of openais _and_ corosync. > > If you want to use corosync you don't need openais. Same than before, > > you don't need heartbeat if you plan to use pacemaker (or the opposite) > > though that shouldn't hurt. > > Pacemaker needs either corosync or heartbeat. > If you have corosync, you can also add openais on top - but thats only > necessary when using GFS2. > > Try this getting started doc: > > http://www.clusterlabs.org/mediawiki/images/5/56/Cluster_from_Scratch_-_Fedora_12.pdf > > > Then, start simple, use a copy of the default corosync.conf in > > /etc/corosync/ and use one ring. It seems you are trying to use an old > > openais configuration which actually could work but to debug correctly > > add your needs one by one (2nd ring, new parameters, etc). Starting with > > the lot is usually more complicated to debug than progressively > > increasing complexity. > > > > Good luck > > Thomas. > > _______________________________________________ > > Openais mailing list > > [email protected] > > https://lists.linux-foundation.org/mailman/listinfo/openais > > >
_______________________________________________ Openais mailing list [email protected] https://lists.linux-foundation.org/mailman/listinfo/openais
