-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 11/29/2012 10:14 PM, Robinson, Eric wrote:
> Bump... does anyone have some insight on this? Google is not
> turning up anything useful.
>
> Our newest cluster will not failover master/slave drbd resources.
> It works fine manually using drbdadm from a shell prompt, but when
> we try it using 'crm node standby' and letting the cluster manage
> the resource, crm_mon just keeps saying the resource FAILED.
>
> We see a lot of these messages in the corosync.log file:
>
> drbd(p_drbd1)[12814]: 2012/11/27_15:31:59 DEBUG: ha02_mysql:
> Calling drbdadm -c /etc/drbd.conf primary ha02_mysql
> drbd(p_drbd1)[12814]: 2012/11/27_15:31:59 ERROR: ha02_mysql:
> Called drbdadm -c /etc/drbd.conf primary ha02_mysql
> drbd(p_drbd1)[12814]: 2012/11/27_15:31:59 ERROR: ha02_mysql: Exit
> code 11
>
> There is no indication of what may be causing the 'Exit code 11'
>
> Here is a link to the corosync log, taken from the standby server
> (ha09a) where we are trying to fail the resource to...
>
> www.psmnv.com/downloads/corosync1.log<http://www.psmnv.com/downloads/corosync1.log>
>
> Here is what I have installed...
>
> corosync-1.4.1-7.el6_3.1.x86_64 corosynclib-1.4.1-7.el6_3.1.x86_64
> pacemaker-1.1.8-4.el6.x86_64 pacemaker-cli-1.1.8-4.el6.x86_64
> pacemaker-cluster-libs-1.1.8-4.el6.x86_64
> pacemaker-libs-1.1.8-4.el6.x86_64
>
> Following is my crm config. It's pretty basic.
>
>
> node ha09a \ attributes standby="off" node ha09b \ attributes
> standby="off" primitive p_drbd0 ocf:linbit:drbd \ params
> drbd_resource="ha01_mysql" \ op monitor interval="60s" primitive
> p_drbd1 ocf:linbit:drbd \ params drbd_resource="ha02_mysql" \ op
> monitor interval="45s" primitive p_vip_clust08
> ocf:heartbeat:IPaddr2 \ params ip="192.168.10.210"
> cidr_netmask="32" \ op monitor interval="30s" primitive
> p_vip_clust09 ocf:heartbeat:IPaddr2 \ params ip="192.168.10.211"
> cidr_netmask="32" \ op monitor interval="30s" ms ms_drbd0 p_drbd0
> \ meta master-max="1" master-node-max="1" clone-max="2"
> clone-node-max="1" notify="true" target-role="Master" ms ms_drbd1
> p_drbd1 \ meta master-max="1" master-node-max="1" clone-max="2"
> clone-node-max="1" notify="true" target-role="Master" property
> $id="cib-bootstrap-options" \ dc-version="1.1.8-4.el6-394e906" \
> cluster-infrastructure="openais" \ expected-quorum-votes="2" \
> stonith-enabled="false" \ no-quorum-policy="ignore" \
> last-lrm-refresh="1352846885" rsc_defaults $id="rsc-options" \
> resource-stickiness="100"
I am not sure if that will really help you - but in my cluster (ok
older pacemaker version) I ahve the following to define a master slave
resource:
primitive rsc_sap_HA0_ASCS00 ocf:heartbeat:SAPInstance \
operations $id="rsc_sap_HA0_ASCS00-operations" \
op monitor interval="11" role="Slave" timeout="60" \
op monitor interval="13" role="Master" timeout="60" \
params \
InstanceName="HA0_ASCS00_sapha0as" \
START_PROFILE="/usr/sap/HA0/SYS/profile/HA0_ASCS00_sapha0as" \
ERS_InstanceName="HA0_ERS10_sapha0er"
ERS_START_PROFILE="/usr/sap/HA0/SYS/profile/HA0_ERS10_sapha0er"
ms msl_sap_enqrepl_HA0 rsc_sap_HA0_ASCS00 \
meta clone-max="2" target-role="Started" master-max="1" \
is-managed="true"
So I have a defined operation role="Master" on the primitive but NOT a
targe-role="Master" on the Master/Slave.
Additionally I have a colocation constraint between primitives/group
which must run together with the promoted clone:
colocation col_grp_sap_as_HAO_msl_sap_enqrepl_HA0_MASTER inf: \
grp_sap_as_HA0 msl_sap_enqrepl_HA0:Master
Sorry - I did not have checked, if the syntax has changed here, or if
your syntax where valid also in the past - so it might be that my hint
is completely useless ;-) I just wanted to point on a thing where your
config is completely different to my config.
Hopefully ma hint helps...
Fabian
>
> -- Eric Robinson
>
>
>
> Disclaimer - November 29, 2012 This email and any files transmitted
> with it are confidential and intended solely for General Linux-HA
> mailing list. If you are not the named addressee you should not
> disseminate, distribute, copy or alter this email. Any views or
> opinions presented in this email are solely those of the author and
> might not represent those of Physicians' Managed Care or Physician
> Select Management. Warning: Although Physicians' Managed Care or
> Physician Select Management has taken reasonable precautions to
> ensure no viruses are present in this email, the company cannot
> accept responsibility for any loss or damage arising from the use
> of this email or attachments. This disclaimer was added by Policy
> Patrol: http://www.policypatrol.com/
> _______________________________________________ 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
>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.19 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://www.enigmail.net/
iQEcBAEBAgAGBQJQvlFOAAoJEJ1uHhrzMvZRcj8IAIrNf4T4dFvzblLnkHSSUHvN
KdWYPdXBIiIqLSTbHqb4kwQMQa0e4P+pZti+sqlHJe5muE1lbgeM9cSZsiMGdXJU
1wjaN3A6uy/o+WkUV505CSGN7X+2WmoKaY2PxQKVR8AU5cy4egQziuMq8+d3tI8+
kkONSlJajGxi7Cw2NKaAsZkcXNk7nsLqc0SlCRk9PQaUrGR8/Lxxvuy9dX9gS2I7
94+F2MLz09sxqgEjeUh47WOLY4qmklxAeEXV/Qi6NBO8Z/oVzJhAMD3molHgy1By
sPClKWD7PhnAyc+rnCnsfnjDq1VemAUbkpTyw+B5//uDODIdFTEZcKnrguiC0Mg=
=+Nr6
-----END PGP SIGNATURE-----
_______________________________________________
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
