_mon command came to send trap.
> >
> > Please reflect a correction in Master repository.
> >
> > Best Regards,
> > Hideo Yamauchi.
> >
> >
> >
> > - Original Message -----
> >> From: "renayama19661...@ybb.ne.jp"
>
2015-04-13 19:53 GMT+09:00 Andrei Borzenkov :
> On Mon, Apr 13, 2015 at 12:32 PM, Kazunori INOUE
> wrote:
>> 2015-04-10 15:09 GMT+09:00 Andrei Borzenkov :
>>> On Fri, Apr 10, 2015 at 8:22 AM, Kazunori INOUE
>>> wrote:
Hi,
I defined multiple instance_attributes [*].
*
ht
On Mon, Apr 13, 2015 at 12:32 PM, Kazunori INOUE
wrote:
> 2015-04-10 15:09 GMT+09:00 Andrei Borzenkov :
>> On Fri, Apr 10, 2015 at 8:22 AM, Kazunori INOUE
>> wrote:
>>> Hi,
>>>
>>> I defined multiple instance_attributes [*].
>>> *
>>> http://clusterlabs.org/doc/en-US/Pacemaker/1.1-pcs/html/Pace
2015-04-10 15:09 GMT+09:00 Andrei Borzenkov :
> On Fri, Apr 10, 2015 at 8:22 AM, Kazunori INOUE
> wrote:
>> Hi,
>>
>> I defined multiple instance_attributes [*].
>> *
>> http://clusterlabs.org/doc/en-US/Pacemaker/1.1-pcs/html/Pacemaker_Explained/_using_rules_to_control_resource_options.html
>> A
Am 29.10.2014 01:39, schrieb Andrew Beekhof:
I just have one question about how a resource agent should behave on "reload"
invoked if the resource is currently stopped. Should the resource be started or remain
stopped?
I don't think that is defined. Certainly pacemaker wont trigger that case
> On 28 Oct 2014, at 6:07 pm, Felix Zachlod wrote:
>
> Hello folks,
>
>
> I just have one question about how a resource agent should behave on "reload"
> invoked if the resource is currently stopped. Should the resource be started
> or remain stopped?
I don't think that is defined. Certainl
Hello folks,
I just have one question about how a resource agent should behave on
"reload" invoked if the resource is currently stopped. Should the
resource be started or remain stopped? I did not find anything about
that in the documentation, in gernel there are not mant informations
about
On 14 Aug 2014, at 2:58 pm, Alex Samad - Yieldbroker
wrote:
> Hi
>
> pcs status
> Online: [ alcdmz1 gsdmz1 ]
>
> Full list of resources:
>
> dnsip-a(ocf::yb:namedVIP): Started alcdmz1
> dnsip-b(ocf::yb:namedVIP): Started gsdmz1
> squidip-a (ocf::yb:squidVIP):
Hi
pcs status
Online: [ alcdmz1 gsdmz1 ]
Full list of resources:
dnsip-a(ocf::yb:namedVIP): Started alcdmz1
dnsip-b(ocf::yb:namedVIP): Started gsdmz1
squidip-a (ocf::yb:squidVIP): Started gsdmz1
squidip-b (ocf::yb:squidVIP): Started alcdmz1
So
>
> - Original Message -
>> From: "renayama19661...@ybb.ne.jp"
>> To: Andrew Beekhof ; The Pacemaker cluster resource
>> manager
>> Date: 2014/7/25, Fri 14:21
>> Subject: Re: [Pacemaker] [Question] About snmp trap of crm_mon.
>>
&g
mon command came to send trap.
Please reflect a correction in Master repository.
Best Regards,
Hideo Yamauchi.
- Original Message -
>From: "renayama19661...@ybb.ne.jp"
>To: Andrew Beekhof ; The Pacemaker cluster resource
>manager
>Date: 2014/7/25, Fri 14:21
&
--
> From: Andrew Beekhof
> To: renayama19661...@ybb.ne.jp; The Pacemaker cluster resource manager
>
> Cc:
> Date: 2014/7/25, Fri 14:02
> Subject: Re: [Pacemaker] [Question] About snmp trap of crm_mon.
>
>
> On 24 Jul 2014, at 6:32 pm, Andrew Beekhof w
On 24 Jul 2014, at 6:32 pm, Andrew Beekhof wrote:
>
> On 24 Jul 2014, at 11:54 am, renayama19661...@ybb.ne.jp wrote:
>
>> 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
>>
On 24 Jul 2014, at 6:49 pm, Michael Schwartzkopff wrote:
> Am Donnerstag, 24. Juli 2014, 18:32:40 schrieb Andrew Beekhof:
>> On 24 Jul 2014, at 11:54 am, renayama19661...@ybb.ne.jp wrote:
>>> Hi All,
>>>
>>> We were going to confirm snmptrap function in crm_mon of Pacemaker1.1.12.
>>> However,
Am Donnerstag, 24. Juli 2014, 18:32:40 schrieb Andrew Beekhof:
> On 24 Jul 2014, at 11:54 am, renayama19661...@ybb.ne.jp wrote:
> > 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
On 24 Jul 2014, at 11:54 am, renayama19661...@ybb.ne.jp wrote:
> 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.
dammit :(
>
>
> void
> crm_diff_update(const char *even
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
hello everyone
I have 4 resource agents A B C and D.
A B C should run on the same node, but D should mutex with any of A B C.
The following is my configure, is it correct?
crm configure collocation ABC INFINITY: A B C
crm configure collocation D-mutex-ABC -INFINITY: D (A B C)
please give my so
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 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
On 15 May 2014, at 9:57 am, renayama19661...@ybb.ne.jp wrote:
> 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
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
On 13 May 2014, at 3:14 pm, renayama19661...@ybb.ne.jp wrote:
> 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.
>
>
>
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,
> > 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.
On 9 May 2014, at 2:05 pm, renayama19661...@ybb.ne.jp wrote:
> 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 instance
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
On 8 May 2014, at 1:37 pm, renayama19661...@ybb.ne.jp wrote:
> 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 quo
On 9 May 2014, at 11:59 am, Jacob Nikom wrote:
> Hi,
>
> I created Pacemaker resource configuration file, but it does not accepts it.
> It complanes:
> /home/jnikom/Kiva/dev/Prod/flvr/pace loadConstraintsXML
> clu_con_init_2014_05_08_001.xml
>error: unpack_rsc_op:No further recover
Hi,
I created Pacemaker resource configuration file, but it does not accepts it.
It complanes:
/home/jnikom/Kiva/dev/Prod/flvr/pace loadConstraintsXML
clu_con_init_2014_05_08_001.xml
error: unpack_rsc_op:No further recovery can be attempted for
mysqlres: stop action failed with 'not i
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
Why are you using ssh as stonith? i don't think the fencing is working
because your nodes are in unclean state
2014-05-08 5:37 GMT+02:00 :
> Hi All,
>
> I composed Master/Slave resource of three nodes that set
> quorum-policy="freeze".
> (I use Stateful in Master/Slave resource.)
>
> ---
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:
On 7 May 2014, at 10:03 am, Jacob Nikom wrote:
> Hi,
>
> I have question about colocation constraints – are they symmetrical
> (commutative) or not?
>
> What I mean is the following.
>
> If we have the colocation constraint like
>with-rsc="reource2" score="-INFINITY"/>
>
> Does it produ
Hi,
I have question about colocation constraints – are they symmetrical
(commutative) or not?
What I mean is the following.
If we have the colocation constraint like
Does it produces the same behavior as the constraint
Thank you,
Jacob Nikom
On 14 Mar 2014, at 7:11 am, Digimer wrote:
> On 13/03/14 04:08 PM, Andreas Sinn wrote:
>> stonith-enabled="false" \
>> no-quorum-policy="ignore"
>
> I can't speak to your main question, but this is a split-brain waiting to
> happen. Please configure and test stonith.
Agree.
A
I don't use vmware myself, but look at 'fence_vmware', it should do the
trick for you.
digimer
On 14/03/14 01:28 AM, Andreas Sinn wrote:
Hello,
it is a virtual machine on esxi 5.5.0 Server. What can I use?
VirtualCenter?
BR
Andreas
Am 13.03.2014 21:48, schrieb Digimer:
ou (a
__
Hello,
it is a virtual machine on esxi 5.5.0 Server. What can I use? VirtualCenter?
BR
Andreas
Am 13.03.2014 21:48, schrieb Digimer:
ou (a
___
Pacemaker mailing list: Pacemaker@oss.clusterlabs.org
http://oss.clusterlabs.org/mailman/listinfo/pacem
Stonith config depends on the hardware/hypervisor you plan to use to
terminate a failed node. What hardware do your nodes use? Do they have
IPMI (or iRMC/iLO/iDRAC/etc)? If so, then you can use fence_ipmilan and
the config is pretty simple. If you (also) have switched PDUs, like the
APC AP7900,
Do you know a simple stonith configuration?
Am 13.03.2014 21:11, schrieb Digimer:
On 13/03/14 04:08 PM, Andreas Sinn wrote:
stonith-enabled="false" \
no-quorum-policy="ignore"
I can't speak to your main question, but this is a split-brain waiting
to happen. Please configure
On 13/03/14 04:08 PM, Andreas Sinn wrote:
stonith-enabled="false" \
no-quorum-policy="ignore"
I can't speak to your main question, but this is a split-brain waiting
to happen. Please configure and test stonith.
--
Digimer
Papers and Projects: https://alteeve.ca/w/
What if t
Hello all,
I have configured an active/active cluster like the description and with
the pacemaker configuration like:
[root@rci-web-hp01 httpd]# crm configure show
node rci-web-node1
node rci-web-node2
primitive ClusterIP ocf:heartbeat:IPaddr2 \
params ip="10.100.77.63" cidr_netmask="3
2014-02-24 12:00 GMT+09:00 Andrew Beekhof :
>
> On 21 Feb 2014, at 9:35 pm, Kazunori INOUE wrote:
>
>> 2014-02-20 18:59 GMT+09:00 Andrew Beekhof :
>>>
>>> On 20 Feb 2014, at 8:37 pm, Kazunori INOUE
>>> wrote:
>>>
Hi,
Is this by design although log levels differ with a stonith reso
On 21 Feb 2014, at 9:35 pm, Kazunori INOUE wrote:
> 2014-02-20 18:59 GMT+09:00 Andrew Beekhof :
>>
>> On 20 Feb 2014, at 8:37 pm, Kazunori INOUE wrote:
>>
>>> Hi,
>>>
>>> Is this by design although log levels differ with a stonith resource
>>> and other resources in Pacemaker-1.1.11 ?
>>>
>
2014-02-20 18:59 GMT+09:00 Andrew Beekhof :
>
> On 20 Feb 2014, at 8:37 pm, Kazunori INOUE wrote:
>
>> Hi,
>>
>> Is this by design although log levels differ with a stonith resource
>> and other resources in Pacemaker-1.1.11 ?
>>
>> "P1" is id of ocf:pacemaker:Dummy resource.
>> "F1" is id of ston
On 20 Feb 2014, at 8:37 pm, Kazunori INOUE wrote:
> Hi,
>
> Is this by design although log levels differ with a stonith resource
> and other resources in Pacemaker-1.1.11 ?
>
> "P1" is id of ocf:pacemaker:Dummy resource.
> "F1" is id of stonith (ex. stonith:external/ipmi) resource.
>
> * log
Hi,
Is this by design although log levels differ with a stonith resource
and other resources in Pacemaker-1.1.11 ?
"P1" is id of ocf:pacemaker:Dummy resource.
"F1" is id of stonith (ex. stonith:external/ipmi) resource.
* log at "probe"
crmd[22860]: notice: process_lrm_event: LRM operation P1_m
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,
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
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.
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 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
- Original Message -
> From: "David Vossel"
> To: "The Pacemaker cluster resource manager"
> Sent: Wednesday, January 15, 2014 10:27:49 AM
> Subject: Re: [Pacemaker] Question about new migration
>
> - Original Message -
> > Fr
- Original Message -
> From: "Andrew Beekhof"
> To: "The Pacemaker cluster resource manager"
> Sent: Wednesday, January 15, 2014 3:42:23 AM
> Subject: Re: [Pacemaker] Question about new migration
>
>
> On 15 Jan 2014, at 7:12 pm, Kazunori INO
On 15 Jan 2014, at 7:12 pm, Kazunori INOUE wrote:
> Hi David,
>
> With new migration logic, when VM was migrated by 'node standby',
> start was performed in migrate_target. (migrate_from was not performed.)
>
> Is this the designed behavior?
>
>
> # crm_mon -rf1
> Stack: corosync
> Current D
On 18 Dec 2013, at 9:51 pm, Kazunori INOUE wrote:
> Hi,
>
> When I set only migration-limit without setting node-action-limit in
> pacemaker-1.1,
> the number of 'operation' other than migrate_to/from was limited to
> the value of migration-limit.
> (The node that I used has 8 cores.)
>
> [cib
Hi David,
2013/12/19 David Vossel :
>
> - Original Message -
>> From: "Kazunori INOUE"
>> To: "pm"
>> Sent: Wednesday, December 18, 2013 4:56:20 AM
>> Subject: [Pacemaker] Question about behavior of the post-failure during the
>&g
On 19 Dec 2013, at 4:03 am, Brusq, Jerome wrote:
> Dear all,
>
> I have a custom lsb script that launch a custom process.
>
> primitive myscript lsb:ha_swift \
>op start interval="0" timeout="30s" \
>op stop interval="0" timeout="30s" \
>op monitor interval="15s" on-fail="restart
- Original Message -
> From: "Kazunori INOUE"
> To: "pm"
> Sent: Wednesday, December 18, 2013 4:56:20 AM
> Subject: [Pacemaker] Question about behavior of the post-failure during the
> migrate_to
>
> Hi,
>
> When a node crashed
Dear all,
I have a custom lsb script that launch a custom process.
primitive myscript lsb:ha_swift \
op start interval="0" timeout="30s" \
op stop interval="0" timeout="30s" \
op monitor interval="15s" on-fail="restart" \
When this one crashes, I have the feeling that pacemaker do :
"/
Le 18/12/2013 17:20, Brusq, Jerome a écrit :
Dear all,
It is maybe a stupid question… Sorry I’m a new user of pacemaker.
Not at all.
I have 2 nodes and 5 resources (resource1, resource2, resource3,
resource4 and resource5). The 5 resources have to work together on the
same node.
I tried the
Dear all,
It is maybe a stupid question... Sorry I'm a new user of pacemaker.
I have 2 nodes and 5 resources (resource1, resource2, resource3, resource4 and
resource5). The 5 resources have to work together on the same node.
I tried the feature group and colocation .. but I have always the same
Hi,
When I set only migration-limit without setting node-action-limit in
pacemaker-1.1,
the number of 'operation' other than migrate_to/from was limited to
the value of migration-limit.
(The node that I used has 8 cores.)
[cib]
property \
no-quorum-policy="freeze" \
stonith-enabled="true" \
On 14 Nov 2013, at 5:53 pm, Kazunori INOUE wrote:
> Hi, Andrew
>
> 2013/11/13 Kazunori INOUE :
>> 2013/11/13 Andrew Beekhof :
>>>
>>> On 16 Oct 2013, at 8:51 am, Andrew Beekhof wrote:
>>>
On 15/10/2013, at 8:24 PM, Kazunori INOUE
wrote:
> Hi,
>
> I'm usin
Hi, Andrew
2013/11/13 Kazunori INOUE :
> 2013/11/13 Andrew Beekhof :
>>
>> On 16 Oct 2013, at 8:51 am, Andrew Beekhof wrote:
>>
>>>
>>> On 15/10/2013, at 8:24 PM, Kazunori INOUE wrote:
>>>
Hi,
I'm using pacemaker-1.1 (the latest devel).
I started resource (f1 and f2) which fe
On 16 Oct 2013, at 8:51 am, Andrew Beekhof wrote:
>
> On 15/10/2013, at 8:24 PM, Kazunori INOUE wrote:
>
>> Hi,
>>
>> I'm using pacemaker-1.1 (the latest devel).
>> I started resource (f1 and f2) which fence vm3 on vm1.
>>
>> $ crm_mon -1
>> Last updated: Tue Oct 15 15:16:37 2013
>> Last ch
Hi David,
2013/11/6 David Vossel :
> - Original Message -
>> From: "Kazunori INOUE"
>> To: "pm"
>> Sent: Friday, November 1, 2013 4:43:53 AM
>> Subject: [Pacemaker] Question about new migration logic
>>
>> Hi David,
>&
- Original Message -
> From: "Kazunori INOUE"
> To: "pm"
> Sent: Friday, November 1, 2013 4:43:53 AM
> Subject: [Pacemaker] Question about new migration logic
>
> Hi David,
>
> Because I have a plan to test the function of migration in
>
Thanks! It works now :)
From: emmanuel segura [mailto:emi2f...@gmail.com]
Sent: sábado, 2 de noviembre de 2013 14:31
To: The Pacemaker cluster resource manager; The Pacemaker cluster resource
manager
Subject: Re: [Pacemaker] Question regarding collocation
your order constrain it should
your order constrain it should be
order PSQL_ORDER inf: PSQL_DISK_MS:promote PSQL:start
2013/11/2 Neocox
> Hi!
>
>
>
> I have Corosync + Pacemaker installed on my Debian wheezy:
>
> root@rasp02:~# dpkg -s pacemaker | grep ^Version
>
> Version: 1.1.7-1
>
> root@rasp02:~# dpkg -s corosync | grep
Hi!
I have Corosync + Pacemaker installed on my Debian wheezy:
root@rasp02:~# dpkg -s pacemaker | grep ^Version
Version: 1.1.7-1
root@rasp02:~# dpkg -s corosync | grep ^Version
Version: 1.4.2-3
And although I think that I have correctly configured resource collocation,
the resource PSQL
Hi David,
Because I have a plan to test the function of migration in
pacemaker-1.1, I am interested in this commit.
https://github.com/davidvossel/pacemaker/commit/673e8599e4
If this "new migration logic" is merged into ClusterLabs,
when do you think it will be merged?
Best Regards,
Kazunori INO
On 15/10/2013, at 8:24 PM, Kazunori INOUE wrote:
> Hi,
>
> I'm using pacemaker-1.1 (the latest devel).
> I started resource (f1 and f2) which fence vm3 on vm1.
>
> $ crm_mon -1
> Last updated: Tue Oct 15 15:16:37 2013
> Last change: Tue Oct 15 15:16:21 2013 via crmd on vm1
> Stack: corosync
>
On 2013-10-15T18:24:46, Kazunori INOUE wrote:
> Oct 15 15:17:16 vm2 stonith-ng[9160]: warning: log_operation: f1:9273
> [ Performing: stonith -t external/libvirt -T reset vm3 ]
> Oct 15 15:17:46 vm2 stonith-ng[9160]: warning: log_operation: f1:9588
> [ Performing: stonith -t external/libvirt -T
>>
>> On 01/08/2013, at 2:00 AM, David Vossel wrote:
>>
>>> - Original Message -
>>>> From: "Kazunori INOUE"
>>>> To: "pacemaker@oss"
>>>> Sent: Wednesday, July 31, 2013 1:20:58 AM
>>>> Sub
aker@oss"
Sent: Wednesday, July 31, 2013 1:20:58 AM
Subject: [Pacemaker] Question about behavior when a resource was put into
unmanaged mode
Hi,
I'm using pacemaker-1.1.10. (4ae1f17)
When I put a primitive (p1) of group resource into unmanaged mode, low-order
primitive (p2)
Fixed:
https://github.com/beekhof/pacemaker/commit/0c996a1
On 01/08/2013, at 2:00 AM, David Vossel wrote:
> - Original Message -
>> From: "Kazunori INOUE"
>> To: "pacemaker@oss"
>> Sent: Wednesday, July 31, 2013 1:20:58 AM
>> Subj
Hi David,
I opened Bugzilla about this.
* http://bugs.clusterlabs.org/show_bug.cgi?id=5173
Best Regards.
(13.08.01 01:00), David Vossel wrote:
- Original Message -
From: "Kazunori INOUE"
To: "pacemaker@oss"
Sent: Wednesday, July 31, 2013 1:20:58 AM
Subject:
- Original Message -
> From: "Kazunori INOUE"
> To: "pacemaker@oss"
> Sent: Wednesday, July 31, 2013 1:20:58 AM
> Subject: [Pacemaker] Question about behavior when a resource was put into
> unmanaged mode
>
> Hi,
>
> I'm using
Hi,
I'm using pacemaker-1.1.10. (4ae1f17)
When I put a primitive (p1) of group resource into unmanaged mode, low-order
primitive (p2) restarted.
In the case of pacemaker-1.0.13, p2 doesn't stop (it continues "Started").
Is this the assumed behavior?
node $id="3232261523" dev2
node $id="323226152
On 25/07/2013, at 7:03 PM, Kazunori INOUE wrote:
> (13.07.25 11:00), Andrew Beekhof wrote:
>>
>> On 24/07/2013, at 7:40 PM, Kazunori INOUE
>> wrote:
>>
>>> (13.07.18 19:23), Andrew Beekhof wrote:
On 17/07/2013, at 6:53 PM, Kazunori INOUE
wrote:
> (13.07.16 21:18),
(13.07.25 18:03), Kazunori INOUE wrote:
(13.07.25 11:00), Andrew Beekhof wrote:
On 24/07/2013, at 7:40 PM, Kazunori INOUE wrote:
(13.07.18 19:23), Andrew Beekhof wrote:
On 17/07/2013, at 6:53 PM, Kazunori INOUE wrote:
(13.07.16 21:18), Andrew Beekhof wrote:
On 16/07/2013, at 7:04 PM,
(13.07.25 11:00), Andrew Beekhof wrote:
On 24/07/2013, at 7:40 PM, Kazunori INOUE wrote:
(13.07.18 19:23), Andrew Beekhof wrote:
On 17/07/2013, at 6:53 PM, Kazunori INOUE wrote:
(13.07.16 21:18), Andrew Beekhof wrote:
On 16/07/2013, at 7:04 PM, Kazunori INOUE wrote:
(13.07.15 11:00)
On 24/07/2013, at 7:40 PM, Kazunori INOUE wrote:
> (13.07.18 19:23), Andrew Beekhof wrote:
>>
>> On 17/07/2013, at 6:53 PM, Kazunori INOUE
>> wrote:
>>
>>> (13.07.16 21:18), Andrew Beekhof wrote:
On 16/07/2013, at 7:04 PM, Kazunori INOUE
wrote:
> (13.07.15 11:00),
(13.07.18 19:23), Andrew Beekhof wrote:
On 17/07/2013, at 6:53 PM, Kazunori INOUE wrote:
(13.07.16 21:18), Andrew Beekhof wrote:
On 16/07/2013, at 7:04 PM, Kazunori INOUE wrote:
(13.07.15 11:00), Andrew Beekhof wrote:
On 12/07/2013, at 6:28 PM, Kazunori INOUE wrote:
Hi,
I'm using p
On 17/07/2013, at 6:53 PM, Kazunori INOUE wrote:
> (13.07.16 21:18), Andrew Beekhof wrote:
>>
>> On 16/07/2013, at 7:04 PM, Kazunori INOUE
>> wrote:
>>
>>> (13.07.15 11:00), Andrew Beekhof wrote:
On 12/07/2013, at 6:28 PM, Kazunori INOUE
wrote:
> Hi,
>
>
(13.07.16 21:18), Andrew Beekhof wrote:
On 16/07/2013, at 7:04 PM, Kazunori INOUE wrote:
(13.07.15 11:00), Andrew Beekhof wrote:
On 12/07/2013, at 6:28 PM, Kazunori INOUE wrote:
Hi,
I'm using pacemaker-1.1.10.
When a pacemaker's process crashed, the node is sometimes fenced or is not
s
On 16/07/2013, at 7:04 PM, Kazunori INOUE wrote:
> (13.07.15 11:00), Andrew Beekhof wrote:
>>
>> On 12/07/2013, at 6:28 PM, Kazunori INOUE
>> wrote:
>>
>>> Hi,
>>>
>>> I'm using pacemaker-1.1.10.
>>> When a pacemaker's process crashed, the node is sometimes fenced or is not
>>> sometimes f
(13.07.12 22:48), emmanuel segura wrote:
Hi
try to disable selinux
Though I tried it, the result did not change.
+++
Jul 12 16:46:10 dev1 setroubleshoot: SELinux is preventing /usr/bin/virsh
from getattr access on the file
(13.07.15 11:00), Andrew Beekhof wrote:
On 12/07/2013, at 6:28 PM, Kazunori INOUE wrote:
Hi,
I'm using pacemaker-1.1.10.
When a pacemaker's process crashed, the node is sometimes fenced or is not
sometimes fenced.
Is this the assumed behavior?
Yes.
Sometimes the dev1 respawns the process
On 12/07/2013, at 6:28 PM, Kazunori INOUE wrote:
> Hi,
>
> I'm using pacemaker-1.1.10.
> When a pacemaker's process crashed, the node is sometimes fenced or is not
> sometimes fenced.
> Is this the assumed behavior?
Yes.
Sometimes the dev1 respawns the processes fast enough that dev2 gets th
On 12/07/13 04:28, Kazunori INOUE wrote:
Hi,
I'm using pacemaker-1.1.10.
When a pacemaker's process crashed, the node is sometimes fenced or is not
sometimes fenced.
Is this the assumed behavior?
procedure:
$ systemctl start pacemaker
$ crm configure load update test.cli
$ pkill -9 lrmd
attac
Hi
try to disable selinux
+++
Jul 12 16:46:10 dev1 setroubleshoot: SELinux is preventing /usr/bin/virsh
from getattr access on the file /usr/bin/ssh. For complete SELinux
messages. run sealert -l 3d5afba4-40a5-41ff-9530-3839da8a8c
-
Von: Andrew Beekhof [mailto:and...@beekhof.net]
Gesendet: Dienstag, 9. Juli 2013 04:09
An: The Pacemaker cluster resource manager
Betreff: Re: [Pacemaker] Question concerning pacemaker-1-1-10-rc6
On 08/07/2013, at 5:57 PM, Andreas Mock wrote:
Hi Andrew,
I'm taking the builds from
-
Von: Andrew Beekhof [mailto:and...@beekhof.net]
Gesendet: Dienstag, 9. Juli 2013 04:09
An: The Pacemaker cluster resource manager
Betreff: Re: [Pacemaker] Question concerning pacemaker-1-1-10-rc6
On 08/07/2013, at 5:57 PM, Andreas Mock wrote:
> Hi Andrew,
>
> I'm taking t
On 08/07/2013, at 5:57 PM, Andreas Mock wrote:
> Hi Andrew,
>
> I'm taking the builds from
> http://clusterlabs.org/rpm-test-next/rhel-6/x86_64/
> to avoid compiling on my own.
> Do these build relate to the release candidates you're announcing?
Not at all, those are whatever I happen to be t
Hi Andrew,
I'm taking the builds from
http://clusterlabs.org/rpm-test-next/rhel-6/x86_64/
to avoid compiling on my own.
Do these build relate to the release candidates you're announcing?
If yes, could you also announce the version strings?
Best regards
Andreas Mock
__
Am 02.07.2013 um 01:35 schrieb Andreas Mock :
> Hi Leon,
>
> thank you for the pointer to the manuals. I read it already.
>
> My 2-node-cluster seems not to fence the other node
> at startup. And I do not have an explanation. That's the reason
> I asked (after reading the docs).
>
> - CMAN_QUORU
our?
Best regards
Andreas Mock
-Ursprüngliche Nachricht-
Von: Leon Fauster [mailto:leonfaus...@googlemail.com]
Gesendet: Montag, 1. Juli 2013 19:45
An: The Pacemaker cluster resource manager
Betreff: Re: [Pacemaker] Question to fencing/stonithing
Am 01.07.2013 um 14:28 schrieb Andreas Mock :
> H
1 - 100 of 349 matches
Mail list logo
