Hi,
I'm a bit confused about recource options for a group. Does a resource
group need options like 'target-role' and 'is-managed?
According to the 'Pacemake_explained' normal (simple) resources have got
a default 'target-role=started', so i asume i do not have to configure
those for the resour
Hello Andrew/Thomas,
Stupid me it was indeed an inode problem, nothing to do with the
cluster-software. The /var/lib/pengine directory was a bit full.
//I configured the pe-*-serires-max options so this should not happen
again, thanks.
On Fri, Mar 5, 2010 at 3:38 PM, Kees wrote
Debian-packages from madkiss.
Greeting,
Kees
Thanks in advance for your help.
Kees Koehoorn
___
Pacemaker mailing list
Pacemaker@oss.clusterlabs.org
http://oss.clusterlabs.org/mailman/listinfo/pacemaker
ms
resource gets promoted.
Op 11-2-2010 11:03, Alexandr Krylovskiy schreef:
On Wed, 10 Feb 2010 13:42:42 +0100
Kees wrote:
Hello Andrew/All,
Thanks. It works again. This is what I had running after I wanted to
move on to a 3-node cluster.
Two drbd-nodes for storage and one as a webserver
-nodes back to where they are now. Right?
PS I'm a newbie to this so sorry this stupid mistake!
Greetings,
Kees Koehoorn
target-role="Started"<--- this isnt going to be helping.
nor is
symmetric-cluster="false"
without defining any location constraints.
On W
drbd_websites:promote websites:start
property $id="cib-bootstrap-options" \
expected-quorum-votes="1024" \
dc-version="1.0.7-54d7869bfe3691eb723b1d47810e5585d8246b58" \
cluster-infrastructure="openais" \
no-quorum-policy="ignor
false" \
last-lrm-refresh="1265725342"
drbd.conf:
global {
usage-count yes;
}
common {
protocol C;
}
resource r0 {
device /dev/drbd0;
meta-disk internal;
on test1 {
disk /dev/sda11;
address 10.100.5.1:7789;
}
on test2 {
disk /dev/sda10;
address 10.100.5.2:7789;
}
}
Thanks in advance for your help.
Kees Koehoorn
___
Pacemaker mailing list
Pacemaker@oss.clusterlabs.org
http://oss.clusterlabs.org/mailman/listinfo/pacemaker
cond ring, when i try to do that i get an
error: status = Marking ringid 1 interface 192.168.0.1 FAULTY -
adminisrtative intervention required.
I seems corosync.conf has to be the same on all nodes, is that true? if
so, is there a way to let the drdb work on is own link?
Never mind, I found it in Mercurial;
http://hg.clusterlabs.org/pacemaker/stable-1.0/rev/33da369d36e3
Applied the fix, rebuilded the packages and it seems to work nicely again.
-kees
> -Original Message-
> From: Kees Hoekzema [mailto:k...@tweakers.net]
> Sent: maandag 19 oktobe
h and rebuild the packages myself if I just knew where to apply this
fix. So does anyone know in which file this fix should be, or does anyone
have a patch for this somewhere?
-kees
___
Pacemaker mailing list
Pacemaker@oss.clusterlabs.org
http:
estion: Is it normal for aisexec, using these packages, to consume this
much cpu? If it is not, how can I fix it, and if it is normal; is there a
way to make it consume less cpu? The cpu in this server is an X5570, one of
the fastest CPU's you can get n
11 matches
Mail list logo
