[Pacemaker] Clearing a resource which returned "not installed" from START
Bob Schatz
bschatz at yahoo.com
Thu Mar 31 03:06:24 UTC 2011
I am running Pacemaker 1.0.9 and Heartbeat 3.0.3.
I started a resource and the agent start method returned "OCF_ERR_INSTALLED".
I have fixed the problem and I would like to restart the resource and I cannot
get it to restart.
Any ideas?
Thanks,
Bob
The failcounts are 0 as shown below and with the crm_resource command:
# crm_mon -1 -f
============
Last updated: Wed Mar 30 19:55:39 2011
Stack: Heartbeat
Current DC: mgraid-s0000d6661-0 (f4e5e15c-d06b-4e37-89b9-4621af05128f) -
partition with quorum
Version: 1.0.9-89bd754939df5150de7cd76835f98fe90851b677
2 Nodes configured, unknown expected votes
5 Resources configured.
============
Online: [ mgraid-s0000d6661-1 mgraid-s0000d6661-0 ]
Clone Set: Fencing
Started: [ mgraid-s0000d6661-1 mgraid-s0000d6661-0 ]
Clone Set: cloneIcms
Started: [ mgraid-s0000d6661-1 mgraid-s0000d6661-0 ]
Clone Set: cloneOmserver
Started: [ mgraid-s0000d6661-1 mgraid-s0000d6661-0 ]
Master/Slave Set: ms-SSS0000D6661
Masters: [ mgraid-s0000d6661-0 ]
Slaves: [ mgraid-s0000d6661-1 ]
Master/Slave Set: ms-SSJ0000D6662
Masters: [ mgraid-s0000d6661-0 ]
Stopped: [ SSJ0000D6662:0 ]
Migration summary:
* Node mgraid-s0000d6661-0:
* Node mgraid-s0000d6661-1:
Failed actions:
SSJ0000D6662:0_start_0 (node=mgraid-s0000d6661-1, call=27, rc=5,
status=complete): not installed
I have also tried to cleanup the resource with these commands:
# crm_resource --resource SSJ0000D6662:0 --cleanup --node
mgraid-s0000d6661-1
# crm_resource --resource SSJ0000D6662:1 --cleanup --node
mgraid-s0000d6661-1
# crm_resource --resource SSJ0000D6662:0 --cleanup --node
mgraid-s0000d6661-0
# crm_resource --resource SSJ0000D6662:1 --cleanup --node mgraid-s0000d6661-0
# crm_resource --resource ms-SSJ0000D6662 --cleanup --node mgraid-s0000d6661-1
# crm resource start SSJ0000D6662:0
My configuration is:
node $id="856c1f72-7cd1-4906-8183-8be87eef96f2" mgraid-s0000d6661-1
node $id="f4e5e15c-d06b-4e37-89b9-4621af05128f" mgraid-s0000d6661-0
primitive SSJ0000D6662 ocf:omneon:ss \
params ss_resource="SSJ0000D6662"
ssconf="/var/omneon/config/config.J0000D6662" \
op monitor interval="3s" role="Master" timeout="7s" \
op monitor interval="10s" role="Slave" timeout="7" \
op stop interval="0" timeout="20" \
op start interval="0" timeout="300"
primitive SSS0000D6661 ocf:omneon:ss \
params ss_resource="SSS0000D6661"
ssconf="/var/omneon/config/config.S0000D6661" \
op monitor interval="3s" role="Master" timeout="7s" \
op monitor interval="10s" role="Slave" timeout="7" \
op stop interval="0" timeout="20" \
op start interval="0" timeout="300"
primitive icms lsb:S53icms \
op monitor interval="5s" timeout="7" \
op start interval="0" timeout="5"
primitive mgraid-stonith stonith:external/mgpstonith \
params hostlist="mgraid-canister" \
op monitor interval="0" timeout="20s"
primitive omserver lsb:S49omserver \
op monitor interval="5s" timeout="7" \
op start interval="0" timeout="5"
ms ms-SSJ0000D6662 SSJ0000D6662 \
meta clone-max="2" notify="true" globally-unique="false"
target-role="Started"
ms ms-SSS0000D6661 SSS0000D6661 \
meta clone-max="2" notify="true" globally-unique="false"
target-role="Started"
clone Fencing mgraid-stonith
clone cloneIcms icms
clone cloneOmserver omserver
location ms-SSJ0000D6662-master-w1 ms-SSJ0000D6662 \
rule $id="ms-SSJ0000D6662-master-w1-rule" $role="master" 100: #uname eq
mgraid-s0000d6661-1
location ms-SSS0000D6661-master-w1 ms-SSS0000D6661 \
rule $id="ms-SSS0000D6661-master-w1-rule" $role="master" 100: #uname eq
mgraid-s0000d6661-0
order orderms-SSJ0000D6662 0: cloneIcms ms-SSJ0000D6662
order orderms-SSS0000D6661 0: cloneIcms ms-SSS0000D6661
property $id="cib-bootstrap-options" \
dc-version="1.0.9-89bd754939df5150de7cd76835f98fe90851b677" \
cluster-infrastructure="Heartbeat" \
dc-deadtime="5s" \
stonith-enabled="true" \
last-lrm-refresh="1301536426"
More information about the Pacemaker
mailing list