>>> Greg Woods <wo...@ucar.edu> schrieb am 22.04.2013 um 17:50 in Nachricht <1366645842.4475.4.ca...@mongoliad.scd.ucar.edu>: > On Mon, 2013-04-22 at 10:12 +1000, Andrew Beekhof wrote: > > On Saturday, April 20, 2013, Greg Woods wrote: > > Often one of the > > > nodes gets stuck at "Stopping HA Services" > > > > > > That means pacemaker is waiting for one of your resources to stop. > > Do you have anything that would take a long time (or fail to stop)? > > Not that I am aware of. But some things that came up during this > weekend's powerdown make me think that some of the stop actions are > failing, because setting the stop-all-resources=true property sometimes > caused nodes to be fenced.
Maybe try to grep for a string like "will be fenced" to get a starting point. Then go back in the logs to find out why. Occasionally things fail when executed in parallel, while they work fine when executed sequentially. > > I always dread having to try and find useful information in the > voluminous Pacemaker/Heartbeat logs, but I'll have to try. Of course, > this doesn't happen on the test clusters, and it is hard to debug it > when reproducing it requires creating a service outage on a production > cluster. Usually the incremental approach works: Isolate the problem, try to fix it, then retry. Don't try to fix too much with one change. Regards, Ulrich _______________________________________________ Linux-HA mailing list Linux-HA@lists.linux-ha.org http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems