Re: [ClusterLabs] Fwd: Getting error when building Pacemaker-1.1 from source

2016-03-01 Thread Klaus Wenninger 
I would strongly recommend installing everything at the final
destination  - in a changeroot
build environment if you don't want to taint your build-host.

Regards,
Klaus

On 03/02/2016 03:46 AM, Sharat Joshi wrote:
> Hi List Folk,
>
> I am very new to Pacemaker and I am trying to build using sources.
> After successfully installing libqb and corosync under
> /disk1/software/libqb and /disk1/software/corosync and setting 
>
> $ export
> PKG_CONFIG_PATH=/disk1/software/libqb/lib/pkgconfig:/disk1/software/corosync/lib/pkgconfig
>
> $./autogen.sh && ./configure --prefix=/disk1/software/pacemaker
>
> I try building the final peice Pacemaker and I get the following...
>
> configure: WARNING: Unable to support Corosync: corosync/libqb IPC
> libraries not found by pkg_config
>
> checking for supported stacks... configure: error: in
> `/disk1/software/pacemaker-1.1':
>
> configure: error: You must support at least one cluster stack
> (heartbeat or corosync)
>
>
> I am stuck in this error since a day now, Please help.
>
> Thanks,
>
> Sharat Joshi
>
>
>
>
> ___
> Users mailing list: Users@clusterlabs.org
> http://clusterlabs.org/mailman/listinfo/users
>
> Project Home: http://www.clusterlabs.org
> Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
> Bugs: http://bugs.clusterlabs.org

___
Users mailing list: Users@clusterlabs.org
http://clusterlabs.org/mailman/listinfo/users

Project Home: http://www.clusterlabs.org
Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
Bugs: http://bugs.clusterlabs.org

[ClusterLabs] Fwd: Getting error when building Pacemaker-1.1 from source

2016-03-01 Thread Sharat Joshi 
Hi List Folk,

I am very new to Pacemaker and I am trying to build using sources.
After successfully installing libqb and corosync under
/disk1/software/libqb and /disk1/software/corosync and setting

$ export
PKG_CONFIG_PATH=/disk1/software/libqb/lib/pkgconfig:/disk1/software/corosync/lib/pkgconfig
$./autogen.sh && ./configure --prefix=/disk1/software/pacemaker

I try building the final peice Pacemaker and I get the following...

configure: WARNING: Unable to support Corosync: corosync/libqb IPC
libraries not found by pkg_config

checking for supported stacks... configure: error: in
`/disk1/software/pacemaker-1.1':

configure: error: You must support at least one cluster stack (heartbeat or
corosync)


I am stuck in this error since a day now, Please help.

Thanks,

Sharat Joshi
___
Users mailing list: Users@clusterlabs.org
http://clusterlabs.org/mailman/listinfo/users

Project Home: http://www.clusterlabs.org
Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
Bugs: http://bugs.clusterlabs.org

[ClusterLabs] ELEMENTARY :: Please Help :: Getting error when building Pacemaker-1.1 from source

2016-03-01 Thread Sharat Joshi 
Hi List Folk,

I am very new to Pacemaker and I am trying to build using sources.
After successfully installing libqb and corosync under
/disk1/software/libqb and /disk1/software/corosync and setting

$ export
PKG_CONFIG_PATH=/disk1/software/libqb/lib/pkgconfig:/disk1/software/corosync/lib/pkgconfig
$./autogen.sh && ./configure --prefix=/disk1/software/pacemaker

I try building the final peice Pacemaker and I get the following...

configure: WARNING: Unable to support Corosync: corosync/libqb IPC
libraries not found by pkg_config

checking for supported stacks... configure: error: in
`/disk1/software/pacemaker-1.1':

configure: error: You must support at least one cluster stack (heartbeat or
corosync)


I am stuck in this error since a day now, Please help.

Thanks,

Sharat Joshi
___
Users mailing list: Users@clusterlabs.org
http://clusterlabs.org/mailman/listinfo/users

Project Home: http://www.clusterlabs.org
Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
Bugs: http://bugs.clusterlabs.org

Re: [ClusterLabs] Connectivity is degraded (Expected=300)

2016-03-01 Thread Ken Gaillot 
On 03/01/2016 08:24 AM, Rafał Sanocki wrote:
> Hello
> Can you tell if that message is correct "
> 
>  #crm_mon -A
> Online: [ nodeA nodeB ]
> failover-ip1(ocf::pacemaker:wall):  Started nodeB
>  Clone Set: my-conn
>  Started: [ nodeA nodeB ]
>  Clone Set: my-connp
>  Started: [ nodeA nodeB ]
> Node Attributes:
> * Node nodeA:
> + arping: 0
> + pingd : 200   : Connectivity
> is degraded (Expected=300)

crm_mon prints messages like this for ping/pingd resources. The expected
value is the number of nodes in the resource's host_list parameter
multiplied by its multiplier parameter (default 1 if not specified). If
the actual value is less than the expected value, it will print the message.

Whether that's "correct" depends on what you mean by that. It's correct
in that the actual value is less than the expected value.

> * Node nodeB:
> + arping: 100
> + pingd : 200   : Connectivity
> is degraded (Expected=300)


___
Users mailing list: Users@clusterlabs.org
http://clusterlabs.org/mailman/listinfo/users

Project Home: http://www.clusterlabs.org
Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
Bugs: http://bugs.clusterlabs.org

Re: [ClusterLabs] [Announce] libqb 10.rc3 release

2016-03-01 Thread Christine Caulfield 
On 26/02/16 07:58, Jan Pokorný wrote:
> On 26/02/16 14:27 +0900, Keisuke MORI wrote:
>> As of libqb-1.0rc3, Pacemaker fails to build upon it with the gcc
>> warnings as below.
>> There was no such a problem until 1.0rc2, and it seems that the
>> changes in the pull request #175 is related.
>>
>> https://github.com/ClusterLabs/libqb/pull/175
>>
>> {{{
>> [root@build-centos71 pacemaker ((Pacemaker-1.1.14))]# rpm -qa | grep libqb
>> libqb-1.0rc3-1.el7.x86_64
>> libqb-devel-1.0rc3-1.el7.x86_64
>>
>> [root@build-centos71 pacemaker ((Pacemaker-1.1.14))]# git checkout
>> Pacemaker-1.1.14
>> HEAD is now at 70404b0... Merge pull request #892 from kgaillot/1.1
>> [root@build-centos71 pacemaker ((Pacemaker-1.1.14))]# make release
>> (snip)
>> In file included from ../../include/crm_internal.h:33:0,
>>  from ipc.c:19:
>> ipc.c: In function 'crm_ipcs_flush_events':
>> ../../include/crm/common/logging.h:140:23: error: format '%d' expects
>> argument of type 'int', but argument 10 has type 'ssize_t'
>> [-Werror=format=]
>>  static struct qb_log_callsite *trace_cs = NULL; \
>>^
>> ../../include/crm/common/logging.h:254:37: note: in expansion of macro
>> 'do_crm_log_unlikely'
>>  #  define crm_trace(fmt, args...)   do_crm_log_unlikely(LOG_TRACE,
>> fmt , ##args)
>>  ^
>> [...]
> 
> Looks like that PR of mine turned out to be generally a good thing as it
> effectively discovers wrong printf-format usage compared to the actual
> arguments, exactly according to what you report :-)
> 
> Will take care of the problematic code in Pacemaker.
> 
> 

Good work :-)

Chrissie


___
Users mailing list: Users@clusterlabs.org
http://clusterlabs.org/mailman/listinfo/users

Project Home: http://www.clusterlabs.org
Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
Bugs: http://bugs.clusterlabs.org