Andrew Beekhof schrieb:
> yep.
> thats a very strange place to crash.
> can you try printing the values of lpc and *node please?
Sorry, no idea how to do that
> but generally speaking, the config doesn't make sense.
> symmetrical was a short-term hack that wont do what you think it will.
>
>
On Tue, May 19, 2009 at 2:45 PM, Steinhauer Juergen wrote:
> Hi!
>
> I hope that's what you meant with stack trace:
yep.
thats a very strange place to crash.
can you try printing the values of lpc and *node please?
but generally speaking, the config doesn't make sense.
symmetrical was a short-te
Hi!
I hope that's what you meant with stack trace:
(gdb) bt
#0 0x00a3f70b in pe_find_node_id (nodes=0x82cad00,
id=0x82c7418 "04057199-76a0-4fe6-8963-c3fe931b0dfe") at status.c:294
#1 0x00a656bd in node_list_update (list1=0x82c25b0, list2=0x82cad00,
factor=1)
at native.c:704
#2 0x00a6
On Tue, May 19, 2009 at 1:11 PM, Steinhauer Juergen wrote:
> Hi guys!
>
> I'm running heartbeat 2.1.3 with pacemaker 0.6.
> I have a resource "ip" and two resources "app1, app2", depending on "ip".
> I want to achieve, that switching "app1" or "app2" to the other node,
> also moves the "ip" and th
Hi guys!
I'm running heartbeat 2.1.3 with pacemaker 0.6.
I have a resource "ip" and two resources "app1, app2", depending on "ip".
I want to achieve, that switching "app1" or "app2" to the other node,
also moves the "ip" and the other app to this node.
As soon as I configure two colocations like
On Tue, May 19, 2009 at 11:54:01AM +0200, Andrew Beekhof wrote:
> Ah, you have a point there, its a while since I've read it :-)
>
> Its basically the amount of time the node will wait for an orderly
> shutdown to occur before simply terminating itself (the process not
> the node).
> This can happ
Ah, you have a point there, its a while since I've read it :-)
Its basically the amount of time the node will wait for an orderly
shutdown to occur before simply terminating itself (the process not
the node).
This can happen if there is a bug in the cluster software, or more
likely, a resource tha
Am Dienstag, 19. Mai 2009 09:58:26 schrieb Andrew Beekhof:
> On Mon, May 18, 2009 at 10:18 PM, Michael Schwartzkopff
>
> wrote:
> > Hi,
> >
> > is there any documentation for the shutdown_escalation timeout? What is
> > it exactly?
> >
> > Thanks.
>
> /usr/lib/heartbeat/crmd metadata is your frie
/usr/lib/heartbeat/crmd metadata is your friend in this instance
On Mon, May 18, 2009 at 10:18 PM, Michael Schwartzkopff
wrote:
> Hi,
>
> is there any documentation for the shutdown_escalation timeout? What is it
> exactly?
>
> Thanks.
> --
> Dr. Michael Schwartzkopff
> MultiNET Services GmbH
> A
