26.11.2014 18:36, David Vossel wrote: > > > ----- Original Message ----- >> 25.11.2014 23:41, David Vossel wrote: >>> >>> >>> ----- Original Message ----- >>>> Hi! >>>> >>>> is subj implemented? >>>> >>>> Trying echo c > /proc/sysrq-trigger on remote nodes and no fencing occurs. >>> >>> Yes, fencing remote-nodes works. Are you certain your fencing devices can >>> handle >>> fencing the remote-node? Fencing a remote-node requires a cluster node to >>> invoke the agent that actually performs the fencing action on the >>> remote-node. >> >> Yes, if I invoke fencing action manually ('crm node fence <rnode>' in >> crmsh syntax), node is fenced. So the issue seems to be related to the >> detection of a "need fencing". >> >> Comments in related git commits are a little bit terse in this area. So >> could you please explain what exactly needs to happen on a remote node >> to initiate fencing? >> >> I tried so far: >> * kill pacemaker_remoted when no resources are running. systemd restated >> it and crmd reconnected after some time. >> * crash kernel when no resources are running >> * crash kernel during massive start of resources > > this last one should definitely cause fencing. What version of pacemaker are > you using? I've made changes in this area recently. Can you provide a > crm_report.
It's c191bf3. crm_report is ready, but I still wait an approval from a customer to send it. > > -- David > >> >> No fencing happened. In the last case that start actions 'hung' and were >> failed by timeout (it is rather long), node was not even listed as >> failed. My customer asked me to stop crashing nodes because one of them >> does not boot anymore (I "like" that modern UEFI hardware very much.), >> so it is hard for me to play more with that. >> >> Best, >> Vladislav >> >> >>> >>> -- Vossel >>> >>>> >>>> Best, >>>> Vladislav >>>> >>>> _______________________________________________ >>>> Pacemaker mailing list: Pacemaker@oss.clusterlabs.org >>>> http://oss.clusterlabs.org/mailman/listinfo/pacemaker >>>> >>>> Project Home: http://www.clusterlabs.org >>>> Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf >>>> Bugs: http://bugs.clusterlabs.org >>>> >>> >>> _______________________________________________ >>> Pacemaker mailing list: Pacemaker@oss.clusterlabs.org >>> http://oss.clusterlabs.org/mailman/listinfo/pacemaker >>> >>> Project Home: http://www.clusterlabs.org >>> Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf >>> Bugs: http://bugs.clusterlabs.org >>> >> >> >> _______________________________________________ >> Pacemaker mailing list: Pacemaker@oss.clusterlabs.org >> http://oss.clusterlabs.org/mailman/listinfo/pacemaker >> >> Project Home: http://www.clusterlabs.org >> Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf >> Bugs: http://bugs.clusterlabs.org >> > > _______________________________________________ > Pacemaker mailing list: Pacemaker@oss.clusterlabs.org > http://oss.clusterlabs.org/mailman/listinfo/pacemaker > > Project Home: http://www.clusterlabs.org > Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf > Bugs: http://bugs.clusterlabs.org > _______________________________________________ Pacemaker mailing list: Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org