[Pacemaker] corosync stop and consequences

[andreas graeper]

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.corosync.stop :

drbd:promote OK
lvm:start OK
filesystem:start OK
but ipaddr2 still stopped ?

n1::drbd:demote works ?! so i would expect that all that depending resource
should have been
stopped successfully ?!
and if not, why ? why should ipaddr2:stop fail
and if it would fail, can filesystem:stop , lvm:stop , drbd:demote succeed
?

how can i find some hint in logs why ipaddr fails to start ?

thanks
andreas
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.clusterlabs.org/pipermail/pacemaker/attachments/20130625/f95cca97/attachment-0002.html>