I'm using version 1.1.15-11.el7_3.2-e174ec8. As far as I know the latest
stable version in Centos 7.3
Gerard
On Wed, Oct 18, 2017 at 4:42 PM, Ken Gaillot <kgail...@redhat.com> wrote:
> On Wed, 2017-10-18 at 14:25 +0200, Gerard Garcia wrote:
> > So I think I found the problem. Th
resource.
If I change the name to forwarderbgp, the problem disappears. So it seems
that the problem is that Pacemaker mixes the bgpforwarder and forwarder
names. Is it a bug?
Gerard
On Tue, Oct 17, 2017 at 6:27 PM, Gerard Garcia <ger...@talaia.io> wrote:
> That makes sense. I've trie
On Tue, Oct 17, 2017 at 3:35 PM, Ken Gaillot <kgail...@redhat.com> wrote:
> On Tue, 2017-10-17 at 11:47 +0200, Gerard Garcia wrote:
> > Thanks Ken. Yes, inspecting the logs seems that the failcount of the
> > correctly running resource reaches the maximum number of allowed
, Ken Gaillot <kgail...@redhat.com> wrote:
> On Mon, 2017-10-16 at 18:30 +0200, Gerard Garcia wrote:
> > Hi,
> >
> > I have a cluster with two ocf:heartbeat:anything resources each one
> > running as a clone in all nodes of the cluster. For some reason when
> &g
Hi,
I have a cluster with two ocf:heartbeat:anything resources each one running
as a clone in all nodes of the cluster. For some reason when one of them
fails to start the other one stops. There is not any constrain configured
or any kind of relation between them.
Is it possible that there is
