Hello list,
I have following configuration (2 node cluster, pacemaker 1.0.3,
heartbeat 2.99.2). Logfiles are available upon request. Final cib.xml
is attached.
$ ip addr sh
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue state UNKNOWN
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
inet 192.168.178.100/0 scope global lo:0
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast
state UP qlen 1000
link/ether 00:0c:29:e4:00:7b brd ff:ff:ff:ff:ff:ff
inet 192.168.160.101/24 brd 192.168.160.255 scope global eth0
inet6 fe80::20c:29ff:fee4:7b/64 scope link
valid_lft forever preferred_lft forever
3: eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast
state UP qlen 1000
link/ether 00:0c:29:e4:00:85 brd ff:ff:ff:ff:ff:ff
inet 192.168.178.101/24 brd 192.168.178.255 scope global eth1
inet6 fe80::20c:29ff:fee4:85/64 scope link
valid_lft forever preferred_lft forever
My haresources looks like:
orad01 ldirectord::ldirectord.cf LVSSyncDaemonSwap::master
IPaddr::192.168.178.100/32/eth1 #group_LVS
My ha.cf looks like:
keepalive 2
deadtime 15
warntime 5
initdead 30
mcast eth1 225.0.0.1 694 1 0
auto_failback off
node orad01
node orad02
ping 192.168.178.1
use_logd yes
conn_logd_time 60
compression zlib
compression_threshold 2
coredumps true
crm respawn
I convert the V1 to 0.6
$ /usr/lib/heartbeat/haresources2cib.py --stdout -c ha.cf haresources
> cib.xml.initial
$ crm_verify -VVV -x cib.xml.initial
crm_verify[10794]: 2009/07/03_16:04:43 info: main: =#=#=#=#= Getting
XML =#=#=#=#=
crm_verify[10794]: 2009/07/03_16:04:43 notice: update_validation: Upgrading
pacemaker-0.6-style configuration to transitional-0.6 with
/usr/share/pacemaker/upgrade06.xsl
crm_verify[10794]: 2009/07/03_16:04:43 info: update_validation: Transformation
/usr/share/pacemaker/upgrade06.xsl successful
crm_verify[10794]: 2009/07/03_16:04:43 notice: update_validation:
Upgraded from <none> to
pacemaker-1.0 validation
crm_verify[10794]: 2009/07/03_16:04:43 WARN: cli_config_update: Your
configuration was
internally updated to the latest version (pacemaker-1.0)
crm_verify[10794]: 2009/07/03_16:04:43 WARN: cluster_status: We do not
have quorum -
fencing and resource management disabled
Warnings found during check: config may not be valid
I convert V0.6 to Pacemaker 1
$ xsltproc /usr/share/pacemaker/upgrade06.xsl cib.xml.initial >
cib-pm.xml.initial
$ crm_verify -VVV -x cib-pm.xml.initial
crm_verify[10802]: 2009/07/03_16:06:19 info: main: =#=#=#=#= Getting
XML =#=#=#=#=
crm_verify[10802]: 2009/07/03_16:06:19 WARN: cluster_status: We do not
have quorum -
fencing and resource management disabled
orad01:/etc/ha.d# cp cib-pm.xml.initial /var/lib/heartbeat/crm/cib.xml
orad01:/etc/ha.d# chown hacluster:haclient /var/lib/heartbeat/crm/cib.xml
But when I start my cluster with /etc/init.d/heartbeat start the
cluster resources fail.
ipvsadm -L -n --stats ; echo ; crm_mon -1; echo ; ip addr sh
Fri Jul 3
16:22:21 2009
IP Virtual Server version 1.2.1 (size=4096)
Prot LocalAddress:Port Conns InPkts OutPkts InBytes OutBytes
-> RemoteAddress:Port
UDP 192.168.178.100:1812 0 0 0 0 0
-> 192.168.178.101:1812 0 0 0 0 0
-> 192.168.178.102:1812 0 0 0 0 0
============
Last updated: Fri Jul 3 16:22:21 2009
Current DC: orad01 (c565bd14-8b2d-40d5-931b-40fefb1f89f3) - partition
with quorum
Version: 1.0.3-b133b3f19797c00f9189f4b66b513963f9d25db9
1 Nodes configured, unknown expected votes
1 Resources configured.
============
Online: [ orad01 ]
Resource Group: group_LVS
ldirectord_1 (heartbeat:ldirectord): Started orad01 FAILED
LVSSyncDaemonSwap_2 (heartbeat:LVSSyncDaemonSwap): Stopped
IPaddr_192_168_178_100 (ocf::heartbeat:IPaddr): Stopped
Failed actions:
IPaddr_192_168_178_100_monitor_0 (node=orad01, call=4, rc=1,
status=complete):
unknown error
ldirectord_1_monitor_120000 (node=orad01, call=92, rc=7,
status=complete): not running
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue state UNKNOWN
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast
state UP qlen 1000
link/ether 00:0c:29:e4:00:7b brd ff:ff:ff:ff:ff:ff
inet 192.168.160.101/24 brd 192.168.160.255 scope global eth0
inet6 fe80::20c:29ff:fee4:7b/64 scope link
valid_lft forever preferred_lft forever
3: eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast
state UP qlen 1000
link/ether 00:0c:29:e4:00:85 brd ff:ff:ff:ff:ff:ff
inet 192.168.178.101/24 brd 192.168.178.255 scope global eth1
inet6 fe80::20c:29ff:fee4:85/64 scope link
valid_lft forever preferred_lft forever
Whats wrong with this ?
Thanks for your reply in advance.
Thomas.
----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.
<?xml version="1.0" encoding="UTF-8"?>
<cib admin_epoch="0" epoch="0" num_updates="0" dc-uuid="0" have-quorum="false" remote-tls-port="0" validate-with="pacemaker-1.0">
<configuration>
<crm_config>
<cluster_property_set id="cib-bootstrap-options"><nvpair id="nvpair.id262613" name="symmetric-cluster" value="true"/><nvpair id="nvpair.id262621" name="no-quorum-policy" value="stop"/><nvpair id="nvpair.id262629" name="default-resource-stickiness" value="0"/><nvpair id="nvpair.id262638" name="default-resource-failure-stickiness" value="0"/><nvpair id="nvpair.id262647" name="stonith-enabled" value="false"/><nvpair id="nvpair.id262656" name="stonith-action" value="reboot"/><nvpair id="nvpair.id262665" name="startup-fencing" value="true"/><nvpair id="nvpair.id262674" name="stop-orphan-resources" value="true"/><nvpair id="nvpair.id262683" name="stop-orphan-actions" value="true"/><nvpair id="nvpair.id262692" name="remove-after-stop" value="false"/><nvpair id="nvpair.id262701" name="short-resource-names" value="true"/><nvpair id="nvpair.id262710" name="transition-idle-timeout" value="5min"/><nvpair id="nvpair.id262720" name="default-action-timeout" value="20s"/><nvpair id="nvpair.id262729" name="is-managed-default" value="true"/><nvpair id="nvpair.id262738" name="cluster-delay" value="60s"/><nvpair id="nvpair.id262747" name="pe-error-series-max" value="-1"/><nvpair id="nvpair.id262756" name="pe-warn-series-max" value="-1"/><nvpair id="nvpair.id262765" name="pe-input-series-max" value="-1"/></cluster_property_set>
</crm_config>
<nodes/>
<resources>
<group id="group_LVS"><meta_attributes id="group-group_LVS.meta"/>
<primitive id="ldirectord_1" class="heartbeat" type="ldirectord"><meta_attributes id="primitive-ldirectord_1.meta"/>
<operations>
<op name="monitor" interval="120s" id="ldirectord_1_mon" timeout="60s"/>
</operations>
<instance_attributes id="instance_attributes.id262811"><nvpair id="nvpair.id262818" name="1" value="ldirectord.cf"/></instance_attributes>
</primitive>
<primitive id="LVSSyncDaemonSwap_2" class="heartbeat" type="LVSSyncDaemonSwap"><meta_attributes id="primitive-LVSSyncDaemonSwap_2.meta"/>
<operations>
<op name="monitor" interval="120s" id="LVSSyncDaemonSwap_2_mon" timeout="60s"/>
</operations>
<instance_attributes id="instance_attributes.id262855"><nvpair id="nvpair.id262862" name="1" value="master"/></instance_attributes>
</primitive>
<primitive id="IPaddr_192_168_178_100" class="ocf" provider="heartbeat" type="IPaddr"><meta_attributes id="primitive-IPaddr_192_168_178_100.meta"/>
<operations>
<op name="monitor" interval="5s" id="IPaddr_192_168_178_100_mon" timeout="5s"/>
</operations>
<instance_attributes id="instance_attributes.id262899"><nvpair id="nvpair.id262906" name="ip" value="192.168.178.100"/><nvpair id="nvpair.id262914" name="nic" value="eth1"/><nvpair id="nvpair.id262923" name="cidr_netmask" value="32"/></instance_attributes>
</primitive>
</group>
</resources>
<constraints>
<rsc_location id="rsc_location_group_LVS" rsc="group_LVS">
<rule id="prefered_location_group_LVS" score="100">
<expression attribute="#uname" id="expression.id262954" operation="eq" value="orad01"/>
</rule>
</rsc_location>
</constraints>
</configuration>
<status/>
</cib>
_______________________________________________
Linux-HA mailing list
[email protected]
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems
