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
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' and 'with-rsc-role'.
Yet when I use them it get smacked
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 configured as Master/Slave and sofar it is fine
On: Thu, 10 Feb 2011 08:51:01 +0100, Andrew Beekhof wrote:
On Wed, Feb 9, 2011 at 2:48 PM, Stephan-Frank Henry frank.he...@gmx.net
wrote:
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
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 everything 'returns to normal
On: Thu, 10 Feb 2011 09:25:22 +0100, Andrew Beekhof wrote:
On Thu, Feb 10, 2011 at 9:09 AM, Stephan-Frank Henry
frank.he...@gmx.net wrote:
You forgot
0) Configure stonith
If data is being written to both sides, one of the sets is always
going to be lost.
Agreed and acceptable
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
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, when I do a /etc/init.d/corosync stop, while
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
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
Original-Nachricht
Datum: Thu, 21 Oct 2010 18:46:32 +0200
Von: Stephan-Frank Henry Frank dot Henry at gmx dot net
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
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 completely?
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
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
Original-Nachricht
Datum: Thu, 02 Sep 2010 19:08:00 +0200
Von: Stephan-Frank Henry Frank dot Henry at gmx dot net
An: The Pacemaker cluster resource manager pacemaker@oss.clusterlabs.org
Betreff: Re: [Pacemaker] Setting up routing for a virtual ip
Original
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
Original-Nachricht
Datum: Thu, 02 Sep 2010 11:40:13 +0200
Von: Stephan-Frank Henry Frank dot Henry at gmx dot net
An: pacemaker@oss.clusterlabs.org
Betreff: [Pacemaker] Setting up routing for a virtual ip
Hello everyone,
I am currently stuck trying to set up routing
17 matches
Mail list logo
