Any objections Mori-san?
Seems like a reasonable change to me.
On Tue, Nov 9, 2010 at 1:26 PM, Vadym Chepkov wrote:
>
> Would it be too much harm to restore the previous behavior at least partially?
>
> diff -r 7f2e453eedfa -r ab2da8a98b47 tools/crm_mon.c
> --- a/tools/crm_mon.c Mon Nov 08 23:1
У вт, 2010-11-09 у 15:15 +0100, Pavlos Parissis пише:
> On 9 November 2010 15:06, Vadim S. Khondar wrote:
> > У вт, 2010-11-09 у 14:57 +0100, Pavlos Parissis пише:
> >> On 9 November 2010 14:14, Vadim S. Khondar wrote:
> >> >
> >> >
> >> >
> >> > If after this I edit CIB and apply it, all LRM mes
Message: 2
Date: Tue, 9 Nov 2010 08:50:21 +0100
From: Andrew Beekhof
To: The Pacemaker cluster resource manager
Subject: Re: [Pacemaker] there is bug in pingd?
Message-ID:
Content-Type: text/plain; charset="iso-8859-1"
On Tue, Nov 9, 2010 at 2:59 AM, jiaju liu wrote:
>> I want to
Hi,
We constituted a cluster by two node constitution.
The migration-threshold set it to 2.
We confirmed a phenomenon in the next procedure.
Step1) Start two nodes and send config5.crm. (The clnDiskd-resources is
original.)
Last updated: Tue Nov 9 21:10:49 2010
Stack: Heartbeat
C
I am using 1.0.9.1 of Pacemaker.
I have applied the fix for bug 2477 and it is not working for me.
I started with this: # crm_mon -n -1 Last updated: Mon Nov 8
09:49:07 2010 Stack: Heartbeat Current DC: mgraid-mkp9010repk-0
(f4e5e15c-d06b-4e37-89b9-4621af05128f) - partition wi
On 2010/11/09 7:07 PM, Vladimir Legeza wrote:
The only solution I know, is to change "/clone-node-max/" param on the fly.
See
http://oss.clusterlabs.org/pipermail/pacemaker/2010-November/008148.html
for details.
I have read the thread - it is a slightly different problem. In your
case, it is
The only solution I know, is to change "*clone-node-max*" param on the fly.
See http://oss.clusterlabs.org/pipermail/pacemaker/2010-November/008148.htmlfor
details.
Vladimir
On Tue, Nov 9, 2010 at 7:51 PM, Chris Picton wrote:
> From a previous thread (crm_resource - migrating/halt a cloned reso
Hello,
I have a cluster 2 nodes (RL 5.2) using pacemaker (1.0.9) with corosync
value="1.0.9-89bd754939df5150de7cd76835f98fe90851b677"/>
name="cluster-infrastructure" value="openais"/>
name="expected-quorum-votes" value="2"/>
name="no-quorum-policy" value="ignore"/>
name="stonith-enabled" valu
From a previous thread (crm_resource - migrating/halt a cloned resource)
Andrew Beekhof wrote:
> bottom line, you don't get to chose where specific clone instances
> get placed.
In my case, I have a clone:
primitive clusterip-9 ocf:heartbeat:IPaddr2 \
params ip="192.168.0.9" cidr_netmask
У вт, 2010-11-09 у 14:57 +0100, Pavlos Parissis пише:
> On 9 November 2010 14:14, Vadim S. Khondar wrote:
> >
> >
> >
> > If after this I edit CIB and apply it, all LRM messages disappear and
> > resource starts managed as it should.
>
> what do you mean edit CIB?
I mean
crm(live)#configure
crm(
On 9 November 2010 14:14, Vadim S. Khondar wrote:
>
>
>
> If after this I edit CIB and apply it, all LRM messages disappear and
> resource starts managed as it should.
what do you mean edit CIB?
BTW, I have seen that behavior as well on 1.0.9
Cheers,
Pavlos
___
On Tue, Nov 9, 2010 at 1:17 PM, Lars Kellogg-Stedman wrote:
>> It seems however, that there is more interest in running 1.1 on EPEL5
>> than I previously realized.
>> We're going to try and figure out how to make it happen for 1.1.5
>
> There are a *lot* of people out here still on RHEL5-derived p
On Tue, Nov 9, 2010 at 3:30 AM, Andrew Beekhof wrote:
> On Fri, Nov 5, 2010 at 6:39 PM, Vadym Chepkov wrote:
>>
>> On Nov 5, 2010, at 1:29 PM, Keisuke MORI wrote:
>>
>>> Hi Vadym,
>>>
>>> Could you provide the output of 'cibadmin -Q' to see what's happening
>>> over there?
>>>
>>> Thanks,
>>
>> A
> It seems however, that there is more interest in running 1.1 on EPEL5
> than I previously realized.
> We're going to try and figure out how to make it happen for 1.1.5
There are a *lot* of people out here still on RHEL5-derived platforms!
We're often restricted by organizational policy or by pa
У вт, 2010-11-09 у 09:49 +0100, Andrew Beekhof пише:
> being unmanaged is a side-effect of a) the resource failing to stop
> and b) no fencing being configured
> once you've fixed the error, run crm resource cleanup as misch suggested
>
I understand that.
However, for example, in situation when V
On Tuesday, November 09, 2010, Pavlos Parissis wrote:
> On 9 November 2010 11:25, Pavlos Parissis wrote:
> > Hi,
> >
> > Has anyone see the below error on a Filesytem resource?
> > 11:19:33 crmd: [3296]: info: do_lrm_rsc_op: Performing
> > key=13:19:0:9d7002dc-2865-4610-9240-ff844f62205d op=fs_01
On 9 November 2010 11:25, Pavlos Parissis wrote:
> Hi,
>
> Has anyone see the below error on a Filesytem resource?
> 11:19:33 crmd: [3296]: info: do_lrm_rsc_op: Performing
> key=13:19:0:9d7002dc-2865-4610-9240-ff844f62205d op=fs_01_stop_0 )
> 11:19:33 lrmd: [3293]: info: rsc:fs_01:74: stop
> 11:1
Hi,
Has anyone see the below error on a Filesytem resource?
11:19:33 crmd: [3296]: info: do_lrm_rsc_op: Performing
key=13:19:0:9d7002dc-2865-4610-9240-ff844f62205d op=fs_01_stop_0 )
11:19:33 lrmd: [3293]: info: rsc:fs_01:74: stop
11:19:33 Filesystem[31487]: [31493]: ERROR: Please set OCF_RESKEY_de
On 9 November 2010 09:47, Andrew Beekhof wrote:
[...snip...]
> > Since there is no realistic upgrade path to 1.1.4 on EPEL, I am
> > wondering if there any benefit of staying on 1.1.3 compared to using
> > 1.0.10.
>
>
> Its already out :-)
> Plus the ordering code is much improved.
>
I've just ch
On Mon, Nov 08, 2010 at 10:48:13PM +0100, Dejan Muhamedagic wrote:
> On Thu, Nov 04, 2010 at 10:50:53AM +0100, Eberhard Kuemmerle wrote:
> > On 3 Nov 2010 19:21, Dejan Muhamedagic wrote:
> > >> There are still some strange entries in /var/log/messages, but the
> > >> STONITH action is performed cor
On Sun, Oct 31, 2010 at 10:21 PM, Nikola Ciprich
wrote:
>> well, I was using 1.1.3 for a while, but I reverted to 1.0 line for
>> stability reasons.
>> furthermore, from what andrew said, 1.1.4 needs newer glib2 which complicates
>> things for us conservative people even more :)
>> but if the bug
On Mon, Nov 1, 2010 at 8:50 AM, Nikola Ciprich wrote:
>> I'd build it as a parallel package, f.e. glib224, with includes in
>> /usr/include/glib-2.24 and .so symlinks in /usr/lib/glib-2.24. Thus
>> you'll have everything in directories (separate from a "main" glib2
>> package) which you should man
being unmanaged is a side-effect of a) the resource failing to stop
and b) no fencing being configured
once you've fixed the error, run crm resource cleanup as misch suggested
On Wed, Nov 3, 2010 at 7:53 PM, Vadim S. Khondar wrote:
> Hello everyone.
>
> How can I take the resource back into manag
On Fri, Oct 29, 2010 at 2:14 PM, Pavlos Parissis
wrote:
> On 29 October 2010 12:23, Andrew Beekhof wrote:
>> On Fri, Oct 29, 2010 at 11:58 AM, Pavlos Parissis
>> wrote:
>>> On 29 October 2010 11:47, Andrew Beekhof wrote:
>>> [...snip..]
>> There wont be unfortunately.
>> Some of the cha
On Fri, Oct 29, 2010 at 10:16 PM, Lars Ellenberg
wrote:
> On Fri, Oct 29, 2010 at 12:58:47PM -0600, Serge Dubrouski wrote:
>> Hello -
>>
>> I'd like to translate some documents from Clusterlabs Wiki site to
>> Russian. How do I create a version of a page in a particular Language?
>
> You'd need to
On Mon, Nov 1, 2010 at 9:44 AM, Pavlos Parissis
wrote:
>
>
> On 1 November 2010 09:19, Pavlos Parissis wrote:
>>
>> Hi,
>> I have been using 1.1.3 on CentOS and I decided to downgrade to
>> 1.0.9.1-1.15.el5.
>> The procedure was the following
>> stop heartbeat on all cluster members
>> downgrade
On Fri, Nov 5, 2010 at 6:39 PM, Vadym Chepkov wrote:
>
> On Nov 5, 2010, at 1:29 PM, Keisuke MORI wrote:
>
>> Hi Vadym,
>>
>> Could you provide the output of 'cibadmin -Q' to see what's happening
>> over there?
>>
>> Thanks,
>
> As Yuusuke IIDA pointed out this is a new and expected behavior of cr
27 matches
Mail list logo
