[Pacemaker] re-manage a resource

Lars Marowsky-Bree lmb at suse.com
Fri Jun 21 08:41:58 EDT 2013


On 2013-06-21T12:56:17, andreas graeper <agraeper at googlemail.com> wrote:

> maybe i asked this before, but i could not find message + answer.
> 
> when a resource gets unmanaged and the problems has gone, i want the
> resource get managed by pacemaker again. what is to do ?
> 
> situation: only on node left (other ill)
>  drbd could not get promoted
>  now it is standalone,primary,uptodate but not managed and all other
> resource stopped (cause depend on drbd:master )

"crm resource cleanup" is the command you're looking for, probably. It's
not unmanaged due to the meta-attribute, but due to an error the cluster
couldn't recover from.

Perhaps it'd make sense if crm_mon distinguished these two modes better
and printed "FAULTY" instead.

(It probably also indicates you don't have fencing configured correctly,
which is the normal way how pacemaker would recover from a resource that
failed to stop, which is the most common path leading to this state.)


Regards,
    Lars

-- 
Architect Storage/HA
SUSE LINUX Products GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 21284 (AG Nürnberg)
"Experience is the name everyone gives to their mistakes." -- Oscar Wilde





More information about the Pacemaker mailing list