Hi all,
is it possible that a ping_clone goes down on a node because there is no
connectivity and never comes up again when the connectivity returns?
The ping and clone resource is declared like this:
primitive ping ocf:pacemaker:ping \
params host_list="192.168.100.1" name="ping" \
op monitor interval="10s" timeout="60s" \
op start interval="0" timeout="60s" \
op stop interval="0" timeout="60s"
clone ping_clone ping meta globally-unique="false"
I had to force a cleanup on this resource to make it up again. Also if
there are some resources connected by a location like this:
location tomcat_on_connected_node tomcat_clone \
rule $id="tomcat_on_connected_node-rule" -inf: not_defined ping or ping
lte 0
to the ping status those went down when the ping dies and obviously
never comes up again when the connection returns.
Are there some parameters to force the cleanup or to manage these kind
of situations?
Thanks a lot!
--
RaSca
Mia Mamma Usa Linux: Niente รจ impossibile da capire, se lo spieghi bene!
[email protected]
http://www.miamammausalinux.org
_______________________________________________
Linux-HA mailing list
[email protected]
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems
