On 5 Jul 2014, at 1:00 am, Giuseppe Ragusa wrote:
> From: and...@beekhof.net
> Date: Fri, 4 Jul 2014 22:50:28 +1000
> To: pacemaker@oss.clusterlabs.org
> Subject: Re: [Pacemaker] Pacemaker 1.1: cloned stonith resources require
> --force to be added to levels
>
>
> On 4 Jul 2014, at 1:29
Fingers crossed, this will be the last pre-release of 1.1.12.
In this update:
- SUSE has contributed some additional logic around the removal of 'old' nodes
- Handling of resources that require neither quorum nor fencing is improved
- systemd resources that take a while to reach the 'active' state
On 4 Jul 2014, at 1:05 am, Bryan Bueter wrote:
> I have a two node active/standby cluster that I'm building and I cant get
> pacemaker to promote my DRBD resource. I'm thinking I have something
> wrong in the configuration but I dont see it.
>
> The errors I get on NODE1 are:
> /var/log/corosy
On 4 Jul 2014, at 3:16 pm, Giuseppe Ragusa wrote:
> Hi all,
> I'm trying to create a script as per subject (on CentOS 6.5, CMAN+Pacemaker,
> only DRBD+KVM active/passive resources; SNMP-UPS monitored by NUT).
>
> Ideally I think that each node should stop (disable) all locally-running
> Virtu
On 8 Jul 2014, at 2:39 am, Ron Kerry wrote:
> On 7/3/14, 10:23 PM, Andrew Beekhof wrote:
>>
>> Seems to be fixed in the latest 1.1.12 beta:
>>
>> # tools/crm_verify -x ~/Downloads/cibadmin-Ql.txt -VVV
>> notice: update_validation: pacemaker-1.2-style configuration is
>> also valid
> Date: Mon, 7 Jul 2014 10:04:20 +0200
> From: lars.ellenb...@linbit.com
> To: drbd-u...@lists.linbit.com; pacemaker@oss.clusterlabs.org
> Subject: Re: [Pacemaker] [DRBD-user] DRBD active/passive on Pacemaker+CMAN
> cluster unexpectedly performs STONITH when promoting
>
> On Fri, Jul 04, 2014 at
> Date: Mon, 7 Jul 2014 08:57:48 +0400
> From: nsfo...@gmail.com
> To: pacemaker@oss.clusterlabs.org
> Subject: Re: [Pacemaker] [DRBD-user] DRBD active/passive on Pacemaker+CMAN
> cluster unexpectedly performs STONITH when promoting
>
> I think that thread related to your question about fence-pee
Hi,
Thanks for the help Andrew! It turns out that I mistakenly started the f5
agent's unix service on all three nodes before adding its resource to
pacemaker, and this was causing the above errors. Once I ensured that only
one service was brought up (on the node on which I added it as a resource
t
On 7/3/14, 10:23 PM, Andrew Beekhof wrote:
Seems to be fixed in the latest 1.1.12 beta:
# tools/crm_verify -x ~/Downloads/cibadmin-Ql.txt -VVV
notice: update_validation: pacemaker-1.2-style configuration is also valid
for pacemaker-1.3
notice: update_validation: Upgrading pacemaker-
>> How do I tell Pacemaker to demote and not stop DRBD?
>you are using the drbd-resource from linbit with a master-slave-clone?
This is my current config:
http://pastebin.com/r2fHS95t
Thanks
Dan
___
Pacemaker mailing list: Pacemaker@oss.clusterlabs
On Fri, Jul 04, 2014 at 06:04:12PM +0200, Giuseppe Ragusa wrote:
> > > The setup "almost" works (all seems ok with: "pcs status", "crm_mon
> > > -Arf1", "corosync-cfgtool -s", "corosync-objctl | grep member") , but
> > > every time it needs a resource promotion (to Master, i.e. becoming
> > > prima
11 matches
Mail list logo
