Hello Andrei, thanks for this hint, but I need this "special" order. In an other setup it works.
best regards Stefan > Gesendet: Freitag, 22. Juni 2018 um 06:57 Uhr > Von: "Andrei Borzenkov" <[email protected]> > An: [email protected] > Betreff: Re: [ClusterLabs] corosync doesn't start any resource > > 21.06.2018 16:04, Stefan Krueger пишет: > > Hi Ken, > > > >> Can you attach the pe-input file listed just above here? > > done ;) > > > > And thank you for your patience! > > > > You delete all context which makes it hard to answer. This is not web > forum where users can simply scroll up to see previous reply. > > Both your logs and pe-input show that nfs-server and vm-storage wait for > each other. > > My best guess is that you have incorrect ordering for start and stop > which causes loop in pacemaker decision. Your start order is "nfs-server > vm-storage" and your stop order is "nfs-server vm-storage", while it > should normally be symmetrical. Reversing order in one of sets makes it > work as intended (verified). > > I would actually expect that asymmetrical configuration still should > work, so I leave it to pacemaker developers to comment whether this is a > bug or feature :) > > _______________________________________________ > Users mailing list: [email protected] > https://lists.clusterlabs.org/mailman/listinfo/users > > Project Home: http://www.clusterlabs.org > Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf > Bugs: http://bugs.clusterlabs.org > _______________________________________________ Users mailing list: [email protected] https://lists.clusterlabs.org/mailman/listinfo/users Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org
