On 02/22/2016 05:23 PM, Jeremy Matthews wrote:
> Thanks for the quick response again, and pardon for the delay in responding.
> A colleague of mine and I have been trying some different things today.
>
> But from the reboot on Friday, further below are the logs from corosync.log
> from the time
cluded my original email and Ken Gaillot's
response embedded in it below.
Message: 3
Date: Thu, 18 Feb 2016 13:37:31 -0600
From: Ken Gaillot <kgail...@redhat.com>
To: users@clusterlabs.org
Subject: Re: [ClusterLabs] ClusterIP location constraint reappears
after reboot
Message-ID:
On 02/18/2016 01:07 PM, Jeremy Matthews wrote:
> Hi,
>
> We're having an issue with our cluster where after a reboot of our system a
> location constraint reappears for the ClusterIP. This causes a problem,
> because we have a daemon that checks the cluster state and waits until the
>
Hi,
We're having an issue with our cluster where after a reboot of our system a
location constraint reappears for the ClusterIP. This causes a problem, because
we have a daemon that checks the cluster state and waits until the ClusterIP is
started before it kicks off our application. We didn't
