[Debian-ha-maintainers] Resource cannot run anywhere

Leonhardt,Christian christian.leonhardt at dako.de
Mon Jul 27 17:01:21 BST 2015


Hi everyone,

I just want to inform you that my problem is solved with some help from
the ClusterLabs guys. :-)
The problem was the colocation chaining that prevented the resouce from
moving to the other node.
After moving the colocation of p_apache2, p_bind9, p_lighttpd and
p_squid3 to a higher primitive the failover scenario is working.
These are the new colocations:

colocation co_p_apache2_with_g_net-dev1 inf: p_apache2 g_net-dev1
colocation co_p_bind9_with_g_net-dev1 inf: p_bind9 g_net-dev1
colocation co_p_lighttpd_with_g_net-dev1 inf: p_lighttpd g_net-dev1
colocation co_p_squid3_with_g_net-dev1 inf: p_squid3 g_net-dev1

Thank you for the help and i am looking forward for the new cluster
stack in Jessie.

Greetings
Christian
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 473 bytes
Desc: This is a digitally signed message part
URL: <http://lists.alioth.debian.org/pipermail/debian-ha-maintainers/attachments/20150727/06fda27c/attachment.sig>


More information about the Debian-ha-maintainers mailing list