On 16 Apr 2013, at 15:57, "fabian.herschel" <[email protected]> wrote:
> Just a tryal ... could you check the failcounts on both nodes? > Maybe we also need more from your messages, as we only see the status > changing to policy engine and not the next state. In you few lines the > cluster is still not in status idle again, so there still could be pending > actings or something like that. Apparently no failcounts at all - running 'crm_mon --failcounts' just lists the two nodes with no errors. # crm_failcount -G -U proxy1 -r proxyfloat3 scope=status name=fail-count-proxyfloat3 value=0 There is more later on in the log, but nothing that looks bad: Apr 16 13:32:35 proxy1 crmd: [2952]: info: do_pe_invoke_callback: Invoking the PE: query=150, ref=pe_calc-dc-1366119155-102, seq=4, quorate=1 Apr 16 13:32:35 proxy1 pengine: [28796]: notice: unpack_config: On loss of CCM Quorum: Ignore Apr 16 13:32:35 proxy1 pengine: [28796]: notice: unpack_rsc_op: Operation ip1arp_last_failure_0 found resource ip1arp active on proxy2 Apr 16 13:32:35 proxy1 pengine: [28796]: notice: unpack_rsc_op: Operation ip2arp_last_failure_0 found resource ip2arp active on proxy2 Apr 16 13:32:35 proxy1 pengine: [28796]: notice: unpack_rsc_op: Operation ip3arp_last_failure_0 found resource ip3arp active on proxy2 Apr 16 13:32:35 proxy1 pengine: [28796]: notice: unpack_rsc_op: Operation ip4arp_last_failure_0 found resource ip4arp active on proxy2 Apr 16 13:32:35 proxy1 pengine: [28796]: notice: unpack_rsc_op: Operation ip5arp_last_failure_0 found resource ip5arp active on proxy2 Apr 16 13:32:35 proxy1 pengine: [28796]: notice: unpack_rsc_op: Operation ip5arp_last_failure_0 found resource ip5arp active on proxy1 Apr 16 13:32:35 proxy1 pengine: [28796]: notice: unpack_rsc_op: Operation ip2arp_last_failure_0 found resource ip2arp active on proxy1 Apr 16 13:32:35 proxy1 pengine: [28796]: notice: unpack_rsc_op: Operation ip1arp_last_failure_0 found resource ip1arp active on proxy1 Apr 16 13:32:35 proxy1 pengine: [28796]: notice: unpack_rsc_op: Operation ip3_last_failure_0 found resource ip3 active on proxy1 Apr 16 13:32:35 proxy1 pengine: [28796]: notice: unpack_rsc_op: Operation ip3arp_last_failure_0 found resource ip3arp active on proxy1 Apr 16 13:32:35 proxy1 pengine: [28796]: notice: unpack_rsc_op: Operation ip4arp_last_failure_0 found resource ip4arp active on proxy1 Apr 16 13:32:35 proxy1 pengine: [28796]: notice: LogActions: Leave email_alert#011(Started proxy1) Apr 16 13:32:35 proxy1 pengine: [28796]: notice: LogActions: Leave ip1#011(Started proxy1) Apr 16 13:32:35 proxy1 pengine: [28796]: notice: LogActions: Leave ip1arp#011(Started proxy1) Apr 16 13:32:35 proxy1 pengine: [28796]: notice: LogActions: Leave ip1email#011(Started proxy1) Apr 16 13:32:35 proxy1 pengine: [28796]: notice: LogActions: Leave ip2#011(Started proxy1) Apr 16 13:32:35 proxy1 pengine: [28796]: notice: LogActions: Leave ip2arp#011(Started proxy1) Apr 16 13:32:35 proxy1 pengine: [28796]: notice: LogActions: Leave ip2email#011(Started proxy1) Apr 16 13:32:35 proxy1 pengine: [28796]: notice: LogActions: Leave ip3#011(Started proxy1) Apr 16 13:32:35 proxy1 pengine: [28796]: notice: LogActions: Leave ip3arp#011(Started proxy1) Apr 16 13:32:35 proxy1 pengine: [28796]: notice: LogActions: Leave ip3email#011(Started proxy1) Apr 16 13:32:35 proxy1 pengine: [28796]: notice: LogActions: Leave ip4#011(Started proxy1) Apr 16 13:32:35 proxy1 pengine: [28796]: notice: LogActions: Leave ip4arp#011(Started proxy1) Apr 16 13:32:35 proxy1 pengine: [28796]: notice: LogActions: Leave ip4email#011(Started proxy1) Apr 16 13:32:35 proxy1 crmd: [2952]: info: do_state_transition: State transition S_POLICY_ENGINE -> S_TRANSITION_ENGINE [ input=I_PE_SUCCESS cause=C_IPC_MESSAGE origin=handle_response ] Apr 16 13:32:35 proxy1 pengine: [28796]: notice: LogActions: Leave ip5#011(Started proxy1) Apr 16 13:32:35 proxy1 crmd: [2952]: info: unpack_graph: Unpacked transition 25: 0 actions in 0 synapses Apr 16 13:32:35 proxy1 pengine: [28796]: notice: LogActions: Leave ip5arp#011(Started proxy1) Apr 16 13:32:35 proxy1 crmd: [2952]: info: do_te_invoke: Processing graph 25 (ref=pe_calc-dc-1366119155-102) derived from /var/lib/pengine/pe-input-127.bz2 Apr 16 13:32:35 proxy1 pengine: [28796]: notice: LogActions: Leave ip5email#011(Started proxy1) Apr 16 13:32:35 proxy1 crmd: [2952]: info: run_graph: ==================================================== Apr 16 13:32:35 proxy1 crmd: [2952]: notice: run_graph: Transition 25 (Complete=0, Pending=0, Fired=0, Skipped=0, Incomplete=0, Source=/var/lib/pengine/pe-input-127.bz2): Complete Apr 16 13:32:35 proxy1 crmd: [2952]: info: te_graph_trigger: Transition 25 is now complete Apr 16 13:32:35 proxy1 crmd: [2952]: info: notify_crmd: Transition 25 status: done - <null> Apr 16 13:32:35 proxy1 crmd: [2952]: info: do_state_transition: State transition S_TRANSITION_ENGINE -> S_IDLE [ input=I_TE_SUCCESS cause=C_FSA_INTERNAL origin=notify_crmd ] Apr 16 13:32:35 proxy1 crmd: [2952]: info: do_state_transition: Starting PEngine Recheck Timer Apr 16 13:32:35 proxy1 pengine: [28796]: notice: process_pe_message: Transition 25: PEngine Input stored in: /var/lib/pengine/pe-input-127.bz2 Apr 16 13:33:17 proxy1 cib: [2948]: info: cib_stats: Processed 5 operations (6000.00us average, 0% utilization) in the last 10min There's a lot there, but nothing that clearly says "I moved proxyfloat3", or more to the point, didn't... Marcus -- Marcus Bointon Synchromedia Limited: Creators of http://www.smartmessages.net/ UK info@hand CRM solutions [email protected] | http://www.synchromedia.co.uk/ _______________________________________________ Linux-HA mailing list [email protected] http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
