> From: Andrew Beekhof
> To: The Pacemaker cluster resource manager
> Cc:
> Date: Mon, 26 Aug 2013 09:26:32 +1000
> Subject: Re: [Pacemaker] Pacemaker 1.1.7 and negative corosync nodeid
>
> On 24/08/2013, at 5:26 AM, Nate Clark wrote:
>
> > I have a few systems running pacemaker 1.1.7 using coro
Hi Andrew,
as this is a real showstopper at the moment I invested some other
hours to be sure (as far as possible) not having made an error.
Some additions:
1) I mirrored the whole mini drbd config to another pacemaker cluster.
Same result: pacemaker 1.1.8 works, pacemaker 1.1.10 not
2) When I r
Thanks your reply. I did a lot of test when I use
> clone WebIP ClusterIP \
> meta globally-unique="true" clone-max="2" clone-node-max="2"
The result will be like my previous post.
The cluster IP always only running on one node after standby test.
Then I change the
Clone-node-max="1" then
27.08.2013, 05:39, "Andrew Beekhof" :
> On 26/08/2013, at 3:09 PM, Andrey Groshev wrote:
>
>> 26.08.2013, 03:34, "Andrew Beekhof" :
>>> On 23/08/2013, at 9:39 PM, Andrey Groshev wrote:
Hello,
Today I try remake my test cluster from cman to corosync2.
I drew attention
On 27/08/2013, at 3:31 AM, Andreas Mock wrote:
> Hi all,
>
> while the linbit drbd resource agent seems to work perfectly on
> pacemaker 1.1.8 (standard software repository) we have problems
> with the last release 1.1.10 and also with the newest head
> 1.1.11.xxx.
>
> As using drbd is not so
On 20/08/2013, at 9:48 PM, WenWen wrote:
> Hi,
> I am doing active/active cluster with drbd pacemaker and apache.
> when i start cman and pacemaker service on both nodes at the first time
> everything is ok.
>
> then I set node1 to standby then online again.
> The apache and VIP can not back t
You could potentially use:
crm_resource --get-parameter --resource $ANOTHER_RESOURCE
and cycle through the list of Postgres children (filtering out those running as
Master or Stopped)
On 26/08/2013, at 6:00 PM, Gregg Jaskiewicz wrote:
> Hi Guys,
>
> I need to write an resource agent for ou
Specifying 'action="off"' for a device was not possible prior to 1.1.10
(because we perform other actions on the devices too, so it was unconditionally
overwritten)
You should be using this cluster property from "man pengine"
stonith-action = enum [reboot]
Action to send to STO
On 26/08/2013, at 3:09 PM, Andrey Groshev wrote:
>
>
> 26.08.2013, 03:34, "Andrew Beekhof" :
>> On 23/08/2013, at 9:39 PM, Andrey Groshev wrote:
>>
>>> Hello,
>>>
>>> Today I try remake my test cluster from cman to corosync2.
>>> I drew attention to the following:
>>> If I reset cluster
On 26/08/2013, at 7:48 PM, Francis SOUYRI wrote:
> Hello Andrew,
>
> About your document
> "http://blog.clusterlabs.org/blog/2013/mixing-pacemaker-versions/";
>
>
>1. stop the cluster on both nodes
>2. on both nodes, run:
>
>CIB_file=/path/to/cib.xml cibadmin -M -X ''
>
>3.
Hi Matthew,
thank you for that hint. I'll recheck once again.
I'm pretty sure this is not the problem. But who knows... ;-)
Best regards
Andreas Mock
-Ursprüngliche Nachricht-
Von: Matthew O'Connor [mailto:m...@ecsorl.com]
Gesendet: Montag, 26. August 2013 21:12
An: The Pacemaker clust
On 08/26/2013 01:31 PM, Andreas Mock wrote:
> cat /proc/drbd
> version: 8.4.3 (api:1/proto:86-101)
> GIT-hash: 89a294209144b68adb3ee85a73221f964d3ee515 build by root@dis03-test,
> 2013-07-24 17:19:24
>
> on both nodes. The drbd resource was shutdown previously in a clean state,
> so that any node
On 2013-08-23T15:16:17, Jan Christian Kaldestad wrote:
> It looks like pacemaker 1.1.10 fixes a few things related to crmd and
> fencing failures, so I'd like to test 1.1.10. Unfortunately it's not
> available for SLES yet, so I guess I just have to wait...
If you have SLE, please file a request
Hi all,
while the linbit drbd resource agent seems to work perfectly on
pacemaker 1.1.8 (standard software repository) we have problems
with the last release 1.1.10 and also with the newest head
1.1.11.xxx.
As using drbd is not so uncommon I really hope to find interested
people helping me out.
Hello Andrew,
About your document
"http://blog.clusterlabs.org/blog/2013/mixing-pacemaker-versions/";
1. stop the cluster on both nodes
2. on both nodes, run:
CIB_file=/path/to/cib.xml cibadmin -M -X 'crm_feature_set="3.0.7"/>'
3. start node1 and wait until it is elected as
Hello Andrew,
Thank you for your reply...
I set this corosync config:
totem {
version: 2
secauth: off
cluster_name: cluster
interface {
ringnumber: 0
bindnetaddr: 192.168.1.0
ttl: 1
}
transport: udpu
}
nodelist {
node {
ring0_addr: noeud1..fr
n
Hi Guys,
I need to write an resource agent for our little service here.
The service will only run on the same node as PostgreSQL master.
However, the service needs to know eth0 IPs of every 'slave' postgresql
node.
Each node's host name represents its eth1 IP.
What's the best way to accomplish t
17 matches
Mail list logo