On Thu, Mar 18, 2010 at 3:45 AM, Serge Dubrouski wrote:
> Both version of pingd expose the same problem for me. After fresh
> start CIB doesn't get updated with pingd attributes for the cluster
> nodes so my location rule:
>
> location connected myGroup \
> rule $id="connected-rule" -inf: n
Both version of pingd expose the same problem for me. After fresh
start CIB doesn't get updated with pingd attributes for the cluster
nodes so my location rule:
location connected myGroup \
rule $id="connected-rule" -inf: not_defined pingd or pingd lte 0
prevents resources from starting.
On Wed, Mar 17, 2010 at 9:10 PM, Serge Dubrouski wrote:
> Hello -
>
> I've just installed fresh new Pacemaker 1.0.8 and ran into a problem
> with pind. When Corosync/Pacemaker/Pingd start it doesn't initialize
> pingd attribute for the nodes so the resources in the cluster stay
> down. Then if I c
Hello -
I've just installed fresh new Pacemaker 1.0.8 and ran into a problem
with pind. When Corosync/Pacemaker/Pingd start it doesn't initialize
pingd attribute for the nodes so the resources in the cluster stay
down. Then if I change configuration (delete/add pingd resource or
clone, stop/start
