On Fri, Feb 12, 2010 at 10:50 AM, Alexandr Krylovskiy <w...@tversu.ru> wrote: > On Thu, 11 Feb 2010 12:00:55 +0100 > Andrew Beekhof <and...@beekhof.net> wrote: > >> On Thu, Feb 11, 2010 at 11:58 AM, Alexandr Krylovskiy <w...@tversu.ru> wrote: >> > I have two-nodes cluster with openAIS and Pacemaker. After rebooting one >> > of >> > the nodes, on the another one I'm getting: >> > >> > ERROR: te_connect_stonith: Sign-in failed: triggered a retry >> > crmd: [2451]: info: te_connect_stonith: Attempting connection to fencing >> > daemon... crmd: [2451]: ERROR: stonithd_signon: Can't initiate connection >> > to stonithd >> >> we connect to the stonith daemon even if we never use it >> > So, /usr/lib/heartbeat/stonithd should be started at the boot time (invoked by > corosync)?
yes > Then, I think, there are some problems with pacemaker initialization in Debian > (latest packages from madkiss repo). > After boot time the corosync process tree is: > /usr/sbin/corosync > \_ /usr/sbin/corosync I imagine this is supposed to be the stonithd process. > \_ /usr/lib/heartbeat/cib > \_ /usr/lib/heartbeat/lrmd > \_ /usr/lib/heartbeat/attrd > \_ /usr/lib/heartbeat/pengine > \_ /usr/lib/heartbeat/crmd > > -- > Alexandr Krylovskiy > > _______________________________________________ > Pacemaker mailing list > Pacemaker@oss.clusterlabs.org > http://oss.clusterlabs.org/mailman/listinfo/pacemaker > _______________________________________________ Pacemaker mailing list Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker
