03.09.2013 21:36, Lars Marowsky-Bree wrote: > On 2013-09-03T21:14:02, Vladislav Bogdanov <bub...@hoster-ok.com> 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.
Yes, but I thought it is a no-go with just drbd replicated disks (usual case for 2-node clusters). > I'm contemplating how do to this in a generic fashion. It is quite straight-forward with SysVinit and its emulation with upstart, but could be tricky with native upstart and systemd. Need to investigate... _______________________________________________ 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
