On 27/06/2013, at 3:40 AM, andreas graeper wrote:
> thanks four your answer.
> but still question open.
>
> when i switch off the active node: though this is done reliable for me, the
> still passive node wants to know for sure and will kill the (already dead)
> former active node.
> i have
thanks four your answer.
but still question open.
when i switch off the active node: though this is done reliable for me, the
still passive node wants to know for sure and will kill the (already dead)
former active node.
i have no stonith-hardware (and i could not find till now stonith:null what
w
Am Mittwoch, 26. Juni 2013, 16:36:43 schrieb andreas graeper:
> hi and thanks.
> a primitive can be moved to another node. how can i move (change roles) of
> drbd:master to the other node ?
Switch off the other node.
> and will all the depending resources follow?
Depends on your constraints(ord
hi and thanks.
a primitive can be moved to another node. how can i move (change roles) of
drbd:master to the other node ? and will all the depending resources follow
?
then i can stop (and start again) corosync on passive node without problem
(my tiny experience).
another question: i found a locat
On 26/06/2013, at 12:24 AM, Digimer wrote:
> On 06/25/2013 07:29 AM, andreas graeper wrote:
>> hi,
>> maybe again and again the same question, please excuse.
>>
>> two nodes (n1 active / n2 passive) and `service corosync stop` on active.
>> does the node, that is going down, tells the other tha
(in addition)
n1 (former active/master node) is still stopped
n2 : corosync stop + start
now drbd is slave on n2 and nothing else starts
there is a location-constraint
Master, -INF uname __ne__ lisel1
i would interprete :
master must not start where ?node-nam
On 06/25/2013 07:29 AM, andreas graeper wrote:
> hi,
> maybe again and again the same question, please excuse.
>
> two nodes (n1 active / n2 passive) and `service corosync stop` on active.
> does the node, that is going down, tells the other that he has gone,
> before he actually disconnect ?
> so
hi,
maybe again and again the same question, please excuse.
two nodes (n1 active / n2 passive) and `service corosync stop` on active.
does the node, that is going down, tells the other that he has gone, before
he actually disconnect ?
so that there is no reason for n2 to kill n1 ?
on n2 after n1.
