On Monday 20 August 2007, Christian Rishøj wrote:
> Some of my resources occasionally go into the UNMANAGED state.
>
> I suspect it happens when a monitor action times out. What other
> likely causes can there be?
Wrong:

a) the stop operation on a runing resurce fails
b) resource was already started before you started heartbeat (means the 
probe - which is a monitor before start - returned running)

>
> Ideally, I would like Heartbeat to not give up UNMANAGED resources,
> but rather to recover them and include them in the managed resources
> again. How do I go about and achieve this - automatic recovery of
> unmanaged resources?
an error on a stop is considered as really bad ---> the only way to reover 
from this automatically is with a STONITH - means your node is shot down 
(rebooted) to force a realease of the resource.


>
> Running Heartbeat 2.1.2.
>
> Best regards,
> Christian
> _______________________________________________
> Linux-HA mailing list
> [email protected]
> http://lists.linux-ha.org/mailman/listinfo/linux-ha
> See also: http://linux-ha.org/ReportingProblems

_______________________________________________
Linux-HA mailing list
[email protected]
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems

Reply via email to