If the promote of DRBD on one node cannot be done, this might
be because the demote on the other node cannot be achieved.
Do you mount a FS ? If so, force : umount -fl /mountpoint
Double check (cat /proc/drbd) that the DRBD resource is
really secondary on the demoted node.
This is with no
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 12/04/2012 08:34 PM, Lars Marowsky-Bree wrote:
On 2012-12-04T20:38:54, Fabian Herschel fabian.hersc...@arcor.de
wrote:
Specifying target-role=Master is completely different from
specifying a role=Master/Slave on an operation.
The former
Okay, I think I have some new information on this problem.
First, upgrading to drbd 8.4.2 did not help.
I believe the problem is that when I do 'crm node offline' Pacemaker is fully
stopping the drbd service. This causes drbd on the secondary to go into a
WFConnection state. It refuses to
On 12/05/2012 12:05 PM, Robinson, Eric wrote:
I believe the problem is that when I do 'crm node offline' Pacemaker
is fully stopping the drbd service. This causes drbd on the secondary to
go into a WFConnection state. It refuses to promote to primary in that
state.
Probably not relevant, but
-Original Message-
From: linux-ha-boun...@lists.linux-ha.org
[mailto:linux-ha-boun...@lists.linux-ha.org] On Behalf Of
Dimitri Maziuk
Sent: Wednesday, December 05, 2012 10:18 AM
To: linux-ha@lists.linux-ha.org
Subject: Re: [Linux-HA] master/slave drbd resource STILL
On 12/05/2012 01:36 PM, Robinson, Eric wrote:
I think the more revelant issue is that Pacemaker is fulling
stopping
drbd, which canses the standby to go into a WFConnection state, so it
refuses to promote.
I was thinking drbd losing packets and thus falling back to WFC rather
than pacemaker
I was thinking drbd losing packets and thus falling back to
WFC rather than pacemaker ordering a full stop.
Gotcha. Well, I think it is demonstrably the case that it is losing packets
because the service is stopped.
you could probably find the stop action in the
RA and replace it with
you could probably find the stop action in the
RA and replace it with (e.g.) logger 'AIE ***I did not
want this***' and then see what gets logged.
--
Well, that worked, in the sense that the resource now fails over. I replaced
the start and stop actions in the RA with logger
On 12/05/2012 09:31 PM, Robinson, Eric wrote:
you could probably find the stop action in the
RA and replace it with (e.g.) logger 'AIE ***I did not
want this***' and then see what gets logged.
--
Well, that worked, in the sense that the resource now fails over. I replaced
the start
-Original Message-
From: linux-ha-boun...@lists.linux-ha.org
[mailto:linux-ha-boun...@lists.linux-ha.org] On Behalf Of
Vladislav Bogdanov
Sent: Saturday, December 01, 2012 10:40 PM
To: General Linux-HA mailing list
Subject: Re: [Linux-HA] master/slave drbd resource STILL
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 11/29/2012 10:14 PM, Robinson, Eric wrote:
Bump... does anyone have some insight on this? Google is not
turning up anything useful.
Our newest cluster will not failover master/slave drbd resources.
It works fine manually using drbdadm from a
--
Eric Robinson
Director of Information Technology
Physician Select Management, LLC
775-885-2211 x 111
I am not sure if that will really help you - but in my
cluster (ok older pacemaker version) I ahve the following to
define a master slave
resource:
primitive rsc_sap_HA0_ASCS00
On 2012-12-04T20:38:54, Fabian Herschel fabian.hersc...@arcor.de wrote:
I am not sure if that will really help you - but in my cluster (ok
older pacemaker version) I ahve the following to define a master slave
resource:
primitive rsc_sap_HA0_ASCS00 ocf:heartbeat:SAPInstance \
operations
If the promote of DRBD on one node cannot be done, this might be because
the demote on the other node cannot be achieved.
Do you mount a FS ? If so, force : umount -fl /mountpoint
Double check (cat /proc/drbd) that the DRBD resource is really secondary on
the demoted node.
Maybe you could play
Try to set 'target-role=Started' in both of them.
Okay, but how does that address the problem of error code 11 from drbdadm?
--Eric
Disclaimer - December 1, 2012
This email and any files transmitted with it are confidential and intended
solely for 'General Linux-HA mailing list'. If
02.12.2012 00:34, Robinson, Eric wrote:
Try to set 'target-role=Started' in both of them.
Okay, but how does that address the problem of error code 11 from drbdadm?
Well, you have error promoting resources. 11 is EAGAIN, usually meaning
you did not demote the other side.
Your logs contain
30.11.2012 00:14, Robinson, Eric wrote:
Bump... does anyone have some insight on this? Google is not turning up
anything useful.
Our newest cluster will not failover master/slave drbd resources. It works
fine manually using drbdadm from a shell prompt, but when we try it using
'crm node
Bump... does anyone have some insight on this? Google is not turning up
anything useful.
Our newest cluster will not failover master/slave drbd resources. It works fine
manually using drbdadm from a shell prompt, but when we try it using 'crm node
standby' and letting the cluster manage the
I posted about this a couple of weeks ago but didn't get a response.
Our newest cluster will not failover master/slave drbd resources. It works fine
manually using drbdadm from a shell prompt, but when we try it using 'crm node
standby' and letting the cluster manage the resource, crm_mon just
19 matches
Mail list logo
