On 09/19/2016 10:04 AM, Jan Pokorný wrote: > On 19/09/16 10:18 +0000, Auer, Jens wrote: >> Ok, after reading the log files again I found >> >> Sep 19 10:03:45 MDA1PFP-S01 crmd[7797]: notice: Initiating action 3: stop >> mda-ip_stop_0 on MDA1PFP-PCS01 (local) >> Sep 19 10:03:45 MDA1PFP-S01 crmd[7797]: notice: >> MDA1PFP-PCS01-mda-ip_monitor_1000:14 [ ocf-exit-reason:Unknown interface >> [bond0] No such device.\n ] >> Sep 19 10:03:45 MDA1PFP-S01 IPaddr2(mda-ip)[8745]: ERROR: Unknown interface >> [bond0] No such device. >> Sep 19 10:03:45 MDA1PFP-S01 IPaddr2(mda-ip)[8745]: WARNING: [findif] failed >> Sep 19 10:03:45 MDA1PFP-S01 lrmd[7794]: notice: mda-ip_stop_0:8745:stderr [ >> ocf-exit-reason:Unknown interface [bond0] No such device. ] >> Sep 19 10:03:45 MDA1PFP-S01 crmd[7797]: notice: Operation mda-ip_stop_0: ok >> (node=MDA1PFP-PCS01, call=16, rc=0, cib-update=49, confirmed=true) >> Sep 19 10:03:46 MDA1PFP-S01 crmd[7797]: notice: Transition 3 (Complete=2, >> Pending=0, Fired=0, Skipped=0, Incomplete=0, >> Source=/var/lib/pacemaker/pengine/pe-input-501.bz2): Complete >> Sep 19 10:03:46 MDA1PFP-S01 crmd[7797]: notice: State transition >> S_TRANSITION_ENGINE -> S_IDLE [ input=I_TE_SUCCESS cause=C_FSA_INTERNAL >> origin=notify_crmd ] >> Sep 19 10:03:46 MDA1PFP-S01 crmd[7797]: notice: State transition S_IDLE -> >> S_POLICY_ENGINE [ input=I_PE_CALC cause=C_FSA_INTERNAL >> origin=abort_transition_graph ] >> Sep 19 10:03:46 MDA1PFP-S01 pengine[7796]: notice: On loss of CCM Quorum: >> Ignore >> Sep 19 10:03:46 MDA1PFP-S01 pengine[7796]: warning: Processing failed op >> monitor for mda-ip on MDA1PFP-PCS01: not configured (6) >> Sep 19 10:03:46 MDA1PFP-S01 pengine[7796]: error: Preventing mda-ip from >> re-starting anywhere: operation monitor failed 'not configured' (6) >> >> I think that explains why the resource is not started on the other >> node, but I am not sure this is a good decision. It seems to be a >> little harsh to prevent the resource from starting anywhere, >> especially considering that the other node will be able to start the >> resource.
The resource agent is supposed to return "not configured" only when the *pacemaker* configuration of the resource is inherently invalid, so there's no chance of it starting anywhere. As Jan suggested, make sure you've applied any resource-agents updates. If that doesn't fix it, it sounds like a bug in the agent, or something really is wrong with your pacemaker resource config. > > The problem to start with is that based on > >> Sep 19 10:03:45 MDA1PFP-S01 IPaddr2(mda-ip)[8745]: ERROR: Unknown interface >> [bond0] No such device. >> Sep 19 10:03:45 MDA1PFP-S01 IPaddr2(mda-ip)[8745]: WARNING: [findif] failed > > you may be using too ancient version resource-agents: > > https://github.com/ClusterLabs/resource-agents/pull/320 > > so until you update, the troubleshooting would be quite moot. _______________________________________________ Users mailing list: Users@clusterlabs.org http://clusterlabs.org/mailman/listinfo/users Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org
