On Fri, Oct 08, 2010 at 06:38:26PM +0200, Dejan Muhamedagic wrote: > Hi, > > On Fri, Oct 08, 2010 at 03:35:13PM +0200, Nikita Michalko wrote: > > Hi all! > > > > My very simple 2 nodes test cluster with Pacemaker&Heartbeat make me some > > headaches. Here are my versions: > > > > cluster-glue: 1.0.6 > > resource-agents: 1.0.3 > > Heartbeat STABLE: 3.0.3 > > pacemaker: 1.1.3 (all from wiki sources) > > OS: SLES11/SP1 > > After succesfully starting Heartbeat on the first node "opter" > > (the other node was for test not up- dead) with stonith > > disabled (see my configuration below) did the first node > > reboot. Why on my own node? Do I need stonith on symmetric > > cluster? > > Yes. > > > HB_Report attached ... > > stonith-ng failed to connect to the cluster: > > Oct 08 13:03:27 opteron heartbeat: [10872]: WARN: Client [stonith-ng] pid > 10898 failed authorization [no default client auth] > Oct 08 13:03:27 opteron heartbeat: [10872]: ERROR: > api_process_registration_msg: cannot add client(stonith-ng) > ... > Oct 08 13:03:27 opteron stonith-ng: [10898]: CRIT: main: Cannot sign in to > the cluster... terminating > > which made heartbeat reboot. I guess that you can add sth like > this to ha.cf: > > apiauth stonith-ng uid=root > > If you want to prevent reboots, use "crm respawn".
see also http://hg.linux-ha.org/dev/rev/9624b66a6b82 will be released with heartbeat 3.0.4 -- : Lars Ellenberg : LINBIT | Your Way to High Availability : DRBD/HA support and consulting http://www.linbit.com DRBD® and LINBIT® are registered trademarks of LINBIT, Austria. _______________________________________________ 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
