On 03/06/2017 08:29 PM, cys wrote: > At 2017-03-07 05:47:19, "Ken Gaillot" <kgail...@redhat.com> wrote: >> To figure out why a resource was stopped, you want to check the logs on >> the DC (which will be the node with the most "pengine:" messages around >> that time). When the PE decides a resource needs to be stopped, you'll >> see a message like >> >> notice: LogActions: Stop <resource-name> (<node-name>) >> >> Often, by looking at the messages before that, you can see what led it >> to decide that. Shortly after that, you'll see something like >> > > Thanks Ken. It's really helpful. > Finally I found the debug log of pengine(in a separate file). It has this > message: > "All nodes for resource p_vs-scheduler are unavailable, unclean or shutting > down..." > So it seems this caused vs-scheduler disabled. > > If all nodes come back to be in good state, will pengine start the resource > automatically? > I did it manually yesterday.
Yes, whenever a node changes state (such as becoming available), the pengine will recheck what can be done. _______________________________________________ Users mailing list: Users@clusterlabs.org http://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
