Confused
I made your solution, but now i dont have Failover again.
location loc_drbd_on_connected_node ms_drbd_service \
rule $id="loc_drbd_on_connected_node-rule" pingd: defined pingd
But in my solution, the DRBD dont come up after reboot.
-----------------
My actual Config
node $id="3e20966a-ed64-4972-8f5a-88be0977f759" server1 \
attributes standby="off"
node $id="5262f929-1082-4a85-aa05-7bd1992f15be" server2 \
attributes standby="off"
primitive pri_FS_drbd_t3 ocf:heartbeat:Filesystem \
params device="/dev/drbd0" directory="/mnt/drbd_daten" fstype="ext3"
options="noatime"
primitive pri_IP_Cluster ocf:heartbeat:IPaddr2 \
params ip="192.168.1.253" cidr_netmask="24" nic="eth1" \
op monitor interval="3"
primitive pri_apache_Dienst ocf:heartbeat:apache \
op monitor interval="15" \
params configfile="/etc/apache2/apache2.conf" httpd="/usr/sbin/apache2"
port="80"
primitive pri_drbd_Dienst ocf:linbit:drbd \
params drbd_resource="t3" \
op monitor interval="15" \
op start interval="0" timeout="240" \
op stop interval="0" timeout="100"
primitive pri_pingd ocf:pacemaker:pingd \
params name="pingd" host_list="192.168.1.1 \ 192.168.4.10"
multiplier="100" \
op monitor interval="15s" timeout="20s"
group group_t3 pri_FS_drbd_t3 pri_IP_Cluster pri_apache_Dienst \
meta is-managed="true" target-role="Started"
ms ms_drbd_service pri_drbd_Dienst \
meta notify="true" target-role="Started"
clone clo_pingd pri_pingd \
meta globally-unique="false" interleave="true" target-role="Started"
location loc_drbd_on_connected_node ms_drbd_service \
rule $id="loc_drbd_on_connected_node-rule" pingd: defined pingd
colocation col_apache_after_drbd inf: group_t3 ms_drbd_service:Master
order ord_apache_after_drbd inf: ms_drbd_service:promote group_t3:start
property $id="cib-bootstrap-options" \
dc-version="1.0.8-2c98138c2f070fcb6ddeab1084154cffbf44ba75" \
cluster-infrastructure="Heartbeat" \
no-quorum-policy="ignore" \
default-resource-stickiness="100" \
last-lrm-refresh="1271410912" \
startup-fencing="false" \
stonith-enabled="false" \
default-action-timeout="120s"
-------- Original-Nachricht --------
> Datum: Thu, 15 Apr 2010 17:05:48 +0200
> Von: Michael Schwartzkopff <mi...@multinet.de>
> An: The Pacemaker cluster resource manager <pacemaker@oss.clusterlabs.org>
> Betreff: Re: [Pacemaker] Failover after fail on Ethernet Fails (Solved)
> Am Donnerstag, 15. April 2010 14:49:10 schrieb Stefan Kelemen:
> > I found the Issue.
> > As location i used the key resource ms_drbd_service. Why does i cant use
> > group or a Part of the group as key resource.
> >
> > location loc_Cluster_IP_on_pingd ms_drbd_service \
> > rule $id="loc_Cluster_IP_on_pingd-rule" -inf: not_defined pingd
> or
> > pingd number:lte 0
> >
> > Regards Stefan Kelemen
>
> Better:
>
> location loc_DRBD_on_connected_node ms_drbd_service \
> rule loc_DRBD_on_connected_node_rule pingd: defined pingd
>
> if fact, much better!
>
> --
> Dr. Michael Schwartzkopff
> MultiNET Services GmbH
> Addresse: Bretonischer Ring 7; 85630 Grasbrunn; Germany
> Tel: +49 - 89 - 45 69 11 0
> Fax: +49 - 89 - 45 69 11 21
> mob: +49 - 174 - 343 28 75
>
> mail: mi...@multinet.de
> web: www.multinet.de
>
> Sitz der Gesellschaft: 85630 Grasbrunn
> Registergericht: Amtsgericht München HRB 114375
> Geschäftsführer: Günter Jurgeneit, Hubert Martens
>
> ---
>
> PGP Fingerprint: F919 3919 FF12 ED5A 2801 DEA6 AA77 57A4 EDD8 979B
> Skype: misch42
>
> _______________________________________________
> 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
--
GRATIS für alle GMX-Mitglieder: Die maxdome Movie-FLAT!
Jetzt freischalten unter http://portal.gmx.net/de/go/maxdome01
_______________________________________________
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
