What is the point of clonning stonith primitive adviced in manual?
2011/3/1 Dejan Muhamedagic
> > Question: What should happen to start pacemaker fence some node?
>
> In case the status of a node or a resource running on a node
> cannot be established. Practically, that means no heartbeat from
>
Hi,
Having deep issues with my cluster setup. Everything works ok until
I add a VirtualDomain RA in. Then things go pearshaped in that it seems
to ignore the "order" crm config for it and starts as soon as it can.
The crm config is provided below. Basically p-vd_vg.test1 attempts to
start despite
On 3/3/2011 at 09:17 AM, Klaus Darilion wrote:
> Hi!
>
> I just updated by Debian box to wheezy to test Pacemaker 1.0.10. dpkg
> reports version 1.0.10 but crm_mon reports version 1.0.9. So, which
> version is really running? Is really 1.0.9 running or is this due to the
> previously used 1
Hi,
I'm trying to simulate various scenarios and what to do to correct the
problem. I have a DRBD cluster as defined below; if the primary fails
(ie power cycled drbd01.test), the secondary (drbd02.test) takes over
successfully, so DRBD:master now runs on drbd02.test. When node
drbd01.test co
Hi!
I just updated by Debian box to wheezy to test Pacemaker 1.0.10. dpkg
reports version 1.0.10 but crm_mon reports version 1.0.9. So, which
version is really running? Is really 1.0.9 running or is this due to the
previously used 1.0.9 version?
# dpkg -l|grep pacem
ii pacemaker1.0.1
I have narrowed this down to an issue that I feel is really a bug in the way pacemaker is dealing
with constraints made between resource groups as opposed to resource primitives. The version of
pacemaker involved here is:
libpacemaker3-1.1.2-0.7.1
pacemaker-1.1.2-0.7.1
A configuration which
> Robert,
>
> My cluster has two nodes, in this case what happens with pacemaker-corosync
> without quorum disk? It's possible?
>
> Until now this cluster run with Heartbeat but this not run correctly because
> when one node down, the other fencing this a this fencing the other and two
> restar
Robert van Leeuwen writes:
>
> -Original message-
> To: pacemaker@...;
> From: victor
> Sent: Wed 02-03-2011 11:29
> Subject: [Pacemaker] Cluster proxy pacemaker-corosync in a BladeCenter
> > Hi,
> > I plan mount a cluster proxy without shared storage in a BladeCenter but I
> >
Hi,
On Wed, Mar 02, 2011 at 04:17:41PM +0800, jiaju liu wrote:
> when I use order crm configure ...it often shows
> WARNING: status: operation not recognizedWARNING: force-reload: operation not
> recognizedWARNING: force-reload: operation not recognizedWARNING: status:
> operation not recogn
Hi,
On Wed, Mar 02, 2011 at 04:00:12PM +0800, jiaju liu wrote:
>
> Hi
> my configuration has two node and I add file system lustre in cluster.
> however, when I use crm resource stop datavol_vol(filesystem), stonith reboot
> the node, it is not happen every time but very often. I am not sure i
-Original message-
To: pacema...@clusterlabs.org;
From: victor
Sent: Wed 02-03-2011 11:29
Subject:[Pacemaker] Cluster proxy pacemaker-corosync in a BladeCenter
> Hi,
> I plan mount a cluster proxy without shared storage in a BladeCenter but I
> can't
> use disk quorum be
Hi,
I plan mount a cluster proxy without shared storage in a BladeCenter but I
can't
use disk quorum because I haven't fibre channels for the disks.
It's possible? and run correctly?
For fencing I use RSA, I must open any port?
Thanks
___
Pacemaker m
Hi,
HealthSMART RA seems not working properly when you specified 'devices' option.
Suggest the attached patch.
Thanks,
--
Keisuke MORI
HealthSMART: fix devices option
diff -r cf4e9febed8e extra/resources/HealthSMART
--- a/extra/resources/HealthSMART Wed Feb 23 14:52:34 2011 +0100
+++ b/extra/re
when I use order crm configure ...it often shows
WARNING: status: operation not recognizedWARNING: force-reload: operation not
recognizedWARNING: force-reload: operation not recognizedWARNING: status:
operation not recognizedWARNING: status: operation not recognizedWARNING:
force-reload: ope
Hi
my configuration has two node and I add file system lustre in cluster. however,
when I use crm resource stop datavol_vol(filesystem), stonith reboot the node,
it is not happen every time but very often. I am not sure it is the problem
about pacemaker corosync or lustreThanks a lot
_
15 matches
Mail list logo