Hi All,
The next change was accomplished by Mr. Lars.
https://github.com/ClusterLabs/pacemaker/commit/6a17c003b0167de9fe51d5330fb6e4f1b4ffe64c
I may lack the correction of other parts which are not the patch which I sent.
Best Regards,
Hideo Yamauchi.
--- On Mon, 2014/2/17, renayama19661...@
example: colocation ipwithpgsql inf: virtualip psql:Master
2014-02-17 6:25 GMT+01:00 Tomasz Kontusz :
>
>
> Andrew Beekhof napisał:
> >
> >On 16 Feb 2014, at 6:53 am, emmanuel segura wrote:
> >
> >> i think, if you use pacemaker_remote inside the container, the
> >container will be a normal no
Andrew Beekhof napisał:
>
>On 16 Feb 2014, at 6:53 am, emmanuel segura wrote:
>
>> i think, if you use pacemaker_remote inside the container, the
>container will be a normal node of you cluster, so you can run pgsql +
>vip in it
>>
>>
>> 2014-02-15 19:40 GMT+01:00 Tomasz Kontusz :
>> Hi
>> I'
Hi All,
The crm_mon tool which is attached to Pacemaker1.1 seems to have a problem.
I send a patch.
Best Regards,
Hideo Yamauchi.
trac2781.patch
Description: Binary data
___
Pacemaker mailing list: Pacemaker@oss.clusterlabs.org
http://oss.clusterlabs.o
14.02.2014 17:23, Beo Banks ?:
hi stefan,
it seems that's more stable but after 2 minute the issue is back again.
hopefully isn't a bug because it can reproduce it
node2 sents only unicast at sequenz 256...
node1
omping 10.0.0.22 10.0.0.21
10.0.0.22 :unicast, seq=257, size=69 bytes, dist=0,
17.02.2014, 02:27, "Andrew Beekhof" :
> With no quick follow-up, dare one hope that means the patch worked? :-)
>
Hi,
No, unfortunately the chief changed my plans on Friday and all day I was
engaged in a parallel project.
I hope that today have time to carry out the necessary tests.
> On 14 Feb
On 16 Feb 2014, at 6:53 am, emmanuel segura wrote:
> i think, if you use pacemaker_remote inside the container, the container will
> be a normal node of you cluster, so you can run pgsql + vip in it
>
>
> 2014-02-15 19:40 GMT+01:00 Tomasz Kontusz :
> Hi
> I'm setting up a cluster which will u
On 12 Feb 2014, at 1:39 am, Ajay Aggarwal wrote:
> Yes, we have cman (version: cman-3.0.12.1-49). We use manual fencing ( I know
> it is not recommended). There is an external monitoring and fencing service
> that we use (our own).
>
> Perhaps subject line "resource is too active problem in
Hi Andrew,
> >> Is this related to your email about symmetrical not being defaulted
> >> consistently between colocate_rsc_sets() and unpack_colocation_set()?
> >
> > Yes.
> > I think that a default is not handled well.
> > I will not have any problem when "sequential" attribute is set in cib by
On 17 Feb 2014, at 12:47 pm, renayama19661...@ybb.ne.jp wrote:
> Hi Andrew,
>
> Thank you for comments.
>
>> Is this related to your email about symmetrical not being defaulted
>> consistently between colocate_rsc_sets() and unpack_colocation_set()?
>
> Yes.
> I think that a default is not ha
Hi Andrew,
I found your correction.
https://github.com/beekhof/pacemaker/commit/37ff51a0edba208e6240e812936717fffc941a41
Many Thanks!
Hideo Yamauchi.
--- On Wed, 2014/2/12, renayama19661...@ybb.ne.jp
wrote:
> Hi All,
>
> There is difference in two between handling of "sequential" of "resouc
Hi Andrew,
Thank you for comments.
> Is this related to your email about symmetrical not being defaulted
> consistently between colocate_rsc_sets() and unpack_colocation_set()?
Yes.
I think that a default is not handled well.
I will not have any problem when "sequential" attribute is set in cib
Attachments beat pastebin as they don't expire :)
What does your config look like after you run:
crm resource migrate nfs_services nfs01
?
On 7 Feb 2014, at 5:00 am, Andrew J. Caines wrote:
> I'm new to Pacemaker and am working on my RTFM+STFW efforts, but have an
> urgent need to find the cau
On 31 Jan 2014, at 3:18 am, Pascal BERTON wrote:
> Hi !
>
> I recently changed hosting platform versions for my PCMK clusters, from
> RHEL6.0 equivalent towards SL6.4. Also changed from pcmk 1.1.2+corosync 1.3.3
> to pcmk 1.1.10+corosync 1.4.1 that come with SL6.
> Until now, I used to mana
On 7 Feb 2014, at 8:54 pm, Frank Brendel wrote:
>
>> Its somewhat inferred in the description of cluster-recheck-interval
>>
>>cluster-recheck-interval = time [15min]
>>Polling interval for time based changes to options, resource
>> parameters and constraints.
>>
>>
Is this related to your email about symmetrical not being defaulted
consistently between colocate_rsc_sets() and unpack_colocation_set()?
On 22 Jan 2014, at 3:05 pm, renayama19661...@ybb.ne.jp wrote:
> Hi All,
>
> My test seemed to include a mistake.
> It seems to be replaced by two limitation.
On 11 Feb 2014, at 8:23 pm, Bauer, Stefan (IZLBW Extern)
wrote:
> Hi List,
>
> we’ve recovered a cluster after a failure and used a previously exported
> cib.xml. Everything is back to normal state.
> The strange thing is, that the order in the output of crm_mon is not like
> before.
>
>
On 11 Feb 2014, at 2:49 am, Vladislav Bogdanov wrote:
> Hi,
>
> cannot find anywhere (am I blind?), is it possible to manually inject
> 'reload' op for a given resource?
>
> Background for this is if some configuration files are edited, and
> resource-agent (or LSB script) supports 'reload' op
On 7 Feb 2014, at 10:22 pm, Asgaroth wrote:
> On 06/02/2014 05:52, Vladislav Bogdanov wrote:
>> Hi,
>>
>> I bet your problem comes from the LSB clvmd init script.
>> Here is what it does do:
>>
>> ===
>> ...
>> clustered_vgs() {
>> ${lvm_vgdisplay} 2>/dev/null | \
>> awk 'B
On 25 Jan 2014, at 12:55 am, Parveen Jain wrote:
> Hi All,
> Can there be any problem if we install pacemaker/corosync on different
> subnets(for a simple two machine setup cluster) ?
Corosync uses multicast by default which I could easily imagine would not like
this kind of setup.
Perhaps
On 22 Jan 2014, at 12:18 am, Robert Lindgren wrote:
> Hi,
>
> I'm trying to get rid of some stonith info logging but I fail :(
Turn off debug and, for everything else, edit the C source code
>
> The log-lines are like this in syslog:
> Jan 21 13:24:15 wolf1 stonith-ng: [6349]: info: stonith_
On 21 Jan 2014, at 10:50 pm, Néstor C. wrote:
> Hello.
>
> When you need that some primitives switch in block you can use a group.
Groups are just a syntactic shortcut for ordering and colocation constraints.
>
> There is a manner to get this when you have a clone or a master/slave
> involv
Was there a question here somewhere?
On 20 Jan 2014, at 9:59 pm, Praveen wrote:
> [root@pcmk-2 ~]# pcs status
> Cluster name: mycluster
> Last updated: Mon Jan 20 15:56:13 2014
> Last change: Mon Jan 20 15:47:11 2014 via crm_attribute on pcmk-1
> Stack: corosync
> Current DC: pcmk-2 (2) - partit
On 20 Jan 2014, at 8:05 pm, Axel wrote:
> Hi all,
>
> this is my first post, i hope i meet all required informations and netiquette
> on this list.
>
> I need help to backup and restore resource configuration i made with corosync
> / pacemaker an an ubuntu server (precise)
>
> I configured
On 17 Jan 2014, at 4:33 pm, Michael Monette wrote:
> Hi,
>
> I have 2 servers setup with Postgres and /dev/drbd1 is mounted at
> /var/lib/pgsql. I also have pacemaker setup and it's setup to fail back and
> forth between the 2 nodes. It works really well for the most part.
>
> I am having th
On 13 Feb 2014, at 9:56 am, Andrew Daugherity wrote:
> I noticed in recent discussions on this list that this RA is apparently a
> SUSE thing and not upstreamed into resource-agents. This was news to me, but
> apparently is indeed the case.
>
> I guess it's SUSE's decision whether to push it
With no quick follow-up, dare one hope that means the patch worked? :-)
On 14 Feb 2014, at 3:37 pm, Andrey Groshev wrote:
> Yes, of course. Now beginning build world and test )
>
> 14.02.2014, 04:41, "Andrew Beekhof" :
>> The previous patch wasn't quite right.
>> Could you try this new one?
>>
27 matches
Mail list logo
