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
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 of the reboot command to the constraint being added.
I a
of CCM Quorum: Ignore
> Feb 19 15:22:23 [1998] g5se-f3efce pengine: info: unpack_status:
> Node g5se-f3efce is in standby-mode
>
> I'm not sure what all has to be included my original email and Ken Gaillot's
> response embedded in it below.
>
hat all has to be included 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
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
> ClusterIP
