[Pacemaker] cloned pingd resource problem

[fatcharly at gmx.de]

Hi,

I`, running a two node cluster on a fully updated CentOS 7 (pacemaker-1.1.13-10.el7_2.2.x86_64 pcs-0.9.143-15.el7.x86_64) . I see on one of our nodes a lot of this in the logfiles:

Mar 30 12:32:13 localhost crmd[12986]:  notice: State transition S_IDLE -> S_POLICY_ENGINE [ input=I_PE_CALC cause=C_TIMER_POPPED origin=crm_timer_popped ]
Mar 30 12:32:13 localhost pengine[12985]:  notice: On loss of CCM Quorum: Ignore
Mar 30 12:32:13 localhost pengine[12985]: warning: Processing failed op monitor for ping_fw:0 on kathie2: unknown error (1)
Mar 30 12:32:13 localhost pengine[12985]: warning: Processing failed op start for ping_fw:1 on stacy2: unknown error (1)
Mar 30 12:32:13 localhost pengine[12985]: warning: Forcing ping_fw-clone away from stacy2 after 1000000 failures (max=1000000)
Mar 30 12:32:13 localhost pengine[12985]: warning: Forcing ping_fw-clone away from stacy2 after 1000000 failures (max=1000000)
Mar 30 12:32:13 localhost pengine[12985]:  notice: Calculated Transition 1823: /var/lib/pacemaker/pengine/pe-input-355.bz2
Mar 30 12:32:13 localhost crmd[12986]:  notice: Transition 1823 (Complete=0, Pending=0, Fired=0, Skipped=0, Incomplete=0, Source=/var/lib/pacemaker/pengine/pe-input-355.bz2): Complete
Mar 30 12:32:13 localhost crmd[12986]:  notice: State transition S_TRANSITION_ENGINE -> S_IDLE [ input=I_TE_SUCCESS cause=C_FSA_INTERNAL origin=notify_crmd ]


What can I do to resolve the problem ? 

Any suggestions are welcome

Kind regards

fatcharly