Hi Andrew,

Thanks for the reply. I did that experiment again, with Apache and Dummy
Resource.

Below is my configuration:

========================================================
[root@prod-hb-nmn-002 ~]# crm configure show
node $id="208b3c7f-f713-4c06-86c9-24aa948f0859" prod-hb-nmn-001
node $id="45cbbd64-e048-4e8d-aff4-0f8cbc708b13" prod-hb-nmn-002
primitive ApacheServer ocf:heartbeat:apache \
        params configfile="/etc/httpd/conf/httpd.conf" \
        op monitor interval="60s" timeout="120s" on-fail="restart" \
        op start interval="0" timeout="40s" \
        op stop interval="0" timeout="60s" \
        meta target-role="Started" \
        meta is-managed="true" \
        meta resource-stickiness="100" \
        meta migration-threshold="2" \
        meta multiple-active="stop_start" \
        meta failure-timeout="300" \
        meta allow-migrate="true"
primitive Dummy ocf:heartbeat:Dummy \
        op monitor interval="60s" timeout="120s" on-fail="restart" \
        op start interval="0" timeout="40s" \
        op stop interval="0" timeout="60s" \
        meta target-role="Started" \
        meta is-managed="true" \
        meta resource-stickiness="100" \
        meta migration-threshold="2" \
        meta multiple-active="stop_start" \
        meta failure-timeout="300" \
        meta allow-migrate="true"
group DUMMY-AND-APACHE Dummy ApacheServer
colocation DUMMY-WITH-APACHE inf: Dummy ApacheServer
order APACHE-BEFORE-DUMMY inf: ApacheServer Dummy
property $id="cib-bootstrap-options" \
        dc-version="1.0.9-89bd754939df5150de7cd76835f98fe90851b677" \
        cluster-infrastructure="Heartbeat" \
        no-quorum-policy="ignore" \
        stonith-enabled="false" \
        expected-quorum-votes="2" \
        default-resource-stickiness="100"
========================================================

Then stopped the Apache Server manually using /etc/init.d/httpd stop
and this time monitor did noticed a stopped resource:

========================================================
[root@prod-hb-nmn-002 ~]# crm_mon -1r
============
Last updated: Fri Jun 21 08:11:12 2013
Stack: Heartbeat
Current DC: prod-hb-nmn-002 (45cbbd64-e048-4e8d-aff4-0f8cbc708b13) -
partition with quorum
Version: 1.0.9-89bd754939df5150de7cd76835f98fe90851b677
2 Nodes configured, 2 expected votes
1 Resources configured.
============

Online: [ prod-hb-nmn-001 prod-hb-nmn-002 ]

Full list of resources:

 Resource Group: DUMMY-AND-APACHE
     Dummy      (ocf::heartbeat:Dummy): Started prod-hb-nmn-002
     ApacheServer       (ocf::heartbeat:apache):        Started prod-hb-nmn-002 
FAILED

Failed actions:
    ApacheServer_monitor_60000 (node=prod-hb-nmn-002, call=7, rc=7,
status=complete): not running
========================================================

but the pacemaker failed to do the Transition. I have also attached the full 
pacemaker-error.log
<http://linux-ha.996297.n3.nabble.com/file/n14716/pacemaker-error.log>  log
for pacemaker where it has failed.

Pacemaker Log:
========================================================
Jun 21 07:42:13 prod-hb-nmn-002 pengine: [26325]: notice: RecurringOp: 
Start recurring monitor (60s) for ApacheServer on prod-hb-nmn-002
Jun 21 07:42:13 prod-hb-nmn-002 pengine: [26325]: notice: LogActions:
Restart resource Dummy    (Started prod-hb-nmn-002)
Jun 21 07:42:13 prod-hb-nmn-002 pengine: [26325]: notice: LogActions:
Recover resource ApacheServer     (Started prod-hb-nmn-002)
Jun 21 07:42:13 prod-hb-nmn-002 crmd: [26205]: info: do_state_transition:
State transition S_POLICY_ENGINE -> S_TRANSITION_ENGINE [ input=I_PE_SUCCESS
cause=C_IPC_MESSAGE origin=handle_response ]
Jun 21 07:42:13 prod-hb-nmn-002 pengine: [26325]: info: process_pe_message:
Transition 9: PEngine Input stored in: /var/lib/pengine/pe-input-18.bz2
Jun 21 07:42:13 prod-hb-nmn-002 crmd: [26205]: info: unpack_graph: Unpacked
transition 9: 11 actions in 11 synapses
Jun 21 07:42:13 prod-hb-nmn-002 crmd: [26205]: info: do_te_invoke:
Processing graph 9 (ref=pe_calc-dc-1371800533-71) derived from
/var/lib/pengine/pe-input-18.bz2
Jun 21 07:42:13 prod-hb-nmn-002 crmd: [26205]: info: te_pseudo_action:
Pseudo action 13 fired and confirmed
Jun 21 07:42:13 prod-hb-nmn-002 crmd: [26205]: notice: run_graph:
====================================================
Jun 21 07:42:13 prod-hb-nmn-002 crmd: [26205]: WARN: run_graph: Transition 9
(Complete=1, Pending=0, Fired=0, Skipped=0, Incomplete=10,
Source=/var/lib/pengine/pe-input-18.bz2): Terminated
Jun 21 07:42:13 prod-hb-nmn-002 crmd: [26205]: ERROR: te_graph_trigger:
Transition failed: terminated
Jun 21 07:42:13 prod-hb-nmn-002 crmd: [26205]: WARN: print_graph: Graph 9
(11 actions in 11 synapses): batch-limit=30 jobs, network-delay=60000ms
Jun 21 07:42:13 prod-hb-nmn-002 crmd: [26205]: WARN: print_graph: Synapse 0
is pending (priority: 0)
Jun 21 07:42:13 prod-hb-nmn-002 crmd: [26205]: WARN: print_elem:     [Action
11]: Pending (id: DUMMY-AND-APACHE_start_0, type: pseduo, priority: 0)
Jun 21 07:42:13 prod-hb-nmn-002 crmd: [26205]: WARN: print_elem:      *
[Input 13]: Completed (id: DUMMY-AND-APACHE_stop_0, type: pseduo, priority:
0)
Jun 21 07:42:13 prod-hb-nmn-002 crmd: [26205]: WARN: print_elem:      *
[Input 14]: Pending (id: DUMMY-AND-APACHE_stopped_0, type: pseduo, priority:
0)
Jun 21 07:42:13 prod-hb-nmn-002 crmd: [26205]: WARN: print_graph: Synapse 1
is pending (priority: 0)
Jun 21 07:42:13 prod-hb-nmn-002 crmd: [26205]: WARN: print_elem:     [Action
12]: Pending (id: DUMMY-AND-APACHE_running_0, type: pseduo, priority: 0)
Jun 21 07:42:13 prod-hb-nmn-002 crmd: [26205]: WARN: print_elem:      *
[Input 9]: Pending (id: Dummy_start_0, loc: prod-hb-nmn-002, priority: 0)
Jun 21 07:42:13 prod-hb-nmn-002 crmd: [26205]: WARN: print_elem:      *
[Input 10]: Pending (id: ApacheServer_start_0, loc: prod-hb-nmn-002,
priority: 0)
Jun 21 07:42:13 prod-hb-nmn-002 crmd: [26205]: WARN: print_elem:      *
[Input 11]: Pending (id: DUMMY-AND-APACHE_start_0, type: pseduo, priority:
0)
========================================================

Regards,
Parkirat Singh Bagga



--
View this message in context: 
http://linux-ha.996297.n3.nabble.com/Resource-Collocation-v-s-Resource-Groups-tp14699p14716.html
Sent from the Linux-HA mailing list archive at Nabble.com.
_______________________________________________
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