On Wed, Feb 17, 2010 at 9:03 AM, Alexandr Krylovskiy <w...@tversu.ru> wrote: > On Tue, 16 Feb 2010 21:33:06 +0100 > Andrew Beekhof <and...@beekhof.net> wrote: > >> On Mon, Feb 15, 2010 at 9:45 AM, Alexandr Krylovskiy <w...@tversu.ru> wrote: >> > On Fri, 12 Feb 2010 12:50:45 +0300 >> > 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)? >> >> 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 >> >> \_ /usr/lib/heartbeat/cib >> >> \_ /usr/lib/heartbeat/lrmd >> >> \_ /usr/lib/heartbeat/attrd >> >> \_ /usr/lib/heartbeat/pengine >> >> \_ /usr/lib/heartbeat/crmd >> >> >> > >> > It seems like changing corosync init script start levels resolved my issue. >> > Startup links was: >> > /etc/rc0.d/K07corosync >> > /etc/rc1.d/K07corosync >> > /etc/rc6.d/K07corosync >> > /etc/rcS.d/S59corosync >> > >> > I changed this with: >> > # update-rc.d corosync start 90 S . stop 07 0 1 6 . >> > Adding system startup for /etc/init.d/corosync ... >> > /etc/rc0.d/K07corosync -> ../init.d/corosync >> > /etc/rc1.d/K07corosync -> ../init.d/corosync >> > /etc/rc6.d/K07corosync -> ../init.d/corosync >> > /etc/rcS.d/S90corosync -> ../init.d/corosync >> > >> > And it works on both nodes. >> > Is this a package bug or my setup specific? I can give more details of my >> > setup if needed. >> >> Debian by any chance? What arch? >> > > Debian Lenny 5.04 2.6.26-2-openvz-686 > Pacemaker and all the other stuff from madkiss repo
Why is it always debian :-( Is this an image that you could upload somewhere? (I could learn debian and create one myself, but that would probably take much longer ;-) _______________________________________________ Pacemaker mailing list Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker
