I am trying to setup a new resource on my heartbeat, but for some reason the resour doesn't come on.
Does anyone have some hint, please?
root@cloud9:/etc/heartbeat# crm_mon -1
============
Last updated: Tue Nov 20 10:45:38 2012
Last change: Tue Nov 20 10:41:57 2012 via crm_shadow on cloud9
Stack: Heartbeat
Current DC: cloud9 (55e3a080-6988-4bb4-814c-f63b20137601) - partition with quorum
Version: 1.1.6-9971ebba4494012a93c03b40a2c58ec0eb60f50c
2 Nodes configured, unknown expected votes
2 Resources configured.
============
Online: [ cloud10 cloud9 ]
FAILOVER-IP (ocf::heartbeat:IPaddr): Started cloud9 FAILED
Failed actions:
FAILOVER-IP_start_0 (node=cloud9, call=92, rc=1, status=complete): unknown error
failover-ip_start_0 (node=cloud9, call=4, rc=1, status=complete): unknown error
FAILOVER-IP_start_0 (node=cloud10, call=4, rc=1, status=complete): unknown error
failover-ip_start_0 (node=cloud10, call=48, rc=1, status=complete): unknown error
root@cloud9:/etc/heartbeat#
My ha.cf file is like this:
# enable pacemaker, without stonith
crm yes
# log where ?
logfacility local0
# warning of soon be dead
warntime 10
# declare a host (the other node) dead after:
deadtime 20
# dead time on boot (could take some time until net is up)
initdead 120
# time between heartbeats
keepalive 2
# What UDP port to use for udp or ppp-udp communication?
# udpport 694
# bcast eth0
# mcast eth0 225.0.0.1 694 1 0
# ucast eth0 192.168.188.9
# What interfaces to heartbeat over?
# udp eth0
# the nodes
node cloud9
node cloud10
# heartbeats, over dedicated replication interface!
ucast eth0 192.168.188.9 # ignored by node1 (owner of ip)
ucast eth0 192.168.188.10 # ignored by node2 (owner of ip)
# ping the switch to assure we are online
ping 192.168.178.1
Best Regards,
Felipe
--
--
-- Felipe Oliveira Gutierrez
-- Felipe.o.Gutierrez@xxxxxxxxx
-- https://sites.google.com/site/lipe82/Home/diaadia
-- Linux-cluster mailing list Linux-cluster@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/linux-cluster
