Re: [Pacemaker] Pengine assert in qb_log_from_external_source()

2012-12-05 Thread Vladislav Bogdanov
29.11.2012 09:36, Angus Salkeld wrote: ... >>> so, qb_array_index() fails once idx spans uint16_t boundary (0x) and >>> (uint16_t)idx > 0. >>> IMHO this naturally means some kind of integer overflow. >> >> Well done, I'll have a closer look at it. > > Patch here: > https://github.com/asalkeld/

Re: [Pacemaker] pacemaker processes RSS growth

2012-12-05 Thread Vladislav Bogdanov
06.12.2012 06:05, Andrew Beekhof wrote: > I wonder what the growth looks like with the recent libqb fix. > That could be an explanation. Valid point. I will watch. > > On Sat, Sep 15, 2012 at 5:23 AM, Vladislav Bogdanov > wrote: >> 14.09.2012 09:54, Vladislav Bogdanov wrote: >>> 13.09.2012 15:1

Re: [Pacemaker] Enable remote monitoring

2012-12-05 Thread Gao,Yan
Hi Andrew, Thanks for the comments! On 12/06/12 09:44, Andrew Beekhof wrote: > > On 05/12/2012, at 11:27 PM, "Gao,Yan" wrote: > >> Hi, >> This is the first step - the support of "restart-origin" for order >> constraint along with the test cases: >> >> https://github.com/gao-yan/pacemaker/commit

[Pacemaker] Nodes OFFLINE with "not in our membership" messages

2012-12-05 Thread pavan tc
Hi, I have now hit this issue twice in my setup. I see the following github commit addressing this issue: https://github.com/ClusterLabs/pacemaker/commit/03f6105592281901cc10550b8ad19af4beb5f72f >From the patch, it appears there is an incorrect conclusion about the status of the membership of nod

Re: [Pacemaker] node status does not change even if pacemakerd dies

2012-12-05 Thread Andrew Beekhof
On Wed, Dec 5, 2012 at 8:32 PM, Kazunori INOUE wrote: > (12.12.05 02:02), David Vossel wrote: >> >> >> >> - Original Message - >>> >>> From: "Kazunori INOUE" >>> To: "The Pacemaker cluster resource manager" >>> >>> Sent: Monday, December 3, 2012 11:41:56 PM >>> Subject: Re: [Pacemaker] n

Re: [Pacemaker] Corosync version '1.4.4' and its compatability with Pacemaker version.

2012-12-05 Thread Andrew Beekhof
On Wed, Dec 5, 2012 at 2:46 PM, Dhiraj Hadkar wrote: > Andrew, > > Thanks for your response > My Questions were: > which version of pacemaker Is coro 1.4.4 compatible with. Anything in the last few years. > can rhel 5.4 support coro 1.4.4. I believe so. I put up some RHEL5 rpms up at http://cl

Re: [Pacemaker] pacemaker processes RSS growth

2012-12-05 Thread Andrew Beekhof
I wonder what the growth looks like with the recent libqb fix. That could be an explanation. On Sat, Sep 15, 2012 at 5:23 AM, Vladislav Bogdanov wrote: > 14.09.2012 09:54, Vladislav Bogdanov wrote: >> 13.09.2012 15:18, Vladislav Bogdanov wrote: >> >> ... >> >>> and now it runs on my testing clust

Re: [Pacemaker] Enable remote monitoring

2012-12-05 Thread Andrew Beekhof
On 05/12/2012, at 9:05 AM, Lars Marowsky-Bree wrote: > On 2012-12-04T14:48:50, David Vossel wrote: > >> The resource ordered set with the 'restart-origin' option gets us half way >> there in the constraint definition. We still have to build the colocation >> set between the vm and the resou

Re: [Pacemaker] Enable remote monitoring

2012-12-05 Thread Andrew Beekhof
On 06/12/2012, at 5:00 AM, "Gao,Yan" wrote: > On 12/06/12 00:36, David Vossel wrote: >> >> >> - Original Message - >>> From: "Yan Gao" >>> To: pacemaker@oss.clusterlabs.org >>> Sent: Wednesday, December 5, 2012 6:27:05 AM >>> Subject: Re: [Pacemaker] Enable remote monitoring >>> >>>

Re: [Pacemaker] Enable remote monitoring

2012-12-05 Thread Andrew Beekhof
On 05/12/2012, at 11:27 PM, "Gao,Yan" wrote: > Hi, > This is the first step - the support of "restart-origin" for order > constraint along with the test cases: > > https://github.com/gao-yan/pacemaker/commits/restart-origin > > It looks straight-forward to me. Hope I didn't miss anything ;-) >

Re: [Pacemaker] Enable remote monitoring

2012-12-05 Thread Andrew Beekhof
On 05/12/2012, at 4:05 AM, Lars Marowsky-Bree wrote: > On 2012-12-04T11:45:16, David Vossel wrote: > >> I am okay with this constraint option being implemented, as it is the basis >> for this whole concept. When it comes time to make this usable, don't make >> the abstraction people use to

Re: [Pacemaker] Enable remote monitoring

2012-12-05 Thread Andrew Beekhof
On 05/12/2012, at 3:45 AM, David Vossel wrote: > - Original Message - >> From: "Lars Marowsky-Bree" >> To: "The Pacemaker cluster resource manager" >> Sent: Tuesday, December 4, 2012 6:59:08 AM >> Subject: Re: [Pacemaker] Enable remote monitoring >> >> On 2012-12-04T19:48:18, "Gao,Yan

Re: [Pacemaker] Enable remote monitoring

2012-12-05 Thread Andrew Beekhof
On 04/12/2012, at 9:20 AM, Lars Marowsky-Bree wrote: > On 2012-12-03T16:32:14, David Vossel wrote: > >>> + >>> + >>> + >> >> I don't feel strongly about this. Here's what comes to mind for me. >> >> force-recover - force recovery of both sides of the constraint if either >> s

Re: [Pacemaker] Enable remote monitoring

2012-12-05 Thread Gao,Yan
On 12/06/12 04:52, David Vossel wrote: Hi, This is the first step - the support of "restart-origin" for order constraint along with the test cases: https://github.com/gao-yan/pacemaker/commits/restart-origin It looks straight-forward to me. Hope I didn't miss

Re: [Pacemaker] Enable remote monitoring

2012-12-05 Thread David Vossel
- Original Message - > From: "Yan Gao" > To: pacemaker@oss.clusterlabs.org > Sent: Wednesday, December 5, 2012 12:00:57 PM > Subject: Re: [Pacemaker] Enable remote monitoring > > On 12/06/12 00:36, David Vossel wrote: > > > > > > - Original Message - > >> From: "Yan Gao" > >>

Re: [Pacemaker] Enable remote monitoring

2012-12-05 Thread Gao,Yan
On 12/06/12 00:36, David Vossel wrote: > > > - Original Message - >> From: "Yan Gao" >> To: pacemaker@oss.clusterlabs.org >> Sent: Wednesday, December 5, 2012 6:27:05 AM >> Subject: Re: [Pacemaker] Enable remote monitoring >> >> Hi, >> This is the first step - the support of "restart-ori

Re: [Pacemaker] Enable remote monitoring

2012-12-05 Thread David Vossel
- Original Message - > From: "Yan Gao" > To: pacemaker@oss.clusterlabs.org > Sent: Wednesday, December 5, 2012 6:27:05 AM > Subject: Re: [Pacemaker] Enable remote monitoring > > Hi, > This is the first step - the support of "restart-origin" for order > constraint along with the test cas

Re: [Pacemaker] Getting Started

2012-12-05 Thread Andrew Martin
Brett, The ocf:heartbeat:pingd resource agent is used to monitor network availability. This resource agent is actually deprecated - the recommended replacement is ocf:pacemaker:pingd. You can use ocf:pacemaker:pingd with a location constraint to move resources away from a node if it loses netw

Re: [Pacemaker] Enable remote monitoring

2012-12-05 Thread Gao,Yan
Hi, This is the first step - the support of "restart-origin" for order constraint along with the test cases: https://github.com/gao-yan/pacemaker/commits/restart-origin It looks straight-forward to me. Hope I didn't miss anything ;-) If restart-origin="true" combines with kind="Optional", it jus

Re: [Pacemaker] Difference between "crm resource" and crm_resource

2012-12-05 Thread pavan tc
> > They are not. "crm" shell just provides a more coherent wrapper around > the various commands. > > > Also, I see that "crm" has a -w option (which gives synchronous behaviour > > to the command) > > Is there something similar for crm_resource? > > No. crm shell then watches the DC until the tra

Re: [Pacemaker] Difference between "crm resource" and crm_resource

2012-12-05 Thread Lars Marowsky-Bree
On 2012-12-05T16:51:14, pavan tc wrote: > Hi, > > Can someone please explain how the commands - > > crm resource stop > > and > > crm_resource --resource --set-parameter target-role --meta > --parameter-value Stopped > > are different? They are not. "crm" shell just provides a more cohere

[Pacemaker] Difference between "crm resource" and crm_resource

2012-12-05 Thread pavan tc
Hi, Can someone please explain how the commands - crm resource stop and crm_resource --resource --set-parameter target-role --meta --parameter-value Stopped are different? Also, I see that "crm" has a -w option (which gives synchronous behaviour to the command) Is there something similar fo

Re: [Pacemaker] Getting Started

2012-12-05 Thread Brett Maton
Ok, almost there :) I'm having some trouble with VIPs either not starting or starting on the wrong node (so something isn't right :)). Lab04 should be the master (vipMaster), lab05 slave (vipSlave) (Postgres is up and running as a replication slave on lab05, although it's being reported as

Re: [Pacemaker] node status does not change even if pacemakerd dies

2012-12-05 Thread Kazunori INOUE
(12.12.05 02:02), David Vossel wrote: - Original Message - From: "Kazunori INOUE" To: "The Pacemaker cluster resource manager" Sent: Monday, December 3, 2012 11:41:56 PM Subject: Re: [Pacemaker] node status does not change even if pacemakerd dies (12.12.03 20:24), Andrew Beekhof wro