[Pacemaker] cmrd problem when building from source

[David Vossel]

----- Original Message -----
> From: "David Vossel" <dvossel at redhat.com>
> To: "The Pacemaker cluster resource manager" <pacemaker at oss.clusterlabs.org>
> Sent: Monday, January 30, 2012 9:32:03 AM
> Subject: Re: [Pacemaker] cmrd problem when building from source
> 
> ----- Original Message -----
> > From: "Andrew Beekhof" <andrew at beekhof.net>
> > To: "The Pacemaker cluster resource manager"
> > <pacemaker at oss.clusterlabs.org>
> > Sent: Monday, January 30, 2012 12:01:47 AM
> > Subject: Re: [Pacemaker] cmrd problem when building from source
> > 
> > On Mon, Jan 30, 2012 at 2:19 PM, David Vossel <dvossel at redhat.com>
> > wrote:
> > > Howdy,
> > >
> > > I'm interested in contributing to pacemaker, but I am having a
> > > little trouble getting pacemaker going from source. Everything
> > > works great for me using the FC16 packages though :)
> > >
> > > Right now I'm building both corosync and pacemaker from the
> > > current
> > > head of their git master branches. Maybe this isn't even
> > > recommended for development purposes and I should be taking a
> > > different approach... If that's the case stop me here and we'll
> > > start with that.
> > 
> > Normally thats fine, however the corosync quorum API only just
> > arrived
> > and at the same time they dropped support for plugins (which
> > pacemaker
> > had been using).
> > So things are a little fragile in master at the moment.
> > 
> > I've been working through some of the issues lately, you might have
> > more joy with my github repo.
> 
> I have been using the github repo,
> https://github.com/ClusterLabs/pacemaker.git.  Just so I can have a
> starting point I know should work, can someone point me to a recent
> revision in both the pacemaker and corosync github repos that
> appears to be stable for them?
> 
> -- David
> 

I figured out what my problem was with crmd failing. The libcrmcluster.so file crmd was using was wrong.  I apparently had an old version of libscrmcluster in /usr/lib that I hadn't cleaned out.  The one I wanted crmd to use was in /usr/lib64/.  I guess it was defaulting to the one in /usr/lib/ that I didn't even know existed.

-- David