[prev in list] [next in list] [prev in thread] [next in thread] 

List:       redhat-linux-cluster
Subject:    [Linux-cluster] new Resources on heartbeat can't start
From:       Felipe Gutierrez <felipe.o.gutierrez () gmail ! com>
Date:       2012-11-20 13:54:46
Message-ID: CAPOsGyYQhMupJca80_Ptzp8=v9u-ym4E4QROK8NK9z9XGD1g7Q () mail ! gmail ! com
[Download RAW message or body]

[Attachment #2 (multipart/alternative)]


Hi everyone,

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@gmail.com
-- https://sites.google.com/site/lipe82/Home/diaadia*

[Attachment #5 (text/html)]

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



-- 
Linux-cluster mailing list
Linux-cluster@redhat.com
https://www.redhat.com/mailman/listinfo/linux-cluster

[prev in list] [next in list] [prev in thread] [next in thread] 

Configure | About | News | Add a list | Sponsored by KoreLogic