On Thu, May 28, 2009 at 01:25:41PM +0200, Sebastian Kösters wrote:
> Hi,
>
> i installed to Servers with Heartbeat (2.1.3-3.el5) and drbd (8.3.1).
>
> my HA config:
>
> node weisswasser.v121.dus1.th bayreuth.v121.dus1.th
>
> ucast bond0.121 10.10.121.135
> ucast bond0.121 10.10.121.136
>
> auto_failback off
>
> debugfile /var/log/ha-debug
> logfile /var/log/ha-log
>
> keepalive 2
> warntime 10
> deadtime 30
> initdead 120
>
>
> my haresources:
>
> weisswasser.v121.dus1.th drbddisk::drbd0
> Filesystem::/dev/drbd0::/weisswasser::ext3
> bayreuth.v121.dus1.th drbddisk::drbd1 Filesystem::/dev/drbd1::/bayreuth::ext3
>
> my drbd config:
>
> resource drbd0 {
> protocol C;
>
> startup {
> become-primary-on weisswasser.v121.dus1.th;
outch.
do not do that.
either you want _heartbeat_ to decide what resource is started where,
or you want the drbd init script to do that for you.
not both.
just delete that "become-primary-on" line from your drbd config.
then learn about hb_takeover resp. hb_standby
(it even takes an argument: "local", "foreign" and "all").
or forget about haresources style heartbeat and go for CRM.
but do not have init activate something,
and then tell the cluster manager it was responsible.
that simply won't work.
--
: 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
