On 2013-09-03T21:14:02, Vladislav Bogdanov <[email protected]> wrote:
> > To solve problem 2, simply disable corosync/pacemaker from starting on > > boot. This way, the fenced node will be (hopefully) back up and running, > > so you can ssh into it and look at what happened. It won't try to rejoin > > the cluster though, so no risk of a fence loop. > Enhancement to this would be enabling corosync/pacemaker back during the > clean shutdown and disabling it after boot. There's something in "sbd" which does this. See https://github.com/l-mb/sbd/blob/master/man/sbd.8.pod and the -S option. I'm contemplating how do to this in a generic fashion. Regards, Lars -- Architect Storage/HA SUSE LINUX Products GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 21284 (AG Nürnberg) "Experience is the name everyone gives to their mistakes." -- Oscar Wilde _______________________________________________ Linux-HA mailing list [email protected] http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
