[Linux-HA] ocf:heartbeat:apache resource agent and timeouts

[Lars Ellenberg]

On Sun, Apr 08, 2012 at 03:03:58PM +0200, David Gubler wrote:
> On 05.04.2012 17:14, Dejan Muhamedagic wrote:
> > Hmm, the process running the monitor operation should be removed
> > (killed) by lrmd on timeout. If that doesn't happen, then you
> > just hit a jackpot bug!
> 
> Ok, that's crucial information I've been missing, and thus I 
> misinterpreted my test results. Back to square one...
> 
> TEST 1: *Unpatched* Apache resource agent with this configuration:
> 
> root at node2:/etc/ha.d# crm configure show
> node $id="aa9dea56-ae1e-42a9-a37b-f7c9f5dc5860" node1
> node $id="aec6cf09-e141-415d-8957-a7b94e09df7f" node2
> primitive apache ocf:heartbeat:apache \
>      params statusurl="http://localhost/server-status" \
>      op monitor interval="15s" timeout="5s" \
>      meta is-managed="false"
> clone apacheClone apache
> property $id="cib-bootstrap-options" \
>      dc-version="1.1.5-01e86afaaa6d4a8c4836f68df80ababd6ca3902f" \
>      cluster-infrastructure="Heartbeat" \
>      stonith-enabled="false" \
>      no-quorum-policy="ignore" \
>      last-lrm-refresh="1333886776"
> 
> 
> crm_mon shows
>   Clone Set: apacheClone [apache]
>       apache:0   (ocf::heartbeat:apache):        Started node2 (unmanaged)
>       apache:1   (ocf::heartbeat:apache):        Started node1 (unmanaged)
> Thus all is well.

Nothing is well.
They are "unmanaged" already ...
Which means the cluster will still attempt to monitor for changes,
but will not take action.


-- 
: Lars Ellenberg
: LINBIT | Your Way to High Availability
: DRBD/HA support and consulting http://www.linbit.com