[ClusterLabs] resource was disabled automatically

cys chaoys155 at 163.com
Mon Mar 6 21:29:08 EST 2017


At 2017-03-07 05:47:19, "Ken Gaillot" <kgaillot at 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.


More information about the Users mailing list