Hello, all. 
I have been attempting to get a two-node cluster to work.  So far I have 
followed 6 tutorials and spent 4 days.
all I want right no is to get apache2 up and running.
I am configuring a two node-cluster but am just working on one, www1.
I cannot manage to get a virtual ip running as a resource.
Apache2 will not start.
I am on a virtual machine and using Ubuntu 8.04 with the latest Apache and 
updates.
Is the virtual ip supposed to be configured and started before configuring 
heartbeat?  I have tried both ways.  I have the 
impression that the ip is started and monitored by heartbeat.  Is it created by 
heartbeat by using haresources?
I have configured /etc/networks/interfaces with eth0:0.  It starts at boot-up.
 
haresources: 
    www1u IPaddr2::144.120.10.49
 
cib.xml :
 
  <?xml version="1.0" ?> 
- <cib admin_epoch="0" epoch="0" num_updates="0">
- <configuration>
- <crm_config>
- <cluster_property_set id="cib-bootstrap-options">
- <attributes>
  <nvpair id="cib-bootstrap-options-symmetric-cluster" name="symmetric-cluster" 
value="true" /> 
  <nvpair id="cib-bootstrap-options-no-quorum-policy" name="no-quorum-policy" 
value="stop" /> 
  <nvpair id="cib-bootstrap-options-default-resource-stickiness" 
name="default-resource-stickiness" value="0" /> 
  <nvpair id="cib-bootstrap-options-default-resource-failure-stickiness" 
name="default-resource-failure-stickiness" value="0" /> 
  <nvpair id="cib-bootstrap-options-stonith-enabled" name="stonith-enabled" 
value="false" /> 
  <nvpair id="cib-bootstrap-options-stonith-action" name="stonith-action" 
value="reboot" /> 
  <nvpair id="cib-bootstrap-options-startup-fencing" name="startup-fencing" 
value="true" /> 
  <nvpair id="cib-bootstrap-options-stop-orphan-resources" 
name="stop-orphan-resources" value="true" /> 
  <nvpair id="cib-bootstrap-options-stop-orphan-actions" 
name="stop-orphan-actions" value="true" /> 
  <nvpair id="cib-bootstrap-options-remove-after-stop" name="remove-after-stop" 
value="false" /> 
  <nvpair id="cib-bootstrap-options-short-resource-names" 
name="short-resource-names" value="true" /> 
  <nvpair id="cib-bootstrap-options-transition-idle-timeout" 
name="transition-idle-timeout" value="5min" /> 
  <nvpair id="cib-bootstrap-options-default-action-timeout" 
name="default-action-timeout" value="20s" /> 
  <nvpair id="cib-bootstrap-options-is-managed-default" 
name="is-managed-default" value="true" /> 
  <nvpair id="cib-bootstrap-options-cluster-delay" name="cluster-delay" 
value="60s" /> 
  <nvpair id="cib-bootstrap-options-pe-error-series-max" 
name="pe-error-series-max" value="-1" /> 
  <nvpair id="cib-bootstrap-options-pe-warn-series-max" 
name="pe-warn-series-max" value="-1" /> 
  <nvpair id="cib-bootstrap-options-pe-input-series-max" 
name="pe-input-series-max" value="-1" /> 
  </attributes>
  </cluster_property_set>
  </crm_config>
  <nodes /> 
- <resources>
- <primitive class="ocf" id="IPaddr2_1" provider="heartbeat" type="IPaddr2">
- <operations>
  <op id="IPaddr2_1_mon" interval="5s" name="monitor" timeout="5s" /> 
  </operations>
- <instance_attributes id="IPaddr2_1_inst_attr">
- <attributes>
  <nvpair id="IPaddr2_1_attr_0" name="ip" value="144.120.10.49" /> 
  </attributes>
  </instance_attributes>
  </primitive>
  </resources>
- <constraints>
- <rsc_location id="rsc_location_IPaddr2_1" rsc="IPaddr2_1">
- <rule id="prefered_location_IPaddr2_1" score="100">
  <expression attribute="#uname" id="prefered_location_IPaddr2_1_expr" 
operation="eq" value="www1u" /> 
  </rule>
  </rsc_location>
  </constraints>
  </configuration>
  <status /> 
  </cib>
Thanks for any help you care to give.  I'm exhausted :o)
Thanks
Larry
_______________________________________________
Linux-HA mailing list
[email protected]
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems

Reply via email to