[Pacemaker] Error when managing network with ping/pingd.

[Andreas Kurz]

On 2013-09-17 09:45, Francis SOUYRI wrote:
> Hello,
> 
> Some help about my problem ?
> 
> I have a corosync/pacemaker with 2 nodes and 2 nets by nodes,
> 192.168.1.0/24 for cluster access, 10.1.1.0/24 for drbd in bond, both
> used by corosync.
> I try to used ocf:pacemaker:ping to monitor the 192.168.1.0/24 I have
> the configuration below, but when I remove the cable of the noeud1 the
> named group resource do not migrate to noeud2.

Looks like the extra score 100 from pingd of node2 is not high enough to
overrule the location constraints with score 50 and the
resource-stickiness of 100 ... you can e.g. increase the "multiplier"
value of your pingd resource to 1000 to be sure it overrules these
constraints and the stickiness.

Regards,
Andreas

-- 
Need help with Pacemaker?
http://www.hastexo.com/now


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 287 bytes
Desc: OpenPGP digital signature
URL: <https://lists.clusterlabs.org/pipermail/pacemaker/attachments/20130917/678e6841/attachment-0003.sig>