Re: [ClusterLabs] monitor failed actions not cleared

2017-10-18 Thread Ken Gaillot
On Mon, 2017-10-02 at 13:29 +, LE COQUIL Pierre-Yves wrote: > Hi, >   > I finally found my mistake: > I have set up the failure-timeout like the lifetime example in the > RedHat Documentation with the value PT1M. > If I set up the failure-timeout with 60, it works like it should. This is a

Re: [ClusterLabs] monitor failed actions not cleared

2017-10-02 Thread LE COQUIL Pierre-Yves
Hi, I finally found my mistake: I have set up the failure-timeout like the lifetime example in the RedHat Documentation with the value PT1M. If I set up the failure-timeout with 60, it works like it should. Just trying a last question ...: Couldn't it be something in the log telling the value

Re: [ClusterLabs] monitor failed actions not cleared

2017-09-27 Thread LE COQUIL Pierre-Yves
De : LE COQUIL Pierre-Yves Envoyé : lundi 25 septembre 2017 16:58 À : 'users@clusterlabs.org' Objet : monitor failed actions not cleared Hi, I'am using Pacemaker 1.1.15-11.el7_3.4 / Corosync 2.4.0-4.el7 under CentOS 7.3.1611 ð Is this configuration too old ? (yum

[ClusterLabs] monitor failed actions not cleared

2017-09-25 Thread LE COQUIL Pierre-Yves
Hi, I'am using Pacemaker 1.1.15-11.el7_3.4 / Corosync 2.4.0-4.el7 under CentOS 7.3.1611 My subject is very close to the post "clearing failed actions" initiated by Attila Megyeri in May 2017. But the issue doesn't fit my case. What I want to do is: - 2 systemd resources running on