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

Re: [ClusterLabs] Is "Process pause detected" triggered too easily?

2017-09-27 Thread Jean-Marc Saffroy
On Wed, 27 Sep 2017, Jan Friesse wrote: > I don't think scheduling is the case. If scheduler would be the case > other message (Corosync main process was not scheduled for ...) would > kick in. This looks more like a something is blocked in totemsrp. Ah, interesting! > > Also, it looks like

Re: [ClusterLabs] Transition aborted when disabling resource

2017-09-27 Thread Ken Gaillot
On Wed, 2017-09-27 at 09:26 +, Roberto Muñoz Gomez wrote: > Hi, > > > It is common to get a "Transition aborted" error when try to disable > a resource? Yes, "Transition aborted" is not an error (notice the log is at "info:" level), just an indication that something in the configuration or

Re: [ClusterLabs] Is "Process pause detected" triggered too easily?

2017-09-27 Thread Jan Friesse
Jean, Hello, As the subject line suggests, I am wondering why I see so many of these log lines (many means about 10 times per minute, usually several in the same second): Sep 26 19:56:24 [950] vm0 corosync notice [TOTEM ] Process pause detected for 2555 ms, flushing membership messages. Sep

[ClusterLabs] Transition aborted when disabling resource

2017-09-27 Thread Roberto Muñoz Gomez
Hi, It is common to get a "Transition aborted" error when try to disable a resource? I have some cron task to disable and enable resources, I see it works well most of the time. But sometimes I get errors like: Sep 25 23:50:08 [4501] vttwinformlrz1 crmd: info: