Hi,
You are right, the problems seem to come from some services that are
started at startup.
My installation script disables all startup options for all services we
use, that's why I didn't focus on this possibility.
But after a quick investigation, a colleague had the good idea to make a
No problem! That's what we're here for. I'm glad it's sorted out :)
On Fri, Aug 28, 2020 at 12:27 AM Citron Vert
wrote:
> Hi,
>
> You are right, the problems seem to come from some services that are
> started at startup.
>
> My installation script disables all startup options for all services
Hi Quentin,
in order to get help it will be easier if you provide both corosync and
pacemaker configuration.
Best Regards,
Strahil Nikolov
В четвъртък, 27 август 2020 г., 17:10:01 Гринуич+3, Citron Vert
написа:
Hi,
Sorry for using this email adress, my name is Quentin. Thank
Hi, Quentin. Thanks for the logs!
I see you highlighted the fact that SERVICE1 was in "Stopping" state on
both node 1 and node 2 when node 1 was rejoining the cluster. I also noted
the following later in the logs, as well as some similar messages earlier:
Aug 27 08:47:02 [1330] NODE2pengine:
Hi, Citron.
Based on your description, it sounds like some resources **might** be
moving from node 1 to node 2, failing on node 2, and then moving back to
node 1. If that's what's happening (and even if it's not), then it's
probably smart to set some resource stickiness as a resource default. The
Hello,
I am contacting you because I have a problem with my cluster and I
cannot find (nor understand) any information that can help me.
I have a 2 nodes cluster (pacemaker, corosync, pcs) installed on CentOS
7 with a set of configuration.
Everything seems to works fine, but here is what
