[Pacemaker] after `corosync stop` on master, drbd:master moves to peer, but all other resource stopped

andreas graeper agraeper at googlemail.com
Tue Jul 9 02:46:47 EDT 2013


cant remember if at all and where i put that logs
next time ..
thanks


2013/7/9 Andrew Beekhof <andrew at beekhof.net>

>
> On 19/06/2013, at 3:03 AM, andreas graeper <agraeper at googlemail.com>
> wrote:
>
> > hi,
> > i stopped n1 (drbd:master + all managed resources)
> > the n2 became drbd:master but all resources stopped.
> >
> > i started n1.corosync again and stopped once more and than n2 took over
> everything as expected.
> >
> > in log i found lots of messages ~ signing into stonith-ng failed
> (similiar)
> > logs are saved, maybe i can send ?
>
> Yes. Not much we can do without them
>
>
> _______________________________________________
> Pacemaker mailing list: Pacemaker at oss.clusterlabs.org
> http://oss.clusterlabs.org/mailman/listinfo/pacemaker
>
> Project Home: http://www.clusterlabs.org
> Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
> Bugs: http://bugs.clusterlabs.org
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.clusterlabs.org/pipermail/pacemaker/attachments/20130709/3d1bb204/attachment-0003.html>


More information about the Pacemaker mailing list