Hi ,

Thanks for your extended support and advise. I would like to give some 
background information about my exercise, which will give some fair idea to you 
folks. 

We are planning to use pacemaker + Corosync + CMAN stack in RHEL 6.5 OS. For 
the same, we are trying to collect the source from Clusterlab.

Initially we got the Pacemaker and Corosync Source successfully from Clusterlab 
and we were unable to fetch the source for CMAN from Cluster lab.

As you suggested, We already tried to use the latest set of Pacemaker with its 
prerequisites (Corosync) on top of RHEL 6.5, but it fails due to dependencies 
of RHEL 7.x Components (Systemd).

So we are requesting you to provide the below information.

Is it possible for me to get the source code for CMAN from Cluster lab ??? 
(since we are planning to use it for our production purpose, that's why we 
don't want to go with Red hat sites (even for Publicly available)).


With Regards
Somanath Thilak J

-----Original Message-----
From: Jan Pokorný <[email protected]> 
Sent: Friday, August 30, 2019 20:15
To: [email protected]
Subject: Re: [ClusterLabs] Pacemaker 1.1.12 does not compile with CMAN Stack.

On 30/08/19 13:03 +0000, Somanath Jeeva wrote:
> In Pacemaker 1.1.12 version try to compile with CMAN Stack,

midly put, it's like trying to run with dinosaurs; that version of pacemaker 
together with that effectively superseded bundle of other components will 
hardly receive any attention in 2019.

But let's assume there's a reason.

> but we are unable to achieve that .
> 
> Source taken path : 
> https://github.com/ClusterLabs/pacemaker/tree/Pacemaker-1.1.12
> 
> After Extracting, we installed required dependencies as per 
> README.markdown,
> 
> ## Installing from source
> 
>     $ ./autogen.sh
>     $ ./configure
>     $ make
>     $ sudo make install
> 
> After performing above task, we are unable to start pacemaker due to 
> cman stack is unrecognized service.

Well, pacemaker alone won't magically bootstrap these other prerequisites, you 
need to take an effort of grabbing them as well.

For CMAN in particular, look here:

https://pagure.io/linux-cluster/cluster/blob/STABLE32/f/cman
https://ftp.redhat.com/pub/redhat/linux/enterprise/6Server/en/RHS/SRPMS/cluster-3.0.12.1-73.el6.src.rpm

> # service pacemaker status
> pacemakerd dead but pid file exists
> #service cman status
> cman: unrecognized service

Easy, no /etc/init.d/cman around, for the mentioned reason.

Still, I am not sure how far you'll get, sounds like an uphill battle.
Settling with the rather recent state of development may avoid significant 
chunks of troubles, incl. those that were only fixed in later versions of 
pacemaker.

> Please find the ./configure screenshot of the system:
> 
> pacemaker configuration:
>   Version                  = 1.1.12 (Build: 561c4cfda1)
>   Features                 = libqb-logging libqb-ipc lha-fencing nagios  
> corosync-plugin cman acls
> 
>   Prefix                   = /usr
>   Executables              = /usr/sbin
>   Man pages                = /usr/share/man
>   Libraries                = /usr/lib64
>   Header files             = /usr/include
>   Arch-independent files   = /usr/share
>   State information        = /var
>   System configuration     = /etc
>   Corosync Plugins         = /usr/libexec/lcrso
> 
>   Use system LTDL          = yes
> 
>   HA group name            = haclient
>   HA user name             = hacluster
> 
>   CFLAGS                   = -g -O2 -I/usr/include -I/usr/include/heartbeat   
>    -ggdb  -fgnu89-inline -fstack-protector-all -Wall -Waggregate-return 
> -Wbad-function-cast -Wcast-align -Wdeclaration-after-statement -Wendif-labels 
> -Wfloat-equal -Wformat=2 -Wmissing-prototypes -Wmissing-declarations 
> -Wnested-externs -Wno-long-long -Wno-strict-aliasing 
> -Wunused-but-set-variable -Wpointer-arith -Wwrite-strings -Werror
>   Libraries                = -lgnutls -lqb -lplumb -lpils -lqb -lbz2 -lxslt 
> -lxml2 -lc -luuid -lpam -lrt -ldl  -lglib-2.0   -lltdl -lqb -ldl -lrt 
> -lpthread
>   Stack Libraries          =   -lcoroipcc   -lcpg   -lcfg   -lconfdb   -lcman 
>   -lfenced
> 
> 
> Is there anything I am missing in the configure, to get the cman 
> stack.

I think having "cman" enumerated amongst features might be enough, but once 
you'll get past the "cman: unrecognized service" phase, you shall see.

Hope this helps.

--
Jan (Poki)
_______________________________________________
Manage your subscription:
https://lists.clusterlabs.org/mailman/listinfo/users

ClusterLabs home: https://www.clusterlabs.org/

Reply via email to