Hi, This is about the tarball compiling. I have installed pacemaker + corosync using the rpm provided by RHEL6.2 ( Pacemaker 1.1.6-3 and Corosync 1.4.1-4).
While compiling sbd the configure command does not succeed due to a suspect pacemaker package missing (but pacemaker is installed and works fine) [root@NCM_A@IPMB-SLOT:-:/home/gug/sbd-1837fd8cc64a]# ./configure checking build system type... x86_64-unknown-linux-gnu checking host system type... x86_64-unknown-linux-gnu checking for a BSD-compatible install... /usr/bin/install -c checking whether build environment is sane... yes checking for a thread-safe mkdir -p... /bin/mkdir -p checking for gawk... gawk checking whether make sets $(MAKE)... yes checking for style of include used by make... GNU checking for gcc... gcc checking for C compiler default output file name... a.out checking whether the C compiler works... yes checking whether we are cross compiling... no checking for suffix of executables... checking for suffix of object files... o checking whether we are using the GNU C compiler... yes checking whether gcc accepts -g... yes checking for gcc option to accept ISO C89... none needed checking dependency style of gcc... gcc3 checking whether gcc and cc understand -c and -o together... yes checking for pkg-config... /usr/bin/pkg-config checking pkg-config is at least version 0.9.0... yes checking for glib... yes checking for libcoroipcc... yes checking for pacemaker... no checking for pcmk... no configure: error: No package 'pacemaker' found Should I add some libs I'm not aware of? Actually, after launching the 'autoreconf' command the pacemaker_CFLAG variable doesn't seem to be set anywhere [root@NCM_A@IPMB-SLOT:-:/home/gug/sbd-1837fd8cc64a]# grep pacemaker_CFLAGS * config.log:ac_cv_env_pacemaker_CFLAGS_set= config.log:ac_cv_env_pacemaker_CFLAGS_value= config.log:pacemaker_CFLAGS='' configure:pacemaker_CFLAGS configure:pacemaker_CFLAGS configure: pacemaker_CFLAGS configure:if test -n "$pacemaker_CFLAGS"; then configure: pkg_cv_pacemaker_CFLAGS="$pacemaker_CFLAGS" configure: pkg_cv_pacemaker_CFLAGS=`$PKG_CONFIG --cflags "pacemaker, pacemaker-cib" 2>/dev/null` configure: pacemaker_CFLAGS=$pkg_cv_pacemaker_CFLAGS configure: CFLAGS="$CFLAGS $glib_CFLAGS $pacemaker_CFLAGS" configure.ac: CFLAGS="$CFLAGS $glib_CFLAGS $pacemaker_CFLAGS" Makefile.in:pacemaker_CFLAGS = @pacemaker_CFLAGS@ Any suggestion? I don't recall this issue has been treated since I am part of the mailing list Thanks G. -----Messaggio originale----- Da: linux-ha-boun...@lists.linux-ha.org [mailto:linux-ha-boun...@lists.linux-ha.org] Per conto di Lars Marowsky-Bree Inviato: mercoledì 10 aprile 2013 21:49 A: General Linux-HA mailing list Oggetto: Re: [Linux-HA] Fwd: stonith with sbd not working On 2013-04-10T17:47:56, Fredrik Hudner <fredrik.hud...@gmail.com> wrote: > Hi Lars, > I wouldn't mind to try to install one of the tar balls from > http://hg.linux-ha.org/sbd, only I'm not sure how to do it after I've > unzipped/tar it. I saw someone from a discussion group that wanted to > do it as well.. > If you only tell me how to get it installed (will upgrade pacemaker to > 1.1.8) sbd-1837fd8cc64a that would be great. > > I noticed after after I checked a bit closer that all those > sbd-common.c, sbd.h etc were missing.. (so yeah it was a packaging issue as such). Uhm, well. The tar ball you got from there is one you must compile. sbd-common.c etc are not intended to be present on an installed system. Thanks to Florian, sbd builds like any other autoconf project. But I don't think your problem is with sbd itself, but the init script of the cluster stack. On SLE HA, sbd ties into the openais/corosync scripts - to make sure that the cluster stack isn't started before sbd is running. You need to port that over to the RHEL environment. (And personally, no, I don't think a separate sbd script that pacemaker depends on would be good enough; we *really* don't want resources to start on a node we can't fence.) Also, it appears you're not getting call-outs to the external/sbd agent working. That may be a problem with how cluster-glue is build on RHEL; but then, 1.0.6 is not the most recent release either. If I'm not mistaken, cluster-glue will go away on RHEL anyway. You may want to inquire to RHT what their plans are for supporting the fence agents it included, if any such plans exist. Regards, Lars -- Architect Storage/HA SUSE LINUX Products GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 21284 (AG Nürnberg) "Experience is the name everyone gives to their mistakes." -- Oscar Wilde _______________________________________________ Linux-HA mailing list Linux-HA@lists.linux-ha.org http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems _______________________________________________ Linux-HA mailing list Linux-HA@lists.linux-ha.org http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
