On 12/04/2012 08:56 PM, Emmanuel Saint-Joanis wrote:
This setup might do the trick :
primitive srv-mysql lsb:mysql \
op monitor interval=120 \
op start interval=0 timeout=60 on-fail=restart \
op stop interval=0 timeout=60s on-fail=ignore
primitive srv-websphere lsb:websphere \
op
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 will
not
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
On 12/05/2012 10:49 PM, Felipe Gutierrez wrote:
Hi,
I configured wrong my pacemaker. I have resources that are wrong. So I need
to delete them and configure again.
Does any one know how to remove resources and how to configure them
correctly?
to clean your complete configuration and
Thanks Andreas,
It works very well!
Do you have some link to help to configure pacemaker? I have
DRBD+Xen+heartbeat configured, but when I pull out the cable from the
primary machine, the secondary machine doesn't recognize. I believe I need
to use Stonith...
Best Regards
Felipe
On Wed, Dec 5,
a) Please reply on the thread.
b) I am not affiliated with Linux-HA, so I have no control over their
website.
On 12/05/2012 08:48 PM, Pang ChongYang wrote:
Please add this note
‘If you are starting a new project, you should not use heartbeat. It is
no longer developed and has been replaced
On Wed, Dec 5, 2012 at 6:52 AM, Felipe Gutierrez
felipe.o.gutier...@gmail.com wrote:
I think I found how to configure. I change eth0 to xenbr0, because I
modified the networ/interface (ifconfig)
# cat ha.cf
logfacility daemon
keepalive 2
deadtime 10
warntime 5
initdead 120
udpport 694
14 matches
Mail list logo
