On Mon, Aug 20, 2007 at 03:24:44PM +0200, Dejan Muhamedagic wrote: > On Mon, Aug 20, 2007 at 03:00:27PM +0200, 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? > > There should be a failover attempted in that case. > > > 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? > > In case a resource gets into the UNMANAGED state, that means that > the cluster is short on ideas on what to do with the resource. > One of the following happened: a) the resource failed on all > eligible nodes or b) the resource was active on more than one > node.
Hmm, a resource recovery should be tried in case b): stop the resource on all nodes and then try to start it on one. > The cluster is hoping that a human is going to intervene > and put the cluster back into a manageable state. > > You should look through the logs and find out what is happening. > If you can't, post the logs and you configuration. > > > 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 _______________________________________________ Linux-HA mailing list [email protected] http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
