pcs constraint colocation set fs_ldap-clone sftp01-vip ldap1
sequential=true
Let me know if this does or doesn't work for you.
I have been testing this now for a couple days and I think I must be
doing something wrong, firstly though, the command itself completes
successfully:
# pcs cons
>
> I think there's an error in the man page (which I'll work on getting
fixed).
Thanks Chris.
> Can you try: (removing 'setoptions' from your command)
>
>
> pcs constraint colocation set fs_ldap-clone sftp01-vip ldap1
sequential=true
>
>
> Let me know if this does or doesn't work for you.
>
Hi All,
I have several resources that depend on a cloned share file system and vip
that need to be up and operational before the resource can start, I was
reading the pacemaker documentation and it looks like colocation sets is
what I am after. I can see in the documentation that you can define a
istance in this issue.
From: Asgaroth [mailto:li...@blueface.com]
Sent: 10 February 2014 11:46
To: 'Mailing List: Pacemaker'
Subject: RE: node1 fencing itself after node2 being fenced
Hi All,
OK, here is my testing using cman/clvmd enabled on system startup and clvmd
outside of
>
> I would really love to see logs at this point.
> Both from pacemaker and the system in general (and clvmd if it produces
> any).
>
> Based on what you say below, there doesn't seem to be a good reason for
> the hang (ie. no reason to be trying to fence anyone)
>
I will try to get some logs
>
> Just a guess. Do you have startup fencing enabled in dlm-controld (I actually
> do not remember if it is applicable to cman's version, but it exists in
> dlm-4) or
> cman?
> If yes, then that may play its evil game, because imho it is not intended to
> use with pacemaker which has its own sta
> i sometimes have the same situation. sleep ~30 seconds between startup
> cman and clvmd helps a lot.
>
Thanks for the tip, I just tried this (added sleep 30 in the start section of
case statement in cman script, but this did not resolve the issue for me), for
some reason clvmd just refuses to
>
> The 3rd node should (and needs to be) fenced at this point to allow the
> cluster to continue.
> Is this not happening?
The fencing operation appears to complete successfully, here is the
sequence:
[1] All 3 nodes running properly
[2] On node 3 I run "echo c > /proc/sysrq-trigger" which "han
> -Original Message-
> From: Andrew Beekhof [mailto:and...@beekhof.net]
> Sent: 17 February 2014 00:55
> To: li...@blueface.com; The Pacemaker cluster resource manager
> Subject: Re: [Pacemaker] node1 fencing itself after node2 being fenced
>
>
> If you have configured cman to use fence_p
> -Original Message-
> From: Vladislav Bogdanov [mailto:bub...@hoster-ok.com]
> Sent: 11 February 2014 03:44
> To: pacemaker@oss.clusterlabs.org
> Subject: Re: [Pacemaker] node1 fencing itself after node2 being fenced
>
> Nope, it's Centos6. In few words, It is probably safer for you to st
-Original Message-
From: Vladislav Bogdanov [mailto:bub...@hoster-ok.com]
Sent: 10 February 2014 13:27
To: pacemaker@oss.clusterlabs.org
Subject: Re: [Pacemaker] node1 fencing itself after node2 being fenced
I cannot really recall if it hangs or returns error for that (I moved to
coros
Hi All,
OK, here is my testing using cman/clvmd enabled on system startup and clvmd
outside of pacemaker control. I still seem to be getting the clvmd hang/fail
situation even when running outside of pacemaker control, I cannot see
off-hand where the issue is occurring, but maybe it is related
On 06/02/2014 04:30, Nikita Staroverov wrote:
Why do you need clvmd as a cluster resource? If you start clvmd
outside of a cluster your problem will be no problem at all.
I was running it under pacemaker because it is a neat way of seeing
dependant services. When I remove dlm/clvmd from pacema
On 06/02/2014 05:52, Vladislav Bogdanov wrote:
Hi,
I bet your problem comes from the LSB clvmd init script.
Here is what it does do:
===
...
clustered_vgs() {
${lvm_vgdisplay} 2>/dev/null | \
awk 'BEGIN {RS="VG Name"} {if (/Clustered/) print $1;}'
}
clustered_active_lvs()
On 05/02/2014 18:57, Никита Староверов wrote:
It seems to me, clvmd can't answer to pacemaker monitor operation in
30 sec because it is also locked by dlm.
You don't need clvmd and dlvm resources on cman-based clusters. clvm
can simply start after cman. both dlvm and fenced are configured by
cman
On 05/02/2014 16:12, Digimer wrote:
You say it's working now? If so, excellent. If you have any troubles
though, please share your cluster.conf and 'pcs config show'.
Hi Digimer, no its not working as I expect it to when I test a crash of
node 2, clvmd goes in to a failed state and then node
On 05/02/2014 13:44, Nikita Staroverov wrote:
Your setup is completely wrong, sorry. You must use RHEL6
documentation not RHEL7.
in short, you should create cman cluster according to RHEL6 docs, but
use pacemaker instead of rgmanager and fence_pcmk as fence agent for cman.
Thanks, for the info
Hi All,
First of all, thanks for the brilliant documentation at clusterlabs and
the alteeva.ca tutorials! They helped me out a lot.
I am relatively new to pacemaker but come from a Solaris background with
cluster experience, I am now trying to get on board with pacemaker
I have setup a 2 no
18 matches
Mail list logo
