Hi All,
We confirmed a state of the recognition of the cluster in the next procedure.
We confirm it by the next combination.(RHEL6.4 guest)
* corosync-2.3.0
* pacemaker-Pacemaker-1.1.10-rc3
-
Step 1) Start all nodes and constitute a cluster.
[root@rh64-coro1 ~]# crm_mo
Hi All,
I registered this problem with Bugzilla.
* http://bugs.clusterlabs.org/show_bug.cgi?id=5160
Best Regards,
Hideo Yamauchi.
--- On Tue, 2013/6/4, renayama19661...@ybb.ne.jp
wrote:
> Hi All,
>
> We confirmed a state of the recognition of the cluster in the next procedure.
> We confirm
Hi Andrew,
> Yep, sounds like a problem.
> I'll follow up on bugzilla
All right!
Many Thanks!
Hideo Yamauchi.
--- On Tue, 2013/6/4, Andrew Beekhof wrote:
>
> On 04/06/2013, at 3:00 PM, renayama19661...@ybb.ne.jp wrote:
>
> >
> > It is right movement that recognize other nodes in a UNCLEAN
Hi All,
Though the trouble is only once, two error information is displayed in crm_mon.
-
[root@rh64-coro2 ~]# crm_mon -1 -Af
Last updated: Thu Aug 29 18:11:00 2013
Last change: Thu Aug 29 18:10:45 2013 via cibadmin on rh64-coro2
Stack: corosync
Current DC
Hi Andres,
Thank you for comment.
> But to be seriously: I see this phaenomena, too.
> (pacemaker 1.1.11-1.el6-4f672bc)
If the version that you confirm is the same as next, probably it will be that
the same problem happens.
There is a similar cord.
(https://github.com/ClusterLabs/pacemaker/blob
Hi Andrew,
> > Hi All,
> >
> > Though the trouble is only once, two error information is displayed in
> > crm_mon.
>
> Have you got the full cib for when crm_mon is showing this?
No.
I reproduce a problem once again and acquire cib.
Best Regards,
Hideo Yamauchi.
_
Hi Andrew,
> > > Though the trouble is only once, two error information is displayed in
> > > crm_mon.
> >
> > Have you got the full cib for when crm_mon is showing this?
>
> No.
> I reproduce a problem once again and acquire cib.
I send the result that I acquired by cibadmin -Q command.
Best
Hi Andrew,
I confirmed that a problem was solved in a revision.
Thanks!
Hideo Yamauchi.
--- On Wed, 2013/9/4, Andrew Beekhof wrote:
> Thanks (also to Andreas for sending me an example too)!
>
> Fixed:
> https://github.com/beekhof/pacemaker/commit/a32474b
>
> On 04/09/2013, at 11:02 AM, re
Hi Andrew,
Hi Takatsuka san,
What kind of procedure did the problem that became this problem cause it in?
If a problem easily happens in the environment of the user, we think that it is
necessary to contact a user using Pacemaker1.0.13.
Best Regards,
Hideo Yamauchi.
--- On Thu, 2013/11/14, TAKA
Hi All,
I contributed next bugzilla by a problem to occur for the difference of the
timing of the attribute update by attrd before.
* https://developerbugs.linuxfoundation.org/show_bug.cgi?id=2528
We can evade this problem now by using crmd-transition-delay parameter.
I confirmed whether I cou
Hi Andrew,
Thank you for comments.
> Are you using the new attrd code or the legacy stuff?
I use new attrd.
>
> If you're not using corosync 2.x or see:
>
> crm_notice("Starting mainloop...");
>
> then its the old code. The new code could also be used with CMAN but isn't
> configured t
Hi Andrew,
> >> Are you using the new attrd code or the legacy stuff?
> >
> > I use new attrd.
>
> And the values are not being sent to the cib at the same time?
As far as I looked. . .
When the transmission of the attribute of attrd of the node was late, a leader
of attrd seemed to send an a
Hi All,
When a user changes the "globally-unique" attribute of the resource, a problem
occurs.
When it manages the resource with PID file, this occurs, but this is because
PID file name changes by "globally-unique" attribute.
(snip)
if [ ${OCF_RESKEY_CRM_meta_globally_unique} = "false" ]; then
Hi Andrew,
Thank you for comment.
> > But, the resource does not stop because PID file was changed as for the
> > changed resource of the "globally-unique" attribute.
>
> I'd have expected the stop action to be performed with the old attributes.
> crm_report tarball?
Okay.
I register this top
Hi Andrew,
Sorry
This problem is a thing of Pacemaker1.0.
On Pacemaker1.1.11, the resource did movement to stop definitely.
When "globally-unique" attribute changed somehow or other in Pacemaker1.1,
Pacemkaer seems to carry out the reboot of the resource.
(snip)
Jan 15 18:29:40 rh64-2744 p
Hi All,
We confirm a function of resource_set.
There were the resource of the group and the resource of the clone.
(snip)
Stack: corosync
Current DC: srv01 (3232238180) - partition WITHOUT quorum
Version: 1.1.10-f2d0cbc
1 Nodes configured
7 Resources configured
Online: [ srv01 ]
Resource Gro
Hi All,
My test seemed to include a mistake.
It seems to be replaced by two limitation.
> However, I think that symmetircal="false" is applied to all order limitation
> in this.
> (snip)
>
>
>
>
>
>
> ...
>
>
Hi Andrew,
It became late.
I registered this problem by Bugzilla.
The report file is attached, too.
* http://bugs.clusterlabs.org/show_bug.cgi?id=5194
Best Regards,
Hideo Yamauchi.
--- On Tue, 2014/1/14, Andrew Beekhof wrote:
>
> On 14 Jan 2014, at 4:33 pm, renayama19661...@ybb.ne.jp wrote:
Hi All,
We tried to set sequential attribute of resource_set of colocation in true in
crmsh.
We tried the next method, but true was not able to set it well.
-
[pengine]# crm --version
2.0 (Build 7cd5688c164d2949009accc7f172ce559cadbc4b)
- Pattern 1 -
colocation rsc_colocat
Hi Kristoffer.
Thank you for comments.
We wait for a correction.
Many Thanks!
Hideo Yamauchi.
--- On Wed, 2014/2/5, Kristoffer Grönlund wrote:
> On Wed, 5 Feb 2014 15:55:42 +0900 (JST)
> renayama19661...@ybb.ne.jp wrote:
>
> > Hi All,
> >
> > We tried to set sequential attribute of resource
Hi Kristoffer,
In RHEL6.4, crmsh-c8f214020b2c gives the next error and cannot install it.
Does a procedure of any installation have a problem?
---
[root@srv01 crmsh-c8f214020b2c]# cat /etc/redhat-release
Red Hat Enterprise Linux Server release 6.4 (Santiago)
Hi Kristoffer,
Thank you for comments.
I tested it.
However, the problem seems to still occur.
---
[root@srv01 crmsh-8d984b138fc4]# pwd
/opt/crmsh-8d984b138fc4
[root@srv01 crmsh-8d984b138fc4]# ./autogen.sh
autoconf: autoconf (GNU Autoconf) 2.63
aut
Hi All,
There is difference in two between handling of "sequential" of "resouce_set" of
colocation.
Is either one not a mistake?
static gboolean
unpack_colocation_set(xmlNode * set, int score, pe_working_set_t * data_set)
{
xmlNode *xml_rsc = NULL;
resource_t *w
Hi Kristoffer,
Thank you for comments.
> Could you try with the latest changeset 337654e0cdc4?
However, the problem seems to still occur.
[root@srv01 crmsh-337654e0cdc4]# make install
Making install in doc
make[1]: Entering directory `/opt/crmsh-337654e0cdc4/doc'
a2x -f manpage crm.8.txt
WARNIN
Hi Kristoffer,
Thank you for comments.
By crmsh-7f620e736895.tar.gz, I did "make install" well.
I seem to be able to set the sequential attribute definitely.
The sequential attribute does become true.
---
(snip)
colocation rsc_colocation-master INFINITY: [ vip-maste
Hi Kristoffer,
Thank you for comments.
> > But the next information appeared when I put crm.
> > Does this last message not have any problem?
> >
> > ---
> > [root@srv01 ~]# crm configure load update
> > db2-resource_set_0207.crm WARNING: pgsql: action monitor not
> >
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
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,
> >> 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
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
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...@
Hi All,
I confirmed movement at the time of the trouble in one of Master/Slave in
Pacemaker1.1.11.
-
Step1) Constitute a cluster.
[root@srv01 ~]# crm_mon -1 -Af
Last updated: Tue Feb 18 18:07:24 2014
Last change: Tue Feb 18 18:05:46 2014 via crmd on srv01
St
Hi Andrew,
> I'm confused... that patch seems to be the reverse of yours.
> Are you saying that we need to undo Lars' one?
No, I do not understand the meaning of the correction of Mr. Lars.
However, as now, crm_mon does not display a right attribute.
Possibly did you not discuss the correction t
Hi Andrew,
Thank you for comments.
> can I see the config of yours that crm_mon is not displaying correctly?
It is displayed as follows.
-
[root@srv01 tmp]# crm_mon -1 -Af
Last updated: Tue Feb 18 19:51:04 2014
Last change: Tue Feb 18 19:48:55 2014 via
Hi Andrew,
I attach the result of the cibadmin -Q command.
Best Regards,
Hideo Yamauchi.
--- On Tue, 2014/2/18, Andrew Beekhof wrote:
>
> On 18 Feb 2014, at 1:45 pm, renayama19661...@ybb.ne.jp wrote:
>
> > Hi Andrew,
> >
> > Thank you for comments.
> >
> >> can I see the config of yours t
Hi David,
Thank you for comments.
> You have resource-stickiness=INFINITY, this is what is preventing the
> failover from occurring. Set resource-stickiness=1 or 0 and the failover
> should occur.
>
However, the resource moves by a calculation of the next state transition.
By a calculation of
Hi Andrew,
> I'll follow up on the bug.
Thanks!
Hideo Yamauch.
--- On Wed, 2014/2/19, Andrew Beekhof wrote:
> I'll follow up on the bug.
>
> On 19 Feb 2014, at 10:55 am, renayama19661...@ybb.ne.jp wrote:
>
> > Hi David,
> >
> > Thank you for comments.
> >
> >> You have resource-stickiness
Hi Andrew,
Thank you for comments.
> So I'm confused as to what the problem is.
> What are you expecting crm_mon to show?
I wish it is displayed as follows.
* Node srv01:
+ default_ping_set : 0 : Connectivity is lost
Best Regards,
Hideo Yamauchi.
--- On Wed, 2
Hi Andrew,
> > I wish it is displayed as follows.
> >
> >
> > * Node srv01:
> > + default_ping_set : 0 : Connectivity is
> >lost
>
> Ah! https://github.com/beekhof/pacemaker/commit/5d51930
It was displayed definitely.
Many Thanks!
Hideo Yamauchi.
--- On Wed
Hi All,
The timer which is not stopped at the time of the stop of the monitor of the
master slave resource of the local node runs.
Therefore, warning to cancel outputs a timer when crmd handles the transition
that is in a new state.
I confirm it in the next procedure.
Step1) Constitute a clust
Hi All,
I made a patch.
Please confirm the contents of the patch.
If there is not a problem, please reflect it in github.
Best Regards,
Hideo Yamauchi.
--- On Thu, 2014/2/20, renayama19661...@ybb.ne.jp
wrote:
> Hi All,
>
> The timer which is not stopped at the time of the stop of the monitor
Hi All,
I composed Master/Slave resource of three nodes that set quorum-policy="freeze".
(I use Stateful in Master/Slave resource.)
-
Current DC: srv01 (3232238280) - partition with quorum
Version: 1.1.11-830af67
3 Nodes configured
9 Resources configured
Online:
Hi Emmanuel,
> Why are you using ssh as stonith? i don't think the fencing is working
> because your nodes are in unclean state
No, STONITH is not carried out because all nodes lose quorum.
This is right movement of Pacemaker.
It is an example to use STONITH of ssh.
Best Regards,
Hideo Yamauch
Hi All,
We confirmed a problem when we performed "clean up" of the Master/Slave
resource in Pacemaker1.0.
When this problem occurs, "probe" processing is not carried out.
I registered the problem with Bugzilla.
* http://bugs.clusterlabs.org/show_bug.cgi?id=5211
In addition, I wrote the method
Hi Andrew,
Thank you for comment.
> > Is it responsibility of the resource agent side to prevent a state of these
> > plural Master?
>
> No.
>
> In this scenario, no nodes have quorum and therefor no additional instances
> should have been promoted. Thats the definition of "freeze" :)
> Even
Hi Andrew,
> > Okay.
> > I wish this problem is revised by the next release.
>
> crm_report?
I confirmed a problem again in PM1.2-rc1 and registered in Bugzilla.
* http://bugs.clusterlabs.org/show_bug.cgi?id=5212
Towards Bugzilla, I attached the crm_report file.
Best Regards,
Hideo Yamauchi.
Hi All,
We assume special resource constitution.
Master of master-slave depends on primitive resource for the constitution.
We performed the setting that Master stopped becoming it in Slave node
experimentally.
location rsc_location-msStateful-1 msPostgresql \
rule $role="master" 20
Hi Andrew,
Thank you for comments.
> Do you guys have any timeframe for moving away from 1.0.x?
> The 1.1 series is over 4 years old now and quite usable :-)
>
> There is really a (low) limit to how much effort I can put into support for
> it.
We gradually move from Pacemaker1.0 to Pacemaker1.
Hi Andrew,
> > It is not necessary at all to revise it for Pacemaker1.0.
>
> Maybe we need to add KnownIssues.md to the repo for anyone thats slow to
> update.
> Are there any 1.0 bugs that really really need fixing or shall we move them
> all to the KnownIssues file?
That's a good idea.
In th
Hi Andrew,
Thank you for comments.
> > We do not want to be promoted to Master in the node that primitive resource
> > does not start.
> > Is there the setting of colocation and order which are not promoted to
> > Master of the Master node?
>
> Your config looks reasonable... almost certainly
Hi Andrew,
> >> Your config looks reasonable... almost certainly a bug in the PE.
> >> Do you happen to have the relevant pengine input file available?
> >
> > Really?
>
> I would expect that:
>
> colocation rsc_colocation-master-1 INFINITY: msPostgresql:Master A-master
>
> would only promot
Hi Andrwe,
> Here we go:
>
> https://github.com/ClusterLabs/pacemaker-1.0/blob/master/README.md
>
> If any additional bugs are found in 1.0, we should create a new entry at
> bugs.clusterlabs.org, add it to the above README and as long as 1.1 is
> unaffected: close the bug as WONTFIX.
All
Hi Andrew,
I registered a problem in Bugzilla.
And I attached a file of crm_report.
* http://bugs.clusterlabs.org/show_bug.cgi?id=5213
Best Regards,
Hideo Yamauchi.
--- On Thu, 2014/5/15, renayama19661...@ybb.ne.jp
wrote:
> Hi Andrew,
>
> > >> Your config looks reasonable... almost certain
Hi All,
The attrd_updater command ignores the "dampen" parameter and updates an
attribute.
Step1) Start one node.
[root@srv01 ~]# crm_mon -1 -Af
Last updated: Tue May 27 19:36:35 2014
Last change: Tue May 27 19:34:59 2014
Stack: corosync
Current DC: srv01 (3232238180) - partition WITHOUT quorum
Hi Andrew,
Thank you for comment.
> > --- attrd/command.c -
> > (snip)
> > /* this only involves cluster nodes. */
> > if(v->nodeid == 0 && (v->is_remote == FALSE)) {
> > if(crm_element_value_int(xml, F_ATTRD_HOST_ID, (int*)&v->nodeid) ==
> >0) {
> > /* Create the nam
Hi Andrew,
> > I'd expect that block to hit this clause though:
> >
> > } else if(mainloop_timer_running(a->timer)) {
> > crm_info("Write out of '%s' delayed: timer is running", a->id);
> > return;
>
> Which point of the source code does the suggested code mentioned above re
Hi Andrew,
> Perhaps try:
>
> diff --git a/attrd/commands.c b/attrd/commands.c
> index 7f1b4b0..7342e23 100644
> --- a/attrd/commands.c
> +++ b/attrd/commands.c
> @@ -464,6 +464,15 @@ attrd_peer_update(crm_node_t *peer, xmlNode *xml, bool
> filter)
>
> a->changed |= changed;
>
> + if
Hi Andrew,
I confirmed movement at once.
Your patch solves a problem.
Many Thanks!
Hideo Yamauchi.
--- On Wed, 2014/5/28, renayama19661...@ybb.ne.jp
wrote:
> Hi Andrew,
>
> > Perhaps try:
> >
> > diff --git a/attrd/commands.c b/attrd/commands.c
> > index 7f1b4b0..7342e23 100644
> > --- a/at
Hi All,
I submitted a problem in next bugziila in the past.
* https://developerbugs.linuxfoundation.org/show_bug.cgi?id=2501
A similar phenomenon is generated in attrd of latest Pacemaker.
Step 1) Set the setting of the cluster as follows.
export PCMK_fail_fast=no
Step 2) Start a cluster.
St
Hi Andrew,
Thank you for comennts.
> Please use bugs.clusterlabs.org in future.
> I'll follow up in bugzilla
Okay!
Best Regards,
Hideo Yamauchi.
--- On Tue, 2014/6/10, Andrew Beekhof wrote:
>
> On 9 Jun 2014, at 12:01 pm, renayama19661...@ybb.ne.jp wrote:
>
> > Hi All,
> >
> > I submitted
Hi All,
We were going to confirm snmptrap function in crm_mon of Pacemaker1.1.12.
However, crm_mon does not seem to support a message for a new difference of cib.
void
crm_diff_update(const char *event, xmlNode * msg)
{
int rc = -1;
long now = time(NULL);
(snip)
if (crm_mail_to || sn
Hi Andrew,
> Perhaps someone feels like testing this:
> https://github.com/beekhof/pacemaker/commit/3df6aff
>
> Otherwise I'll do it on monday
An immediate correction, thank you.
I confirm snmp by the end of Monday.
Many Thanks!
Hideo Yamauchi.
- Original Message -
> From: Andrew
Hi Andrew,
>> Perhaps someone feels like testing this:
>> https://github.com/beekhof/pacemaker/commit/3df6aff
>>
>> Otherwise I'll do it on monday
I confirmed the output of the SNMP trap of the resource and the SNMP trap of
STONITH.
By your correction, the crm_mon command came to send trap.
Hi All,
We put pgsql resource of Master/Slave and original RA together and constituted
a cluster.
However, the problem that colocation condition did not become effective
happened.
Therefore promote is carried out.
Step1) Start a node not to be used to Master earlier.
Step2) VIPCheck resources st
Hi All,
We confirmed it about negative setting of colocation.
It is colocation with with-rsc-role designation.
We checked it in the next procedure.
Step1) Start the first node. And we send cib.
Last updated: Wed Jun 27 22:58:15 2012
Stack: Heartbeat
Current DC: rh62-test1 (4a7c480
Hi All,
I registered these contents with Bugzilla.
* http://bugs.clusterlabs.org/show_bug.cgi?id=5074
And I attached hb_report.
Best Regards,
Hideo Yamauchi.
--- On Wed, 2012/6/27, renayama19661...@ybb.ne.jp
wrote:
> Hi All,
>
> We confirmed it about negative setting of colocation.
>
> It
Hi Andrew,
All right.
We wait for a correction.
Best Regards,
Hideo Yamauchi.
--- On Thu, 2012/6/28, Andrew Beekhof wrote:
> On Wed, Jun 27, 2012 at 4:27 PM, wrote:
> > Hi All,
> >
> > I registered these contents with Bugzilla.
> > * http://bugs.clusterlabs.org/show_bug.cgi?id=5074
>
> Ex
Hi Andrew,
Thank you for comment.
All right.
We wait for a correction.
Best Regards,
Hideo Yamauchi.
--- On Thu, 2012/6/28, Andrew Beekhof wrote:
> On Tue, Jun 12, 2012 at 3:33 PM, wrote:
> > Hi All,
> ...
> > I registered these contents with Bugzilla.
> > * http://bugs.clusterlabs.org/sh
Hi All,
We identified order of the master/slave resource as primitive resource.
We set order limitation as follows.
However, promote was carried out even if primitvei resource caused start
trouble.
Last updated: Fri Jun 29 19:20:09 2012
Stack: Heartbeat
Current DC: rh62-test1 (c9ae
Hi All,
Sorry...I forgot it
> We set order limitation as follows.
Best Regards,
Hideo Yamauchi.
--- On Fri, 2012/6/29, renayama19661...@ybb.ne.jp
wrote:
> Hi All,
>
> We identified order of the master/slave resource as primitive resource.
>
> We set order limitation as
Hi Phillip,
Thank you for comment.
However, the result was the same even if I used the Group resource.
(snip)
(snip)
(snip)
Last updated: Mon Jul 2 17:56:27 2012
Stack: Heartbeat
Current DC: rh62-test1 (6d
Hi All,
The constitution of the cluster became right by a redundant resource and
addition and a change of the limitation as follows.
However, we do not want to perform the redundant setting.
(snip)
Hi All,
We performed setting avoiding the next problem.
* http://www.gossamer-threads.com/lists/linuxha/pacemaker/80250
-> http://bugs.clusterlabs.org/show_bug.cgi?id=5070
* http://www.gossamer-threads.com/lists/linuxha/pacemaker/80549
-> http://bugs.clusterlabs.org/show_bug.cgi?id=5075
Hi All,
We confirmed movement of order which combined a master with clone.
We performed it by a very simple combination.
Step1) We change it to produce start error in Dummy resource.
(snip)
dummy_start() {
return $OCF_ERR_GENERIC
dummy_monitor
(snip)
Step2) We start one node and send cib.
Hi All,
I registered hb_report file with Bugzilla.
* http://bugs.clusterlabs.org/show_bug.cgi?id=5086
Best Regards,
Hideo Yamauchi.
--- On Fri, 2012/7/20, renayama19661...@ybb.ne.jp
wrote:
> Hi All,
>
> We confirmed movement of order which combined a master with clone.
> We performed it by
Hi David,
Thank you for comments.
> http://www.clusterlabs.org/doc/en-US/Pacemaker/1.1/html/Pacemaker_Explained/ch06s03s02.html
I confirmed it in INFINITY.
(snip)
(snip)
By the start only for Master nodes, it was controlled well.
[root@drbd1 ~]# crm_mon -1 -f
Last
Hi Andrew,
Thank you or commets.
> > Online: [ drbd1 drbd2 ]
> >
> > Master/Slave Set: msDrPostgreSQLDB
> > Masters: [ drbd2 ]
> > Slaves: [ drbd1 ] ---> Started and Status
> > Slave.
>
> Yep, looks like a bug. I'll follow up on the bugzilla.
I talked wi
Hi All,
I registered this problem with Bugzilla.
* http://bugs.clusterlabs.org/show_bug.cgi?id=5089
Best Regards,
Hideo Yamauchi.
--- On Wed, 2012/8/1, renayama19661...@ybb.ne.jp
wrote:
> Hi All,
>
> When the ID of the resource changed, we confirmed that control of different
> colocation
Hi Andrew
Thank you for comments.
> The problem with this approach is that ordering of the constraints in
> the cib is not preserved between the nodes.
> I will follow up further on the bugzilla.
All right!
Many Thanks,
Hideo Yamauchi.
--- On Tue, 2012/8/7, Andrew Beekhof wrote:
> The probl
Hi Andrew,
> > The first method)
> > * Set colocation in clnPingd and msDrPostgreSQLDB.
> >
> > The second method)
> > * Set interleave option in clnPingd.
> >
> > Do my two methods include a mistake?
>
> No.
>
> Looking closer, the initial constraint says only that the Master must
> be on a n
Hi Andrew,
Thank you for comments.
> > Is this specifications?
> > Or is it a bug?
> >
> > * I registered a problem with Bugzilla.
> > * http://bugs.clusterlabs.org/show_bug.cgi?id=5079
>
> Excellent. I'll follow up there (likewise for the other bugs you've
> sent to the list recently :-)
I
Hi All,
We found a problem at the time of Porobe error.
It is the following simple resource constitution.
Last updated: Wed Aug 22 15:19:50 2012
Stack: Heartbeat
Current DC: drbd1 (6081ac99-d941-40b9-a4a3-9f996ff291c0) - partition with quorum
Version: 1.0.12-c6770b8
1 Nodes configur
Hi Andrew,
Thank you for comments.
> > Question 1) Is there right setting in cib.xml to evade this problem?
>
> No.
>
> >
> > Question 2) In Pacemaker1.1, does this problem occur?
>
> Yes. I'll see what I can do.
>
> >
> > Question 3) I added following order.
> >
> >
> >
> >
Hi Alberto,
I think that I should set plural external/vcenter if your problem is practice
of stonith when vcenter falls and is not usable.
Please refer to the next email and patch.
* http://www.gossamer-threads.com/lists/linuxha/dev/78702
Best Regards,
Hideo Yamauchi.
--- On Sun, 2012/9/9, Al
Hi All,
We confirmed movement of the trouble of the clone resource that we combined
with Master/Slave resource.
The master / slave resources are replaced under the influence of the trouble of
the clonal resource.
We confirmed it in the next procedure.
Step1) We start a cluster and send cib.
Hi All,
I watched a source of crmd of
ClusterLabs-pacemaker-1.0-Pacemaker-1.0.12-116-gf372204.zip.
I found the log("Quorum lost: ") processing that was never output.
The cause that log is not output is fsa_have_quorum.
This value is always FALSE.
(snip)
* crmd/callback.c
#if SUPPORT_HEARTBE
Hi Andrew,
Thank you for comments.
Even your correction is good, but one place of correction is necessary.
#if SUPPORT_HEARTBEAT
-static gboolean fsa_have_quorum = FALSE;
gboolean ccm_dispatch(int fd, gpointer user_data)
{
@@ -575,14 +574,14 @@
if(update_quorum) {
crm_
Hi All,
I registered a problem at bugzilla in place of Miss Ikeda.
* http://bugs.clusterlabs.org/show_bug.cgi?id=5133
Best Regards,
Hideo Yamauchi.
--- On Thu, 2013/1/10, Junko IKEDA wrote:
>
>
> Hi,
>
> I'm running Stateful RA with Pacemaker 1.0.12, and found that its demote
> behavior
Hi Dejan,
Hi Andrew,
As for the crm shell, the check of the meta attribute was revised with the next
patch.
* http://hg.savannah.gnu.org/hgweb/crmsh/rev/d1174f42f4b3
This patch was backported in Pacemaker1.0.13.
*
https://github.com/ClusterLabs/pacemaker-1.0/commit/fa1a99ab36e0ed015f1bcbbb2
Hi Dejan,
Hi Andrew,
Thank you for comment.
I confirm the movement of the patch and report it.
Best Regards,
Hideo Yamauchi.
--- On Wed, 2013/3/6, Dejan Muhamedagic wrote:
> Hi Hideo-san,
>
> On Wed, Mar 06, 2013 at 10:37:44AM +0900, renayama19661...@ybb.ne.jp wrote:
> > Hi Dejan,
> > Hi Andr
Hi Dejan,
The problem was settled with your patch.
However, I have a question.
I want to use "resource_set" which Mr. Andrew proposed, but do not understand a
method to use with crm shell.
I read two next cib.xml and confirmed it with crm shell.
Case 1) sequential="false".
(snip)
Hi Andrew,
I tried "resource_set sequential" designation.
* http://www.gossamer-threads.com/lists/linuxha/pacemaker/84578
I caused an error in start of the vip-master resource and confirmed movement.
(snip)
Hi Andrew,
Thank you for comment.
It was colocation.
I make modifications and confirm movement.
Many Thanks!
Hideo Yamauchi.
--- On Thu, 2013/3/7, Andrew Beekhof wrote:
> Oh!
>
> You use the resource sets _instead_ of a group.
> If you want group.ordered=false, then use a colocation set
Hi Andrew,
> > You use the resource sets _instead_ of a group.
> > If you want group.ordered=false, then use a colocation set (with
> > sequential=true).
In "colocation", I used "resource_set".
However, a result did not include the change.
Will this result be a mistake of my setting?
Case 1) se
Hi Dejan,
Thank you for comment.
> sequential=true is the default. In that case it's not possible to
> have an unequivocal representation for the same construct and, in
> this particular case, the conversion XML->CLI->XML yields a
> different XML. There's a later commit which helps here, I think
Hi Andrew,
> In "colocation", I used "resource_set".
> However, a result did not include the change.
Please, about the result that I tried, give me comment.
Best Regards,
Hideo Yamauchi.
--- On Thu, 2013/3/7, renayama19661...@ybb.ne.jp
wrote:
> Hi Andrew,
>
> > > You use the resource sets _
Hi Dejan,
> > changeset: 789:916d1b15edc3
> > user:Dejan Muhamedagic
> > date:Thu Aug 16 17:01:24 2012 +0200
> > summary: Medium: cibconfig: drop attributes set to default on cib import
I confirmed that I was set definitely without becoming xml if you made the
modification
Hi Andrew,
I registered this question with Bugzilla.
* http://bugs.clusterlabs.org/show_bug.cgi?id=5147
Best Regards,
Hideo Yamauchi.
--- On Thu, 2013/3/14, renayama19661...@ybb.ne.jp
wrote:
> Hi Andrew,
>
> > In "colocation", I used "resource_set".
> > However, a result did not include th
Hi Andrew,
Thank your for comments.
> > > You use the resource sets _instead_ of a group.
> > > If you want group.ordered=false, then use a colocation set (with
> > > sequential=true).
>
> In "colocation", I used "resource_set".
> However, a result did not include the change.
> Will this result
Hi Andrew,
Thank your for comment.
> Sorry, I'm not sure I understand the question.
Sorry
When we use resource_set in substitution for ordered of a thing of group
resource, do we use "colocation set"?
Or do we use "ordering set "?
It does not seem to do work same as "group ordered=fase" i
1 - 100 of 376 matches
Mail list logo
