[Pacemaker] Corosync resources actions when a node (re)joins

2011-03-29 Thread Stephan-Frank Henry
Hello again, I was doing some tests with some LSB resources and noticed that when one of the nodes is removed (corosync stop) and then rejoins (start), regardless of who is currently master and who is slave, the LSB resource will fire a [stop] and then a [start]. As I am trying to control a re

Re: [Pacemaker] rsc_colocation version problem?

2011-02-14 Thread Stephan-Frank Henry
> On: Mon, 14 Feb 2011 09:52:57 +0100, Andrew Beekhof wrote: > On Thu, Feb 10, 2011 at 6:02 PM, Stephan-Frank Henry > > Hello again, > > > > on quick question. > > In many examples I see rsc_colocation variants with keys 'rsc', > 'with-rsc' an

Re: [Pacemaker] A/P Corosync, PGSQL and Split Brains questions

2011-02-11 Thread Stephan-Frank Henry
> On: Fri, 11 Feb 2011 01:54:04 +0100, Lars Ellenberg worte: > On Wed, Feb 09, 2011 at 02:48:52PM +0100, Stephan-Frank Henry wrote: > > My scenario: > > Acive/Passive 2 node cluster (serverA & serverB) with Corosync, DRBD & > PGSQL. > > The resources are configu

[Pacemaker] rsc_colocation version problem?

2011-02-10 Thread Stephan-Frank Henry
Hello again, on quick question. In many examples I see rsc_colocation variants with keys 'rsc', 'with-rsc' and 'with-rsc-role'. Yet when I use them it get smacked by crm_verify: cib.xml:102: element rsc_colocation: validity error : Element rsc_colocation does not carry attribute to cib.xml:102:

Re: [Pacemaker] A/P Corosync, PGSQL and Split Brains questions

2011-02-10 Thread Stephan-Frank Henry
> On: Thu, 10 Feb 2011 09:25:22 +0100, Andrew Beekhof wrote: > On Thu, Feb 10, 2011 at 9:09 AM, Stephan-Frank Henry > wrote: > > > >> You forgot > >> 0) Configure stonith > >> > >> If data is being written to both sides, one of the sets

Re: [Pacemaker] A/P Corosync, PGSQL and Split Brains questions

2011-02-10 Thread Stephan-Frank Henry
Original-Nachricht > On: Thu, 10 Feb 2011 08:55:56 +0100, Florian Haas wrote:> On 02/09/2011 02:48 > PM, Stephan-Frank Henry wrote: > > Hello agian, > > > > after fixing up my VirtualIP problem, I have been doing some Split Brain > tests and while

Re: [Pacemaker] A/P Corosync, PGSQL and Split Brains questions

2011-02-10 Thread Stephan-Frank Henry
> On: Thu, 10 Feb 2011 08:51:01 +0100, Andrew Beekhof wrote: > On Wed, Feb 9, 2011 at 2:48 PM, Stephan-Frank Henry > wrote: > > Hello agian, > > > > after fixing up my VirtualIP problem, I have been doing some Split Brain > tests and while everything 'returns

[Pacemaker] A/P Corosync, PGSQL and Split Brains questions

2011-02-09 Thread Stephan-Frank Henry
Hello agian, after fixing up my VirtualIP problem, I have been doing some Split Brain tests and while everything 'returns to normal', it is not quite what I had desired. My scenario: Acive/Passive 2 node cluster (serverA & serverB) with Corosync, DRBD & PGSQL. The resources are configured as Mas

Re: [Pacemaker] Corosync & IPAddr problems(?)

2011-02-09 Thread Stephan-Frank Henry
Howdy, > On Mon, 7 Feb 2011 16:36:46 +0100, Dejan Muhamedagic wrote:> Hi, > > On Mon, Feb 07, 2011 at 02:01:11PM +0100, Stephan-Frank Henry wrote: > > Hello again, > > > > I am having some possible problems with Corosync and IPAddr. > > To be more specific, w

[Pacemaker] Corosync & IPAddr problems(?)

2011-02-07 Thread Stephan-Frank Henry
Hello again, I am having some possible problems with Corosync and IPAddr. To be more specific, when I do a /etc/init.d/corosync stop, while everything shuts down more or less gracefully, the virtual ip never is released (still visible with ifconfig). if I do a 'sudo ifdown --force eth0:0' it wo

Re: [Pacemaker] Strange behavior when starting up Corosync in a single node setup

2010-10-25 Thread Stephan-Frank Henry
Original-Nachricht > Datum: Thu, 21 Oct 2010 18:46:32 +0200 > Von: "Stephan-Frank Henry" > > Andrew Beekhof > > Mon, 13 Sep 2010 06:25:48 -0700 > > > > Looks like corosync can't talk to itself - ie. it never sees the > > mul

Re: [Pacemaker] Strange behavior when starting up Corosync in a single node setup

2010-10-21 Thread Stephan-Frank Henry
> Andrew Beekhof > Mon, 13 Sep 2010 06:25:48 -0700 > > Looks like corosync can't talk to itself - ie. it never sees the > multicast messages it sends out. > This would result in the pacemaker errors you're seeing. > > Almost always this is a firewall issue :-) > Perhaps try disabling it completel

[Pacemaker] Corosync node detection working too good

2010-10-04 Thread Stephan-Frank Henry
Hello all, still working on my nodes and although the last problem is not officially solved (I hard coded certain versions of the packages and that seems to be ok now) I have a different interesting feature I need to handle. I am setting up my nodes by default as single node setups. But today w

[Pacemaker] Strange behavior when starting up Corosync in a single node setup

2010-09-10 Thread Stephan-Frank Henry
Hello again, new week new problem. :D Setup: Single node setup (default via my installer) /etc/hosts 127.0.0.1 localhost 172.16.0.1 cmsserver001 the installer basically already takes care of setting everything up for a single node by using both above as nodes in the drbd.conf. This h

Re: [Pacemaker] Setting up routing for a virtual ip

2010-09-03 Thread Stephan-Frank Henry
Original-Nachricht > Datum: Thu, 02 Sep 2010 19:08:00 +0200 > Von: "Stephan-Frank Henry" > An: The Pacemaker cluster resource manager > Betreff: Re: [Pacemaker] Setting up routing for a virtual ip > Original-Nachricht > > D

Re: [Pacemaker] Setting up routing for a virtual ip

2010-09-02 Thread Stephan-Frank Henry
Original-Nachricht > Datum: Thu, 02 Sep 2010 11:40:13 +0200 > Von: "Stephan-Frank Henry" > An: pacemaker@oss.clusterlabs.org > Betreff: [Pacemaker] Setting up routing for a virtual ip > Hello everyone, > > I am currently stuck trying to set up r

[Pacemaker] Setting up routing for a virtual ip

2010-09-02 Thread Stephan-Frank Henry
Hello everyone, I am currently stuck trying to set up routing for a configured virtual ip to the static ip on the same host. static ip: 150.158.1.2 (I have two nics in use, but this is the important one) virtual ip: 1.2.3.4 nic: eth0 versions: Debian Lenny 2.6.33.3 x86_64 corosync : 1.2.1-1 lib