IBM Support

Clearing a failed resource with crm_mon

Question & Answer


Question

How do I clean a failed resource from crm_mon ?

Answer

You can use the crm_resource command to clear a failed resource. The syntax is as follows:

    #crm_resource -r <the-failed-resource> -C -H <hostname>

For example:

#crm_mon
 
Subject: RE: Check RPC SNMP command
 
Refresh in 13s...
 
============
Last updated: Wed Apr 21 14:13:50 2010
Current DC: pronetz06 (70726b79-0792-451d-99a5-befb0d7b1fa6)
2 Nodes configured.
3 Resources configured.
============
 
 Node: pronetz06 (70726b79-0792-451d-99a5-befb0d7b1fa6): online
Node: pronetz05 (2f3e058c-f170-4662-a576-a5b00d381506): online
 
Resource Group: nps
    drbd_exphome_device (heartbeat:drbddisk):   Started pronetz05
    drbd_nz_device      (heartbeat:drbddisk):   Started pronetz05
    exphome_filesystem  (heartbeat::ocf:Filesystem):    Started pronetz05
    nz_filesystem       (heartbeat::ocf:Filesystem):    Started pronetz05
    fabric_ip   (heartbeat::ocf:IPaddr):        Started pronetz05
    wall_ip     (heartbeat::ocf:IPaddr):        Started pronetz05
    nz_dnsmasq  (lsb:nz_dnsmasq):       Started pronetz05
    nzinit      (lsb:nzinit):   Started pronetz05
    vip3-gig    (heartbeat::ocf:IPaddr):        Started pronetz05
    vip3-mgmt   (heartbeat::ocf:IPaddr):        Started pronetz05
    nps_mgmt    (heartbeat::ocf:IPaddr):        Started pronetz05
fencing_route_to_ha2    (stonith:apcmastersnmp):        Started pronetz05
 
Failed actions:
    fencing_route_to_ha1_start_0 (node=pronetz06, call=17, rc=1): Error

To clear the failed action (fencing_route_to_ha1_start_0 in the above example), run the following command once the problem has been resolved:
    #crm_resource -r fencing_route_to_ha1 -C -H pronetz06

Next, run crm_mon once more to confirm the error has been cleared.

#crm_mon
 
Refresh in 14s...
 
============
Last updated: Wed Apr 21 14:22:31 2010
Current DC: pronetz06 (70726b79-0792-451d-99a5-befb0d7b1fa6)
2 Nodes configured.
3 Resources configured.
============
 
Node: pronetz06 (70726b79-0792-451d-99a5-befb0d7b1fa6): online
Node: pronetz05 (2f3e058c-f170-4662-a576-a5b00d381506): online
 
Resource Group: nps
    drbd_exphome_device (heartbeat:drbddisk):   Started pronetz05
    drbd_nz_device      (heartbeat:drbddisk):   Started pronetz05
    exphome_filesystem  (heartbeat::ocf:Filesystem):    Started pronetz05
    nz_filesystem       (heartbeat::ocf:Filesystem):    Started pronetz05
    fabric_ip   (heartbeat::ocf:IPaddr):        Started pronetz05
    wall_ip     (heartbeat::ocf:IPaddr):        Started pronetz05
    nz_dnsmasq  (lsb:nz_dnsmasq):       Started pronetz05
    nzinit      (lsb:nzinit):   Started pronetz05
    vip3-gig    (heartbeat::ocf:IPaddr):        Started pronetz05
    vip3-mgmt   (heartbeat::ocf:IPaddr):        Started pronetz05
    nps_mgmt    (heartbeat::ocf:IPaddr):        Started pronetz05
fencing_route_to_ha1    (stonith:apcmastersnmp):        Started pronetz06
fencing_route_to_ha2    (stonith:apcmastersnmp):        Started pronetz05

[{"Product":{"code":"SSULQD","label":"IBM PureData System"},"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Component":null,"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"1.0.0","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}}]

Historical Number

NZ513373

Document Information

Modified date:
17 October 2019

UID

swg21578276