Hi there,
meanwhile I managed getting a logfile by a simple reboot of both nodes.
The real problem I have is that Heartbeat doesn't start a configured
Filesystem resource. The logfile entry is rather cryptic and doesn't
help me understand the problem. Here ist my cib.xml.
<cib generated="true" admin_epoch="0" have_quorum="true"
ignore_dtd="false" num_peers="2" cib_feature_revision="2.0"
num_updates="1" epoch="77" cib-last-written="Mon Aug 25 12:23:21 2008"
ccm_transition="2" dc_uuid="57800321-0f0f-4a7e-98c6-5e14042ff55a">
<configuration>
<crm_config>
<cluster_property_set id="cib-bootstrap-options">
<attributes>
<nvpair id="cib-bootstrap-options-dc-version"
name="dc-version" value="2.1.3-node:
552305612591183b1628baa5bc6e903e0f1e26a3"/>
<nvpair name="last-lrm-refresh"
id="cib-bootstrap-options-last-lrm-refresh" value="1219658546"/>
</attributes>
</cluster_property_set>
</crm_config>
<nodes>
<node uname="viktor-02" type="normal"
id="57800321-0f0f-4a7e-98c6-5e14042ff55a">
<instance_attributes id="nodes-57800321-0f0f-4a7e-98c6-5e14042ff55a">
<attributes>
<nvpair name="standby"
id="standby-57800321-0f0f-4a7e-98c6-5e14042ff55a" value="off"/>
</attributes>
</instance_attributes>
</node>
<node id="6e108c00-7e90-4bef-88ec-1458243b97b5"
uname="viktor-01" type="normal"/>
</nodes>
<resources>
<master_slave id="ms_drbd_ip">
<meta_attributes id="fec72675-f56b-421b-87a8-3c3c1cf489ff">
<attributes>
<nvpair name="notify" value="yes"
id="7b79ad84-80ae-4a5a-8a8e-3ae373b23899"/>
</attributes>
</meta_attributes>
<primitive id="drbd" class="ocf" provider="heartbeat" type="drbd">
<instance_attributes id="83ef4a5b-1c95-4c6c-9888-34be084d9bae">
<attributes>
<nvpair name="drbd_resource" value="r0"
id="693f86ee-084b-4a15-b4f1-8f23755ceb35"/>
</attributes>
</instance_attributes>
<operations>
<op name="monitor" interval="29s" timeout="10s"
role="Master" id="1c08b33e-53cb-480b-ad5e-46948065d922"
start_delay="0" disabled="false"/>
<op name="monitor" interval="30s" timeout="10s"
role="Slave" id="efd555d5-2f11-4744-a43d-55902dd6d5a4" start_delay="0"
disabled="false"/>
</operations>
<instance_attributes id="b9aeaaf4-5303-4850-815a-2c9f1ebf708b">
<attributes>
<nvpair name="drbd_resource" value="r0"
id="09654301-543d-499d-8acc-d9faee758c22"/>
</attributes>
</instance_attributes>
</primitive>
<meta_attributes id="ab72fc54-5fd6-47c3-b82a-d49d8bedc2c5">
<attributes>
<nvpair name="notify" value="yes"
id="71e8d177-9257-4039-9405-cf2d4e19b181"/>
</attributes>
</meta_attributes>
</master_slave>
<group id="rg_ip_fs">
<primitive class="ocf" type="IPaddr2" provider="heartbeat"
id="ip_common">
<instance_attributes id="58d0fb5b-186d-4408-97aa-20c2dd129bd0">
<attributes>
<nvpair name="ip" value="212.66.145.22"
id="85a68a28-fe8f-4722-a136-1210c34f75d8"/>
<nvpair name="nic" value="eth0"
id="e2be8f61-583c-48a5-bbe4-79f46a8bf7c0"/>
</attributes>
</instance_attributes>
<instance_attributes id="14bdaa30-27b2-4983-a949-c04cc70213b8">
<attributes>
<nvpair name="ip" value="212.66.145.22"
id="a50b4af0-5cd6-454b-8ded-4e2a0da96dc0"/>
<nvpair name="nic" value="eth0"
id="6d4ff239-09a6-4d68-ac25-95fef42e951e"/>
</attributes>
</instance_attributes>
<meta_attributes id="ip_common_meta_attrs">
<attributes>
<nvpair id="ip_common_metaattr_target_role"
name="target_role" value="started"/>
</attributes>
</meta_attributes>
</primitive>
<meta_attributes id="rg_ip_fs_meta_attrs">
<attributes/>
</meta_attributes>
<primitive id="fs_mount" class="ocf" type="Filesystem"
provider="heartbeat"> <!-- this one does not start! -->
<instance_attributes id="fs_mount_instance_attrs">
<attributes>
<nvpair name="fstype" value="ext3"
id="d3e224b6-6573-47b9-8dfa-44f6e"/>
<nvpair name="device" value="/dev/drbd0"
id="d3e224b6-6573-47b9-8dfa-44f6e09b3b"/>
<nvpair name="directory" value="/mnt/drbd0"
id="d3e224b6-6573-47b9-8dfa-44f6e09b3cb"/>
</attributes>
</instance_attributes>
<meta_attributes id="fs_mount_meta_attrs">
<attributes>
<nvpair id="fs_mount_metaattr_target_role"
name="target_role" value="started"/>
</attributes>
</meta_attributes>
</primitive>
</group>
</resources>
<constraints>
<rsc_order id="ip_fs_after_drbd" from="rg_ip_fs" action="start"
to="ms_drbd_ip" to_action="promote" type="after"/>
<rsc_colocation id="ip_fs_on_drbd" to="ms_drbd_ip"
to_role="master" from="rg_ip_fs" score="INFINITY"/>
</constraints>
</configuration>
</cib>
This is the corresponding error message in ha-log when I try to start
it via GUI:
mgmtd[2994]: 2008/08/25_13:44:51 ERROR: unpack_rsc_op: Remapping
fs_mount_start_0 (rc=2) on viktor-02 to an ERROR
mgmtd[2994]: 2008/08/25_13:44:51 ERROR: unpack_rsc_op: Remapping
fs_mount_start_0 (rc=2) on viktor-01 to an ERROR
ha-debug says:
mgmtd[2994]: 2008/08/25_13:59:22 info: (delete)xml:<nvpair
id="fs_mount_instattr_target_role">
mgmtd[2994]: 2008/08/25_13:59:23 info: on_set_target_role:<group
id="rg_ip_fs"><primitive id="fs_mount"><meta_attributes
id="fs_mount_meta_attrs"><attributes><nvpair
id="fs_mount_metaattr_target_role" name="target_role"
value="started"/></attributes></meta_attributes></primitive></group>
mgmtd[2994]: 2008/08/25_13:59:25 ERROR: unpack_rsc_op: Remapping
fs_mount_start_0 (rc=2) on viktor-02 to an ERROR
mgmtd[2994]: 2008/08/25_13:59:25 ERROR: unpack_rsc_op: Remapping
fs_mount_start_0 (rc=2) on viktor-01 to an ERROR
Thanks for your help.
Christoph
_______________________________________________
Linux-HA mailing list
[email protected]
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems
