Re: [Pacemaker] Pacemaker remote nodes, naming, and attributes

- Original Message - > From: "Lindsay Todd" > To: "The Pacemaker cluster resource manager" > Sent: Thursday, July 11, 2013 12:09:52 PM > Subject: Re: [Pacemaker] Pacemaker remote nodes, naming, and attributes > > So I've switched my cluster to be asymmetric... > > The remote nodes don't

[Pacemaker] strange drbd migration fail

I have run into a strange problem with a DRBD resource migrating master role from one node to the other. 3-node cluster, Pacemaker v1.1.9, Corosync v1.4.5, DRBD 8.3.11. Both Pacemaker and Corosync are built from source. Two of the nodes are running DRBD resources between them in simple single-ma

Re: [Pacemaker] Simulating that a node is down.

Hi Andreas/Jacobo, For one of my network failure tests, I drop all incoming and outgoing packets. I have also tested shutting down the eth interface, as you mentioned below, but have run into DRBD split-brain issues, as I reported in separate mail to this list. I’d be interested to hear if you

Re: [Pacemaker] Issue with an isolated node overriding CIB after rejoining main cluster

Hi Andrew, Thanks for the reply. I have a couple of more questions below. I have seem to have two main problems: isolated node updating CIB; corosync behaviour to ifdown. > Why isn't your normal fencing device working? My normal fencing is working and was in place for nearly all of my testing.

[Pacemaker] Help required translating crm commands into pcs ones

Hi, We have some telephony failover equipment (Digium R850 appliances) that came with a sample Pacemaker configuration using the "crm configure load update" method. Now we are using Fedora 18 Kernel 3.9.4-200 pacemaker 1.1.9-0.1, so pcs is the preferred management interface. For most of the

Re: [Pacemaker] Highly available NFS service in RHEL6.4

Am 15.07.2013 um 14:21 schrieb Leon Fauster : > Am 10.07.2013 um 16:31 schrieb Ron Kerry : >> What is the suggested way to configure a highly available NFS service using >> cman/pacemaker in RHEL6.4? >> >> RHEL 6.4 has two init.d scripts - nfs and nfslock. The available pacemaker >> resource age

Re: [Pacemaker] Highly available NFS service in RHEL6.4

Am 10.07.2013 um 16:31 schrieb Ron Kerry : > What is the suggested way to configure a highly available NFS service using > cman/pacemaker in RHEL6.4? > > RHEL 6.4 has two init.d scripts - nfs and nfslock. The available pacemaker > resource agent script in /usr/libocf/resource.d/heartbeat/nfsserv

Re: [Pacemaker] Different behaviour for cloned resource on 1 and 2 nodes

Hi, I created a bug (http://bugs.clusterlabs.org/show_bug.cgi?id=5170) containing extra explanation and the crm_report. Thanks for taking your time to check this problem! gr. Johan On 15-07-13 04:11, Andrew Beekhof wrote: On 11/07/2013, at 12:21 AM, Johan Huysmans wrote: Hi All, I have

Re: [Pacemaker] RHEL 6.3 + fence_vmware_soap + esx 5.1

Hi Andrew. Here is the ommited /var/log/messages with stonigh-ng sections. Jul 15 09:53:38 PCMK1 stonith-ng[1538]: notice: stonith_device_action: Device vm-fence-pcmk2 not found Jul 15 09:53:38 PCMK1 stonith-ng[1538]: info: stonith_command: Processed st_execute from lrmd: rc=-12 Jul 15 09:5

Re: [Pacemaker] Highly available NFS service in RHEL6.4

On 11/07/2013, at 12:31 AM, Ron Kerry wrote: > What is the suggested way to configure a highly available NFS service using > cman/pacemaker in RHEL6.4? > > RHEL 6.4 has two init.d scripts - nfs and nfslock. The available pacemaker > resource agent script in /usr/libocf/resource.d/heartbeat/nf